quicklisted

# quick Run a small implementation from the current conversation to a verified receipt with the minimum ceremony that still proves the result. What this path keeps from the PRD pipeline: acceptance criteria pinned by content hash, mechanical checks before the judge, an independent judge verdict over the diff and declared runtime evidence, a retry budget, user-only override, and a pin on the exact diff that was judged so a PASS is invalidated when the code changes afterwards. What it drops: the interview, the 12-section PRD, gap-audit/spec gates, the implement state harness, profile reviews, and ship delivery. The cost of that trade: the acceptance criteria are the whole spec and there is no separate fidelity lane. Up to eight machine-judged criteria stay in one routine judge call. Larger contracts split into balanced criterion lanes that run concurrently, so the user still gets the quick path without one oversized judgment. There is no hard cap - the user's invocation of `$quick` is the only switch - but say so in the final report when the contract grew past a handful of criteria. Normal-sized diffs are pushed into the judge prompt. When one lane exceeds the prompt budget, an agentic-capable routine backend receives the exact changed-file allowlist in a scoped read-only workspace; its command trace is audited and recorded. This fallback reads evidence but never executes project code, writes, browses, or explores broadly. ## Preflight - Derive a kebab-case `<slug>` from