coderail-grill-contractlisted

# CodeRail Grill Contract Converge on the next bounded, verifiable, reversible slice without making a clear request endure an interview. ## CodeRail boundary - Read `AGENTS.md`, `docs/NORTH_STAR.md`, `docs/TASKS.md`, relevant decisions, and `git status` before asking repository facts. - Look up facts in the repository. Ask the user only for decisions, priorities, risk authority, or information unavailable from evidence. - Treat drafts and deltas as conversation artifacts, not canonical task state. - Do not write `.coderail/tasks.json` or edit task state behind the CLI. - Never stage or commit task changes. - Do not change business code during contract convergence. - Any later implementation finishes through `python .coderail/coderail.py done`. ## Dispatch and frame 1. If a deterministic red reproduction already exists, route to `coderail-diagnose` and stop contract grilling. Do not reopen settled product scope merely because a bug needs diagnosis. 2. Otherwise invoke `$coderail-frame` internally with the request, repository evidence, and current draft if one exists. 3. Consume its `quick` or `guided` result. Do not expose candidate-lens brainstorming or an exhaustive expert checklist to the user. 4. Build or update one live Contract Draft. Do not create a PRD, issue, local ticket, alternate handoff, glossary, or ADR as a second source of truth. ## Type the draft Use exactly one epistemic state for every material item: - `FACT`: cite observable evi