Reference
Use the source-backed public reference pages when you need exact PatchPatrol contracts after the quickstarts.
Reference
This section turns the PatchPatrol public reference surface into a source-backed guide for the shipped workflow.
Use it when the quickstarts are already working and you want exact details for supported configuration, policy controls, CLI behavior, and the current public API scope.
Public boundary: this section stays focused on the supported public SaaS user surface. Internal notes, roadmap material, self-hosted operator runbooks, and private rollout guidance stay outside
/docs/reference.
Configuration
See the supported environment variables, defaults, and bounded meanings for the public workflow.
Advanced configuration
Review intentionally exposed advanced knobs and explicit legacy/compatibility controls.
Artifacts & schema
Understand the shipped artifact files, JSON shape, and schema-enforced enum values.
Policy controls
Start from the recommended artifact-first posture, then understand which controls to change and why.
CLI reference
Review the shipped `ai-review run` and `ai-review test` contract, including the supported flags.
API scope
Understand what PatchPatrol publicly documents today and where the API boundary stops.
Start from the canonical guides
Return to the onboarding pages first if you are still validating the baseline path:
If the question is "why did this run fail?" rather than "what does this variable mean?", leave the reference pages and use Troubleshooting first.
What belongs here
These reference pages are derived from shipped PatchPatrol contracts such as the runtime configuration, CLI help, and public support posture already present in the repository.
They are designed to help public users move from the recommended GitLab artifact-first setup into exact product detail without crossing into maintainer-only guidance.
Next step: Configuration