@entelligentsia/forgecli 1.0.10 → 1.0.20

package/dist/forge-payload/meta/workflows/meta-review-plan.md

@@ -27,7 +27,7 @@ deps:
 
 - Evaluate the plan against what the task actually requires, not against what the plan claims to deliver. Plans routinely understate complexity, omit edge cases, or skip security steps. Your job is adversarial review, not approval.
 - Read `.forge/personas/supervisor.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.
+- All store I/O via `forge_store` (or `node .forge/tools/store-cli.cjs`). Never edit `.forge/store/*.json` directly.
 
 ## Store-Write Verification
 
@@ -38,9 +38,8 @@ deps:
 ```
 
 0a. Pre-flight Gate Check:
-   - Resolve FORGE_ROOT (`node -e "console.log(require('./.forge/config.json').paths.forgeRoot)"`).
    - **Entity-mode resolution:** read the kickoff arguments. `--task {id}` → `entity_kind = "task"`, `record_id = {id}`. `--bug {id}` → `entity_kind = "bug"`, `record_id = {id}`. All store-cli calls below substitute `{entity_kind}` and `{record_id}` for the literal "task"/{taskId} placeholders.
-   - Run: `node "$FORGE_ROOT/tools/preflight-gate.cjs" --phase review-plan --{entity_kind} {record_id}`
+   - Run: `node .forge/tools/preflight-gate.cjs --phase review-plan --{entity_kind} {record_id}`
    - Exit 1 (gate failed) → print stderr and HALT. Do not proceed; do not attempt to produce the artifact.
    - Exit 2 (misconfiguration) → print stderr and HALT.
    - Exit 0 → continue.
@@ -49,7 +48,7 @@ deps:
    - If `--force` is present in the invocation arguments, skip this step entirely.
    - If `entity_kind == "bug"`, skip this step entirely (bug state is managed by meta-fix-bug.md).
    - Read current task state:
-     `node "$FORGE_ROOT/tools/store-cli.cjs" read task {record_id} --json`
+     `node .forge/tools/store-cli.cjs read task {record_id} --json`
    - Extract the `status` field from the JSON output.
    - Allowed states for this phase: `planned`.
    - If the current status is NOT in the allowed set:
@@ -61,9 +60,10 @@ deps:
    - If present, extract:
      - `Iteration: N of M` — current attempt number and the configured limit
      - `Is final iteration: true/false`
-   - If absent (user-invoked, not orchestrated): treat as iteration 1 of M, where M is
-     read from `.forge/config.json` → `maxReviewIterations` (default 3 if field absent).
-   - Include `(iteration N of M)` in the opening line of the `PLAN_REVIEW.md` artifact.
+   - If absent (user-invoked, not orchestrated): treat as `iteration 1`, no limit — do
+     NOT read any iteration cap from config. The orchestrator owns loop budgets; a human
+     standalone re-run is the escape hatch for stuck items (forge-engineering#34).
+   - Include `(iteration N of M)` (orchestrated) or `(standalone review)` in the opening line of the `PLAN_REVIEW.md` artifact.
    - If this is the final iteration (`N == M`) and the verdict is `Revision Required`,
      append a `### Next Steps` section to the artifact showing:
      ```
@@ -96,7 +96,7 @@ deps:
        - Approved          → `plan-approved`
        - Revision Required → `plan-revision-required`
        - Out-of-band escapes (any state): `code-revision-required`, `blocked`, `escalated`, `abandoned`
-       Update status: `node "$FORGE_ROOT/tools/store-cli.cjs" update-status task {taskId} status plan-approved` (if Approved) or `... status plan-revision-required` (if Revision Required)
+       Update status: `node .forge/tools/store-cli.cjs update-status task {taskId} status plan-approved` (if Approved) or `... status plan-revision-required` (if Revision Required)
      - **Bug mode** — NO status write. The bug remains `in-progress`. The verdict signal travels through `summaries.review_plan.verdict` (read by `read-verdict.cjs § BUG_PHASE_VERDICT_SOURCE`), not `bug.status`. Writing `bug.status` here violates `meta-fix-bug.md § Iron Laws #2`.
    - **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. Subagents that call `store-cli emit` for phase events hallucinate runtime facts (see Plan 11 / Slice 2). Write the SUMMARY and return.
 
@@ -114,13 +114,14 @@ deps:
      ```
    - Call (task mode):
      ```
-     forge_store({ command:"set-summary", entity:"task", id:"{record_id}", phase:"review_plan" })
+     forge_store({ command:"set-summary", args:["{record_id}", "review_plan"] })
      ```
      Or (bug mode):
      ```
-     forge_store({ command:"set-bug-summary", entity:"bug", id:"{record_id}", phase:"review_plan" })
+     forge_store({ command:"set-bug-summary", args:["{record_id}", "review_plan"] })
      ```
-   - If the set-summary call exits non-zero, fix the sidecar JSON and retry. Do not proceed without a valid summary.
+     `args[1]` is the LITERAL phase key `review_plan`, never the record id; `forge_store` has no `entity`/`id`/`phase` field (see `_fragments/store-cli-verbs.md`).
+   - If set-summary exits non-zero (guard: `expected summary key 'review_plan'`), `args[1]` was wrong — fix it to `review_plan` and retry. Do not return without a valid summary; the orchestrator halts as "verdict missing" if `summaries.review_plan` is absent.
 ```
 
 <!-- See _fragments/generation-instructions.md for Generation Instructions template -->

package/dist/forge-payload/meta/workflows/meta-review-sprint-completion.md

@@ -42,10 +42,10 @@ Verify that all tasks in a sprint have been completed, committed, and validated
 4. Finalize:
    - If step-3 verdict is `Approved`:
      - Update sprint status to `completed` via
-       `node "$FORGE_ROOT/tools/store-cli.cjs" update-status sprint {sprintId} status completed`
+       `node .forge/tools/store-cli.cjs update-status sprint {sprintId} status completed`
    - If step-3 verdict is `Revision Required` and orchestrator passed `mode=partial`:
      - Update sprint status to `partially-completed` via
-       `node "$FORGE_ROOT/tools/store-cli.cjs" update-status sprint {sprintId} status partially-completed`
+       `node .forge/tools/store-cli.cjs update-status sprint {sprintId} status partially-completed`
    - If step-3 verdict is `Revision Required` and orchestrator passed `mode=complete`:
      - Do NOT transition status. Leave the sprint at its current status and exit;
        the orchestrator will surface the verdict to the user.
@@ -64,5 +64,5 @@ Verify that all tasks in a sprint have been completed, committed, and validated
      (Claude Code only); on any other runtime treat as unavailable and proceed.
      Do NOT shell out to a `cost-cli.cjs` — there is no such tool.
   2. Parse: `inputTokens`, `outputTokens`, `cacheReadTokens`, `cacheWriteTokens`, `estimatedCostUSD`.
-  3. Write the usage sidecar via `node "$FORGE_ROOT/tools/store-cli.cjs" emit {sprintId} '{sidecar-json}' --sidecar`.
+  3. Write the usage sidecar via `node .forge/tools/store-cli.cjs emit {sprintId} '{sidecar-json}' --sidecar`.
 - **Event Emission:** Ensure the "complete" event includes the `eventId` passed by the orchestrator.

package/dist/forge-payload/meta/workflows/meta-sprint-intake.md

@@ -23,7 +23,7 @@ Capture sprint requirements via a structured interview and document them for pla
 
 - Capture requirements accurately; do not editorialize or pre-select options on the user's behalf. The product manager documents what the user says, not what the agent thinks is best.
 - Read `.forge/personas/product-manager.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.
+- All store I/O via `forge_store` (or `node .forge/tools/store-cli.cjs`). Never edit `.forge/store/*.json` directly.
 
 ## Algorithm
 
@@ -56,7 +56,7 @@ Capture sprint requirements via a structured interview and document them for pla
    - Ensure all deliverables are measurable and testable
 
 5. Finalize:
-   - Update sprint status via `node "$FORGE_ROOT/tools/store-cli.cjs" update-status sprint {sprintId} status planning`
+   - Update sprint status via `node .forge/tools/store-cli.cjs update-status sprint {sprintId} status planning`
    - **Do NOT emit a phase event yourself.** The orchestrator (or kickoff handler) 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. Subagents that call `store-cli emit` for phase events hallucinate runtime facts (see Plan 11 / Slice 2). Write the SUMMARY and return.
 ```
 
@@ -79,6 +79,6 @@ Capture sprint requirements via a structured interview and document them for pla
      - Set token fields to `null`: `"inputTokens": null, "outputTokens": null, "estimatedCostUSD": null`.
      - Add `"source": "missing"` to sidecar JSON.
      - Log: "Token data unavailable (cost probe failed). Backfill later via estimate-usage.cjs."
-  4. Write the usage sidecar via `node "$FORGE_ROOT/tools/store-cli.cjs" emit {sprintId} '{sidecar-json}' --sidecar`.
+  4. Write the usage sidecar via `node .forge/tools/store-cli.cjs emit {sprintId} '{sidecar-json}' --sidecar`.
   5. **NEVER skip sidecar write.** Always emit (reported or placeholder with nulls).
 - **Event Emission:** Ensure the "complete" event includes the `eventId` passed by the orchestrator.

package/dist/forge-payload/meta/workflows/meta-sprint-plan.md

@@ -31,8 +31,8 @@ Break sprint requirements into a set of estimated tasks with a dependency graph.
 1. Load Context:
    - Query the store to orient on current project state before reading docs:
      ```sh
-     node "$FORGE_ROOT/tools/store-cli.cjs" nlp "latest sprint"
-     node "$FORGE_ROOT/tools/store-cli.cjs" nlp "open bugs"
+     node .forge/tools/store-cli.cjs nlp "latest sprint"
+     node .forge/tools/store-cli.cjs nlp "open bugs"
      ```
      Use results (titles, statuses, excerpts, file refs) to skip manual MASTER_INDEX.md navigation where sufficient.
    - Read SPRINT_REQUIREMENTS.md
@@ -52,11 +52,11 @@ Break sprint requirements into a set of estimated tasks with a dependency graph.
 
 4. Documentation:
    - Write SPRINT_PLAN.md to `engineering/sprints/{sprintId}/SPRINT_PLAN.md`
-   - Create each task via `node "$FORGE_ROOT/tools/store-cli.cjs" write task '{task-json}'`.
+   - Create each task via `node .forge/tools/store-cli.cjs write task '{task-json}'`.
      If the command exits non-zero or the PreToolUse hook blocks the write:
      parse the error, correct the JSON, and retry (see Store-Write Verification).
      Do not proceed to the next task until this write succeeds.
-   - Update the sprint record with all new task IDs via `node "$FORGE_ROOT/tools/store-cli.cjs" write sprint '{updated-sprint-json}'` (the sprint JSON must include the complete `taskIds` array with all newly created task IDs).
+   - Update the sprint record with all new task IDs via `node .forge/tools/store-cli.cjs write sprint '{updated-sprint-json}'` (the sprint JSON must include the complete `taskIds` array with all newly created task IDs).
      If the command exits non-zero or the PreToolUse hook blocks the write:
      parse the error, correct the JSON, and retry (see Store-Write Verification).
      Do not proceed until this write succeeds.
@@ -64,7 +64,7 @@ Break sprint requirements into a set of estimated tasks with a dependency graph.
      * Folder: `engineering/sprints/{sprintId}/{taskId}/`
      * File: `TASK_PROMPT.md` — populate from `.forge/templates/TASK_PROMPT_TEMPLATE.md`
        filling in title, objective, acceptance criteria, entities, DSL/CLI changes, and operational impact
-   - Update sprint status via `node "$FORGE_ROOT/tools/store-cli.cjs" update-status sprint {sprintId} status active`.
+   - Update sprint status via `node .forge/tools/store-cli.cjs update-status sprint {sprintId} status active`.
      If the command exits non-zero, parse the error and retry
      (see Store-Write Verification). Do not proceed until this write succeeds.
 
@@ -141,7 +141,7 @@ environment variable is reserved for emergency operator repair only.
      - Set token fields to `null`: `"inputTokens": null, "outputTokens": null, "estimatedCostUSD": null`.
      - Add `"source": "missing"` to sidecar JSON.
      - Log: "Token data unavailable (cost probe failed). Backfill later via estimate-usage.cjs."
-  4. Write the usage sidecar via `node "$FORGE_ROOT/tools/store-cli.cjs" emit {sprintId} '{sidecar-json}' --sidecar`.
+  4. Write the usage sidecar via `node .forge/tools/store-cli.cjs emit {sprintId} '{sidecar-json}' --sidecar`.
   5. **NEVER skip sidecar write.** Always emit (reported or placeholder with nulls).
 - **Event Emission:** Ensure the "complete" event includes the `eventId` passed by the orchestrator.
 - **Store-Write Verification:** The generated workflow MUST include the "Store-Write

package/dist/forge-payload/meta/workflows/meta-update-implementation.md

@@ -31,7 +31,7 @@ Update the implementation of a task based on a "Revision Required" verdict from
 
 - Address every "Revision Required" item from the review artifact at the correct code location; do not paper over them with comments. If a finding is wrong, escalate rather than ignore.
 - Read `.forge/personas/engineer.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.
+- All store I/O via `forge_store` (or `node .forge/tools/store-cli.cjs`). Never edit `.forge/store/*.json` directly.
 
 ## Store-Write Verification
 
@@ -55,7 +55,7 @@ Update the implementation of a task based on a "Revision Required" verdict from
    - Update PROGRESS.md with a summary of the revisions
 
 4. Finalize:
-   - Update task status via `node "$FORGE_ROOT/tools/store-cli.cjs" update-status task {taskId} status implemented`
+   - Update task status via `node .forge/tools/store-cli.cjs update-status task {taskId} status implemented`
    - **Do NOT emit a phase event yourself.** The orchestrator (or kickoff handler) 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. Subagents that call `store-cli emit` for phase events hallucinate runtime facts (see Plan 11 / Slice 2). Write the SUMMARY and return.
 ```
 

package/dist/forge-payload/meta/workflows/meta-update-plan.md

@@ -31,7 +31,7 @@ Update the implementation plan of a task based on a "Revision Required" verdict
 
 - Address every numbered finding in the review artifact. Do not silently drop items; if a finding is wrong, note the reason in the revised plan rather than ignoring it.
 - Read `.forge/personas/architect.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.
+- All store I/O via `forge_store` (or `node .forge/tools/store-cli.cjs`). Never edit `.forge/store/*.json` directly.
 
 ## Store-Write Verification
 
@@ -55,7 +55,7 @@ Update the implementation plan of a task based on a "Revision Required" verdict
    - Update the "Operational Impact" or "Testing Strategy" if the revision changed them
 
 4. Finalize:
-   - Update task status via `node "$FORGE_ROOT/tools/store-cli.cjs" update-status task {taskId} status planned`
+   - Update task status via `node .forge/tools/store-cli.cjs update-status task {taskId} status planned`
    - **Do NOT emit a phase event yourself.** The orchestrator (or kickoff handler) 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. Subagents that call `store-cli emit` for phase events hallucinate runtime facts (see Plan 11 / Slice 2). Write the SUMMARY and return.
 ```
 

package/dist/forge-payload/meta/workflows/meta-validate.md

@@ -31,7 +31,7 @@ The Supervisor performs a final validation of the implementation against the acc
 
 - Validate against the acceptance criteria as written; do not soften, expand, or reinterpret them. The validator's job is to catch what the implementer optimistically considered "done".
 - Read `.forge/personas/qa-engineer.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.
+- All store I/O via `forge_store` (or `node .forge/tools/store-cli.cjs`). Never edit `.forge/store/*.json` directly.
 
 ## Store-Write Verification
 
@@ -42,9 +42,8 @@ The Supervisor performs a final validation of the implementation against the acc
 ```
 
 0a. Pre-flight Gate Check:
-   - Resolve FORGE_ROOT (`node -e "console.log(require('./.forge/config.json').paths.forgeRoot)"`).
    - **Entity-mode resolution:** read the kickoff arguments. `--task {id}` → `entity_kind = "task"`, `record_id = {id}`. `--bug {id}` → `entity_kind = "bug"`, `record_id = {id}`. All store-cli calls below substitute `{entity_kind}` and `{record_id}` for the literal "task"/{taskId} placeholders.
-   - Run: `node "$FORGE_ROOT/tools/preflight-gate.cjs" --phase validate --{entity_kind} {record_id}`
+   - Run: `node .forge/tools/preflight-gate.cjs --phase validate --{entity_kind} {record_id}`
    - Exit 1 (gate failed) → print stderr and HALT. Do not proceed; do not attempt to produce the artifact.
    - Exit 2 (misconfiguration) → print stderr and HALT.
    - Exit 0 → continue.
@@ -53,7 +52,7 @@ The Supervisor performs a final validation of the implementation against the acc
    - If `--force` is present in the invocation arguments, skip this step entirely.
    - If `entity_kind == "bug"`, skip this step entirely (bug state is managed by meta-fix-bug.md).
    - Read current task state:
-     `node "$FORGE_ROOT/tools/store-cli.cjs" read task {record_id} --json`
+     `node .forge/tools/store-cli.cjs read task {record_id} --json`
    - Extract the `status` field from the JSON output.
    - Allowed states for this phase: `implemented`, `review-approved`.
    - If the current status is NOT in the allowed set:
@@ -65,9 +64,10 @@ The Supervisor performs a final validation of the implementation against the acc
    - If present, extract:
      - `Iteration: N of M` — current attempt number and the configured limit
      - `Is final iteration: true/false`
-   - If absent (user-invoked, not orchestrated): treat as iteration 1 of M, where M is
-     read from `.forge/config.json` → `maxReviewIterations` (default 3 if field absent).
-   - Include `(iteration N of M)` in the opening line of the `VALIDATION_REPORT.md` artifact.
+   - If absent (user-invoked, not orchestrated): treat as `iteration 1`, no limit — do
+     NOT read any iteration cap from config. The orchestrator owns loop budgets; a human
+     standalone re-run is the escape hatch for stuck items (forge-engineering#34).
+   - Include `(iteration N of M)` (orchestrated) or `(standalone review)` in the opening line of the `VALIDATION_REPORT.md` artifact.
    - If this is the final iteration (`N == M`) and the verdict is `Revision Required`,
      append a `### Next Steps` section to the artifact showing:
      ```
@@ -99,7 +99,7 @@ The Supervisor performs a final validation of the implementation against the acc
      - See step 1 for iteration header and final-iteration Next Steps requirements.
 
 5. Finalize:
-   - Update task status via `node "$FORGE_ROOT/tools/store-cli.cjs" update-status task {taskId} status review-approved` (if Approved) or `node "$FORGE_ROOT/tools/store-cli.cjs" update-status task {taskId} status code-revision-required` (if Revision Required)
+   - Update task status via `node .forge/tools/store-cli.cjs update-status task {taskId} status review-approved` (if Approved) or `node .forge/tools/store-cli.cjs update-status task {taskId} status code-revision-required` (if Revision Required)
    - **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. Subagents that call `store-cli emit` for phase events hallucinate runtime facts (see Plan 11 / Slice 2). Write the SUMMARY and return.
 
 6. Emit Summary Sidecar:
@@ -117,7 +117,7 @@ The Supervisor performs a final validation of the implementation against the acc
      ```
    - Call (the sidecar path is auto-resolved from the task record's `path` — never pass it):
      ```
-     node "$FORGE_ROOT/tools/store-cli.cjs" set-summary {task_id} validation
+     node .forge/tools/store-cli.cjs set-summary {task_id} validation
      ```
    - If set-summary exits non-zero, fix the sidecar JSON and retry. Do not proceed without a valid summary.
 ```

package/dist/forge-payload/schemas/config.schema.json

@@ -61,7 +61,7 @@
     },
     "paths": {
       "type": "object",
-      "required": ["engineering", "store", "forgeRoot"],
+      "required": ["engineering", "store"],
       "properties": {
         "engineering":     { "type": "string", "default": "engineering" },
         "store":           { "type": "string", "default": ".forge/store" },
@@ -69,8 +69,7 @@
         "commands":        { "type": "string", "default": ".claude/commands" },
         "templates":       { "type": "string", "default": ".forge/templates" },
         "customCommands":  { "type": "string", "default": "engineering/commands", "description": "Directory for project-specific custom pipeline phase commands. Files here are workflow scripts invoked directly by the orchestrator via the phase workflow field." },
-        "forgeRoot":       { "type": "string", "description": "Absolute path to the installed Forge plugin root. Set at init time and refreshed by /forge:update. Used by generated workflows to invoke Forge tools without requiring $CLAUDE_PLUGIN_ROOT in subagent contexts." },
-        "forgeRef":        { "type": "string", "description": "Pinned Forge plugin reference (tag or commit) the project was generated against." }
+        "forgeRef":        { "type": "string", "description": "Pinned Forge plugin reference (tag or commit) the project was generated against. Used to resolve the plugin root via cache lookup." }
       }
     },
     "pipeline": {

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

@@ -1,6 +1,6 @@
 {
-  "version": "1.0.10",
-  "generated": "2026-05-31",
+  "version": "1.2.13",
+  "generated": "2026-06-03",
   "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/event.schema.json

@@ -55,8 +55,10 @@
         "task-approved",
         "task-validated",
         "task-committed",
+        "sprint-start",
         "sprint-complete",
         "sprint-halted",
+        "task-dispatch",
         "bug-fixed",
 
         "bug-triaged", "fix-planned", "fix-review-passed", "fix-review-failed",
@@ -135,6 +137,20 @@
       },
       "then": { "required": ["bugId", "phase", "iteration"] }
     },
+    {
+      "if": { "properties": { "type": { "const": "sprint-start" } }, "required": ["type"] },
+      "then": {
+        "required": [
+          "eventId", "sprintId", "role", "action",
+          "startTimestamp", "endTimestamp", "durationMinutes",
+          "model", "provider",
+          "taskCount"
+        ],
+        "properties": {
+          "taskCount": { "type": "integer", "minimum": 0 }
+        }
+      }
+    },
     {
       "if": { "properties": { "type": { "const": "sprint-complete" } }, "required": ["type"] },
       "then": {

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

@@ -1,6 +1,6 @@
 {
-  "version": "1.0.10",
-  "generatedAt": "2026-05-31T03:19:45.318Z",
+  "version": "1.2.13",
+  "generatedAt": "2026-06-03T05:20:45.625Z",
   "generatedByTool": "build-manifest.cjs",
   "namespaces": {
     "personas": {
@@ -38,15 +38,12 @@
         "architect_sprint_plan.md",
         "collator_agent.md",
         "commit_task.md",
-        "fix_bug.md",
         "implement_plan.md",
         "migrate_structural.md",
-        "orchestrate_task.md",
         "plan_task.md",
         "quiz_agent.md",
         "review_code.md",
         "review_plan.md",
-        "run_sprint.md",
         "sprint_retrospective.md",
         "triage.md",
         "update_implementation.md",
@@ -106,6 +103,15 @@
         "store-write-verification.md"
       ]
     },
+    "workflows-js": {
+      "logicalKey": "workflows-js",
+      "dir": ".claude/workflows",
+      "files": [
+        "wfl-fix-bug.js",
+        "wfl-run-sprint.js",
+        "wfl-run-task.js"
+      ]
+    },
     "schemas": {
       "logicalKey": "schemas",
       "dir": ".forge/schemas",
@@ -126,6 +132,70 @@
         "structure-versions.schema.json",
         "task.schema.json"
       ]
+    },
+    "tools": {
+      "logicalKey": "tools",
+      "dir": ".forge/tools",
+      "files": [
+        "artifact-store.cjs",
+        "artifact.cjs",
+        "backfill-provider.cjs",
+        "banners.cjs",
+        "build-base-pack.cjs",
+        "build-context-pack.cjs",
+        "build-enum-catalog.cjs",
+        "build-init-context.cjs",
+        "build-manifest.cjs",
+        "build-overlay.cjs",
+        "build-persona-pack.cjs",
+        "check-no-skipped-tests.cjs",
+        "check-structure.cjs",
+        "collate.cjs",
+        "compression-gate.cjs",
+        "delete-candidate-detector.cjs",
+        "estimate-usage.cjs",
+        "forge-preflight.cjs",
+        "friction-emit.cjs",
+        "gen-integrity.cjs",
+        "generation-manifest.cjs",
+        "judge-proposal.cjs",
+        "manage-config.cjs",
+        "manage-versions.cjs",
+        "migrate-slug-maxlen.cjs",
+        "parse-gates.cjs",
+        "postflight-gate.cjs",
+        "preflight-gate.cjs",
+        "proposal-normalize.cjs",
+        "query-logger.cjs",
+        "queue-drain.cjs",
+        "read-verdict.cjs",
+        "replay-scoring.cjs",
+        "rewrite-plugin-urls.cjs",
+        "seed-store.cjs",
+        "store-cli.cjs",
+        "store-query.cjs",
+        "store.cjs",
+        "substitute-placeholders.cjs",
+        "token-forensics.cjs",
+        "validate-store.cjs",
+        "verify-apply.cjs",
+        "verify-integrity.cjs",
+        "verify-phase.cjs",
+        "lib/artifact-kinds.cjs",
+        "lib/forge-root.cjs",
+        "lib/frontmatter.cjs",
+        "lib/fsutil.cjs",
+        "lib/json-io.cjs",
+        "lib/paths.cjs",
+        "lib/pricing.cjs",
+        "lib/project-root.cjs",
+        "lib/schema-loader.cjs",
+        "lib/slug.cjs",
+        "lib/store-facade.cjs",
+        "lib/store-nlp.cjs",
+        "lib/store-query-exec.cjs",
+        "lib/suggest.cjs"
+      ]
     }
   },
   "edges": {
@@ -200,41 +270,6 @@
           "paths.engineering"
         ]
       },
-      "fix_bug": {
-        "personas": [
-          ".forge/personas/bug-fixer.md",
-          ".forge/personas/supervisor.md",
-          ".forge/personas/architect.md",
-          ".forge/personas/engineer.md",
-          ".forge/personas/collator.md"
-        ],
-        "skills": [
-          ".forge/skills/bug-fixer-skills.md",
-          ".forge/skills/supervisor-skills.md",
-          ".forge/skills/architect-skills.md",
-          ".forge/skills/engineer-skills.md",
-          ".forge/skills/generic-skills.md"
-        ],
-        "templates": [
-          ".forge/templates/PROGRESS_TEMPLATE.md"
-        ],
-        "sub_workflows": [
-          ".forge/workflows/plan_task.md",
-          ".forge/workflows/implement_plan.md",
-          ".forge/workflows/review_plan.md",
-          ".forge/workflows/review_code.md",
-          ".forge/workflows/architect_approve.md",
-          ".forge/workflows/commit_task.md"
-        ],
-        "kb_docs": [
-          "{KB_PATH}/architecture/stack.md",
-          "{KB_PATH}/architecture/routing.md"
-        ],
-        "config_fields": [
-          "commands.test",
-          "paths.engineering"
-        ]
-      },
       "implement_plan": {
         "personas": [
           ".forge/personas/engineer.md"
@@ -258,39 +293,6 @@
           "paths.engineering"
         ]
       },
-      "orchestrate_task": {
-        "personas": [
-          ".forge/personas/architect.md",
-          ".forge/personas/engineer.md",
-          ".forge/personas/supervisor.md",
-          ".forge/personas/bug-fixer.md",
-          ".forge/personas/collator.md",
-          ".forge/personas/qa-engineer.md"
-        ],
-        "skills": [
-          ".forge/skills/architect-skills.md",
-          ".forge/skills/engineer-skills.md",
-          ".forge/skills/supervisor-skills.md",
-          ".forge/skills/generic-skills.md"
-        ],
-        "templates": [],
-        "sub_workflows": [
-          ".forge/workflows/plan_task.md",
-          ".forge/workflows/implement_plan.md",
-          ".forge/workflows/review_plan.md",
-          ".forge/workflows/review_code.md",
-          ".forge/workflows/fix_bug.md",
-          ".forge/workflows/architect_approve.md",
-          ".forge/workflows/commit_task.md",
-          ".forge/workflows/validate_task.md"
-        ],
-        "kb_docs": [
-          "{KB_PATH}/architecture/stack.md"
-        ],
-        "config_fields": [
-          "paths.engineering"
-        ]
-      },
       "plan_task": {
         "personas": [
           ".forge/personas/architect.md"

package/dist/forge-payload/skills/refresh-kb-links/SKILL.md

@@ -89,14 +89,21 @@ Personas live in `.forge/personas/`.
 
 Only include rows for workflow files that actually exist on disk. Check each:
 
+Atomic workflows (LLM-generated markdown in `.forge/workflows/`):
+
 - `.forge/workflows/plan_task.md` → "Research codebase → implementation plan"
 - `.forge/workflows/implement_plan.md` → "Execute approved plan → code changes"
-- `.forge/workflows/fix_bug.md` → "Triage → fix → verify"
-- `.forge/workflows/orchestrate_task.md` → "Full task pipeline (plan → implement → review → commit)"
-- `.forge/workflows/run_sprint.md` → "Full sprint orchestration"
 - `.forge/workflows/architect_sprint_plan.md` → "Sprint planning and task decomposition"
 - `.forge/workflows/architect_sprint_intake.md` → "Sprint intake and requirements elicitation"
 
+Orchestration is deterministic JS, not prose. The LLM orchestration workflows
+(`orchestrate_task` / `run_sprint` / `fix_bug`) are **retired** — link the JS
+drivers in `.claude/workflows/` instead (only include rows where the file exists):
+
+- `.claude/workflows/wfl-run-task.js` → "Full task pipeline (plan → implement → review → approve → commit)"
+- `.claude/workflows/wfl-run-sprint.js` → "Full sprint orchestration"
+- `.claude/workflows/wfl-fix-bug.js` → "Triage → fix → verify"
+
 ```markdown
 <!-- forge-workflow-links: managed by Forge — do not edit manually -->
 ## Forge Workflows
@@ -105,13 +112,13 @@ Only include rows for workflow files that actually exist on disk. Check each:
 |----------|---------|
 | [Plan](.forge/workflows/plan_task.md) | Research codebase → implementation plan |
 | [Implement](.forge/workflows/implement_plan.md) | Execute approved plan → code changes |
-| [Fix bug](.forge/workflows/fix_bug.md) | Triage → fix → verify |
-| [Run task](.forge/workflows/orchestrate_task.md) | Full task pipeline (plan → implement → review → commit) |
-| [Run sprint](.forge/workflows/run_sprint.md) | Full sprint orchestration |
+| [Run task](.claude/workflows/wfl-run-task.js) | Full task pipeline (plan → implement → review → approve → commit) |
+| [Run sprint](.claude/workflows/wfl-run-sprint.js) | Full sprint orchestration |
+| [Fix bug](.claude/workflows/wfl-fix-bug.js) | Triage → fix → verify |
 <!-- /forge-workflow-links -->
 ```
 
-(Only include rows where the referenced `.forge/workflows/` file exists on disk.)
+(Only include rows where the referenced file exists on disk.)
 
 ## KB Integrity Check