@entelligentsia/forgecli 0.21.0 → 1.0.3

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/.base-pack/workflows/validate_task.md

@@ -36,38 +36,68 @@ deps:
 
 ```
 
-0. Pre-flight Gate Check:
+0a. 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 validate --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 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.
 
-1. Load Context:
+0b. Pipeline Step Guard (user-invoked state check):
+   - 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`
+   - 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:
+     Print the following and HALT (do not proceed):
+     `× Task {record_id} is in state '{status}' — /forge:implement must complete first. To run the full pipeline: /forge:run-task {record_id}`
+
+1. Read Review Loop Context:
+   - Check the spawning prompt for a `### Review Loop Context` block.
+   - 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 this is the final iteration (`N == M`) and the verdict is `Revision Required`,
+     append a `### Next Steps` section to the artifact showing:
+     ```
+     ### Next Steps
+     - Force-approve (bypass remaining reviews): `/forge:approve --force {task_id}`
+     - Increase iteration limit: edit `config.pipelines.{pipeline}.phases[validate].maxIterations`
+     - Restart from validation: `/forge:validate {task_id}`
+     ```
+
+2. Load Context:
    - Read task prompt
    - Read approved PLAN.md
    - Read the implementation
    - Read PROGRESS.md
 
-2. Validation:
+3. Validation:
    - Execute the "Acceptance Criteria" checklist from the plan
    - Verify that all technical constraints (e.g., performance, security) are met
    - Check for any regressions in related functionality
    - When re-running the test suite, use the **resolved test command** from `commands.test` in `.forge/config.json` (i.e. `` `${commands.test}` ``, e.g. `.venv/bin/python -m pytest`). Template placeholder: {{TEST_COMMAND}}. Do NOT invoke bare `python` / `python3` — the project interpreter is rarely on `$PATH`.
 
-3. Verdict:
+4. Verdict:
    - Write the validation report via:
      `forge_artifact({ command:"write", entity:"{entity_kind}", entityId:"{record_id}", artifact:"validation-report", content:"<markdown>" })`
      The markdown content must use the format:
      **Verdict:** [Approved | Revision Required]
      - If Revision Required: list the failed criteria and required fixes
      - If Approved: confirm the task is validated
+     - See step 1 for iteration header and final-iteration Next Steps requirements.
 
-4. Finalize:
+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)
    - **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:
+6. Emit Summary Sidecar:
    - Write the validation summary via:
      `forge_artifact({ command:"write", entity:"{entity_kind}", entityId:"{record_id}", artifact:"validation-summary", content:"<JSON>" })`
      The JSON content must have the following shape:

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

@@ -1,6 +1,6 @@
 {
   "name": "forge",
-  "version": "0.51.4",
+  "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/config.schema.json

@@ -204,11 +204,6 @@
           }
         }
       }
-    },
-    "mode": {
-      "type": "string",
-      "enum": ["full", "fast"],
-      "description": "Init mode. 'fast' means scaffolding was generated by /forge:init --fast (stubs present, heavy artifacts deferred to first use). 'full' means all artifacts are generated. Absent on pre-0.12 projects — treated as 'full' by all readers. Flipped to 'full' by /forge:regenerate (default) or /forge:materialize --all."
     }
   },
   "additionalProperties": false

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

@@ -1,6 +1,6 @@
 {
-  "version": "0.51.4",
-  "generated": "2026-05-26",
+  "version": "1.0.2",
+  "generated": "2026-05-28",
   "note": "Authoritative enum catalog. Source: build-enum-catalog.cjs. Regenerate via node forge/tools/build-manifest.cjs.",
   "enums": {
     "task.status": [
@@ -35,34 +35,30 @@
     ]
   },
   "commandNames": [
-    "forge:sprint-intake",
+    "forge:new-sprint",
     "forge:plan",
     "forge:review-plan",
     "forge:implement",
     "forge:review-code",
     "forge:fix-bug",
-    "forge:sprint-plan",
+    "forge:plan-sprint",
     "forge:run-task",
     "forge:run-sprint",
-    "forge:collate",
-    "forge:retrospective",
+    "forge:retro",
     "forge:approve",
     "forge:commit",
-    "forge:enhance",
-    "forge:quiz-agent",
+    "forge:check-agent",
     "forge:validate",
     "forge:init",
     "forge:health",
-    "forge:regenerate",
+    "forge:rebuild",
     "forge:update",
     "forge:add-task",
     "forge:add-pipeline",
-    "forge:calibrate",
-    "forge:materialize",
     "forge:remove",
     "forge:report-bug",
-    "forge:store-query",
-    "forge:store-repair",
+    "forge:search",
+    "forge:repair",
     "forge:config",
     "forge:ask",
     "forge:store-custodian",

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

@@ -1,4 +1,67 @@
 {
+  "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",
+    "notes": "v1.0.2 — deprecated command cleanup + init bug fixes. Redirect stubs removed (old command names are now unknown). paths.commands uses project prefix. artifact.cjs strips trailing filenames from store path. Deprecated command references replaced across all meta sources.",
+    "target": "commands,init:phases,init:sdlc-init,tools:artifact",
+    "regenerate": ["commands"],
+    "breaking": false,
+    "manual": [
+      "Deprecated command redirect stubs removed. Old names (sprint-intake, sprint-plan, retrospective, regenerate, store-query, store-repair, quiz-agent, calibrate, update-tools, migrate, materialize) are now unknown commands. See docs/migration/v0-to-v1.md for the mapping.",
+      "If your project has .claude/commands/<prefix>/sprint-intake.md, sprint-plan.md, retrospective.md, or quiz-agent.md — these are stale and can be deleted."
+    ]
+  },
+  "1.0.0": {
+    "version": "1.0.1",
+    "date": "2026-05-27",
+    "notes": "v1.0.1 — init phase decomposition (FORGE-S26-T17). New shared verify-phase.cjs tool; sdlc-init.md rewritten as thin orchestrator; per-phase prompt files extracted to init/phases/.",
+    "target": "tools:verify-phase,init:phases",
+    "regenerate": ["tools"],
+    "breaking": false,
+    "manual": []
+  },
+  "0.52.1": {
+    "version": "1.0.0",
+    "date": "2026-05-26",
+    "notes": "v1.0.0 — v1.0 DevX Overhaul (FORGE-S26). 7 command renames, 6 command removals, fast-mode dead code removal, health --fix, rebuild --enrich, init --migrate, pipeline step guards, revision loop visibility, post-init welcome, Tomoshibi enhancements, forge:status plugin command, v1.0 documentation restructure.",
+    "target": "commands:new-sprint,commands:plan-sprint,commands:retro,commands:rebuild,commands:search,commands:repair,commands:check-agent,commands:calibrate,commands:enhance,commands:migrate,commands:materialize,commands:update-tools,commands:collate,commands:status,workflows:orchestrate_task,workflows:plan_task,workflows:implement_plan,workflows:fix_bug,config:mode",
+    "regenerate": ["commands", "workflows", "tools"],
+    "breaking": true,
+    "manual": [
+      "Removed commands: /forge:update-tools, /forge:materialize, /forge:enhance, /forge:calibrate, /forge:migrate, /forge:collate (user surface). Use /forge:update for schema refresh, /forge:rebuild --enrich for enhancement, /forge:health --fix for calibration, /forge:init --migrate for migration.",
+      "Renamed commands: /forge:sprint-intake → /forge:new-sprint, /forge:sprint-plan → /forge:plan-sprint, /forge:retrospective → /forge:retro, /forge:regenerate → /forge:rebuild, /forge:store-query → /forge:search, /forge:store-repair → /forge:repair, /forge:quiz-agent → /forge:check-agent. Old names redirect with deprecation notice.",
+      "Config: 'mode' field removed from .forge/config.json schema. Remove it manually from existing projects or run /forge:update."
+    ]
+  },
+  "0.52.0": {
+    "version": "0.52.1",
+    "date": "2026-05-26",
+    "notes": "fix(tool-discipline): add forge_artifact and forge_verify_apply discipline lines to meta/fragments/tool-discipline.md — fragment was missing two bullet points present in the FORGE_TOOL_DISCIPLINE TypeScript constant, causing subagents to receive incomplete discipline text when the fragment was present.",
+    "target": "fragments:tool-discipline",
+    "regenerate": [],
+    "breaking": false,
+    "manual": []
+  },
+  "0.51.4": {
+    "version": "0.52.0",
+    "date": "2026-05-26",
+    "notes": "New tools: artifact.cjs, verify-apply.cjs; tool-discipline.md canonical fragment; store-cli list/read --no-summaries, --fields, --limit, --count flags.",
+    "target": "tools:artifact,tools:verify-apply,tools:store-cli",
+    "regenerate": [
+      "tools"
+    ],
+    "breaking": false,
+    "manual": []
+  },
   "0.51.3": {
     "version": "0.51.4",
     "date": "2026-05-26",

package/dist/forge-payload/agents/tomoshibi.md

@@ -65,7 +65,7 @@ Permitted fields: `project.name`, `project.prefix` only.
 
 | Field | Impact |
 |---|---|
-| `project.prefix` | △ Requires regeneration — command folder renames from `.claude/commands/{old_lower}/` to `.claude/commands/{new_lower}/`, and generated workflow slash-command references become stale. Run `/forge:regenerate commands workflows` after confirming. |
+| `project.prefix` | △ Requires regeneration — command folder renames from `.claude/commands/{old_lower}/` to `.claude/commands/{new_lower}/`, and generated workflow slash-command references become stale. Run `/forge:rebuild commands workflows` after confirming. |
 
 *The prefix is stored as provided but the command namespace is always lowercase.*
 | `project.name` | 〇 No regeneration needed. |
@@ -106,7 +106,7 @@ remote check — Tomoshibi only knows the locally installed version.
 ### Workflow or command explanation
 
 Triggered by: "how does sprint planning work?", "explain the implement workflow",
-"what does /forge:calibrate do?", etc.
+"what does /forge:health --fix do?", etc.
 
 Read the relevant file:
 - Workflows: `.forge/workflows/<name>.md`
@@ -138,6 +138,147 @@ Use the Skill tool:
 
 ---
 
+### What now?
+
+Triggered by (fuzzy, case-insensitive, substring match): "what now", "what should i do", "what's next", "where do i start", "next steps", "get started", "how do i begin"
+
+State detection — run in order, stop at first match:
+
+**1. No config:**
+
+If `HAS_CONFIG` env is false or `manage-config.cjs get project` returns an error:
+
+```
+灯 No Forge project found here.
+Run /forge:init to create one, then come back and ask again.
+```
+
+**2. No sprints:**
+
+```sh
+node "$FORGE_ROOT/tools/store-cli.cjs" list sprint status=active
+node "$FORGE_ROOT/tools/store-cli.cjs" list sprint status=planning
+```
+
+If both are empty:
+
+```
+灯 Project initialized, no sprints yet.
+Next step: /forge:new-sprint — start your first sprint by describing what you want to build.
+```
+
+**3. Active sprint — inspect tasks:**
+
+```sh
+node "$FORGE_ROOT/tools/store-cli.cjs" list task status=planned
+node "$FORGE_ROOT/tools/store-cli.cjs" list task status=implementing
+node "$FORGE_ROOT/tools/store-cli.cjs" list task status=committed
+```
+
+Determine sub-state from results:
+
+- **All tasks committed** (no planned, no implementing):
+  ```
+  灯 Sprint {id} complete — all tasks committed.
+  Next step: /forge:retro — capture lessons learned and close the sprint.
+  ```
+
+- **Any tasks implementing** (n implementing, m planned, k committed):
+  ```
+  灯 Sprint {id} in progress — {n} tasks implementing, {m} planned, {k} committed.
+  Next step: /forge:run-task {next-planned-task-id} — continue the pipeline.
+  ```
+
+- **All tasks planned** (none started):
+  ```
+  灯 Sprint {id} ready — {n} tasks planned, none started.
+  Next step: /forge:run-task {first-task-id} — kick off the first task.
+  ```
+
+---
+
+### Commands
+
+Triggered by (fuzzy, case-insensitive, substring match): "commands", "help", "available commands", "what commands", "command list", "what can you do", "list commands", "show commands"
+
+Respond with this static reference (no shell commands needed):
+
+```
+灯 Forge v1.0 command reference:
+
+Tier 1 — Start here:
+  /forge:ask         Ask anything — this command
+  /forge:init        Create a new Forge project
+  /forge:new-sprint  Start a new sprint (intake)
+  /forge:status      Current sprint and task overview
+  /forge:health      Project health check and diagnostics
+
+Tier 2 — Sprint workflow:
+  /forge:plan-sprint  Decompose sprint into tasks
+  /forge:run-sprint   Run all sprint tasks (automated)
+  /forge:run-task     Run a single task through the pipeline
+  /forge:retro        Sprint retrospective
+  /forge:rebuild      Regenerate workflows, personas, commands
+
+Tier 3 — Advanced:
+  /forge:search       Query the task/sprint/bug store
+  /forge:repair       Repair store integrity issues
+  /forge:check-agent  Quiz an agent on project knowledge
+  /forge:config       View or change project configuration
+  /forge:update       Check for and install Forge updates
+  /forge:remove       Remove a task or sprint
+  /forge:add-task     Add a task to an active sprint
+  /forge:add-pipeline Register a custom pipeline
+  /forge:report-bug   File a Forge bug report
+```
+
+---
+
+### KB summary
+
+Triggered by (fuzzy, case-insensitive, substring match): "what did you find", "show me", "kb summary", "knowledge base", "what's in the kb", "findings", "what do you know", "show kb", "summarize"
+
+**1. No config:**
+
+If `HAS_CONFIG` is false:
+
+```
+灯 No project config found — KB summary requires an initialized project.
+Run /forge:init first.
+```
+
+**2. Check calibration baseline:**
+
+```sh
+node "$FORGE_ROOT/tools/manage-config.cjs" get calibrationBaseline 2>/dev/null
+```
+
+- If absent or null → `calibration_status = "× No baseline — run /forge:health --fix to establish one."`
+- If present → `calibration_status = "〇 Baseline established."`
+
+**3. Read KB index:**
+
+```sh
+cat "$PROJECT_ROOT/engineering/MASTER_INDEX.md" 2>/dev/null
+```
+
+**4. Present compact summary:**
+
+```
+灯 Knowledge base summary:
+
+KB freshness: {calibration_status}
+
+Architecture: {n} sections — {list key architecture topics found}
+Business domain: {n} entities — {list key entities found}
+Features: {n} total — {n} active, {n} completed
+Sprints: {n} total — {n} active, {n} completed, {n} abandoned
+
+To explore further: /forge:search — query the store directly.
+```
+
+---
+
 ### Anything else
 
 Ask one clarifying question. Do not guess.
@@ -149,6 +290,9 @@ Ask one clarifying question. Do not guess.
 ```
 🏮 灯 Tomoshibi — I can help you with:
 
+  · What now?          — context-aware next step based on your current project state
+  · Commands           — full Forge v1.0 command reference, tiered by use case
+  · KB summary         — what's in your knowledge base and how fresh it is
   · Project status     — active sprint, open bugs, active features, in-progress tasks
   · Config queries     — show or change project.name / project.prefix
   · Version           — locally installed Forge version
@@ -168,14 +312,14 @@ What would you like to know?
 |---|---|---|
 | `.forge/config.json` | Yes | `project.name`, `project.prefix` only — with `[Y/n]` confirm |
 | `.forge/store/` | `list`/`read` via `store-cli.cjs` only | **Never** — redirect to workflow commands |
-| `.forge/workflows/`, `.forge/personas/`, `.forge/skills/` | Yes — to explain content | **Never** — redirect to `/forge:regenerate` |
-| `engineering/` KB | Yes — to answer questions | **Never** — redirect to `/forge:calibrate` or sprint commands |
-| `.claude/commands/` | Yes — to explain | **Never** — redirect to `/forge:regenerate commands` |
+| `.forge/workflows/`, `.forge/personas/`, `.forge/skills/` | Yes — to explain content | **Never** — redirect to `/forge:rebuild` |
+| `engineering/` KB | Yes — to answer questions | **Never** — redirect to `/forge:health --fix` or sprint commands |
+| `.claude/commands/` | Yes — to explain | **Never** — redirect to `/forge:rebuild commands` |
 | `forge/` plugin source | No — internal impl detail | **Never** |
 
 Forbidden store operations: `write`, `update-status`, `delete`, `emit`, `purge-events`.
 
-Forbidden forge commands to invoke: `/forge:remove`, `/forge:init`, `/forge:migrate` —
+Forbidden forge commands to invoke: `/forge:remove`, `/forge:init` —
 Tomoshibi can *explain* these but never invokes them.
 
 ## Output rules

package/dist/forge-payload/commands/add-pipeline.md

@@ -329,7 +329,7 @@ On success, print next steps:
       and fill in any {PLACEHOLDER} sections before running a task.
    2. Assign this pipeline to a task: set "pipeline": "{NAME}" in the task's
       .forge/store/tasks/{TASK_ID}.json, or let the sprint planner auto-assign it.
-   3. Run /forge:regenerate to update the orchestrator's pipeline routing.
+   3. Run /forge:rebuild to update the orchestrator's pipeline routing.
 ```
 
 ---

package/dist/forge-payload/commands/add-task.md

@@ -48,7 +48,7 @@ If no `--sprint` argument:
 - Filter to sprints with status `active` or `planning` (these are the only
   states where adding tasks makes sense).
 - If no active/planning sprints exist:
-  > △ No active or planning sprints found. Create a sprint first using sprint-intake.
+  > △ No active or planning sprints found. Create a sprint first using new-sprint.
   > Exit without making changes.
 - If only one active/planning sprint: auto-select it and tell the user:
   > 〇 Auto-selected sprint: **{SPRINT_ID}** — {title}