GovZero Quality Gate

Prove the current tree satisfies the repository's own completion contract. The
portable invariant is complete, observed verification; the project supplies the
commands, thresholds, and required evidence.

Discovery and fallback

Prefer, in order:

1. A documented aggregate gate the repository already owns. Read its
   implementation or help before assuming which dimensions it covers.
2. The per-dimension commands the repository declares, assembled into the
   smallest complete sequence.
3. The tools actually configured in the tree, discovered from the build or
   project manifest, the task runner, and the continuous-integration
   definition, then invoked one dimension at a time.

The third rung is the floor and it always exists: a repository that configures
a linter or a test runner can be verified through those tools directly, even
with no aggregate to call. Record which dimensions had no owning command rather
than reporting a pass that covered fewer of them.

Workflow

1. Read applicable repository guidance and inspect the current diff. Determine
   which verification policy governs the changed scope.
2. Discover the canonical aggregate quality command. Prefer a documented
   repository script or task that already sequences lint, formatting checks,
   types, tests, builds, documentation, generated surfaces, and policy checks.
   Read its implementation or help before assuming what it covers.
3. If no aggregate exists, construct the smallest complete sequence from the
   repository's documented commands. Record each required dimension and its
   owning command before running anything; completion means no required
   dimension is silently omitted.
4. Run the gate without filters that mask its exit status. Capture the command,
   exit code, relevant counts, warnings, and generated receipts or reports.
5. When the request includes fixing failures, diagnose and correct failures
   caused by the current work, then rerun from the first affected gate. Preserve
   unrelated user changes and do not weaken thresholds or suppress findings to
   manufacture a pass.
6. Run the final canonical aggregate gate on the unchanged candidate tree.
   Completion requires its observed exit status to be successful and every
   required artifact or report to exist.

Evidence

Report the verified tree identity or worktree scope, commands and exit codes,
test and coverage counts when available, warnings, generated evidence paths,
and every skipped or unavailable dimension. A partial or unavailable gate is
not a full pass.