@entelligentsia/forgecli 1.0.25 → 1.0.40

package/CHANGELOG.md

@@ -7,6 +7,347 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 
 ## [Unreleased]
 
+### Changed
+
+- **Command-tree unification (FORGE-S32-T06).** The former two-tree command
+  model is collapsed into a single unified `commands/` tree. `build-payload.cjs`
+  bundles one `commands/` directory (30 files) and `.base-pack/` no longer
+  carries a `commands/` subdir; `bootstrap.ts` copies one directory with no
+  union/collision precedence; `lib/payload-manifest.ts` drops the
+  loser/winner ordering note. `registerAllForgeCommands` (forge-commands.ts)
+  now enumerates `dist/forge-payload/commands/` instead of
+  `.base-pack/commands/`; `forge:reset` was added to
+  `EXPLICITLY_REGISTERED_NAMES` so the repoint introduces **no new auto-stub**
+  (the slash-command surface is unchanged). The frozen install-set fixture
+  (`expected-install-set.json`) drops the 17 vendored
+  `.forge/.base-pack/commands/*.md` entries; installed `.claude/commands/forge/`
+  byte-parity is preserved.
+
+- **Dead Pass-1 build output removed (FORGE-S32-T05).** `scripts/build-payload.cjs`
+  no longer emits the pre-substituted `personas/`/`skills/`/`workflows/`/
+  `templates/` bundle-root tree (the old `--include-full`-gated Pass 1) or its
+  restore branch. `forge-init.ts` re-runs `substitute-placeholders` against the
+  user's config from `.base-pack/` at runtime (Phase 3b), so that output was
+  never consumed in the default flow. `--include-full` still governs the full
+  `tools/lib/`, `.init/generation/`, and generic `.schemas/` supersets. The
+  non-dot `schemas/` mirror and `schemas/structure-manifest.json` are RETAINED
+  (load-bearing for `health.md`/`update.md` `$FORGE_ROOT/schemas/` reads and
+  `check-structure.cjs` via `/forge:health`). Frozen install-set parity fixture
+  (`expected-install-set.json`) updated to drop the four superseded
+  `init/generation` orchestrator placeholders trimmed on the plugin side.
+
+### Added
+
+- **Payload require-walker CI gate (FORGE-S32-T04).** New build-side tool
+  `tools/check-payload-requires.cjs <payloadRoot>` statically proves that every
+  `require()` target and referenced runtime path in the bundled payload's
+  `.cjs`/`.js` tools and hooks resolves inside the bundle. Generalizes the two
+  narrow regression guards (`bug-025-payload-completeness`,
+  `bug-036-payload-lib-completeness`) into one walker over ALL `.cjs`/`.js`
+  under `dist/forge-payload/{tools,hooks}`. Three reference classes are
+  resolved — static string requires, the runtime-path literals behind dynamic
+  requires, and dynamic `require(<variable>)` sites gated against a structural
+  `DYNAMIC_SITES` allowlist (keyed by file + normalized expression, not line
+  number). Any un-enumerated dynamic require is itself a hard failure (Iron Law
+  5, no silent skips). Exit `0`/`1`/`2` contract. Wired into `tests.yml`
+  (`npm run lint:payload-requires`, post-build) so the MODULE_NOT_FOUND drift
+  class (FORGE-BUG-030 / FORGE-BUG-036) is caught red, build-side. CI-only: no
+  payload bytes change.
+
+### Changed
+
+- **Payload consumers now read a single declarative manifest (FORGE-S32-T03).**
+  `scripts/build-payload.cjs` (bundle), `claude-bootstrap/bootstrap.ts` (vendor)
+  and `claude-bootstrap/uninstall.ts` (remove) are wired to
+  `forge/forge/payload-manifest.json` (authored in T02) instead of the
+  hand-maintained copy/removal lists each carried. build-payload's
+  `TOOLS_TO_COPY` / `LIB_ALLOWLIST` / `SKILLS_TO_COPY` arrays are deleted and
+  derived from the manifest; bootstrap vendors `payloadRoot/<bundle>` →
+  `<project>/<install>` driven solely by the manifest (the entry order encodes
+  the `commands` / `.base-pack/commands` union precedence); uninstall removes
+  install destinations grouped by `owner`, bounding agents/skills removal to
+  payload-declared names so user-authored siblings survive. `bundleOnly`
+  entries (`schemas/transitions`, `migrations.json`, `integrity.json`) ship to
+  the bundle for tool resolution but are never vendored. The build now bundles
+  `payload-manifest.json` itself so the runtime consumers can read it. Adding a
+  payload file is now a single manifest edit — the FORGE-BUG-030/036
+  MODULE_NOT_FOUND lockstep is retired. `4ge init claude .` output is
+  byte-identical (frozen-install-set parity guard in `bootstrap.test.ts`).
+
+### Added
+
+- **`4ge uninstall claude [dir] [--purge] [--yes]`** — the counterpart to
+  `4ge init claude`. Deterministically reverses the bootstrap: removes the
+  vendored Forge scaffold (`.forge/{tools,schemas,init,.base-pack,meta,
+  .claude-plugin,cache}`, `.bootstrap-manifest.json`, `.claude/commands/forge`,
+  `.claude/workflows`, and the payload's agents/skills), un-merges the Forge
+  hooks from `.claude/settings.json`, and un-appends the Forge block from
+  `.gitignore`. Safety: **preserves user data by default** (`.forge/config.json`,
+  `.forge/store/**`, the KB folder); `--purge` also removes config + store (KB
+  is never auto-removed). Refuses to act without a `.bootstrap-manifest.json`
+  (proof the project was forge-bootstrapped), edits `settings.json`/`.gitignore`
+  rather than deleting them, preserves user-authored agents/skills not in the
+  payload, and is idempotent. A `[y/N]` confirm guards it unless `--yes`/`-y` or
+  `FORGE_NON_INTERACTIVE=1`.
+
+### Fixed
+
+- **Halt-recovery advisor output now reaches the human (FORGE-BUG-046).** When a
+  `run-task` / `fix-bug` phase halted on a missing verdict or a preflight/
+  postflight gate failure, the orchestrator spawned an opus-class read-only
+  advisor — but its diagnosis was never surfaced. Two compounding defects:
+  `runHaltAdvisor` discarded the subagent result (never extracted or notified
+  the advisory text), and every caller invoked it with `void` and returned
+  `halted` immediately, so `pipeline-end` fired ~1 ms after the advisor started
+  — before the LLM had produced anything. Now the advisor is awaited before
+  teardown, its final output is surfaced via `ctx.ui.notify` (reaching both the
+  viewport tail and `orchestrator.jsonl`), and the structured `remediation` is
+  printed deterministically — independent of the LLM — so a skipped or failed
+  advisor still leaves a concrete next step. Applies to both the task and bug
+  verdict loops and all five gate-halt call sites.
+
+## [1.0.36] — 2026-06-09
+
+Orchestrator dashboard logs + autonomous run-sprint + KB-refresh, re-landed onto
+the modular-orchestrator decomposition.
+
+### Added
+
+- **Orchestrator decision logs on the dashboard.** The shared
+  `withOrchestratorTranscript` notify-interception now mirrors every
+  orchestrator notify onto its root node (`tree.appendTail(entityId, …)`), and
+  the dashboard renders the Activity log for ALL node kinds (not just leaf). The
+  task/sprint/bug root node now carries the orchestrator's own narrative — gate
+  results, review verdicts, escalations, halts — alongside the per-phase leaf
+  nodes' subagent tool-call activity. New granular per-phase lines: `〇 preflight
+  ok`, `dispatch persona/model`, resolved `verdict`, `〇 postflight ok`.
+- **KB-link refresh is orchestrator-owned in run-task.** After the writeback
+  phase, the pipeline calls `runRefreshKbLinks(cwd)` directly (forge-cli
+  subagents run via the Pi runtime and have no Skill tool, so the prior
+  `forge:refresh-kb-links` Skill-tool instruction caused a multi-call probe
+  loop).
+
+### Changed
+
+- **`/forge:run-sprint` runs to completion.** Removed the per-task "Continue to
+  next task?" confirm and the partial-ceremony-on-decline branch. A sprint
+  command now runs all of its tasks, then the single clean-complete ceremony.
+  The mid-sprint modal previously turned any UI hiccup into a premature partial
+  ceremony (ceremony firing after task 1 with later tasks still draft).
+  Deliberate cancellation (abort signal / task halt) still stops the sprint.
+
+### Fixed
+
+- Dispatch line printed `model=[object Object]` — `modelResolution.model` is a
+  `{provider, model}` object; now formatted as `provider:model`.
+
+## [1.0.35] — 2026-06-07
+
+Re-bundle forge-plugin 1.4.4 — CLI-first field-test gap fixes: paths.commands
+no longer prefix-derived (always `.claude/commands/forge`), explicit
+`paths.forgeRoot=".forge"` write, dev-only tools excluded from the
+structure manifest (instance expectation 49/49, no false /forge:health gaps).
+
+## [1.0.34] — 2026-06-07
+
+No-dead-vendored-references gate (closes the forge#112 failure class).
+
+### Added
+
+- **`tools/check-vendored-refs.cjs`** — scans every vendored text file
+  (commands, drivers, rulebooks, settings, agents, skills) for
+  `.forge/…` / `$FORGE_ROOT/…` path references and fails on any whose
+  target doesn't exist post-bootstrap. Wired in twice: vitest
+  (`vendored-refs.test.ts`, against the real payload) and `tmp-smoke.sh`
+  BOOTSTRAP-9.
+
+### Fixed
+
+- Two dead references the new gate caught immediately:
+  **`forge-preflight.cjs`** (referenced by the run-task driver +
+  meta-fix-bug/meta-orchestrate — /forge:run-task would have hit a dead tool
+  on first use) added to `TOOLS_TO_COPY`, and
+  **`init/workflow-gen-plan.json`** (referenced by rebuild.md) bundled.
+
+## [1.0.33] — 2026-06-07
+
+Re-bundle forge-plugin 1.4.3 — wfl-init.js Phase 2 verify invocations carry
+the required `--kb-path` ([forge#112](https://github.com/Entelligentsia/forge/issues/112) follow-up).
+
+## [1.0.32] — 2026-06-07
+
+Re-bundle forge-plugin 1.4.2 — wfl-init.js Workflow-API rewrite
+([forge#112](https://github.com/Entelligentsia/forge/issues/112): phase
+callbacks silently discarded → init ran 0 agents but reported success;
+parallel() thunks; agent(prompt, opts) arg order; missing schema opts).
+
+### Fixed
+
+- **`build-payload` bundles the full `init/` rulebook tree** — `discovery/`
+  (5 prompts) and `generation/` (11 rulebooks) join `phases/`. Bundling only
+  `phases/` left wfl-init.js discovery/KB-doc subagents with dead rulebook
+  references in vendored projects.
+
+## [1.0.31] — 2026-06-07
+
+Re-bundle forge-plugin 1.4.1 — wfl-init.js Workflow-harness parse fix
+(`export default` wrapper stripped; every `/forge:init` dispatch previously
+failed at launch with "SyntaxError: Unexpected keyword 'export'").
+Projects bootstrapped with the broken driver: re-run `4ge init claude .`
+(idempotent repair overwrites `.claude/workflows/wfl-init.js`).
+
+## [1.0.30] — 2026-06-07
+
+Fixed `/forge:*` command namespace — full project vendoring (bundles forge-plugin 1.4.0).
+
+### Changed
+
+- **Bootstrap Step 4 — full `/forge:*` command surface vendored.** Replaces the
+  init.md-only install: the union of `.base-pack/commands/` (17 sprint-workflow
+  shims, now static `/forge:*` files) and `commands/` (utility commands) vendors
+  into `.claude/commands/forge/`. On name collision (`init.md`, `check-agent.md`,
+  `enhance.md`) the `.base-pack` version wins. Project-prefix namespaces
+  (`/acme:*`, `/hello:*`) are retired — wfl:init no longer generates them
+  (plugin 1.4.0 `getCommandsSubdir()` is fixed to `forge`).
+
+- **Bootstrap Step 4c — Forge-root content vendored into `.forge/`.** `init/`
+  (wfl:init phase rulebooks), `.base-pack/` (Phase 3 materialization source —
+  substitute-placeholders probes it first), `meta/` (rebuild/migrate sources +
+  skill-recommendations), and `.claude-plugin/plugin.json` (version source).
+  The vendored `.forge/` now serves as a complete Forge root for the
+  `${CLAUDE_PLUGIN_ROOT:-$(pwd)/.forge}` fallback every command carries.
+
+- **Bootstrap Step 4d — Claude Code assets vendored into `.claude/`.**
+  `agents/` (store-query-validator, tomoshibi) and `skills/` (4 skill dirs).
+
+- **`forge.bundledVersion`** corrected to track the actually-bundled plugin
+  (1.4.0; had drifted at 1.2.21).
+
+### Fixed
+
+- **`composeUpdateKickoff` directive patch** handles both the plugin ≥ 1.4.0
+  `${CLAUDE_PLUGIN_ROOT:-$(pwd)/.forge}` form and the legacy
+  `${CLAUDE_PLUGIN_ROOT}` form when retargeting `update.md`.
+
+## [1.0.29] — 2026-06-07
+
+`4ge init claude` bootstrap repair, round 2 — hook runtime deps (PostToolUse MODULE_NOT_FOUND in 1.0.28).
+
+### Fixed
+
+- **`hooks/lib/` vendored (bootstrap Step 3b + build-payload 2e4).** Hook scripts
+  require `./lib/common.cjs` / `./lib/write-registry.js` at runtime; neither the
+  payload nor the bootstrap shipped `hooks/lib/`, so `validate-write`, `post-init`,
+  and `post-sprint` failed with MODULE_NOT_FOUND on every matching tool call
+  (fail-open, but noisy in the Claude Code UI).
+
+- **`query-logger.cjs` added to `TOOLS_TO_COPY`.** The settings.json PostToolUse:Bash
+  hook points at `.forge/tools/query-logger.cjs`, but the tool was never bundled into
+  the payload — a hard exit-1 hook error on every Bash call in a bootstrapped project.
+
+- **`tools/package.json` CJS scope marker vendored (FORGE-BUG-030 parity).** The
+  bootstrap copy filter (`*.cjs`/`*.js` only) dropped the `{"type":"commonjs"}`
+  marker build-payload writes into `tools/` — vendored `lib/*.js` would resolve as
+  ESM and crash in `"type":"module"` host projects.
+
+## [1.0.28] — 2026-06-07
+
+`4ge init claude` bootstrap repair — vendor hook scripts + schemas (first-field-test regressions in 1.0.27).
+
+### Fixed
+
+- **Bootstrap Step 3b — hook scripts vendored.** `bootstrapClaudeProject()` now copies
+  `payload/hooks/*.cjs` into `.forge/tools/hooks/` — the exact paths the Step 7 settings
+  wiring points at. In 1.0.27 the copy step was missing entirely, so every wired hook
+  (SessionStart, PreToolUse, PostToolUse, PermissionRequest) fired `node` against a
+  nonexistent file and failed with MODULE_NOT_FOUND on session start.
+
+- **Bootstrap Step 3c — schemas vendored.** `payload/schemas/*.json` + `schemas/_defs/`
+  are now copied into `.forge/schemas/` (previously scaffolded empty), per the
+  cli-first-bootstrap ADR ("vendor tools → `.forge/tools/` + schemas").
+
+- **`settings-merge.ts` — query-logger retarget.** `query-logger.cjs` is a tool, not a
+  hook script (plugin `hooks.json` points it at `tools/query-logger.cjs`); the settings
+  block now targets `$CLAUDE_PROJECT_DIR/.forge/tools/query-logger.cjs` instead of the
+  nonexistent `tools/hooks/query-logger.cjs`.
+
+- Bootstrap manifest `steps` now records `vendor-hooks` and `vendor-schemas`.
+
+## [1.0.27] — 2026-06-07
+
+`4ge init claude` — settings hooks wiring, gitignore, preflight, hand-off UX (FORGE-S31-T03).
+
+### Added
+
+- **`settings-merge.ts`** — new `mergeForgeHooks()` + `buildForgeHooksBlock()` module with
+  merge-not-clobber semantics for wiring Forge hooks into project `.claude/settings.json`.
+  Handles 6 branches: absent file (create), empty object (add hooks key), existing without hooks
+  (merge in), unrelated hooks (merge Forge entries without overwriting), already-present (no-op),
+  malformed JSON (error, never overwrites). Fully idempotent: second run returns `"already-present"`.
+
+- **Bootstrap Step 7** — `bootstrapClaudeProject()` now wires Forge hooks into project
+  `.claude/settings.json` via `mergeForgeHooks()`. All 8 hook entries (7 task-workflow hooks +
+  `forge-permissions`) are written with commands pointing at
+  `$CLAUDE_PROJECT_DIR/.forge/tools/hooks/<name>.cjs`. Outcome (`created`/`skipped`/`warnings`)
+  reported in `BootstrapResult` per existing conventions.
+
+- **Bootstrap Step 8** — idempotent `.gitignore` append. Ported `updateGitignore()` from
+  `phase4-register.ts` as a pure standalone function (no `ctx.ui`). If `.gitignore` is present
+  and does not already contain a `.forge/store/events/` parent pattern, appends the standard
+  Forge gitignore block. Skips silently when absent or already covered.
+
+- **Bootstrap Step 9** — preflight check for Claude Code availability (`runPreflight()`). Detects
+  `claude` binary reachability via `execFileSync("claude", ["--version"])`. Non-fatal: adds an
+  actionable warning to `result.warnings` if unavailable, but does not flip `result.ok`. Returns
+  `BootstrapPreflight { claudeAvailable, workflowToolChecked, warnings }` attached to `BootstrapResult`.
+
+- **`BootstrapPreflight` type** — new sub-object on `BootstrapResult` with `claudeAvailable: boolean`,
+  `workflowToolChecked: boolean` (always `false` in T03 — no reliable offline check), and `warnings: string[]`.
+  Additive change — T02 tests remain green.
+
+- **Hand-off UX** — `init.ts` now prints a structured multi-line message naming `/forge:init`,
+  explaining the one-time hooks-approval prompt, and listing all 7 task-workflow hooks by name
+  and event type. Prepends a warning line if Claude Code was not found on PATH.
+
+- **Test suite** — 9-fixture `settings-merge.test.ts` covering all merge branches; 11 new assertions
+  in `bootstrap.test.ts` for Steps 7–9 and idempotency.
+
+## [1.0.26] — 2026-06-07
+
+CLI-first bootstrap: new `4ge init claude [dir]` bin subcommand (FORGE-S31-T02).
+
+### Added
+
+- **`forge init claude [dir]` subcommand** — new bin route that deterministically
+  bootstraps a Claude Code project from the bundled forge-payload in seconds.
+  Zero LLM tokens, zero network access, pure fs. Scaffolds `.forge/` skeleton
+  + store dirs, vendors tools+lib into `.forge/tools/`, installs
+  `.claude/commands/forge/init.md` from payload, and installs all four
+  `.claude/workflows/wfl-*.js` drivers. Writes `.forge/.bootstrap-manifest.json`
+  with payload version and integrity hash. Idempotent repair: a second consecutive
+  run is a byte-identical no-op; partial bootstraps are repaired file-by-file.
+  `.forge/config.json` and `.forge/store/**` are never touched.
+
+- **`src/extensions/forgecli/claude-bootstrap/bootstrap.ts`** — the pure-fs
+  bootstrap module (`bootstrapClaudeProject(opts)`) with clean/partial/complete
+  idempotency, fast-fail payload validation, and structured `BootstrapResult`
+  (created/skipped/warnings). Grep-negative: no fetch/network, no store writes,
+  no sendUserMessage, no ctx.ui.
+
+- **Vitest tests** in
+  `test/extensions/forgecli/claude-bootstrap/bootstrap.test.ts` — 17 tests
+  covering clean / partial / complete (no-op) / non-writable / payload-validation
+  / init.md install / wfl-drivers / grep-negative ACs branches. All integration-
+  style against the real function (no fs mocking).
+
+- **argv.ts**: extended `ForgeAction` union with `"init"`; added `init claude [dir]`
+  parse branch before the fast-path subcommand block.
+
+- **`src/bin/init.ts`** — `parseInitArgs()` + `runInit()` handler following the
+  `runDoctor` / `runUpdate` / `runConfig` structural convention.
+
+- **forge.ts**: wired `forgeAction === "init"` dispatch branch; updated help text.
+
 ## [1.0.25] — 2026-06-06
 
 Coordinated release matching forge plugin **v1.2.21**. Both changes come from

package/README.md

@@ -18,6 +18,8 @@
 
 forge-cli generates a project-specific engineering knowledge base, sprint workflows, agent personas, and an SDLC pipeline — then drives them from your terminal on the [pi-coding-agent] runtime. Model-agnostic. No editor lock-in.
 
+> **Two ways to run Forge.** Drive it headless in your terminal on the pi runtime (this README), **or** scaffold Forge into a Claude Code project with `4ge init claude .` and run the `/forge:*` slash commands inside Claude Code — remove it with `4ge uninstall claude`. The `4ge init` path is the supported way to add Forge to Claude Code and **replaces the deprecated marketplace plugin install** ([why](https://github.com/Entelligentsia/forge#distribution)).
+
 ## Why
 
 - **Structured SDLC, in any terminal.** Plan → implement → review → validate → commit chains, gated by your own personas and audience rules.

package/dist/CHANGELOG-forge-plugin.md

@@ -5,6 +5,270 @@ Format: newest first. Breaking changes are marked **△ Breaking**.
 
 ---
 
+## [1.5.0] — 2026-06-11
+
+Plugin **shim-only sunset release** (FORGE-S32-T07). The stable skillforge
+marketplace channel stops being a parallel distribution mechanism and becomes a
+one-way migration ramp to the CLI-first install (`npm i -g @entelligentsia/forgecli`,
+the `4ge` binary). A plugin user who invokes `/forge:init` (or `/forge:update` /
+`/forge:rebuild`) on v1.5.0 is shown what changed and — with one explicit consent —
+is migrated to the CLI, with project data (`.forge/config.json`, `.forge/store/**`,
+the KB folder) preserved byte-for-byte.
+
+### Added
+- `forge/forge/tools/apply-plugin-shim.cjs` — a **release-branch** shim-overlay
+  generator (sibling of `rewrite-plugin-urls.cjs`). It overlays the
+  `release`-branch `forge/forge/commands/*.md` with two template tiers and
+  regenerates `integrity.json` so `/forge:health` verification still passes:
+  - **Full consent-gated shim** for `init` / `update` / `rebuild`: migration
+    explanation (what is preserved) + node/npm preflight + a **prose-only**,
+    consent-gated `npm i -g @entelligentsia/forgecli && 4ge init claude .` offer
+    (never auto-executed) + a print-only fallback.
+  - **Short redirect notice** for every other command ("retired; run
+    `/forge:init` to migrate").
+  The tool **refuses to apply without `--target release`** (mirrors the
+  `rewrite-plugin-urls` `--target` discipline) — guarding against a destructive
+  run on `main`.
+
+### Changed
+- README and the skillforge marketplace listing read **CLI-first**; the
+  marketplace appears only as a deprecation / migration note naming v1.5.0 as the
+  shim and the following release as the dual-path strip.
+- `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 CLI npm payload is poured from **main** (real T03–T06 commands)
+  while the plugin carries the release-overlay shims. The channel divergence is
+  intentional and gated.
+
+### Notes
+- **Critical channel split:** 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 bundle — shimming main would
+  poison the CLI payload. The canary `forge@forge` channel tracks main and is
+  intentionally **not** shimmed.
+- The dual-path code strip and the retirement of `apply-plugin-shim.cjs` itself
+  are deferred to S34 (mechanical). Non-breaking; installed projects converge on
+  the next `4ge update` / re-bootstrap.
+
+---
+
+## [1.4.13] — 2026-06-11
+
+Command-tree unification (FORGE-S32-T06). The two payload command trees
+(`forge/forge/commands/` and `forge/forge/init/base-pack/commands/`) are
+collapsed into one. `forge/forge/commands/` is now the single source of truth
+for every `/forge:*` command — "which copy wins" is no longer a question.
+
+### Changed
+- Materialized the union into `forge/forge/commands/`: folded in 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`) and
+  overwrote the three collisions (`init`, `check-agent`, `enhance`) with the
+  base-pack winner bytes. Installed `.claude/commands/forge/` is byte-for-byte
+  identical to the prior union output.
+- `payload-manifest.json` carries a single `commands` entry (the
+  `init/base-pack/commands` entry is removed); `bootstrap` copies one directory
+  with no union/collision ordering.
+- Plugin-channel semantic delta: the plugin-served `init`/`check-agent`/
+  `enhance` bytes now match the base-pack winners. The plugin channel is retired
+  at T07.
+
+### Removed
+- Deleted `forge/forge/init/base-pack/commands/` (17 files). `build-base-pack.cjs`
+  no longer regenerates it — the Section-5 command-generation loop and the
+  `expectedFiles` "Commands (16)" block were removed.
+
+---
+
+## [1.4.7] — 2026-06-10
+
+Declarative payload manifest + source-drift check (FORGE-S32-T02). A new
+`payload-manifest.json` at the payload root names every shipped artifact —
+source path (under `forge/forge/`) → bundle path (`dist/forge-payload/`) →
+install destination (bootstrapped project root) → removal owner (uninstall
+grouping) — spec'd by the sibling `schemas/payload-manifest.schema.json`. This
+replaces the implicit contract previously spread across `build-payload.cjs`,
+`bootstrap.ts`, and `uninstall.ts` hand-maintained copy lists that caused the
+FORGE-BUG-030 / FORGE-BUG-036 `MODULE_NOT_FOUND` class.
+
+### Added
+- `tools/check-payload-manifest.cjs` — deterministic, CI-only source-drift
+  check. Exits non-zero on a manifest entry pointing at a missing source, or a
+  file under a recursively-copied payload tree that no manifest entry claims.
+  Wired into `plugin-ci.yml`. Not vendored into project instances
+  (`build-manifest.cjs` `DEV_ONLY_TOOLS` excludes it).
+
+The three forge-cli consumers are rewired to read the manifest in FORGE-S32-T03.
+
+**Regenerate:** none (build/bootstrap infrastructure; not a materialized
+instance artifact).
+
+---
+
+## [1.4.5] — 2026-06-09
+
+Collate-workflow KB-link refresh is orchestrator-owned under forge-cli. The
+generated collate workflow no longer instructs 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 after the writeback phase. Prose-only change to `collator_agent.md`
+(base-pack) and `meta-collate.md`.
+
+**Regenerate:** workflows:collator_agent
+
+> Manual: run `/forge:update` (or `/forge:rebuild`) to regenerate the collate workflow.
+
+---
+
+## [1.4.4] — 2026-06-07
+
+First full CLI-first field test (git.git, ~500 source files) — `/forge:init`
+passed all phases; gap analysis surfaced three config/manifest defects.
+
+### Fixed
+
+- **`paths.commands` config drift** — `phase-1-collect.md` still carried a
+  prefix-derived instruction ("if prefix is `HELLO`, write
+  `.claude/commands/hello`") that survived the 1.4.0 namespace redesign; the
+  config-writer followed it and check-structure reported commands 0/14. The
+  path is ALWAYS `.claude/commands/forge`.
+- **`paths.forgeRoot` written as an absolute npm-global payload path** — no
+  rulebook said what to write, so the register agent improvised. New explicit
+  `generate-tools.md` step: `paths.forgeRoot = ".forge"` (the vendored
+  `.forge/` IS the Forge root; absolute paths break on upgrades/nvm switches).
+- **False "missing tools" gaps (49/59)** — `build-manifest.cjs` now excludes
+  the 10 plugin-development tools (`build-manifest`, `gen-integrity`,
+  `token-forensics`, …) from the `tools` namespace: the structure manifest
+  describes project instances, and dev tools are never vendored.
+  `structure-manifest.json` regenerated; instance expectation is now 49/49.
+
+## [1.4.3] — 2026-06-07
+
+### Fixed
+
+- **`wfl-init.js` Phase 2 verify invocations matched the tool's real CLI**
+  ([forge#112](https://github.com/Entelligentsia/forge/issues/112) follow-up).
+  Prompts said `verify-phase.cjs --phase 2` bare; the tool requires
+  `--phase 2 --kb-path <path>` and exits 2 without it. Both invocations now
+  pass `--kb-path "${kbFolder}"`. Contract gates added: every driver
+  verify-phase invocation must use a supported phase (1–3) and `--phase 2`
+  must carry `--kb-path`.
+
+## [1.4.2] — 2026-06-07
+
+### Fixed
+
+- **`wfl-init.js` ran zero agents but reported fabricated success
+  ([forge#112](https://github.com/Entelligentsia/forge/issues/112)).** Four
+  Workflow-API misuses: `phase(title, callback)` callbacks (containing every
+  phase body) were silently discarded by the harness; `parallel()` received
+  in-flight promises instead of thunks; `agent()` got the model tier as first
+  arg instead of `opts.model`; structured results lacked `opts.schema` so
+  `.ok` reads were undefined. `/forge:init` "completed" in ~3 ms with 0 agents
+  and hardcoded `ok: true`. Phase bodies now run inline, fan-outs use thunks,
+  every agent call is `agent(prompt, { model, label, phase, schema })`, and
+  the final report reflects real phase results (halts return `ok: false` with
+  the failure reason). Rulebook reads use vendored `.forge/init/...` paths
+  with a direct-analysis fallback for absent prompt files. Fix ported from
+  the field-validated patch authored against the live testbench run.
+
+### Added
+
+- **`wfl-drivers-parse.test.cjs` API-contract gates** — all drivers checked
+  for phase-callback misuse, promise-instead-of-thunk `parallel()` calls,
+  reversed `agent()` args, and dead `init/**.md` rulebook references.
+
+## [1.4.1] — 2026-06-07
+
+### Fixed
+
+- **`wfl-init.js` failed to launch — "SyntaxError: Unexpected keyword 'export'".**
+  The driver shipped wrapped in `export default async function wflInit(args)`,
+  but the Workflow harness permits exactly one export (the leading `meta`
+  literal) and evaluates the remainder as an async function body. The body now
+  runs at top level reading the `args` global, matching the other three
+  drivers. Every `/forge:init` → `workflow('wfl:init')` dispatch was dead on
+  arrival before this fix.
+
+### Added
+
+- **`wfl-drivers-parse.test.cjs`** — regression gate that parses all base-pack
+  `wfl-*.js` drivers exactly the way the Workflow harness does (single meta
+  export, body as async function body with workflow globals in scope).
+
+## [1.4.0] — 2026-06-07
+
+### Changed — △ Breaking
+
+- **Fixed `/forge:*` command namespace (CLI-first redesign).** Project-prefix
+  command namespaces (`/acme:*`, `/hello:*`) are retired — every project gets
+  the same `/forge:*` surface, with full parity between Claude Code and the
+  pure CLI (`4ge`):
+  - `tools/lib/paths.cjs` — `getCommandsSubdir()` returns `'forge'`
+    unconditionally (prefix arg is vestigial, kept for caller compat).
+  - `init/base-pack/commands/*.md` — `/{{PREFIX}}:` → literal `/forge:`
+    (26 occurrences, 17 files). Command templates are now fully static.
+  - `tools/substitute-placeholders.cjs` — materializes commands to
+    `.claude/commands/forge/` regardless of project prefix.
+  - Rulebooks updated: `generate-commands.md`, `phase-3-materialize.md`,
+    `phase-1-collect.md` (config `paths.commands` example), `meta-migrate.md`,
+    `migrate_structural.md`, `commands/add-task.md` next-steps text.
+  - The prefix-derived namespace existed to avoid collisions with the Forge
+    *plugin's* own `/forge:*` commands — moot now that the plugin mechanism
+    is retired in favour of project-vendored commands.
+  - **Migration:** existing projects keep working with their old
+    `.claude/commands/<prefix>/` files; re-materialize to get
+    `.claude/commands/forge/`, then delete the prefix directory.
+
+- **`FORGE_ROOT` vendored fallback in every command.** All 33 resolution
+  lines across `commands/*.md` and `init/base-pack/commands/*.md` change from
+  `${CLAUDE_PLUGIN_ROOT}` to `${CLAUDE_PLUGIN_ROOT:-$(pwd)/.forge}` — in a
+  plugin-installed session the plugin root still wins; in a plugin-less
+  project bootstrapped by `4ge init claude` the vendored `.forge/` (tools,
+  schemas, hooks, init, meta) serves as the Forge root.
+
+## [1.3.0] — 2026-06-07
+
+### Added
+
+- **`init/base-pack/commands/init.md`** — new project-local command wrapper
+  installed by `4ge init claude .` into `.claude/commands/forge/`. Contains
+  the full hoisted-prompt flow (KB folder prompt, CLAUDE.md offer, timestamp
+  minting), dispatches `workflow('wfl:init', args)`, handles the
+  Workflow-tool-missing error explicitly, presents the marketplace-skills offer
+  from `result.skillMatches` post-workflow, invokes `forge:refresh-kb-links`
+  via the Skill tool, and emits the final report (KB doc count, workflow count,
+  command count, accepted/skipped skills). Uses vendored `.forge/tools/` paths
+  only — no `$FORGE_ROOT` / `${CLAUDE_PLUGIN_ROOT}` references.
+
+### Changed
+
+- **`commands/init.md` (plugin-side)** — Execute section rewritten to dispatch
+  `workflow('wfl:init', args)` with hoisted interactive prompts (KB folder
+  prompt, CLAUDE.md offer, timestamp minting). Replaces the previous
+  `Read $FORGE_ROOT/init/sdlc-init.md` instruction. Includes the explicit
+  Workflow-tool-missing error halt (Iron Law 5 — no silent degradation or
+  fallback to `sdlc-init.md`).
+
+- **`init/phases/phase-1-collect.md`** — Pre-flight Knowledge Base Folder block
+  and Step 5 (Marketplace Skills) annotated as orchestrator-owned when the
+  orchestrator pre-supplies the values. Annotations are informational — no step
+  renames or renumbers (forge-cli `run-phases.ts` glob freeze maintained).
+
+- **`init/phases/phase-4-register.md`** — Step 11 (Tomoshibi/refresh-kb-links)
+  and Step 13 (CLAUDE.md prompt) annotated as orchestrator-owned. Same
+  semantics-preserving annotation policy.
+
+- **`init/sdlc-init.md`** — Body reduced to a spec-pointer paragraph: points
+  to `wfl-init.js` (orchestration), `commands/init.md` (dispatch surface), and
+  `init/phases/` (canonical per-phase contracts). Phase/verify table preserved
+  for human readers. File not deleted.
+
+---
+
 ## [1.2.21] — 2026-06-06
 
 ### Fixed