@entelligentsia/forgecli 0.10.0 → 0.11.2

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

@@ -27,7 +27,8 @@ deps:
 
 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 implement --task {taskId}`
+   - **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 implement --{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.
@@ -59,15 +60,17 @@ deps:
    - Tag updates: `<!-- Discovered during {TASK_ID} — {date} -->`
 
 6. Finalize:
-   - Transitions: task FSM legal predecessors are `planned`, `plan-approved`, or `implementing`; target is `implemented`.
-     - `planned`        → `implemented` (workflow-prose path — direct)
-     - `plan-approved`  → `implementing` → `implemented` (supervisor-review path)
-     - Out-of-band escapes (any state): `plan-revision-required`, `code-revision-required`, `blocked`, `escalated`, `abandoned`
-   - Update task status via `node "$FORGE_ROOT/tools/store-cli.cjs" update-status task {taskId} status implemented`
+   - Transitions:
+     - **Task mode** — legal predecessors are `planned`, `plan-approved`, or `implementing`; target is `implemented`.
+       - `planned`        → `implemented` (workflow-prose path — direct)
+       - `plan-approved`  → `implementing` → `implemented` (supervisor-review path)
+       - Out-of-band escapes (any state): `plan-revision-required`, `code-revision-required`, `blocked`, `escalated`, `abandoned`
+       Update status: `node "$FORGE_ROOT/tools/store-cli.cjs" update-status task {taskId} status implemented`
+     - **Bug mode** — NO status write. The bug remains `in-progress` until the commit phase transitions it to `fixed`. 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.
 
 7. Emit Summary Sidecar:
-   - Write `IMPLEMENTATION-SUMMARY.json` to the task directory with the following shape:
+   - Write `IMPLEMENTATION-SUMMARY.json` to the record's directory with the following shape:
      ```json
      {
        "objective":   "<one sentence — what this implementation delivered>",
@@ -77,12 +80,17 @@ deps:
        "artifact_ref":"PROGRESS.md"
      }
      ```
-   - Call:
+   - Call (task mode):
      ```
-     node "$FORGE_ROOT/tools/store-cli.cjs" set-summary {task_id} implementation \
+     node "$FORGE_ROOT/tools/store-cli.cjs" set-summary {taskId} implementation \
        engineering/sprints/{sprint}/{task}/IMPLEMENTATION-SUMMARY.json
      ```
-   - If set-summary exits non-zero, fix the sidecar JSON and retry. Do not proceed without a valid summary.
+     Or (bug mode):
+     ```
+     node "$FORGE_ROOT/tools/store-cli.cjs" set-bug-summary {bugId} implementation \
+       engineering/bugs/{bugDir}/IMPLEMENTATION-SUMMARY.json
+     ```
+   - If the set-summary call exits non-zero, fix the sidecar JSON and retry. Do not proceed without a valid summary.
 ```
 
 ## Iron Laws

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

@@ -27,7 +27,8 @@ deps:
 
 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 plan --task {taskId}`
+   - **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 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.
@@ -64,14 +65,14 @@ deps:
    - If new patterns were discovered, update architecture or business domain docs
 
 5. Finalize:
-   - Transitions: task FSM legal targets from this step
-     - `draft` → `planned` (this workflow's only legal target)
-     - Out-of-band escapes (any state): `plan-revision-required`, `code-revision-required`, `blocked`, `escalated`, `abandoned`
-   - Update task status via `node "$FORGE_ROOT/tools/store-cli.cjs" update-status task {taskId} status planned`
+   - Transitions:
+     - **Task mode** — legal target from this step: `draft → planned`. Out-of-band escapes (any state): `plan-revision-required`, `code-revision-required`, `blocked`, `escalated`, `abandoned`.
+       Update status: `node "$FORGE_ROOT/tools/store-cli.cjs" update-status task {taskId} status planned`
+     - **Bug mode** — NO status write. The bug remains `in-progress` until the commit phase transitions it to `fixed`. 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.
 
 6. Emit Summary Sidecar:
-   - Write `PLAN-SUMMARY.json` to the task directory with the following shape:
+   - Write `PLAN-SUMMARY.json` (task mode) or `BUG-FIX-PLAN-SUMMARY.json` (bug mode) to the record's directory. Shape:
      ```json
      {
        "objective":   "<one sentence — what this plan sets out to build>",
@@ -81,12 +82,17 @@ deps:
        "artifact_ref":"PLAN.md"
      }
      ```
-   - Call:
+   - Call (task mode):
      ```
-     node "$FORGE_ROOT/tools/store-cli.cjs" set-summary {task_id} plan \
+     node "$FORGE_ROOT/tools/store-cli.cjs" set-summary {taskId} plan \
        engineering/sprints/{sprint}/{task}/PLAN-SUMMARY.json
      ```
-   - If set-summary exits non-zero, fix the sidecar JSON and retry. Do not proceed without a valid summary.
+     Or (bug mode):
+     ```
+     node "$FORGE_ROOT/tools/store-cli.cjs" set-bug-summary {bugId} plan \
+       engineering/bugs/{bugDir}/BUG-FIX-PLAN-SUMMARY.json
+     ```
+   - If the set-summary call exits non-zero, fix the sidecar JSON and retry. Do not proceed without a valid summary.
 ```
 
 ## Iron Laws

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

@@ -45,7 +45,8 @@ Never set `FORGE_SKIP_WRITE_VALIDATION=1` — operator-only emergency switch.
 
 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 review-code --task {taskId}`
+   - **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-code --{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.
@@ -71,11 +72,13 @@ Never set `FORGE_SKIP_WRITE_VALIDATION=1` — operator-only emergency switch.
    - Update stack-checklist.md if new patterns or pitfalls were discovered
 
 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)
+   - Transitions:
+     - **Task mode** — Update status: `node "$FORGE_ROOT/tools/store-cli.cjs" update-status task {taskId} status review-approved` (if Approved) or `... status code-revision-required` (if Revision Required).
+     - **Bug mode** — NO status write. The bug remains `in-progress`. The verdict signal travels through `summaries.code_review.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 (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.
 
 6. Emit Summary Sidecar:
-   - Write `REVIEW-IMPL-SUMMARY.json` to the task directory with the following shape:
+   - Write `REVIEW-IMPL-SUMMARY.json` to the record's directory with the following shape:
      ```json
      {
        "objective":   "<one sentence — what this review assessed>",
@@ -85,10 +88,15 @@ Never set `FORGE_SKIP_WRITE_VALIDATION=1` — operator-only emergency switch.
        "artifact_ref":"CODE_REVIEW.md"
      }
      ```
-   - Call:
+   - Call (task mode):
      ```
-     node "$FORGE_ROOT/tools/store-cli.cjs" set-summary {task_id} code_review \
+     node "$FORGE_ROOT/tools/store-cli.cjs" set-summary {taskId} code_review \
        engineering/sprints/{sprint}/{task}/REVIEW-IMPL-SUMMARY.json
      ```
-   - If set-summary exits non-zero, fix the sidecar JSON and retry. Do not proceed without a valid summary.
+     Or (bug mode):
+     ```
+     node "$FORGE_ROOT/tools/store-cli.cjs" set-bug-summary {bugId} code_review \
+       engineering/bugs/{bugDir}/REVIEW-IMPL-SUMMARY.json
+     ```
+   - If the set-summary call exits non-zero, fix the sidecar JSON and retry. Do not proceed without a valid summary.
 ```

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

@@ -46,7 +46,8 @@ Never set `FORGE_SKIP_WRITE_VALIDATION=1` — operator-only emergency switch.
 
 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 review-plan --task {taskId}`
+   - **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}`
    - 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.
@@ -66,15 +67,17 @@ Never set `FORGE_SKIP_WRITE_VALIDATION=1` — operator-only emergency switch.
      - If Approved: provide any advisory notes
 
 4. Finalize:
-   - Transitions: task FSM predecessor must be `planned`.
-     - Approved          → `plan-approved`
-     - Revision Required → `plan-revision-required`
-     - Out-of-band escapes (any state): `code-revision-required`, `blocked`, `escalated`, `abandoned`
-   - Update task status via `node "$FORGE_ROOT/tools/store-cli.cjs" update-status task {taskId} status plan-approved` (if Approved) or `node "$FORGE_ROOT/tools/store-cli.cjs" update-status task {taskId} status plan-revision-required` (if Revision Required)
+   - Transitions:
+     - **Task mode** — predecessor must be `planned`.
+       - 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)
+     - **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.
 
 5. Emit Summary Sidecar:
-   - Write `REVIEW-PLAN-SUMMARY.json` to the task directory with the following shape:
+   - Write `REVIEW-PLAN-SUMMARY.json` to the record's directory with the following shape:
      ```json
      {
        "objective":   "<one sentence — what this review assessed>",
@@ -84,12 +87,17 @@ Never set `FORGE_SKIP_WRITE_VALIDATION=1` — operator-only emergency switch.
        "artifact_ref":"PLAN_REVIEW.md"
      }
      ```
-   - Call:
+   - Call (task mode):
      ```
-     node "$FORGE_ROOT/tools/store-cli.cjs" set-summary {task_id} review_plan \
+     node "$FORGE_ROOT/tools/store-cli.cjs" set-summary {taskId} review_plan \
        engineering/sprints/{sprint}/{task}/REVIEW-PLAN-SUMMARY.json
      ```
-   - If set-summary exits non-zero, fix the sidecar JSON and retry. Do not proceed without a valid summary.
+     Or (bug mode):
+     ```
+     node "$FORGE_ROOT/tools/store-cli.cjs" set-bug-summary {bugId} review_plan \
+       engineering/bugs/{bugDir}/REVIEW-PLAN-SUMMARY.json
+     ```
+   - If the set-summary call exits non-zero, fix the sidecar JSON and retry. Do not proceed without a valid summary.
 ```
 
 ## Generation Notes

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

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

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

@@ -9,7 +9,7 @@
     "title":               { "type": "string" },
     "description":         { "type": "string" },
     "severity":            { "type": "string", "enum": ["critical", "major", "minor"] },
-    "status":              { "type": "string", "enum": ["reported", "triaged", "in-progress", "fixed", "approved", "verified"] },
+    "status":              { "type": "string", "enum": ["reported", "triaged", "in-progress", "fixed"] },
     "path":                { "type": "string" },
     "rootCauseCategory": {
       "type": "string",
@@ -47,7 +47,8 @@
         "findings":    { "type": "array", "items": { "type": "string", "maxLength": 200 }, "maxItems": 12 },
         "verdict":     { "type": "string", "enum": ["approved", "revision", "n/a"] },
         "written_at":  { "type": "string", "format": "date-time" },
-        "artifact_ref":{ "type": "string", "description": "Relative path to the full artifact" }
+        "artifact_ref":{ "type": "string", "description": "Relative path to the full artifact" },
+        "route":       { "type": "string", "enum": ["A", "B"], "description": "Fix-bug pipeline route decision. Only set on the triage phase summary by meta-fix-bug.md. A = short-circuit (skip plan-fix + review-plan); B = full loop (default). Optional and meaningless on non-triage phases — see meta-fix-bug.md § Triage Judgement." }
       },
       "additionalProperties": false
     }

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

@@ -0,0 +1,83 @@
+{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "$id": "forge/config.schema.json",
+  "title": "ForgeConfig",
+  "description": "Schema for .forge/config.json — the per-project Forge configuration file.",
+  "type": "object",
+  "required": ["version", "project", "paths"],
+  "properties": {
+    "version": {
+      "type": "string",
+      "description": "Config schema version (e.g. '1.0')"
+    },
+    "project": {
+      "type": "object",
+      "required": ["prefix", "name"],
+      "properties": {
+        "prefix": { "type": "string", "description": "Task ID prefix (e.g. FORGE)" },
+        "name": { "type": "string", "description": "Human-readable project name" },
+        "description": { "type": "string" }
+      }
+    },
+    "stack": {
+      "type": "object",
+      "properties": {
+        "languages": { "type": "array", "items": { "type": "string" } },
+        "framework": { "type": ["string", "null"] },
+        "frontendFramework": { "type": ["string", "null"] },
+        "database": { "type": ["string", "null"] },
+        "taskQueue": { "type": ["string", "null"] },
+        "containerisation": { "type": ["string", "null"] }
+      }
+    },
+    "commands": {
+      "type": "object",
+      "properties": {
+        "test": { "type": "string" },
+        "lint": { "type": "string" },
+        "syntaxCheck": {}
+      }
+    },
+    "paths": {
+      "type": "object",
+      "required": ["engineering", "store", "forgeRoot"],
+      "properties": {
+        "engineering": { "type": "string" },
+        "store": { "type": "string" },
+        "workflows": { "type": "string" },
+        "commands": { "type": "string" },
+        "templates": { "type": "string" },
+        "customCommands": { "type": "string" },
+        "forgeRoot": { "type": "string" },
+        "forgeRef": { "type": "string" }
+      }
+    },
+    "pipeline": {
+      "type": "object",
+      "properties": {
+        "maxReviewIterations": { "type": "integer", "minimum": 1 }
+      }
+    },
+    "pipelines": {
+      "type": "object",
+      "description": "Custom pipeline definitions keyed by pipeline name"
+    },
+    "installedSkills": {
+      "type": "array",
+      "items": { "type": "string" }
+    },
+    "calibrationBaseline": {
+      "type": "object",
+      "properties": {
+        "lastCalibrated": { "type": "string" },
+        "version": { "type": "string" },
+        "masterIndexHash": { "type": "string" },
+        "sprintsCovered": { "type": "array", "items": { "type": "string" } }
+      }
+    },
+    "mode": {
+      "type": "string",
+      "enum": ["full", "fast"]
+    }
+  }
+}