verification

# Verification Verification is evidence collection, not a generic command recipe or a verdict generator. ## Discover The Gates Discover the project's actual gates from repository instructions, package/task manifests, CI configuration, existing scripts, and nearby tests. Do not invent commands, coverage thresholds, or required tools. Prefer the same entry points maintainers and CI already use. Classify checks by the accepted task boundary: - targeted behavior tests for the changed surface - nearest relevant suite - build, type, lint, format, schema, or generated-artifact checks - broader repository validation when blast radius warrants it - smoke or manual checks that prove the real user path - Git diff/status checks for unintended files and whitespace errors Run independent read-only checks in parallel only when they do not compete for mutable artifacts. ## Execute And Record For every applicable gate, record: - exact command or reproducible manual procedure - exit status and concise result - scope covered - whether evidence is fresh for the current checkout Report a required gate that cannot run as `unavailable or unknown`, with the missing dependency or access. Do not translate absence of evidence into a pass. Deterministic failures cannot be waived by Agent judgment. If the root cause is unclear, use `diagnose`; if a confirmed code behavior needs a test-led fix, use `tdd`. Re-run affected gates after any mutation. ## Artifact And Diff Checks Inspect produced a...