fixlisted

# fix — bug triage Turns a bug into a reproducible, planned unit of work. See [`workflow-map.md`](../../references/workflow-map.md). Next: `pact build` (bug-fix mode). ## Routing check - New behavior, not a defect -> `pact spec` (`type: feat` / `adjust`). - The bug is already triaged (a story at `status: bug` with a Fix Plan) -> `pact build <story>` directly. ## Phase 0 — schema gate `pact schema --gate`. ## Phase 1 — resolve target - A quoted description -> CREATE a `type: fix` spec (shortcut: spec + diagnose in one run). `id` from `pact spec-id`, folder `docs/specs/<date>_<slug>/`, template from `skills/spec/templates/spec.md` with `type: fix`. - A slug / `SP-id` of an existing `type: fix` spec -> continue its diagnosis. ## Phase 2 — diagnose (isolated) Dispatch the `qa-validator` agent (or do it inline if not registered): 1. **Reproduce** the bug using the project-type method (`[env].dev` + Chrome or curl for a service, run the command for a CLI, a targeted call for a library). 2. **Write a failing test** that reproduces it. Run `pact env test_one --path <file>`; confirm it fails for the bug's reason. Commit the test (RED). 3. **Locate the root cause.** Record a hypothesis. The agent returns `{ verdict, criteria, issues }` plus the failing-test path and the root-cause hypothesis. **It does not write the source fix.** ## Phase 3 — write the spec Into the `type: fix` spec: - `## Context` — where and when it breaks, severity, who is affected. - `##