gate

Prompt file imported from Maeximilion/Maex-Voice-Agent (.claude/commands/gate.md). Fill in {{arguments}} before use. Copyright stays with the author.

A gate has been passed: {{arguments}}

Workflow per docs/15_README_STRATEGY.md, section "Gate workflow":

1. Check in docs/00_PCF.md which criteria this gate has, and name evidence for each (eval report, measurement log, roleplay log). If evidence is missing, stop and say which. 1a. Ultrareview reminder per CLAUDE.md "Model Routing": if anything other than .md files changed since the last gate tag (git diff --name-only $(git describe --tags --abbrev=0)..HEAD -- . ':!*.md'; with no tag yet, treat it as changed), tell Maxi in one line that a gate is the point for /code-review ultra on the current branch (billed, started by Maxi only). Go on with step 2 without waiting unless Maxi says to wait. 1b. Security audit (docs/09_OPERATIONS_LEGAL.md section 5), only from G1 on (for G0 skip this step): run bash scripts/audit_due.sh --gate. If it says due, stop and name the kind and the files it prints; the gate waits for that audit. The gate also waits while an audit finding of severity P1 is open in the hardening issue (#252 or its successor). 1c. Gate review: tell Maxi in one line that /gate-review <gate> (saved workflow, read-only, about ten agents) checks the criteria, hard rules, security, evals and docs with a skeptic per lens. Run it only when Maxi asks; go on with step 2 without waiting.
2. docs/01_STATUS.md: gate to "passed" with date, link evidence, update next gate and next steps.
3. Update README.md per mandatory sections in docs/15: the version row of the status table by hand; stage, next gate, "As of", "What works" and "Not yet working" are written by render in step 3a from docs/01_STATUS.md, docs/07_WORKPACKAGES.md and docs/metrics/capabilities.toml (edit a capability's sentence there, never in the README). "Next steps" and the rest by hand. Current state, no promises. 3a. README images: real-model eval runs and voice measurements record themselves on a branch (docs/15_README_STRATEGY.md, "Keeping them current"); run python3 scripts/readme_assets.py pending --record for any made on main, then python scripts/readme_assets.py render --png, and look at every image once rendered (the version on the banner comes from the README table of step 3).
4. Execute quick start from README on a clean checkout. Fix any deviations.
5. CHANGELOG.md: new section for version from commits since last tag.
6. Suggest commit message and tag, execute after confirmation.