specgate-routerlisted

# Using SpecGate ## Route one phase For lifecycle work, choose exactly one phase before acting: - `specgate-project-setup` — initialize, bind, install, refresh, or diagnose SpecGate for a repository. - `specgate-work-preparation` — turn a request or source specification into approved SpecGate work. - `specgate-work-delivery` — implement, resume, review, or rework approved SpecGate work. For a read-only work or lifecycle-status question with a work reference, start with the authoritative read: ```bash specgate change status "$WORK_REF" --json ``` For other SpecGate concept or troubleshooting questions, use the smallest relevant CLI read. Do not force a lifecycle phase or mutate records. Before a mode-dependent write or handoff, run `specgate doctor --json`. Read `data.mode`; never infer Local or Full mode from Docker, URLs, or browser availability. Report an unsuccessful doctor result instead of guessing. Completion criterion: exactly one phase skill is selected, or the request is identified as a read-only SpecGate question. ## Operating contract - The `specgate` CLI is the only product-state read and write surface. Never inspect or edit SpecGate SQLite, Postgres, object storage, deployment volumes, or `.specgate/local` directly. Repository source reads remain allowed. - Drafts, explanations, summaries, and repository reads remain ephemeral until an explicit CLI command persists them. - The originating authoring framework owns durable source documents: their