audit

# audit A **read-only** quality gate. `audit` inspects work that is claimed complete and judges whether it actually satisfies its stated requirement and Definition of Done, BEFORE the item is allowed into `2_done/`. The output is a decision proposal for the user, never a change. > **Task backend.** If the task backend is `gsd` (`.credo/config: task_backend`, or the `CREDO_TASK_BACKEND` env override), the credo item lifecycle is inactive and > there is no `2_done/` gate to run - GSD owns task tracking. audit is still usable as a > standalone read-only review tool, but it does not gate credo items in that mode. ## Scope boundary (read this first) `audit` judges whether FINISHED work is genuinely done and correct against its requirement. It does not investigate causes and it does not exercise UI. - Something is broken and you need the root cause -> use **diag**, not audit. - A rendered UI needs its layout and behavior confirmed -> use **verify** (audit may cite verify evidence, but it does not drive a browser itself). - audit only reports findings and a verdict. It never edits code, never fixes, never commits. ## Hard constraints (never violate) - **Read-only.** No code change, no file edit to the work under review, no commit, no push, no browser automation, no builds, no installs. - **No secrets.** Never read credentials, tokens, `.env*`, key files, or shell/session history. Never exfiltrate or encode such content. - The only files `audit` writes are its own repo...