@entelligentsia/forgecli 1.0.25 → 1.0.40

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

@@ -1,4 +1,100 @@
 {
+  "1.4.13": {
+    "version": "1.5.0",
+    "date": "2026-06-11",
+    "notes": "FORGE-S32-T07: plugin v1.5.0 — shim-only sunset release. The stable skillforge marketplace channel stops being a parallel distribution mechanism and becomes a one-way migration ramp to the CLI-first install (npm @entelligentsia/forgecli, the 4ge binary). NEW forge/forge/tools/apply-plugin-shim.cjs is a release-branch shim-overlay generator (sibling of rewrite-plugin-urls.cjs): it overwrites the release-branch forge/forge/commands/*.md with two template tiers — a FULL consent-gated migration shim for init/update/rebuild (migration explanation + node/npm preflight + prose-only consent-gated `npm i -g @entelligentsia/forgecli && 4ge init claude .` offer + print-only fallback) and a SHORT redirect notice ('run /forge:init to migrate') for every other command — then regenerates integrity.json so /forge:health verification still passes on plugin installs. CRITICAL: the shim is a RELEASE-BRANCH OVERLAY only; main's forge/forge/commands/ stays the real unified T06 tree because build-payload.cjs copies it verbatim into the CLI npm bundle — shimming main would poison the CLI payload. The tool refuses to apply without --target release (mirrors rewrite-plugin-urls --target discipline). README + skillforge marketplace listing are rewritten CLI-first; the marketplace appears only as a deprecation/migration note. The forge-releaser ritual wires apply-plugin-shim into Step 2 on the release branch and makes the build-payload-from-main + verify-publish gate explicit. The dual-path code strip and the retirement of apply-plugin-shim.cjs itself are deferred to S34 (mechanical). No store-record or schema migration; installed, already-bootstrapped projects keep their materialized .claude/commands/forge/ and converge on the next 4ge update / re-bootstrap (idempotent — preserves config/store/KB).",
+    "target": "tools:apply-plugin-shim,commands:release-shim-overlay,release:plugin-sunset",
+    "regenerate": [],
+    "breaking": false,
+    "manual": [
+      "The Forge marketplace plugin is being sunset. Migrate to the CLI-first install: `npm i -g @entelligentsia/forgecli` then `4ge init claude .` in your project. The migration is idempotent and preserves .forge/config.json, .forge/store/** and your knowledge-base folder. On the v1.5.0 plugin, running /forge:init (or /forge:update / /forge:rebuild) walks you through this migration with explicit consent."
+    ]
+  },
+  "1.4.12": {
+    "version": "1.4.13",
+    "date": "2026-06-11",
+    "notes": "FORGE-S32-T06: command-tree unification. The two payload command trees were collapsed into one. forge/forge/commands/ is now the single source of truth for ALL /forge:* commands: the 14 non-colliding base-pack sprint-workflow shims (approve, collate, commit, fix-bug, implement, new-sprint, plan, plan-sprint, retro, review-code, review-plan, run-sprint, run-task, validate) were folded in, and the three former-collision winners (init, check-agent, enhance) overwrite the plugin copies with the base-pack winner bytes. forge/forge/init/base-pack/commands/ was deleted AND build-base-pack.cjs no longer regenerates it (Section-5 command-generation loop + expectedFiles 'Commands (16)' block removed). The payload manifest drops its init/base-pack/commands entry; build-payload bundles one commands/ tree and base-pack/ no longer carries a commands/ subdir; bootstrap copies one directory with no union/collision ordering; registerAllForgeCommands enumerates dist/forge-payload/commands/ (forge:reset added to EXPLICITLY_REGISTERED_NAMES so the repoint introduces no new auto-stub). Installed .claude/commands/forge/ is byte-for-byte identical to the prior union output (AC3 parity preserved) and the frozen expected-install-set.json drops the 17 vendored .forge/.base-pack/commands/*.md entries. Plugin-channel semantic delta: the plugin-served init/check-agent/enhance bytes change to the base-pack winners; the plugin channel is retired at T07. See doc/decisions/command-model.md. No store-record migration; existing projects keep their installed commands and converge on the next 4ge update / re-bootstrap (idempotent).",
+    "target": "commands:*,init:base-pack:commands:*,payload-manifest:commands,tools:build-base-pack,tools:substitute-placeholders,tools:build-manifest",
+    "regenerate": [],
+    "breaking": false,
+    "manual": []
+  },
+  "1.4.11": {
+    "version": "1.4.12",
+    "date": "2026-06-11",
+    "notes": "FORGE-S32-T05: dead-payload trim via manifest. Removed the four superseded init/generation orchestrator placeholders (generate-knowledge-base.md, generate-personas.md, generate-skills.md, generate-templates.md) — each had zero live runtime citation (only historical vision/ docs + migration notes); the live per-subagent rulebooks generate-{commands,kb-doc,persona,skill,template,tools,workflows}.md are retained and the payload-manifest init/generation entry now carries an explicit curated include list. On the builder side (forge-cli) the dead build-payload Pass-1 substitute-placeholders bundle-root output (personas/skills/workflows/templates/) and its --include-full restore branch were removed; runtime re-substitutes from .base-pack/ at init Phase 3b, so that output was never consumed. DELIBERATELY RETAINED (audit verdicts refuted, reconciled): the non-dot schemas/ mirror (health.md/update.md read $FORGE_ROOT/schemas/ with no .schemas/ fallback in both plugin and fallback $FORGE_ROOT modes), schemas/structure-manifest.json (check-structure.cjs reads it via /forge:health step 8 with no --forge-root against installed projects), and the tools/lib store-{nlp,query-exec,facade}.cjs facades (required by store-query.cjs). No store-record migration; existing installs keep their generation copies until /forge:update narrows them.",
+    "target": "payload:init/generation-trim,build-payload:pass1-removed",
+    "regenerate": [],
+    "breaking": false,
+    "manual": []
+  },
+  "1.4.10": {
+    "version": "1.4.11",
+    "date": "2026-06-11",
+    "notes": "FEAT-009 T03: new /forge:reset command + reset-plan.cjs tool — a guardrailed, NLP-backed pipeline-state reset. reset-plan.cjs is a pure, read-only PLANNER: given a task/bug/sprint and a target phase it computes the status transition(s) plus cross-entity referential-integrity warnings (committed-work git divergence, parent-sprint incoherence, dependents resting on rewound work, and sprint cascade of transitive dependents) WITHOUT mutating the store. The /forge:reset command interprets a natural-language request, runs the planner, presents the transitions + integrity implications, requires explicit confirmation, then applies via store-cli update-status --force. Complements forge-cli's deterministic `4ge reset` (single-entity task/bug). New tool + command; structure-manifest/enum-catalog/integrity regenerated. No store-record migration.",
+    "target": "commands:reset,tools:reset-plan",
+    "regenerate": [],
+    "breaking": false,
+    "manual": []
+  },
+  "1.4.9": {
+    "version": "1.4.10",
+    "date": "2026-06-11",
+    "notes": "FORGE-BUG-047: store.cjs FSImpl.writeFeature() read data.feature_id, but feature records key on `id` (matching the schema, the store-cli template, and every FEAT-00x record; writeTask uses data.taskId and writeBug uses data.bugId correctly). data.feature_id was always undefined, so writes misfiled to features/undefined.json — features could not be created or updated through the sanctioned store-cli gateway at all, and store-cli reported exit 0 so the failure was silent. The pre-existing store.test.cjs round-trip used a mock store keyed on yet another name (data.featureId), so it never exercised the real FSImpl and never caught this. Fix: writeFeature now reads data.id; a new real-FSImpl round-trip test (write by id, read back, assert no features/undefined.json) locks it. Tool fix; no store-record migration.",
+    "target": "tools:store",
+    "regenerate": [],
+    "breaking": false,
+    "manual": []
+  },
+  "1.4.8": {
+    "version": "1.4.9",
+    "date": "2026-06-11",
+    "notes": "FORGE-BUG-045: payload-manifest.json's integrity.json entry declared install:'.forge/' but is never vendored into a bootstrapped project's .forge/ tree — the historical bootstrap only HASHES payloadRoot/integrity.json for the .bootstrap-manifest.json integrity field, never installs it. It is bundle-only (shipped to dist/forge-payload/integrity.json for verify-integrity.cjs forge-root resolution). This was the last over-broad-install entry missed by the FORGE-BUG-044 sweep; a manifest-driven bootstrap honouring install (FORGE-S32-T03) would install a phantom .forge/integrity.json, breaking AC4 byte-parity. Fix: the entry now declares bundleOnly:true and drops install (validating against the existing bundleOnly if/then/else contract from FORGE-BUG-044 — no schema or checker code change); a regression-lock test pins the corrected entry. Declarative data correction; no store-record migration.",
+    "target": "schemas:payload-manifest",
+    "regenerate": [],
+    "breaking": false,
+    "manual": []
+  },
+  "1.4.7": {
+    "version": "1.4.8",
+    "date": "2026-06-10",
+    "notes": "FORGE-BUG-044: payload-manifest.json declared install:'.forge/schemas/' for the schemas/transitions dir entry and the migrations.json file entry, but neither is ever vendored into a bootstrapped project's .forge/schemas/ (they are bundle-only — shipped to dist/forge-payload/.schemas/ for transition-guard.ts / migration-engine.ts resolution). A manifest-driven bootstrap honouring install (FORGE-S32-T03) would have installed >=4 phantom files, breaking AC4 byte-parity. Fix: NEW bundleOnly boolean in payload-manifest.schema.json with a draft-07 if/then/else contract (install forbidden when bundleOnly:true, else required; install dropped from base required[]); the two entries now declare bundleOnly:true and drop install; check-payload-manifest.cjs gains a bundle-only self-consistency pass (inconsistencies[] folded into ok + CLI exit) so the over-broad install field cannot recur. Declarative + tooling-enforced; no store-record migration.",
+    "target": "schemas:payload-manifest,tools:check-payload-manifest",
+    "regenerate": [],
+    "breaking": false,
+    "manual": []
+  },
+  "1.4.6": {
+    "version": "1.4.7",
+    "date": "2026-06-10",
+    "notes": "Declarative payload manifest + source-drift check (FORGE-S32-T02). NEW forge/forge/payload-manifest.json names every shipped artifact (source -> bundle -> install -> removal owner), spec'd by NEW forge/forge/schemas/payload-manifest.schema.json, replacing the implicit contract previously spread across build-payload.cjs / bootstrap.ts / uninstall.ts hand-maintained copy lists (the FORGE-BUG-030/036 MODULE_NOT_FOUND class). NEW forge/forge/tools/check-payload-manifest.cjs is a CI-only dev tool (not vendored to instances) that exits non-zero on a missing source or an orphan file under a recursive payload tree; wired into plugin-ci.yml. The three forge-cli consumers are rewired to read the manifest in FORGE-S32-T03. build-manifest.cjs DEV_ONLY_TOOLS now excludes check-payload-manifest.cjs; structure-manifest.json regenerated to list the newly-vendored payload-manifest.schema.json.",
+    "target": "tools:check-payload-manifest,schemas:payload-manifest,schemas:structure-manifest,tools:build-manifest",
+    "regenerate": [],
+    "breaking": false,
+    "manual": []
+  },
+  "1.4.5": {
+    "version": "1.4.6",
+    "date": "2026-06-09",
+    "notes": "Security hardening of the forge-permissions auto-approver (forge-engineering#42). The Bash auto-allow patterns were unanchored command prefixes (`cat *`, `cp *`, `gh issue *`, `git push *`, `node .../tools/*`), so a prompt-injected agent could read a secret and exfiltrate/execute it with no permission prompt. Patterns are now anchored to their argument shape: `cat`/`cp` only within `.forge/`/`engineering/`, `node` tools only from a trusted Forge root ($FORGE_ROOT/$CLAUDE_PLUGIN_ROOT, plugin cache, or a /.forge path), `gh issue` only against the current repo (no -R/--repo), `git push` only to a named remote (no explicit http(s)/ssh/git/file URL). A non-match falls through to Claude Code's normal permission flow (the human is asked) — it never blocks. Legit in-tree Forge workflow commands still auto-allow, so no new prompt storm. New test forge/hooks/__tests__/forge-permissions.test.cjs pins both directions.",
+    "target": "hooks:forge-permissions",
+    "regenerate": [],
+    "breaking": false,
+    "manual": [
+      "Run /forge:update to pick up the hardened forge-permissions hook. Interactive Claude Code sessions may now see a one-time permission prompt for commands outside the Forge working set (e.g. reading files outside .forge/, pushing to an explicit remote URL) — approve as normal. Autonomous forge-cli (pi) runs are unaffected (pi has no permission gate)."
+    ]
+  },
+  "1.2.21": {
+    "version": "1.3.0",
+    "date": "2026-06-07",
+    "notes": "CLI-first bootstrap: /forge:init now dispatches workflow('wfl:init') — the dynamic JS driver added in S31-T04. init.md command wrapper hoists interactive prompts (KB folder, CLAUDE.md offer, marketplace-skills offer). Phase-1 and Phase-4 rulebooks annotated with orchestrator-owned step markers. sdlc-init.md reduced to a spec pointer. New base-pack/commands/init.md project-local wrapper authored. No change to installed projects (init.md is a plugin command, not a materialized base-pack command).",
+    "target": "commands:init,init:wfl-init,init:phases:phase-1-collect,init:phases:phase-4-register,init:sdlc-init,init:base-pack:commands:init",
+    "regenerate": [],
+    "breaking": false,
+    "manual": [
+      "No action required for existing initialized projects. New inits use the dynamic wfl:init driver. The Workflow tool is required; upgrade Claude Code if not available."
+    ]
+  },
   "1.2.20": {
     "version": "1.2.21",
     "date": "2026-06-06",
@@ -2913,5 +3009,79 @@
     ],
     "breaking": false,
     "manual": []
+  },
+  "1.3.0": {
+    "version": "1.4.0",
+    "date": "2026-06-07",
+    "notes": "Fixed /forge:* command namespace (CLI-first redesign). Project-prefix command namespaces (/acme:*, /hello:*) are retired: getCommandsSubdir() now returns 'forge' unconditionally, base-pack command templates carry literal /forge: headings ({{PREFIX}} removed), and substitute-placeholders materializes commands to .claude/commands/forge/. All command .md files (plugin commands/ + base-pack commands/) resolve FORGE_ROOT with a vendored fallback: ${CLAUDE_PLUGIN_ROOT:-$(pwd)/.forge} — full parity for plugin-less projects bootstrapped by '4ge init claude' where tools/schemas/hooks are vendored under .forge/. Rulebooks (generate-commands, phase-3-materialize, phase-1-collect, meta-migrate, migrate_structural) updated to the fixed namespace.",
+    "target": "tools:lib:paths,tools:substitute-placeholders,commands:*,init:base-pack:commands:*,init:generation:generate-commands,init:phases:phase-1-collect,init:phases:phase-3-materialize,meta:workflows:meta-migrate,init:base-pack:workflows:migrate_structural",
+    "regenerate": [
+      "commands"
+    ],
+    "breaking": true,
+    "manual": [
+      "Existing projects with prefix-namespaced commands (.claude/commands/<prefix>/): re-run materialization (or /forge:rebuild) to produce .claude/commands/forge/, then delete the old .claude/commands/<prefix>/ directory. The old commands keep working until removed but will not receive updates."
+    ]
+  },
+  "1.4.0": {
+    "version": "1.4.1",
+    "date": "2026-06-07",
+    "notes": "wfl-init.js Workflow-harness parse fix: the driver shipped wrapped in 'export default async function wflInit(args)' — the Workflow tool permits exactly one export (the meta literal) and evaluates the rest as an async function body, so every /forge:init dispatch failed at launch with \"SyntaxError: Unexpected keyword 'export'\". Body now runs at top level reading the global args. New regression test (wfl-drivers-parse.test.cjs) parses all four base-pack drivers exactly the way the harness does.",
+    "target": "init:base-pack:workflows-js:wfl-init",
+    "regenerate": [
+      "workflows"
+    ],
+    "breaking": false,
+    "manual": [
+      "Projects bootstrapped with the broken driver: re-run '4ge init claude .' (idempotent repair overwrites .claude/workflows/wfl-init.js)."
+    ]
+  },
+  "1.4.1": {
+    "version": "1.4.2",
+    "date": "2026-06-07",
+    "notes": "wfl-init.js Workflow-API rewrite (forge#112): the driver mis-used the harness API four ways — phase(title, callback) callbacks were silently discarded so init ran 0 agents while reporting fabricated ok:true; parallel() received promises instead of thunks; agent() had model as first arg instead of opts.model; structured results lacked opts.schema. Phase bodies now run inline at top level, fan-outs use thunks, all agents use agent(prompt, {model, label, phase, schema}), and the report reflects real phase results. Rulebook reads use vendored .forge/init/... paths with direct-analysis fallback. Contract enforced by wfl-drivers-parse.test.cjs (phase-callback, thunk, arg-order, referenced-rulebook-exists gates).",
+    "target": "init:base-pack:workflows-js:wfl-init",
+    "regenerate": [
+      "workflows"
+    ],
+    "breaking": false,
+    "manual": [
+      "Projects bootstrapped with the broken driver: re-run '4ge init claude .' (idempotent repair overwrites .claude/workflows/wfl-init.js)."
+    ]
+  },
+  "1.4.2": {
+    "version": "1.4.3",
+    "date": "2026-06-07",
+    "notes": "wfl-init.js verify-phase CLI alignment (forge#112 follow-up): the Phase 2 verify prompts invoked 'verify-phase.cjs --phase 2' bare, but the tool requires '--phase 2 --kb-path <path>' (exit 2 without it). Both Phase 2 invocations now pass --kb-path \"${kbFolder}\". New contract gates in wfl-drivers-parse.test.cjs assert every driver verify-phase invocation uses a supported phase (1-3) and that --phase 2 always carries --kb-path.",
+    "target": "init:base-pack:workflows-js:wfl-init",
+    "regenerate": [
+      "workflows"
+    ],
+    "breaking": false,
+    "manual": []
+  },
+  "1.4.3": {
+    "version": "1.4.4",
+    "date": "2026-06-07",
+    "notes": "First full CLI-first field-test gap fixes (config drift + manifest scope): (1) phase-1-collect.md no longer instructs the config-writer to derive paths.commands from the project prefix — it is ALWAYS '.claude/commands/forge' (the prefix-derived instruction survived the 1.4.0 namespace redesign and produced paths.commands='.claude/commands/git' -> check-structure 0/14). (2) generate-tools.md gains an explicit step writing paths.forgeRoot='.forge' — without it the register agent improvised an absolute npm-global payload path, which breaks on version upgrades and nvm switches. (3) build-manifest.cjs excludes 10 plugin-development tools from the tools namespace — the structure manifest describes instances, and expecting dev tools produced false 49/59 'missing tools' gaps in /forge:health.",
+    "target": "init:phases:phase-1-collect,init:generation:generate-tools,tools:build-manifest,schemas:structure-manifest",
+    "regenerate": [],
+    "breaking": false,
+    "manual": [
+      "Existing CLI-first projects with drifted config: run node .forge/tools/manage-config.cjs set paths.commands '\".claude/commands/forge\"' and set paths.forgeRoot '\".forge\"', then re-run '4ge init claude .' to refresh .forge/schemas/structure-manifest.json."
+    ]
+  },
+  "1.4.4": {
+    "version": "1.4.5",
+    "date": "2026-06-09",
+    "notes": "Collate-workflow KB-link refresh is orchestrator-owned under forge-cli. collator_agent.md (base-pack) + meta-collate.md (meta source) no longer instruct the collator subagent to invoke the forge:refresh-kb-links Skill tool: forge-cli subagents run via the Pi runtime, which has no Skill tool, so the instruction triggered a multi-call bash-probe loop before falling back. The Claude Code TUI standalone path still uses the Skill tool; under forge-cli the run-task orchestrator owns the KB refresh (runRefreshKbLinks) after the writeback phase. Prose-only change to the generated collate workflow.",
+    "target": "workflows:collator_agent,meta:meta-collate",
+    "regenerate": [
+      "workflows:collator_agent"
+    ],
+    "breaking": false,
+    "manual": [
+      "Run /forge:update (or /forge:rebuild) to regenerate the collate workflow (collator_agent.md) with the orchestrator-owned KB-refresh guidance."
+    ]
   }
 }

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

@@ -0,0 +1,100 @@
+{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "$id": "https://github.com/Entelligentsia/forge/schemas/payload-manifest.schema.json",
+  "title": "Forge Payload Manifest",
+  "description": "Declarative inventory of every artifact the Forge payload ships: source path (under forge/forge/) -> bundle path (dist/forge-payload/) -> install destination (bootstrapped project root) -> removal owner (uninstall grouping). Replaces the hand-maintained copy lists in build-payload.cjs / bootstrap.ts / uninstall.ts (FORGE-S32). The owner enum and select shape are provisional pending FORGE-S32-T03 consumer wiring.",
+  "type": "object",
+  "additionalProperties": false,
+  "required": ["entries"],
+  "properties": {
+    "$schema": { "type": "string" },
+    "_doc": { "type": "string" },
+    "entries": {
+      "type": "array",
+      "items": { "$ref": "#/definitions/entry" }
+    }
+  },
+  "definitions": {
+    "entry": {
+      "type": "object",
+      "additionalProperties": false,
+      "required": ["source", "bundle", "owner", "kind"],
+      "if": {
+        "properties": { "bundleOnly": { "const": true } },
+        "required": ["bundleOnly"]
+      },
+      "then": {
+        "not": { "required": ["install"] }
+      },
+      "else": {
+        "required": ["install"]
+      },
+      "properties": {
+        "source": {
+          "type": "string",
+          "description": "Repo-relative path under forge/forge/ (file or directory root)."
+        },
+        "bundle": {
+          "type": "string",
+          "description": "Destination path inside dist/forge-payload/ that build-payload.cjs emits."
+        },
+        "install": {
+          "type": "string",
+          "description": "Destination inside a bootstrapped project, relative to project root (e.g. .forge/tools/, .claude/commands/forge/). Required unless bundleOnly:true (the if/then/else contract); forbidden when bundleOnly:true."
+        },
+        "bundleOnly": {
+          "type": "boolean",
+          "description": "True when the artifact ships to dist/forge-payload/ for tool/migration-engine resolution but is NOT installed into a bootstrapped project's tree. Such entries MUST NOT declare install (enforced by the if/then/else contract and check-payload-manifest.cjs). FORGE-BUG-044."
+        },
+        "owner": {
+          "type": "string",
+          "description": "Removal owner consumed by uninstall.ts, encoding the per-subtree removal grouping.",
+          "enum": ["forge-scaffold", "claude-commands", "claude-assets", "workflows"]
+        },
+        "kind": {
+          "type": "string",
+          "enum": ["file", "dir"]
+        },
+        "synthesized": {
+          "type": "boolean",
+          "description": "True when build-payload.cjs generates this artifact rather than copying it from source (e.g. tools/package.json CJS scope marker). Source-drift checks skip the missing-source assertion for synthesized entries."
+        },
+        "select": {
+          "type": "object",
+          "additionalProperties": false,
+          "description": "Selection filter for dir entries, mirroring build-payload.cjs Pass-2 logic.",
+          "properties": {
+            "recursive": {
+              "type": "boolean",
+              "description": "When false, only top-level files are selected; subdirectories are not descended."
+            },
+            "ext": {
+              "type": "array",
+              "items": { "type": "string" },
+              "description": "Allowed file-name suffixes (e.g. .cjs, .schema.json)."
+            },
+            "include": {
+              "type": "array",
+              "items": { "type": "string" },
+              "description": "Explicit allowlist of names for curated subtrees (tools/, skills/). Curated entries are forward-checked only; unlisted siblings are NOT orphans."
+            },
+            "exclude": {
+              "type": "array",
+              "items": { "type": "string" },
+              "description": "Path segments or file names to skip (e.g. __tests__, README.md)."
+            },
+            "prefix": {
+              "type": "array",
+              "items": { "type": "string" },
+              "description": "Required file-name prefixes (e.g. discover-, wfl-, phase-)."
+            }
+          }
+        },
+        "note": {
+          "type": "string",
+          "description": "Free-text rationale, preserving the inline citation comments that today live in build-payload.cjs (FORGE-BUG-030 marker, forge-cli#25 defects, etc.)."
+        }
+      }
+    }
+  }
+}

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

@@ -10,7 +10,7 @@ description: Conversational pipeline manager — add, customize, view, or remove
 ## Setup
 
 ```
-FORGE_ROOT: !`echo "${CLAUDE_PLUGIN_ROOT}"`
+FORGE_ROOT: !`echo "${CLAUDE_PLUGIN_ROOT:-$(pwd)/.forge}"`
 ```
 
 Read project config values:

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

@@ -10,7 +10,7 @@ Add a task to an existing sprint without re-running the full sprint planner.
 ## Setup
 
 ```
-FORGE_ROOT: !`echo "${CLAUDE_PLUGIN_ROOT}"`
+FORGE_ROOT: !`echo "${CLAUDE_PLUGIN_ROOT:-$(pwd)/.forge}"`
 ```
 
 Read project config values:
@@ -256,8 +256,8 @@ Display a summary (substitute `{PREFIX}` with `PROJECT_PREFIX.toLowerCase()`):
    Pipeline:   {PIPELINE}
 
 ── Next steps:
-   1. Run /{PREFIX}:run-task {TASK_ID} to execute the full pipeline.
-   2. Or run /{PREFIX}:plan {TASK_ID} to plan it first.
+   1. Run /forge:run-task {TASK_ID} to execute the full pipeline.
+   2. Or run /forge:plan {TASK_ID} to plan it first.
 ```
 
 ---

package/dist/forge-payload/{.base-pack/commands → commands}/approve.md

@@ -3,14 +3,14 @@ name: approve
 description: Final architect approval gate for a completed task
 ---
 
-# /{{PREFIX}}:approve
+# /forge:approve
 
 Read the approve workflow and follow it.
 
 ## Locate the Forge plugin
 
 ```
-FORGE_ROOT: !`echo "${CLAUDE_PLUGIN_ROOT}"`
+FORGE_ROOT: !`echo "${CLAUDE_PLUGIN_ROOT:-$(pwd)/.forge}"`
 ```
 
 ## Execute

package/dist/forge-payload/commands/ask.md

@@ -10,7 +10,7 @@ Single conversational entry point for all Forge intent.
 ## Locate plugin root
 
 ```
-FORGE_ROOT: !`echo "${CLAUDE_PLUGIN_ROOT}"`
+FORGE_ROOT: !`echo "${CLAUDE_PLUGIN_ROOT:-$(pwd)/.forge}"`
 ```
 
 ## Open with oracle banner

package/dist/forge-payload/commands/check-agent.md

@@ -1,38 +1,22 @@
 ---
 name: check-agent
-description: Verify an agent has loaded and understood the project knowledge base — run a short factual quiz before starting high-stakes tasks
+description: Verify an agent has loaded and understood the project knowledge base
 ---
 
 # /forge:check-agent
 
-Verify that the active agent has correctly read and understood this project's
-knowledge base before beginning a high-stakes task (schema changes, migrations,
-release engineering, significant refactors).
+Read the check-agent workflow and follow it.
 
-## Locate plugin root
+## Locate the Forge plugin
 
 ```
-FORGE_ROOT: !`echo "${CLAUDE_PLUGIN_ROOT}"`
+FORGE_ROOT: !`echo "${CLAUDE_PLUGIN_ROOT:-$(pwd)/.forge}"`
 ```
 
-## Arguments
-
-$ARGUMENTS
-
-## How to Run
-
-Read `.forge/workflows/quiz_agent.md` and follow it exactly.
+## Execute
 
-Pass `$ARGUMENTS` to the workflow so the agent can include task context in its
-responses if provided.
+Read `.forge/workflows/quiz_agent.md` and follow it.
 
-## On error
-
-If `.forge/workflows/quiz_agent.md` does not exist, tell the user:
-
-> △ The quiz_agent workflow is missing. Run `/forge:rebuild workflows` to
-> regenerate it, then retry.
-
-If any other step fails unexpectedly, describe what went wrong and ask:
+## Arguments
 
-> "This looks like a Forge bug. Would you like to file a report to help improve it? Run `/forge:report-bug` — I'll pre-fill the report from this conversation."
+$ARGUMENTS

package/dist/forge-payload/{.base-pack/commands → commands}/collate.md

@@ -3,14 +3,14 @@ name: collate
 description: Regenerate KB documents from the JSON store
 ---
 
-# /{{PREFIX}}:collate
+# /forge:collate
 
 Read the collate workflow and follow it.
 
 ## Locate the Forge plugin
 
 ```
-FORGE_ROOT: !`echo "${CLAUDE_PLUGIN_ROOT}"`
+FORGE_ROOT: !`echo "${CLAUDE_PLUGIN_ROOT:-$(pwd)/.forge}"`
 ```
 
 ## Execute

package/dist/forge-payload/{.base-pack/commands → commands}/commit.md

@@ -3,14 +3,14 @@ name: commit
 description: Stage and commit completed task artifacts
 ---
 
-# /{{PREFIX}}:commit
+# /forge:commit
 
 Read the commit workflow and follow it.
 
 ## Locate the Forge plugin
 
 ```
-FORGE_ROOT: !`echo "${CLAUDE_PLUGIN_ROOT}"`
+FORGE_ROOT: !`echo "${CLAUDE_PLUGIN_ROOT:-$(pwd)/.forge}"`
 ```
 
 ## Execute

package/dist/forge-payload/commands/config.md

@@ -11,7 +11,7 @@ commands (e.g. `paths.forgeRoot` is refreshed by `/forge:update`).
 ## Locate the Forge plugin
 
 ```
-FORGE_ROOT: !`echo "${CLAUDE_PLUGIN_ROOT}"`
+FORGE_ROOT: !`echo "${CLAUDE_PLUGIN_ROOT:-$(pwd)/.forge}"`
 ```
 
 Read `.forge/config.json`. If it does not exist, stop and emit:

package/dist/forge-payload/commands/enhance.md

@@ -1,11 +1,37 @@
 ---
 name: enhance
-description: REMOVED in v1.0 — use /forge:rebuild --enrich instead
+description: Progressive project-specific enrichment of structural elements
 ---
 
-# /forge:enhance — Removed
+# /forge:enhance
 
-× `/forge:enhance` was removed in v1.0. Enhancement is now a flag on `/forge:rebuild`:
+Run the enhancement agent to enrich structural elements with project-specific knowledge.
 
-- `/forge:rebuild --enrich` — runs the full enhancement workflow (Phase 2 KB enrichment + Phase 3 drift detection)
-- Enhancement hooks (post-init `--auto`, post-sprint `--phase 2`) continue to fire automatically — no action needed
+## Locate the Forge plugin
+
+```
+FORGE_ROOT: !`echo "${CLAUDE_PLUGIN_ROOT:-$(pwd)/.forge}"`
+```
+
+## Purpose
+
+The enhancement agent observes the project and enriches structural elements
+over time. It makes absolutely essential minimal modifications, preferring
+runtime mix-in (KB references, `{{placeholder}}` substitution, `project-context.json`)
+over modifying base artifacts.
+
+## Behavior
+
+1. Read `structure-versions.json` to determine current overlay level
+2. Read `project-context.json` for current project specifics
+3. Read KB changes since last enhancement
+4. Scan codebase for patterns discovered since last enhancement
+5. Compare current `.forge/` artifacts against base-pack baseline
+6. For each artifact, determine what project-specific enrichment is warranted
+7. Apply the minimal modification principle
+8. Propose diffs (Phase 2+) or auto-apply (Phase 1)
+9. Create new overlay version in `structure-versions.json` if needed
+
+## Arguments
+
+$ARGUMENTS

package/dist/forge-payload/{.base-pack/commands → commands}/fix-bug.md

@@ -3,14 +3,14 @@ name: fix-bug
 description: Triage, diagnose, and fix a bug
 ---
 
-# /{{PREFIX}}:fix-bug
+# /forge:fix-bug
 
 Read the fix-bug workflow and follow it.
 
 ## Locate the Forge plugin
 
 ```
-FORGE_ROOT: !`echo "${CLAUDE_PLUGIN_ROOT}"`
+FORGE_ROOT: !`echo "${CLAUDE_PLUGIN_ROOT:-$(pwd)/.forge}"`
 ```
 
 ## Execute

package/dist/forge-payload/commands/health.md

@@ -32,7 +32,7 @@ Assess the health and currency of the project's SDLC knowledge base.
 
 First, resolve the plugin root and project root:
 ```
-FORGE_ROOT: !`echo "${CLAUDE_PLUGIN_ROOT}"`
+FORGE_ROOT: !`echo "${CLAUDE_PLUGIN_ROOT:-$(pwd)/.forge}"`
 ```
 
 Open the run with the oracle hero + subtitle:

package/dist/forge-payload/{.base-pack/commands → commands}/implement.md

@@ -3,14 +3,14 @@ name: implement
 description: Execute the approved implementation plan for a task
 ---
 
-# /{{PREFIX}}:implement
+# /forge:implement
 
 Read the implement workflow and follow it.
 
 ## Locate the Forge plugin
 
 ```
-FORGE_ROOT: !`echo "${CLAUDE_PLUGIN_ROOT}"`
+FORGE_ROOT: !`echo "${CLAUDE_PLUGIN_ROOT:-$(pwd)/.forge}"`
 ```
 
 ## Execute