| name | 14-hotfix |
| description | Post-deployment surgical edits for hotfix sessions: bug fixes, patches, small behavioral changes, and dependency updates. Open via 00-context (type hotfix) or resume active_session. Use for production/local bugs — not new features (16-evolve) or greenfield (pipeline).
|
14 — Hotfix
Surgical fix for an existing deployed or local failure: one bug, one repro test, one fix.
Protocol: protocol-card.md
Detail: reference.md (full phases, interview banks, CI, escalation)
Related: bug-investigation · 15-service-health
Corpus first
Open only as needed (docs/CORPUS.md):
| Always | As symptom requires |
|---|
product (feature-list) + system-spec (spec.md) | tech-spec / api / tests / hotfix-log |
Domain deep-dives and guides are opt-in.
When to use / when not
| Use | Do not use |
|---|
| Bug, regression, config/secret patch | New Fn / multi-doc feature → 16-evolve |
| Small behavioral fix with repro | Greenfield → pipeline |
Continue open BUG-* | Ops-only health → 15-service-health |
Prerequisites
- Prefer
active_session type hotfix (via 00-context).
- Bug report path under
docs/bug-reports/ (create in Phase 0).
- Failing repro test before production code change (unless user waives).
Workflow (summary)
Interview (0) → Repro RED (1.25) + user confirms → Investigate (1)
→ Fix until green (2) → Layered verify (2b) → PR/deploy (3–4) → Prevent (5)
- Phase 0 — AskQuestion intent + intake; create
BUG-*.md — reference.md §Phase 0.
- Repro — dedicated failing test under
tests/bugs/; user confirms match before patch.
- Investigate — logs first (Render/Supabase per infra rules); root cause in bug report.
- Fix — minimal code; repro green; run lint/typecheck/relevant tests.
- Verify + deploy — layers in reference §Phase 2b–4; never deploy without approval.
- Prevent — AskQuestion countermeasures / optional Cursor rule; close BUG + hotfix-log.
State
- Stage key:
stages.14-hotfix.
- Batch workflow-state updates per protocol-card.md §State updates.
- Do not edit
workflow-state.yaml directly — workflow-state-manager.
Exit criteria
Output rules
- One bug per report / PR when possible.
- Spec vs code: if corpus wrong, fix docs — do not silently patch around CORPUS.
- Full interview tables, CI notes, escalation: reference.md only.
