@entelligentsia/forgecli 1.0.2 → 1.0.3

package/dist/forge-payload/.base-pack/workflows/fix_bug.md

@@ -23,7 +23,7 @@ Phases`):
 
 | Phase | Role | Persona | Workflow | Path A | Path B |
 |---|---|---|---|---|---|
-| triage | `triage` | bug-fixer | (inline algorithm) | yes | yes |
+| triage | `triage` | bug-fixer | `triage.md` | yes | yes |
 | plan-fix | `plan` | engineer | `plan_task.md` (bug-mode) | no | yes |
 | review-plan | `review-plan` | supervisor | `review_plan.md` | no | yes |
 | implement | `implement` | engineer | `implement_plan.md` (bug-mode) | yes | yes |
@@ -93,24 +93,11 @@ The `route` field is required. Allowed values: `"A"` or `"B"`.
 > Triage subagents MUST NOT touch `bug.path` — that field is set at bug
 > creation and never modified by triage.
 
-### Path A — short-circuit (eligibility)
+### Path A / Path B eligibility
 
-Path A is **eligible only when ALL** of the following hold. Triage subagent
-must enumerate each in its findings:
-
-- `bug.severity ∈ {minor}`
-- Fix is contained in a single file
-- Estimated diff ≤ ~20 lines (judgement call; one screen)
-- No schema, API, migration, security, or build-system change
-- A regression test is obvious from the reproduction script (single short
-  test case, no new fixtures, no test-harness change)
-
-If any criterion fails, the triage subagent MUST select Path B.
-
-### Path B — full loop (default)
-
-Path B runs the same plan/review/implement/review/approve/commit shape as
-`meta-orchestrate.md`. It is the default. Any uncertainty defaults Path B.
+See `triage.md § Path A / Path B Eligibility` for the criteria the triage
+subagent applies. The criteria are single-sourced in the triage workflow;
+this orchestrator only reads the resulting `summaries.triage.route` value.
 
 ### Pipeline selection by path
 
@@ -156,16 +143,11 @@ Differences are confined to the **triage** step and the **path branch**.
      b. If .forge/store/bugs/{BUG_ID}.json does NOT exist, write a fresh record
         via store-cli with status="reported".
      c. Read the now-guaranteed record.
-   - Spawn the triage subagent (persona: bug-fixer). It MUST:
-     • Reproduce the bug (failing test or reproduction script).
-     • Confirm the root cause via codebase research.
-     • Decide Path A vs Path B by the criteria above.
-     • Write triage artifact:
-       forge_artifact({ command:"write", entity:"bug", entityId:"{bugId}", artifact:"triage", content:"<markdown>" })
-     • Write triage-summary artifact (JSON shape documented in § Triage Judgement):
-       forge_artifact({ command:"write", entity:"bug", entityId:"{bugId}", artifact:"triage-summary", content:"<JSON>" })
-     • Call set-bug-summary {bugId} triage via forge_store:
-       forge_store({ command:"set-bug-summary", bugId:"{bugId}", phase:"triage", file:"TRIAGE-SUMMARY.json" })
+   - Spawn the triage subagent (workflow: `triage.md`, persona: bug-fixer).
+     It MUST write `TRIAGE.md` + `TRIAGE-SUMMARY.json` with a `route` field
+     (`"A"` or `"B"`) and call `set-bug-summary {bugId} triage` per
+     `triage.md`. The triage workflow is `audience: subagent`, `phase: triage`;
+     the orchestrator MUST NOT pass any other workflow body to this subagent.
    - On return, orchestrator transitions status:
        store-cli update-status bug {bugId} status triaged
        store-cli update-status bug {bugId} status in-progress

package/dist/forge-payload/.base-pack/workflows/triage.md

@@ -0,0 +1,190 @@
+---
+requirements:
+  reasoning: High
+  context: Medium
+  speed: Medium
+audience: subagent
+phase: triage
+context:
+  architecture: false
+  prior_summaries: delta
+  persona: summary
+  master_index: false
+  diff_mode: false
+deps:
+  personas: [bug-fixer]
+  skills: [bug-fixer, generic]
+  templates: []
+  sub_workflows: []
+  kb_docs: [architecture/stack.md]
+  config_fields: [commands.test, paths.engineering]
+---
+
+
+# Bug Triage
+## Iron Laws
+
+- Reproduce the bug before deciding anything. A bug without a confirmed
+  reproduction has no business going to plan-fix or implement.
+- Read `.forge/personas/bug-fixer.md` first; print the persona identity
+  line (emoji, name, tagline) to stdout before any other tool use.
+- All store I/O via `forge_store` (or `node "$FORGE_ROOT/tools/store-cli.cjs"`).
+  Never edit `.forge/store/*.json` directly.
+- **Triage NEVER writes `bug.status`.** The orchestrator (`meta-fix-bug.md`)
+  owns the `reported → triaged` and `triaged → in-progress` transitions.
+  Writing `bug.status` from this workflow violates `meta-fix-bug.md
+  § Iron Laws #2` (parallel to `meta-review-plan.md`'s "Supervisor NEVER
+  writes entity status" rule).
+- Triage is a **single phase**. Do NOT call `forge_preflight` with any
+  other `--phase` value. Do NOT call `forge_store update-status`,
+  `set-bug-summary` for any non-triage phase, or `forge_store emit`.
+  These are orchestrator-owned or other-phase-owned actions. The
+  phase-ownership guard in forge-cli will reject violations at the tool
+  layer, but the Iron Law names the rule.
+
+## Store-Write Verification
+
+<!-- See _fragments/store-write-verification.md for the canonical block content -->
+
+## Algorithm
+
+```
+
+0. Pre-flight Gate Check:
+   - Resolve FORGE_ROOT (`node -e "console.log(require('./.forge/config.json').paths.forgeRoot)"`).
+   - Run: `node "$FORGE_ROOT/tools/preflight-gate.cjs" --phase triage --bug {bugId}`
+   - Exit 1 (gate failed) → print stderr and HALT. Do not proceed.
+   - Exit 2 (misconfiguration) → print stderr and HALT.
+   - Exit 0 → continue.
+
+1. Load Context:
+   - Read `.forge/personas/bug-fixer.md` first; print the persona identity
+     line to stdout before any other tool use.
+   - Read the bug record:
+     `forge_store({ command:"read", entity:"bug", id:"{bugId}" })`
+   - Read business domain docs relevant to the reported symptom.
+   - store-cli verbs: `read` | `list` | `write` | `emit` |
+     `update-status` | `set-summary` | `set-bug-summary` | `describe` |
+     `nlp` | `query` | `delete` — there is no `get`/`set`/`find`. See
+     `_fragments/store-cli-verbs.md` for full notes.
+
+2. Reproduce:
+   - Construct a minimal reproduction: a failing test, a short script,
+     or a documented manual sequence that triggers the reported symptom.
+   - If reproduction cannot be achieved with the information in the bug
+     record, write what was tried in TRIAGE.md, set the route to "B"
+     (any uncertainty defaults to Path B), and continue to root-cause
+     research with the reporter's narrative as the working hypothesis.
+
+3. Root-Cause Research:
+   - Read the code paths implicated by the reproduction.
+   - Confirm (or revise) the reporter's stated root cause via direct
+     inspection of source files and tests.
+   - Note collateral damage: which other call sites, schemas, or
+     workflows share the defective shape.
+
+4. Path A / Path B Eligibility:
+   - Apply the criteria in § "Path A / Path B Eligibility" below.
+   - Record the route decision and the explicit enumeration of each
+     criterion in the findings section of the triage summary.
+
+5. Write Triage Artifacts:
+   - Write the triage artifact (markdown narrative):
+     `forge_artifact({ command:"write", entity:"bug", entityId:"{bugId}",
+                       artifact:"triage", content:"<markdown>" })`
+   - Write the triage-summary sidecar (JSON shape below):
+     `forge_artifact({ command:"write", entity:"bug", entityId:"{bugId}",
+                       artifact:"triage-summary", content:"<JSON>" })`
+
+6. Finalize:
+   - **No status write.** The orchestrator (`meta-fix-bug.md`) writes the
+     `reported → triaged` and `triaged → in-progress` transitions on
+     return. Writing `bug.status` from this workflow is forbidden by
+     Iron Laws above and is rejected by the phase-ownership guard.
+   - **Do NOT emit a phase event yourself.** The orchestrator owns event
+     emission — it composes the canonical event from runtime telemetry
+     (model, provider, tokens, wall times) plus the SUMMARY you write
+     in the next step.
+
+7. Emit Summary Sidecar:
+   - The JSON written in step 5 MUST have this shape (the `route` field
+     is required; allowed values: `"A"` or `"B"`):
+
+     ```json
+     {
+       "objective":   "Triage FORGE-BUG-NNN — reproduce, locate, decide route.",
+       "key_changes": ["<up to 12 bullets, 200 chars each — findings or actions>"],
+       "findings": [
+         "Root cause: <one line>",
+         "Reproduction: <one line>",
+         "Route decision: A | B",
+         "Rationale: <one line>"
+       ],
+       "verdict":     "n/a",
+       "written_at":  "<current ISO 8601 timestamp>",
+       "artifact_ref":"TRIAGE.md",
+       "route":       "A"
+     }
+     ```
+
+   - Call:
+     ```
+     forge_store({ command:"set-bug-summary", entity:"bug",
+                   id:"{bugId}", phase:"triage",
+                   file:"engineering/bugs/{bugDir}/TRIAGE-SUMMARY.json" })
+     ```
+   - If the set-bug-summary call exits non-zero, fix the sidecar JSON
+     and retry (up to 3 attempts per the Store-Write Verification rule).
+     Do not proceed without a valid summary.
+
+> **Field-naming caution — runtime-tested.** The route field is named
+> `route`, never `path`. The bug schema's top-level `path` field is the
+> bug's **artifact directory** (e.g. `engineering/bugs/EMG-BUG-001-...`).
+> Conflating the two caused EMBERGLOW-BUG-001 (v0.44.0 first run) to land
+> its `TRIAGE.md` under `.forge/store/bugs/` instead of `engineering/bugs/`.
+> Triage MUST NOT touch `bug.path` — that field is set at bug creation
+> and never modified by triage.
+```
+
+## Path A / Path B Eligibility
+
+Path A is **eligible only when ALL** of the following hold. The triage
+summary `findings` array MUST enumerate each criterion explicitly with a
+pass/fail mark, so reviewers can audit the decision:
+
+- `bug.severity ∈ {minor}`
+- Fix is contained in a single file
+- Estimated diff ≤ ~20 lines (judgement call; one screen)
+- No schema, API, migration, security, or build-system change
+- A regression test is obvious from the reproduction script (single short
+  test case, no new fixtures, no test-harness change)
+
+If any criterion fails, the triage subagent MUST select Path B.
+
+**Path B is the default.** Any uncertainty resolves to Path B. It runs the
+same plan/review/implement/review/approve/commit shape as
+`meta-orchestrate.md`. Picking Path A under uncertainty is the documented
+failure mode (over-eager short-circuit).
+
+## Triage Artifact Contents (TRIAGE.md)
+
+The narrative artifact MUST contain:
+
+1. **Reported symptom** — one paragraph summarising the bug report.
+2. **Reproduction** — exact steps, commands, or test case that triggers
+   the symptom; copy of the failing output.
+3. **Root cause** — one or two paragraphs naming the defective code path,
+   schema, or workflow. Cite file paths and line numbers.
+4. **Path A / Path B enumeration** — for each criterion above, mark
+   pass/fail with one-line evidence.
+5. **Route decision and rationale** — the chosen route and the
+   single-sentence justification.
+6. **Collateral findings** — any related shapes, call sites, or
+   workflows that share the defective pattern (filed as follow-ups in
+   the commit phase, not fixed here).
+
+<!-- See _fragments/generation-instructions.md for Generation Instructions template -->
+## Friction Emit
+
+Emit `type:friction` `{workflow:triage, persona:bug-fixer, issue}` per
+`_fragments/friction-emit.md`.

package/dist/forge-payload/.claude-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "forge",
-  "version": "1.0.2",
+  "version": "1.0.3",
   "description": "Self-enhancing AI software development lifecycle — generates project-specific SDLC instances from meta-definitions",
   "license": "MIT",
   "author": {

package/dist/forge-payload/.schemas/enum-catalog.json

@@ -1,6 +1,6 @@
 {
   "version": "1.0.2",
-  "generated": "2026-05-27",
+  "generated": "2026-05-28",
   "note": "Authoritative enum catalog. Source: build-enum-catalog.cjs. Regenerate via node forge/tools/build-manifest.cjs.",
   "enums": {
     "task.status": [

package/dist/forge-payload/.schemas/migrations.json

@@ -1,4 +1,13 @@
 {
+  "1.0.2": {
+    "version": "1.0.3",
+    "date": "2026-05-28",
+    "notes": "v1.0.3 — FORGE-BUG-040 (GH-110) fix. /forge:fix-bug now runs each phase as a phase-scoped subagent: triage uses the new triage.md workflow, plan-fix uses plan_task.md (bug-mode), implement uses implement_plan.md (bug-mode). Previously all three pointed at fix_bug.md (orchestrator-only body), causing the triage subagent to execute the entire lifecycle in one phase. Bug schema, transitions, and store layout are unchanged.",
+    "target": "workflows:triage,workflows:fix_bug",
+    "regenerate": ["workflows:triage", "workflows:fix_bug"],
+    "breaking": false,
+    "manual": []
+  },
   "1.0.1": {
     "version": "1.0.2",
     "date": "2026-05-27",

package/dist/forge-payload/integrity.json

@@ -1,6 +1,6 @@
 {
-  "version": "1.0.2",
-  "generated": "2026-05-27",
+  "version": "1.0.3",
+  "generated": "2026-05-28",
   "note": "Tamper-evident only. Authoritative source: /forge:update from remote.",
   "files": {
     "commands/add-pipeline.md": "529a2fc01be49815efa2cf1147528827ff1bfc12ce2ac8663b5a3a9781f8682e",
@@ -29,7 +29,7 @@
     "schemas/transitions/bug.json": "27b17da42d1cebffbd4f61ab3dcd432a0017aa71997d548ed80d22c2fc3fad6a",
     "schemas/transitions/sprint.json": "2e0a629396e687b0ca88e1814ac3e35d84533a5d55b25237ab67feddce3c9deb",
     "schemas/transitions/task.json": "4c71849747baa0d585756e57c56325ff6219c078178374e60815dff91e25e3e7",
-    "schemas/enum-catalog.json": "af954fc219984ba9944de123867590c90c09c532b8d3d40859648a75e9010e5c",
+    "schemas/enum-catalog.json": "93dc3d1656d9d638c8eaecc14ce66554b63149a4779869e6536cf0e620e5b37b",
     "tools/verify-integrity.cjs": "3ec3c970dd3d7c3001f8f373bcc40556803eadd2fc2afafb14f1c232cba4cc3f"
   }
 }

package/dist/forge-payload/meta/fragments/tool-discipline.md

@@ -1,9 +1,28 @@
 ## Forge Tool Discipline
 
 All forge_* tools wrap local .cjs scripts via direct exec — deterministic, no LLM,
-no agent loop. Prefer them over shelling out.
+no agent loop. Use them for all Forge-managed data — never bypass with god tools.
 
-- Store CRUD: call `forge_store` (named tool). Canonical write is 2-positional:
+### Data boundaries — off-limits to `read`, `cat`, `bash`, `grep`
+
+These paths contain Forge-managed data. Never access them with generic tools.
+
+| Path | Owned by | Use instead |
+|------|----------|-------------|
+| `.forge/store/**` | Store | `forge_store`, `forge_store_query` |
+| `{paths.engineering}/**/` task/bug/sprint dirs | Artifacts | `forge_artifact read` (covers all 15 artifact types) |
+| `{paths.engineering}/**/INDEX.md` | KB | `forge_store_query` or `forge_collate` |
+| `{paths.engineering}/MASTER_INDEX.md` | KB | `forge_store_query` or `forge_collate` |
+
+`{paths.engineering}` is the project's KB folder name from `.forge/config.json`
+(default: `engineering`). Never hardcode it.
+
+Source files (`.py`, `.ts`, `.js`, etc.), persona `.md`, workflow `.md`, and
+project config outside `.forge/store/` are fine to `read`/`grep` directly.
+
+### Tool routing
+
+- **Store CRUD:** call `forge_store` (named tool). Canonical write is 2-positional:
   `{command:"write", args:["<entity>","<json>"]}`. The id lives INSIDE the json
   (e.g. `{"sprintId":"X-S01","title":"...","status":"planning","taskIds":[],"createdAt":"..."}`).
   DO NOT pass id as a separate arg — `["sprint","X-S01","<json>"]` (3-arg) FAILS.

package/dist/forge-payload/meta/workflows/meta-bug-triage.md

@@ -0,0 +1,210 @@
+---
+requirements:
+  reasoning: High
+  context: Medium
+  speed: Medium
+audience: subagent
+phase: triage
+context:
+  architecture: false
+  prior_summaries: delta
+  persona: summary
+  master_index: false
+  diff_mode: false
+deps:
+  personas: [bug-fixer]
+  skills: [bug-fixer, generic]
+  templates: []
+  sub_workflows: []
+  kb_docs: [architecture/stack.md]
+  config_fields: [commands.test, paths.engineering]
+---
+
+# 🍂 Meta-Workflow: Bug Triage
+
+## Purpose
+
+The Bug Fixer reproduces a reported bug, confirms root cause, decides the
+fix route (Path A short-circuit vs Path B full loop), and writes the
+triage artifact + summary. This is the **first phase** of `/forge:fix-bug`
+and the only phase that records the route decision read by the orchestrator
+(`meta-fix-bug.md`) to select `phases_A` vs `phases_B`.
+
+<!-- See _fragments/iron-laws.md for Iron Laws section structure guidance -->
+## Iron Laws
+
+- Reproduce the bug before deciding anything. A bug without a confirmed
+  reproduction has no business going to plan-fix or implement.
+- Read `.forge/personas/bug-fixer.md` first; print the persona identity
+  line (emoji, name, tagline) to stdout before any other tool use.
+- All store I/O via `forge_store` (or `node "$FORGE_ROOT/tools/store-cli.cjs"`).
+  Never edit `.forge/store/*.json` directly.
+- **Triage NEVER writes `bug.status`.** The orchestrator (`meta-fix-bug.md`)
+  owns the `reported → triaged` and `triaged → in-progress` transitions.
+  Writing `bug.status` from this workflow violates `meta-fix-bug.md
+  § Iron Laws #2` (parallel to `meta-review-plan.md`'s "Supervisor NEVER
+  writes entity status" rule).
+- Triage is a **single phase**. Do NOT call `forge_preflight` with any
+  other `--phase` value. Do NOT call `forge_store update-status`,
+  `set-bug-summary` for any non-triage phase, or `forge_store emit`.
+  These are orchestrator-owned or other-phase-owned actions. The
+  phase-ownership guard in forge-cli will reject violations at the tool
+  layer, but the Iron Law names the rule.
+
+## Store-Write Verification
+
+<!-- See _fragments/store-write-verification.md for the canonical block content -->
+
+## Algorithm
+
+```
+
+0. Pre-flight Gate Check:
+   - Resolve FORGE_ROOT (`node -e "console.log(require('./.forge/config.json').paths.forgeRoot)"`).
+   - Run: `node "$FORGE_ROOT/tools/preflight-gate.cjs" --phase triage --bug {bugId}`
+   - Exit 1 (gate failed) → print stderr and HALT. Do not proceed.
+   - Exit 2 (misconfiguration) → print stderr and HALT.
+   - Exit 0 → continue.
+
+1. Load Context:
+   - Read `.forge/personas/bug-fixer.md` first; print the persona identity
+     line to stdout before any other tool use.
+   - Read the bug record:
+     `forge_store({ command:"read", entity:"bug", id:"{bugId}" })`
+   - Read business domain docs relevant to the reported symptom.
+   - store-cli verbs: `read` | `list` | `write` | `emit` |
+     `update-status` | `set-summary` | `set-bug-summary` | `describe` |
+     `nlp` | `query` | `delete` — there is no `get`/`set`/`find`. See
+     `_fragments/store-cli-verbs.md` for full notes.
+
+2. Reproduce:
+   - Construct a minimal reproduction: a failing test, a short script,
+     or a documented manual sequence that triggers the reported symptom.
+   - If reproduction cannot be achieved with the information in the bug
+     record, write what was tried in TRIAGE.md, set the route to "B"
+     (any uncertainty defaults to Path B), and continue to root-cause
+     research with the reporter's narrative as the working hypothesis.
+
+3. Root-Cause Research:
+   - Read the code paths implicated by the reproduction.
+   - Confirm (or revise) the reporter's stated root cause via direct
+     inspection of source files and tests.
+   - Note collateral damage: which other call sites, schemas, or
+     workflows share the defective shape.
+
+4. Path A / Path B Eligibility:
+   - Apply the criteria in § "Path A / Path B Eligibility" below.
+   - Record the route decision and the explicit enumeration of each
+     criterion in the findings section of the triage summary.
+
+5. Write Triage Artifacts:
+   - Write the triage artifact (markdown narrative):
+     `forge_artifact({ command:"write", entity:"bug", entityId:"{bugId}",
+                       artifact:"triage", content:"<markdown>" })`
+   - Write the triage-summary sidecar (JSON shape below):
+     `forge_artifact({ command:"write", entity:"bug", entityId:"{bugId}",
+                       artifact:"triage-summary", content:"<JSON>" })`
+
+6. Finalize:
+   - **No status write.** The orchestrator (`meta-fix-bug.md`) writes the
+     `reported → triaged` and `triaged → in-progress` transitions on
+     return. Writing `bug.status` from this workflow is forbidden by
+     Iron Laws above and is rejected by the phase-ownership guard.
+   - **Do NOT emit a phase event yourself.** The orchestrator owns event
+     emission — it composes the canonical event from runtime telemetry
+     (model, provider, tokens, wall times) plus the SUMMARY you write
+     in the next step.
+
+7. Emit Summary Sidecar:
+   - The JSON written in step 5 MUST have this shape (the `route` field
+     is required; allowed values: `"A"` or `"B"`):
+
+     ```json
+     {
+       "objective":   "Triage FORGE-BUG-NNN — reproduce, locate, decide route.",
+       "key_changes": ["<up to 12 bullets, 200 chars each — findings or actions>"],
+       "findings": [
+         "Root cause: <one line>",
+         "Reproduction: <one line>",
+         "Route decision: A | B",
+         "Rationale: <one line>"
+       ],
+       "verdict":     "n/a",
+       "written_at":  "<current ISO 8601 timestamp>",
+       "artifact_ref":"TRIAGE.md",
+       "route":       "A"
+     }
+     ```
+
+   - Call:
+     ```
+     forge_store({ command:"set-bug-summary", entity:"bug",
+                   id:"{bugId}", phase:"triage",
+                   file:"engineering/bugs/{bugDir}/TRIAGE-SUMMARY.json" })
+     ```
+   - If the set-bug-summary call exits non-zero, fix the sidecar JSON
+     and retry (up to 3 attempts per the Store-Write Verification rule).
+     Do not proceed without a valid summary.
+
+> **Field-naming caution — runtime-tested.** The route field is named
+> `route`, never `path`. The bug schema's top-level `path` field is the
+> bug's **artifact directory** (e.g. `engineering/bugs/EMG-BUG-001-...`).
+> Conflating the two caused EMBERGLOW-BUG-001 (v0.44.0 first run) to land
+> its `TRIAGE.md` under `.forge/store/bugs/` instead of `engineering/bugs/`.
+> Triage MUST NOT touch `bug.path` — that field is set at bug creation
+> and never modified by triage.
+```
+
+## Path A / Path B Eligibility
+
+Path A is **eligible only when ALL** of the following hold. The triage
+summary `findings` array MUST enumerate each criterion explicitly with a
+pass/fail mark, so reviewers can audit the decision:
+
+- `bug.severity ∈ {minor}`
+- Fix is contained in a single file
+- Estimated diff ≤ ~20 lines (judgement call; one screen)
+- No schema, API, migration, security, or build-system change
+- A regression test is obvious from the reproduction script (single short
+  test case, no new fixtures, no test-harness change)
+
+If any criterion fails, the triage subagent MUST select Path B.
+
+**Path B is the default.** Any uncertainty resolves to Path B. It runs the
+same plan/review/implement/review/approve/commit shape as
+`meta-orchestrate.md`. Picking Path A under uncertainty is the documented
+failure mode (over-eager short-circuit).
+
+## Triage Artifact Contents (TRIAGE.md)
+
+The narrative artifact MUST contain:
+
+1. **Reported symptom** — one paragraph summarising the bug report.
+2. **Reproduction** — exact steps, commands, or test case that triggers
+   the symptom; copy of the failing output.
+3. **Root cause** — one or two paragraphs naming the defective code path,
+   schema, or workflow. Cite file paths and line numbers.
+4. **Path A / Path B enumeration** — for each criterion above, mark
+   pass/fail with one-line evidence.
+5. **Route decision and rationale** — the chosen route and the
+   single-sentence justification.
+6. **Collateral findings** — any related shapes, call sites, or
+   workflows that share the defective pattern (filed as follow-ups in
+   the commit phase, not fixed here).
+
+<!-- See _fragments/generation-instructions.md for Generation Instructions template -->
+## Generation Instructions
+
+- The generated `triage.md` MUST include all four markers required by
+  `forge-cli/src/extensions/forgecli/lib/manifest-checker.ts §
+  checkMaterialization`: (1) `## Store-Write Verification` heading;
+  (2) `## Iron Laws` heading; (3) literal `forge_store` token in body;
+  (4) `.forge/personas/bug-fixer.md` referenced in body.
+- Token Reporting: `_fragments/finalize.md` — wire via `file_ref:`.
+- Event Emission: orchestrator-owned; this workflow MUST NOT call
+  `forge_store emit` for phase events.
+
+## Friction Emit
+
+Emit `type:friction` `{workflow:triage, persona:bug-fixer, issue}` per
+`_fragments/friction-emit.md`.

package/dist/forge-payload/meta/workflows/meta-fix-bug.md

@@ -31,7 +31,7 @@ Phases`):
 
 | Phase | Role | Persona | Workflow | Path A | Path B |
 |---|---|---|---|---|---|
-| triage | `triage` | bug-fixer | (inline algorithm) | yes | yes |
+| triage | `triage` | bug-fixer | `triage.md` | yes | yes |
 | plan-fix | `plan` | engineer | `plan_task.md` (bug-mode) | no | yes |
 | review-plan | `review-plan` | supervisor | `review_plan.md` | no | yes |
 | implement | `implement` | engineer | `implement_plan.md` (bug-mode) | yes | yes |
@@ -101,24 +101,11 @@ The `route` field is required. Allowed values: `"A"` or `"B"`.
 > Triage subagents MUST NOT touch `bug.path` — that field is set at bug
 > creation and never modified by triage.
 
-### Path A — short-circuit (eligibility)
+### Path A / Path B eligibility
 
-Path A is **eligible only when ALL** of the following hold. Triage subagent
-must enumerate each in its findings:
-
-- `bug.severity ∈ {minor}`
-- Fix is contained in a single file
-- Estimated diff ≤ ~20 lines (judgement call; one screen)
-- No schema, API, migration, security, or build-system change
-- A regression test is obvious from the reproduction script (single short
-  test case, no new fixtures, no test-harness change)
-
-If any criterion fails, the triage subagent MUST select Path B.
-
-### Path B — full loop (default)
-
-Path B runs the same plan/review/implement/review/approve/commit shape as
-`meta-orchestrate.md`. It is the default. Any uncertainty defaults Path B.
+See `triage.md § Path A / Path B Eligibility` for the criteria the triage
+subagent applies. The criteria are single-sourced in the triage workflow;
+this orchestrator only reads the resulting `summaries.triage.route` value.
 
 ### Pipeline selection by path
 
@@ -164,16 +151,11 @@ Differences are confined to the **triage** step and the **path branch**.
      b. If .forge/store/bugs/{BUG_ID}.json does NOT exist, write a fresh record
         via store-cli with status="reported".
      c. Read the now-guaranteed record.
-   - Spawn the triage subagent (persona: bug-fixer). It MUST:
-     • Reproduce the bug (failing test or reproduction script).
-     • Confirm the root cause via codebase research.
-     • Decide Path A vs Path B by the criteria above.
-     • Write triage artifact:
-       forge_artifact({ command:"write", entity:"bug", entityId:"{bugId}", artifact:"triage", content:"<markdown>" })
-     • Write triage-summary artifact (JSON shape documented in § Triage Judgement):
-       forge_artifact({ command:"write", entity:"bug", entityId:"{bugId}", artifact:"triage-summary", content:"<JSON>" })
-     • Call set-bug-summary {bugId} triage via forge_store:
-       forge_store({ command:"set-bug-summary", bugId:"{bugId}", phase:"triage", file:"TRIAGE-SUMMARY.json" })
+   - Spawn the triage subagent (workflow: `triage.md`, persona: bug-fixer).
+     It MUST write `TRIAGE.md` + `TRIAGE-SUMMARY.json` with a `route` field
+     (`"A"` or `"B"`) and call `set-bug-summary {bugId} triage` per
+     `triage.md`. The triage workflow is `audience: subagent`, `phase: triage`;
+     the orchestrator MUST NOT pass any other workflow body to this subagent.
    - On return, orchestrator transitions status:
        store-cli update-status bug {bugId} status triaged
        store-cli update-status bug {bugId} status in-progress

package/dist/forge-payload/schemas/enum-catalog.json

@@ -1,6 +1,6 @@
 {
   "version": "1.0.2",
-  "generated": "2026-05-27",
+  "generated": "2026-05-28",
   "note": "Authoritative enum catalog. Source: build-enum-catalog.cjs. Regenerate via node forge/tools/build-manifest.cjs.",
   "enums": {
     "task.status": [

package/dist/forge-payload/schemas/structure-manifest.json

@@ -1,6 +1,6 @@
 {
   "version": "1.0.2",
-  "generatedAt": "2026-05-27T08:59:39.257Z",
+  "generatedAt": "2026-05-28T05:59:32.606Z",
   "generatedByTool": "build-manifest.cjs",
   "namespaces": {
     "personas": {
@@ -48,6 +48,7 @@
         "review_plan.md",
         "run_sprint.md",
         "sprint_retrospective.md",
+        "triage.md",
         "update_implementation.md",
         "update_plan.md",
         "validate_task.md"
@@ -180,6 +181,24 @@
           "paths.engineering"
         ]
       },
+      "triage": {
+        "personas": [
+          ".forge/personas/bug-fixer.md"
+        ],
+        "skills": [
+          ".forge/skills/bug-fixer-skills.md",
+          ".forge/skills/generic-skills.md"
+        ],
+        "templates": [],
+        "sub_workflows": [],
+        "kb_docs": [
+          "{KB_PATH}/architecture/stack.md"
+        ],
+        "config_fields": [
+          "commands.test",
+          "paths.engineering"
+        ]
+      },
       "fix_bug": {
         "personas": [
           ".forge/personas/bug-fixer.md",