@entelligentsia/forgecli 1.0.10 → 1.0.20

package/CHANGELOG.md

@@ -7,6 +7,197 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 
 ## [Unreleased]
 
+## [1.0.20] — 2026-06-04
+
+Release roll-up of the post-S30 stabilization train (1.0.15–1.0.19) plus the
+dashboard/status-bar TUI pass. Pairs with forge plugin **v1.2.17**.
+
+### Fixed
+
+- **Status-bar/dashboard TUI pass** (Iron-Laws compliance follow-ups):
+  Focusable/theming/width-safety/timer guards and consolidated entry;
+  ↑/Esc deactivation via the input router with ○ focus indicator;
+  ○/● colour carries node status (accent=running, success=completed,
+  error=failed); spinner shows activity without a redundant node glyph.
+
+## [1.0.19] — 2026-06-04
+
+### Changed
+
+- **Halt-advisor model = the heavy model the runtime resolves point-in-time —
+  the `advisorModel` config entry is removed.** Supersedes the 1.0.18 advisor
+  resolution. There is no dedicated knob: "heavy" is the approve/architect
+  slot resolved through the existing routing cascade (L4 phase override →
+  project → user/global → default), exactly as the approve phase itself would
+  resolve; when the cascade bottoms out at inherit, the session's current
+  model (pi default) is used. This mirrors the Claude Code plugin route, where
+  the advisor runs on the opus-class session model. The `advisorModel` key is
+  dropped from `GlobalConfig`/`ProjectConfig`/`MergedConfig`, the config
+  merge, and `forge-cli-schema.json` (it was never exposed in `/forge:config`
+  and never set in practice).
+
+## [1.0.18] — 2026-06-04
+
+Coordinated release matching forge plugin **v1.2.17** (postflight-gate
+false-halt fixes). Bundles the dashboard Iron-Laws compliance pass
+(Focusable, theming, width-safety, timer guards, consolidated entry).
+
+### Fixed
+
+- **Halt advisor no longer runs on `anthropic/undefined`.** pi's
+  `ModelRegistry.getAvailable()` returns Model objects whose identifier is
+  `.id`, not `.model`; the blind `available[0] as PersonaModel` cast produced
+  `{ provider, model: undefined }` and the advisor dispatched against a
+  nonexistent model (observed on the CART-S03-T01 halt). `resolveAdvisorModel`
+  now maps both shapes, skips entries without a usable identifier, and —
+  before falling back to the registry at all — prefers the **session's
+  current model**, which is provider-neutral and known-good. Config
+  `advisorModel` slot still wins when set.
+
+## [1.0.17] — 2026-06-04
+
+### Fixed
+
+- **Context-governor dedup hardening — reads-only, error-aware, re-queryable.**
+  CART-S02-T04 transcripts surfaced three Rule-1 defects:
+  1. *Write masking (serious):* the dedup key carried no read/write
+     distinction, so a `forge_artifact` WRITE confirmation was replaced by a
+     pointer registered by an earlier READ of the same path — a failed write
+     would have been silently masked. Dedup now applies only to read-like
+     commands (`read`/`get*`/`list`/`describe`/`template`); every mutation
+     result passes through verbatim, and the command participates in the key
+     (read vs list never conflate).
+  2. *Impossible re-query:* the pointer said "re-query if needed", but every
+     re-query of the same key returned another pointer — agents responded by
+     switching to bash `cat` workarounds (wasted turns, path-guess errors).
+     Pointers now ALTERNATE: served at most once in a row, the immediately
+     repeated call is honoured with full (still trimmed/clamped) content.
+     Wording updated to "call again to re-fetch".
+  3. *Error interaction:* errored results were registered and replaced by
+     pointers. Error results now bypass all curation — never registered,
+     never replaced, always verbatim.
+
+## [1.0.16] — 2026-06-03
+
+Coordinated release matching forge plugin **v1.2.15**.
+
+### Fixed
+
+- **Zero-usage "husk" turns no longer corrupt phase telemetry.** Failed/retry
+  turns emit assistant messages with all-zero usage; the accumulator in
+  `forge-subagent.ts` counted them as turns and — because
+  `usage.totalTokens ?? prev` treats `0` as non-nullish — overwrote the
+  running `contextTokens` with 0, which is why every aborted phase transcript
+  reported `contextTokens: 0`. Husk turns are now excluded from `turns` and
+  the context figure only updates on a positive total.
+
+- **Incomplete (cancelled/failed) phase attempts now emit their billed
+  tokens.** The cancel and halt-on-failure branches in `run-task.ts` and
+  `fix-bug.ts` returned without emitting a phase event, so the provider-billed
+  tokens of aborted attempts never reached the store — collate's COST_REPORT
+  under-counted real spend (CART-S02-T03 baseline: 259,950 tokens invisible
+  across two aborted plan passes). New `emitIncompletePhaseEvent` helper emits
+  the canonical phase event with `verdict: "aborted"` (cancel) /
+  `"failed"` (halt) and the captured partial usage; zero-token attempts are
+  skipped (no husk noise). Pairs with forge plugin v1.2.15, whose COST_REPORT
+  gains an **Incomplete Passes** section.
+
+## [1.0.15] — 2026-06-03
+
+### Fixed
+
+- **forge-compress savings prints no longer corrupt the `/forge:dashboard`
+  TUI.** `compressWithTelemetry` (forge-tools.ts) and the `forge_artifact`
+  read path wrote dim `[forge-compress] N→M tok (X% saved)` lines straight to
+  stderr — raw ANSI under an active TUI overlay garbles the screen. The prints
+  were redundant: the same stats already flow through tool-result
+  `details.compression` → viewport-events → session-registry/orchestrator-tree
+  → the dashboard's aggregate `⇌Nt` savings suffix. Removed both stderr writes;
+  the dashboard remains the single surface for compression savings.
+
+- **Context governor was dormant in production — Mechanisms A–D never reached
+  phase subagent sessions.** Benchmarking CART-S02-T03 under
+  `FORGE_CTX_GOVERNOR=1` showed zero curation markers and no token reduction.
+  Three wiring defects, all in the FORGE-S30-T07 integration layer (the
+  mechanisms themselves were correct):
+  1. `registerHookDispatcher(pi, …, governor)` in `index.ts` only governs the
+     **parent** session; every phase runs in an isolated `createAgentSession`
+     subagent the parent's hooks never see.
+  2. `resolvePhaseKey` probed `ctx.persona`/`ctx.phase`, which pi never
+     populates (and `FORGE_PHASE_KEY` is read but never set) — so every phase
+     resolved the inert `default` policy.
+  3. The policy table only shipped `architect/plan` and `engineer/review`,
+     matching **no** real `${personaNoun}/${role}` pipeline key; and
+     `createGovernor` was constructed without `steerFn`/`summarySentinel`/
+     `compactFn`, leaving Mechanism B steer, Mechanism C shed, and the
+     Mechanism E proactive trigger unreachable.
+
+  Fix: new `buildGovernorFactory({ phaseKey, cwd })` (`context-governor.ts`)
+  is constructed **per phase** by `run-task.ts` — which knows the
+  `${personaNoun}/${role}` key — and injected into each subagent session via
+  `extensionFactories`, alongside a `buildForgeCompactionFactory` now carrying
+  warm-tier path opts (`cwd`/`phaseKey`/`entityId`/`sprintId` — previously
+  threaded from `index.ts` with no opts, so warm-tier merge was dead). The
+  factory wires `steerFn` → `pi.sendUserMessage(…, { deliverAs: "steer" })`,
+  `summarySentinel` → read-only `.forge/store/{tasks,bugs}/<id>.json`
+  `summaries[<phase>]` probe, and `compactFn` → `ctx.compact()`. The policy
+  table now ships entries for all six governed pipeline keys (`engineer/plan`,
+  `supervisor/review-plan`, `engineer/implement`, `supervisor/review-code`,
+  `qa-engineer/validate`, `architect/approve`) with `read` budgets kept more
+  generous than `bash` so file reads aren't over-clamped; `writeback`/`commit`
+  stay on `default`. Flag-gating is unchanged (`FORGE_CTX_GOVERNOR=1`), and
+  `registerRunTask`/`registerRunSprint` keep `extensionFactories` as a test
+  seam.
+
+## [1.0.14] — 2026-06-03
+
+Coordinated release matching forge plugin **v1.2.14**.
+
+### Fixed
+
+- **A missing verdict now routes through the halt-recovery advisor instead of a
+  bare escalation.** In `run-task.ts` (and `fix-bug.ts`) the review-phase
+  `verdict === "missing"` branch early-returned `status:"failed"` with a raw
+  *"Escalating"* notify **before** reaching the postflight-gate → `runHaltAdvisor`
+  hand-off — so a subagent that completed but failed to write its phase summary
+  surfaced as an undiagnosed halt. Review-phase workflows declare no `outputs`
+  block, so the postflight gate is a pass-through for them and the `readVerdict`
+  check is the effective gate. The branch now synthesizes a `GateFailureData`
+  (`reasonCode: "verdict-missing"`) and invokes `runHaltAdvisor` (the same path
+  the gate-failure branches use), returning `"halted"`, so the strongest
+  configured model diagnoses the missing-summary cause. Best-effort, non-fatal.
+  Regression test added (`run-task.test.ts` Test 1d).
+
+## [1.0.11] — 2026-06-03
+
+Coordinated release matching forge plugin **v1.2.7** (FORGE-S29 vendored-tools
+sprint — retire FORGE_ROOT via vendored `.forge/tools/`).
+
+### Added
+
+- **`forge:rebuild tools` handler (`runRebuildTools`)** — copies bundled tools
+  (`*.cjs`, `lib/`) from the forge-cli payload into `.forge/tools/` of the
+  target project. Accepts optional `singleTool` for sub-target re-copy.
+  Tested in `test/extensions/forgecli/regenerate.test.ts`.
+- **`forge:rebuild tools` wired in `phase4-register.ts`** — `tools` category
+  registered in the rebuild handler; single-tool sub-targets pass through as
+  `singleTool`.
+- **`migration-engine.ts` `regenerate:tools`** — `applyRegenerate` now handles
+  the `tools` category by delegating to `runRebuildTools`; migrations that
+  include `regenerate:["tools"]` (introduced in plugin v1.2.3–v1.2.7) are
+  applied automatically.
+- **`project-orientation.ts` tools-version check** — `checkForgeTools` added;
+  reads `.forge/tools/.forge-tools-version` and reports stale/absent state so
+  `forge:health` can surface the vendored-tools staleness check (mirrors
+  plugin-side check introduced in v1.2.5).
+- **`tmp-smoke.sh` E2E-T05-TOOLS-VENDORED gate** — new smoke assertion
+  confirms `.forge/tools/` is populated (`.forge-tools-version` marker present)
+  after `/forge:init` runs with the v1.2.x+ plugin.
+
+### Changed
+
+- `forge-subagent.ts` — minor hardening (no observable behaviour change).
+
 ## [1.0.10] — 2026-05-31
 
 Coordinated release matching forge plugin **v1.0.10** (the issue #111

package/dist/CHANGELOG-forge-plugin.md

@@ -5,6 +5,217 @@ Format: newest first. Breaking changes are marked **△ Breaking**.
 
 ---
 
+## [1.2.17] — 2026-06-04
+
+### Fixed
+
+- **Postflight output guard no longer false-halts every phase.** The S26-T19
+  guards were dormant until the v1.2.16 base-pack recompile activated them;
+  their first live firing halted CART-S03-T01's plan phase despite full
+  success. Two deterministic bugs in `postflight-gate.cjs`:
+  1. *Require predicates never resolved* — the outputs blocks use bare record
+     paths (`summaries.plan.verdict`) while the CLI passes
+     `state = { task: record }`; every bare require read `undefined` and
+     failed unconditionally. `readField` now falls back to the entity record
+     (`state.task` / `state.bug`) after the direct walk.
+  2. *Artifact paths missed the `sprints/` segment* — `{sprint}` was
+     substituted with the bare sprintId, probing
+     `<engineering>/<sprintId>/<taskId>` instead of the canonical
+     `<engineering>/sprints/<sprintId>/<taskId>`. New `buildSubstitutions()`
+     resolves `{sprint}` to the path segment under engineering
+     (`sprints/<id>` for tasks, `bugs` for bug records).
+
+---
+
+## [1.2.16] — 2026-06-04
+
+### Fixed
+
+- **Review/validate phases no longer self-limit on iteration count**
+  ([forge-engineering#34](https://github.com/Entelligentsia/forge-engineering/issues/34)).
+  The standalone-invocation fallback in `review_plan` / `review_code` /
+  `validate_task` read `maxReviewIterations` from `.forge/config.json` —
+  producing a *"Key not found"* error on every review phase and, worse,
+  duplicating a protection the orchestrator already owns. Loop budgeting and
+  termination are solely the orchestrator's job (`run-task` enforces
+  `maxIterations` deterministically; exhaustion escalates to a human), and a
+  deliberate human standalone re-run **is** the escape hatch for stuck items —
+  a phase consulting its own cap could refuse exactly that recovery. Workflows
+  now treat user-invoked runs as iteration 1 with no limit and never read an
+  iteration cap from config; orchestrated runs continue to take `N of M` from
+  the orchestrator-injected Review Loop Context block. Prompt-text only.
+
+---
+
+## [1.2.15] — 2026-06-03
+
+### Fixed
+
+- **COST_REPORT now accounts incomplete (aborted/failed) phase attempts.**
+  Cancelled and halted phase attempts bill real provider tokens, but their
+  events arrived as token-less husks — the CART-S02-T03 benchmark baseline
+  under-counted by exactly 259,950 tokens across two aborted plan passes.
+  forge-cli ≥1.0.16 now emits phase events with `verdict: "aborted"` (user
+  cancel) / `"failed"` (halt-on-failure) carrying the captured partial usage;
+  `collate.cjs` adds an **Incomplete Passes** section to COST_REPORT (task,
+  phase, outcome, tokens per attempt). Per-Task / Per-Role / Model-Split
+  totals sum verdict-agnostically, so the previously-invisible spend lands in
+  the totals automatically once events arrive. Report-layer only — no schema
+  change (`verdict` was already a free-string event field); older forge-cli
+  versions simply produce no incomplete-pass events.
+
+---
+
+## [1.2.14] — 2026-06-03
+
+### Fixed
+
+- **Corrected the `set-summary` / `set-bug-summary` call signature in the review and triage workflows.** `meta-review-implementation.md`, `meta-review-plan.md`, and `meta-bug-triage.md` documented a `forge_store` invocation with named `entity`/`id`/`phase` fields — `forge_store({ command:"set-summary", entity:"task", id:"{taskId}", phase:"code_review" })` — but the `forge_store` tool schema accepts only `{ command, args[] }`. Handed a signature that does not exist, subagents mis-built `args` and landed the record id in the phase slot; the phase-ownership guard rejected it (`expected summary key 'code_review'`), `summaries.code_review` was never written, and the orchestrator halted the task as *"verdict missing"*. All sites now use the canonical positional form `forge_store({ command:"set-summary", args:["{taskId}", "code_review"] })` plus a one-line signature reminder; `_fragments/store-cli-verbs.md` now documents the `forge_store { command, args[] }` shape and the "id in both slots" failure. Also fixed a `forge_store read` call in `meta-bug-triage.md` that used the same invalid named form. Prompt-text only — no tool or schema change.
+
+**Regenerate:** workflows:review_code workflows:review_plan workflows:bug-triage
+
+> Manual: Run `/forge:update`, then `/forge:rebuild workflows` to refresh `.forge/workflows/`.
+
+---
+
+## [1.2.3] — 2026-06-02
+
+### Fixed
+
+- **Hardened `FORGE_ROOT` / `.forge/config.json` resolution in the packaged JS workflow drivers.** A friction trace of a real `/fix-bug` run found phase subagents systematically probing `../.forge/config.json` (the **parent** directory — 5 of 11 subagents, blocked as "path escapes project root") and one invoking the preflight gate with an unexported `$FORGE_ROOT` that expanded to `''` → `Cannot find module '/tools/preflight-gate.cjs'`. Root cause: the per-phase subagent preamble said only *"Resolve FORGE_ROOT from .forge/config.json paths.forgeRoot"* — no cwd anchor, and no instruction to **export** `$FORGE_ROOT`, even though every command used it as a shell variable. Replaced all ~23 preamble sites across `wfl-run-task.js` / `wfl-run-sprint.js` / `wfl-fix-bug.js` with a directive that (a) anchors the config to `./.forge/config.json` in the current working directory ("never a parent directory"), (b) tells the agent to **export** `FORGE_ROOT`, and (c) STOPs if `$FORGE_ROOT` is empty or `$FORGE_ROOT/tools` is missing. Added a regression guard in `workflows-js-drift.test.cjs`. Prompt-text only — no orchestration-logic change.
+
+**Regenerate:** workflows-js:wfl-run-task, workflows-js:wfl-run-sprint, workflows-js:wfl-fix-bug
+
+> Manual: Run `/forge:update`, then `/forge:rebuild workflows-js` to refresh `.claude/workflows/wfl-*.js`.
+
+---
+
+## [1.2.2] — 2026-06-02
+
+### Fixed
+
+Three orchestration-logic edge-case bugs in the packaged JS workflow drivers, found by an adversarial review of the v1.2.1 packaged workflows (all are runtime-only — `node --check` and shape tests can't catch them):
+
+- **`wfl-run-sprint.js` — re-dispatch passed an unhonored `resumeFrom`.** The respawn guard called `workflow('wfl:run-task', { taskId, resumeFrom })`, but `wfl:run-task` parses only the task id, so `resumeFrom` was silently dropped. Removed the misleading arg and corrected the comment/log: the retry is a clean re-dispatch that resumes from the task's store state (completed phases are skipped by their pre-flight gates).
+- **`wfl-run-sprint.js` — `blocked` tasks were force-escalated.** A skipped child (`{skipped, taskStatus}`) was treated as non-terminal unless its status was in `{committed, abandoned, escalated}`, so a legitimately `blocked` task (waiting on a dependency) was re-dispatched and then escalated after two no-op attempts. A skipped child is now terminal-acceptable regardless of `taskStatus`.
+- **`wfl-fix-bug.js` — finalize null-dispatch reported a clean fix.** The finalize dispatch had no null guard, so a skipped/errored finalize (`agent()` returns `null`) fell through `finalizeResult?.escalated` and the run returned `bugStatus:'fixed', escalated:false` even though collate + the finalize gate never ran. It now escalates on a null finalize while preserving `bugStatus:'fixed'` (commit already wrote it).
+
+Added text-contract regression guards in `workflows-js-drift.test.cjs`. Deferred to a follow-up (filed for triage): revision-counter/eventId attribution (`wfl-run-task`), count-bucket taxonomy + `full-parallel` dependency ordering (`wfl-run-sprint`), and two MINORs in `wfl-fix-bug` (`phase('Pipeline')` grouping, `escalateBug` `bugId`).
+
+**Regenerate:** workflows-js:wfl-run-sprint, workflows-js:wfl-fix-bug
+
+> Manual: Run `/forge:update`, then `/forge:rebuild workflows-js` to refresh `.claude/workflows/wfl-run-sprint.js` and `wfl-fix-bug.js`.
+
+---
+
+## [1.2.1] — 2026-06-02
+
+### Fixed
+
+- **`wfl-fix-bug.js` could never launch — invalid meta.** The fix-bug JS driver declared its meta with `desc:` and `steps:` instead of `description:` and `phases:`. The Workflow runtime rejects a missing/empty `meta.description` (`"meta.description must be a non-empty string"`), and the named-workflow registry silently skipped it — so `/forge:fix-bug` (and any `/<prefix>:fix-bug`) dispatched `workflow('wfl:fix-bug', …)` to a workflow that wasn't registered. This shipped latent since the driver was authored and was exposed by the v1.2.0 prose retirement (which removed the `fix_bug.md` fallback). Renamed `desc → description` and `steps → phases` (with a `Resolve` phase) to match `wfl-run-task.js` / `wfl-run-sprint.js`. Added a meta-contract regression guard in `workflows-js-drift.test.cjs` asserting every JS driver exposes `name` + non-empty `description` + `phases`.
+
+**Regenerate:** workflows-js:wfl-fix-bug
+
+> Manual: Run `/forge:update`, then `/forge:rebuild workflows-js` to refresh `.claude/workflows/wfl-fix-bug.js`. `/<prefix>:fix-bug` then launches `wfl:fix-bug` correctly.
+
+---
+
+## [1.2.0] — 2026-06-02
+
+### Changed
+
+- **Retired LLM orchestration prose — the JS drivers are the only truth.** The deterministic JS orchestrators (`.claude/workflows/wfl-run-task.js`, `wfl-run-sprint.js`, `wfl-fix-bug.js` — category `workflows-js`) fully replace the prose workflows `orchestrate_task.md`, `run_sprint.md`, and `fix_bug.md`. `/forge:run-task`, `/forge:run-sprint`, and `/forge:fix-bug` already dispatch to them via `workflow(wfl:*)`. The three prose orchestrators are no longer built into the base-pack, no longer generated into `.forge/workflows/`, and no longer tested:
+  - `build-base-pack.cjs` and `build-manifest.cjs` drop the three workflow mappings (`structure-manifest.json` / `enum-catalog.json` regenerated).
+  - `workflow-gen-plan.json` goes 16 → 15 entries (drops `fix_bug`).
+  - The `/forge:rebuild` orchestration-generation step and the `generate-orchestration.md` rulebook are removed; the base-pack `workflows/{orchestrate_task,run_sprint,fix_bug}.md` files are deleted.
+  - The `orchestrators-retired` and `orchestrator-base-pack-parity` drift tests are removed; `base-pack-byte-budget`, `build-base-pack`, `build-manifest`, and `placeholder-coverage` tests updated to the new counts. Only the JS drivers (`wfl-*` tests + `workflows-js-drift`) are tested.
+  - `meta-orchestrate.md` and `meta-fix-bug.md` are **kept in `meta/`** as reference specs only — not built, not generated, not tested.
+
+**Regenerate:** workflows, workflows-js
+
+> Manual: Run `/forge:update` — its `delete-workflow` scan removes the retired `orchestrate_task.md` / `run_sprint.md` / `fix_bug.md` orphans from `.forge/workflows/` (prompting before deleting any you have hand-edited). `/forge:rebuild` only regenerates and clears manifest entries; it does **not** delete files on disk. Orchestration runs through `.claude/workflows/wfl-*.js` — no other action needed.
+
+---
+
+## [1.1.2] — 2026-06-02
+
+### Fixed
+
+- **`collate.cjs` silently skipped task `INDEX.md` when a task's store `path` pointed at a file.** `resolveTaskDir` Case 1 returned `basename(task.path)` assuming `path` was the task *directory*. For records whose `path` pointed at a file inside the dir (e.g. `.../FORGE-S22-T04/PLAN.md`), it returned `PLAN.md`; the downstream `existsSync(sprintDir/PLAN.md)` check then failed and the task's `INDEX.md` was never written. Symptom: 18 task `INDEX.md` files across FORGE-S22/S23 were missing despite valid store records. Case 1 now verifies its candidate resolves to a real directory on disk and otherwise falls through to the filesystem scan, which resolves the dir by `taskId`. Two regression tests added.
+
+**Regenerate:** tools:collate
+
+> Manual: After `/forge:update`, run `/forge:collate` (or `/forge:rebuild`) to regenerate any task `INDEX.md` files that were previously skipped.
+
+---
+
+## [1.1.1] — 2026-06-02
+
+### Changed
+
+- **`wfl-run-task.js` LOW-polish orchestration parity (FORGE-S28-T09).** Five low-severity gaps addressed:
+  - **#19 `task_skipped` event.** `emitSkip()` agent helper added. When the pre-task SKIP_STATUS guard fires (task is `blocked`, `escalated`, `committed`, or `abandoned`), the driver now emits a `task-dispatch/action:skip` event so downstream collators have a complete per-task accounting.
+  - **#20 `writeback` in default pipeline.** The hardcoded default pipeline prompt in the resolve-agent now includes `writeback` (mapping to `update_implementation.md`) between `approve` and `commit`, matching the full `orchestrate_task.md §3` default.
+  - **#21 Progress-Monitor IPC documented as structural limitation.** A comment in the `SIDE-EFFECT OWNERSHIP` section explains that IPC with a Progress-Monitor is a host-layer concern (the Pi/forge-cli TS layer must open the pipe before spawning the Workflow tool); no implementation in the JS driver is possible or correct.
+  - **#22 `BANNER_MAP` constant.** Both `wfl-run-task.js` and `wfl-run-sprint.js` gain a `BANNER_MAP` constant mapping roles/phases to persona banner labels. The `wfl-run-task` phase-start log line now emits `[forge-architect]` / `[forge-engineer]` / `[forge-validator]` for visual phase identity.
+  - **#24 already complete** — orchestrator-side eventId composition was wired in T05 (Gap #14). No further change.
+
+- **`wfl-run-sprint.js` LOW-polish orchestration parity (FORGE-S28-T09).**
+  - **#22 `BANNER_MAP` constant** — as above.
+  - **#23 sprint→`active` before wave loop.** An agent step is added between the sprint-start event and `phase('Execute')` to call `store-cli update-status sprint <id> active`, mirroring `run_sprint.md Step 1`. Without this the sprint stayed in `planned` status during execution.
+
+### Fixed
+
+- **`forge/package.json` no-npm-packages test regression.** An accidental `"dependencies"` field referencing a local `@entelligentsia/forgecli` tgz had been left in `forge/package.json`, causing one failing test in the `placeholder-coverage` suite. Removed.
+
+**Regenerate:** `workflows-js:wfl-run-task`, `workflows-js:wfl-run-sprint`
+
+> Manual: run `/forge:update` then `/forge:rebuild workflows-js` to refresh `.claude/workflows/wfl-*.js`.
+
+---
+
+## [1.1.0] — 2026-06-02
+
+### Added
+
+- **`workflows-js` is now a first-class rebuild/update target.** The JS orchestration workflows under `.claude/workflows/` (`wfl-run-task.js`, `wfl-run-sprint.js`, `wfl-fix-bug.js`) are verbatim copies from the plugin base-pack, but were previously materialized **only** at `/forge:init` time — there was no `/forge:rebuild` or `/forge:update` path to refresh them, so fixes to a base-pack JS workflow could not reach existing installs. `/forge:rebuild workflows-js` (and the granular `workflows-js:wfl-run-task` sub-target) now performs a deterministic verbatim copy + manifest record, `/forge:update` recognises `workflows-js` as a regenerate target, and `build-manifest.cjs` declares a `workflows-js` namespace so `/forge:health` / `check-structure` cover these files. Modeled on the existing `workflows:_fragments` verbatim-copy pattern — no LLM, no placeholder substitution.
+
+  **Regenerate:** `workflows-js:wfl-run-task`
+
+### Fixed
+
+- **FORGE-BUG-041 — `wfl-run-task.js` registered an invalid `StructuredOutput` schema, escalating every task.** `emitRetryEvent` and `mergeSidecar` passed `schema: { type: 'string' }` to `agent()`. The workflow runtime registers the `StructuredOutput` tool using that schema as its `input_schema`, but the Anthropic API rejects any tool whose `input_schema.type` is not `'object'` (HTTP 400). The subagent could therefore never call `StructuredOutput`, and the workflow threw after the nudge limit. Because `mergeSidecar` runs after every phase's complete event, each `wfl:run-task` task succeeded its plan phase then died at the post-phase sidecar merge — so every task in a `wfl:run-sprint` run escalated immediately after planning. Fixed by dropping the invalid `schema` option from both calls (their return value is discarded; this matches the sibling schemaless task-dispatch emit agent). Added a regression guard to `wfl-run-task-parity.test.cjs`. The `workflows-js` rebuild wiring above lets `/forge:update` auto-deliver this fix to existing installs.
+
+---
+
+## [1.0.11] — 2026-05-31
+
+### Added
+
+- **`forge-preflight.cjs` — aggregated pre-dispatch glue tool (A1).** Consolidates all deterministic pre-dispatch checks (entity read, status gate, sprint context, persona load) into a single blob read, eliminating ~20 hand-run tool round-trips from the orchestrator preamble. The orchestrator now opens every task with a single `forge-preflight --task <id>` call and gets a structured blob covering status, sprint context, dependency chain, and persona directive.
+
+- **`preflight-session.cjs` — SessionStart hook pre-warming (A1).** New hook wired into `hooks.json` that runs on session start for `run-task`, `fix-bug`, and `run-sprint` contexts. Pre-warms the preflight blob so the first call into the orchestrator arrives with context already loaded; fails open (no-op) when `.forge/` is absent.
+
+- **`token-forensics.cjs` — message.id dedup harness (NH2).** Stand-alone diagnostic tool for correct through-model token accounting. Deduplicates by `message.id` to prevent double-counting when the same API response appears in multiple cost-reporting paths.
+
+### Changed
+
+- **`banners.cjs` gains `--quiet` flag; `orchestrate_task` loop uses it (A3).** Verbose banner output no longer accretes in the transcript across the orchestration loop. Passing `--quiet` suppresses the decorative banner sections; the orchestrator loop now calls `banners --quiet` by default.
+
+- **`meta-orchestrate.md` state-ledger compaction discipline (A4).** `/compact` is now instructed to retain the one-line `[checkpoint]` ledger entry and shed raw tool output. Prevents state-ledger loss during long orchestration sessions.
+
+- **`meta-fix-bug.md` preflight and digest treatment ported from orchestrate_task (NH1).** A1 preflight cross-reference, A3 `--quiet` flag treatment, and spurious cost-bullet removal applied to the bug-fix workflow glue so fix-bug sessions receive the same waste-reduction treatment as run-task sessions.
+
+### Not shipped in this release
+
+- **A2 (context-pack / forge-compress port)** — escalated; not included. Users will not receive the context-pack or persona-pack build changes in this release. A2 remains open for a follow-on sprint.
+
+**Regenerate:** tools:forge-preflight, hooks:preflight-session, workflows:orchestrate_task, workflows:fix_bug, tools:banners, tools:token-forensics
+
+> Manual: run `/forge:update` to copy the updated tools and hooks into your project.
+
+---
+
 ## [1.0.10] — 2026-05-31
 
 ### Changed

package/dist/extensions/forgecli/config-layer.js.map

@@ -1 +1 @@
-{"version":3,"file":"config-layer.js","sourceRoot":"","sources":["../../../src/extensions/forgecli/config-layer.ts"],"names":[],"mappings":"AAAA,OAAO,KAAK,EAAE,MAAM,SAAS,CAAC;AAC9B,OAAO,SAAS,MAAM,KAAK,CAAC;AAC5B,OAAO,MAAM,MAAM,yBAAyB,CAAC,OAAO,IAAI,EAAE,MAAM,EAAE,CAAC;AACnE,OAAO,EAAE,mBAAmB,EAAE,oBAAoB,EAAE,MAAM,kBAAkB,CAAC;AAE7E,4DAA4D;AAC5D,wDAAwD;AACxD,MAAM,GAAG,GAAI,SAAiB,CAAC,OAAO,EAAE,GAAG,IAAK,SAAiB,CAAC,GAAG,IAAI,SAAS,CAAC;AAiEnF,MAAM,GAAG,GAAG,IAAI,GAAG,CAAC,EAAE,SAAS,EAAE,IAAI,EAAE,CAAC,CAAC;AACzC,MAAM,QAAQ,GAAG,GAAG,CAAC,OAAO,CAAC,MAAM,CAAC,CAAC;AAErC,SAAS,cAAc,CACtB,GAAY,EACZ,KAAa;IAEb,MAAM,EAAE,GAAG,QAAQ,CAAC,GAAG,CAAC,CAAC;IACzB,IAAI,CAAC,EAAE,EAAE,CAAC;QACT,MAAM,QAAQ,GACb,QAAQ,CAAC,MAAM;YACd,EAAE,GAAG,CAAC,CAAC,CAA8C,EAAE,EAAE,CAAC,GAAG,CAAC,CAAC,YAAY,IAAI,GAAG,IAAI,CAAC,CAAC,OAAO,EAAE,CAAC;aACjG,IAAI,CAAC,IAAI,CAAC,IAAI,SAAS,CAAC;QAC3B,OAAO,EAAE,KAAK,EAAE,KAAK,EAAE,KAAK,EAAE,aAAa,KAAK,yBAAyB,QAAQ,EAAE,EAAE,CAAC;IACvF,CAAC;IACD,OAAO,EAAE,KAAK,EAAE,IAAI,EAAE,IAAI,EAAE,GAAmC,EAAE,CAAC;AACnE,CAAC;AAED,SAAS,YAAY,CAAC,QAAgB;IACrC,IAAI,CAAC;QACJ,OAAO,IAAI,CAAC,KAAK,CAAC,EAAE,CAAC,YAAY,CAAC,QAAQ,EAAE,OAAO,CAAC,CAAC,CAAC;IACvD,CAAC;IAAC,OAAO,IAAa,EAAE,CAAC;QACxB,OAAO,IAAI,CAAC;IACb,CAAC;AACF,CAAC;AAED,MAAM,UAAU,iBAAiB,CAAC,GAAW;IAC5C,MAAM,MAAM,GAAa,EAAE,CAAC;IAE5B,MAAM,UAAU,GAAG,mBAAmB,EAAE,CAAC;IACzC,MAAM,WAAW,GAAG,oBAAoB,CAAC,GAAG,CAAC,CAAC;IAE9C,IAAI,YAAY,GAAwB,IAAI,CAAC;IAC7C,IAAI,aAAa,GAAyB,IAAI,CAAC;IAE/C,MAAM,SAAS,GAAG,YAAY,CAAC,UAAU,CAAC,CAAC;IAC3C,IAAI,SAAS,KAAK,IAAI,EAAE,CAAC;QACxB,MAAM,MAAM,GAAG,cAAc,CAAC,SAAS,EAAE,QAAQ,CAAC,CAAC;QACnD,IAAI,MAAM,CAAC,KAAK,EAAE,CAAC;YAClB,YAAY,GAAG,MAAM,CAAC,IAAI,CAAC;QAC5B,CAAC;aAAM,CAAC;YACP,MAAM,CAAC,IAAI,CAAC,MAAM,CAAC,KAAK,CAAC,CAAC;QAC3B,CAAC;IACF,CAAC;IAED,MAAM,UAAU,GAAG,YAAY,CAAC,WAAW,CAAC,CAAC;IAC7C,IAAI,UAAU,KAAK,IAAI,EAAE,CAAC;QACzB,MAAM,MAAM,GAAG,cAAc,CAAC,UAAU,EAAE,SAAS,CAAC,CAAC;QACrD,IAAI,MAAM,CAAC,KAAK,EAAE,CAAC;YAClB,aAAa,GAAG,MAAM,CAAC,IAAI,CAAC;QAC7B,CAAC;aAAM,CAAC;YACP,MAAM,CAAC,IAAI,CAAC,MAAM,CAAC,KAAK,CAAC,CAAC;QAC3B,CAAC;IACF,CAAC;IAED,yEAAyE;IACzE,MAAM,mBAAmB,GAAqB;QAC7C,GAAG,CAAC,YAAY,EAAE,CAAC,gBAAgB,CAAC,IAAI,EAAE,CAAC;QAC3C,GAAG,CAAC,aAAa,EAAE,CAAC,gBAAgB,CAAC,IAAI,EAAE,CAAC;KAC5C,CAAC;IAEF,MAAM,MAAM,GAAiB;QAC5B,OAAO,EAAE,YAAY;QACrB,QAAQ,EAAE,aAAa;KACvB,CAAC;IAEF,IAAI,MAAM,CAAC,IAAI,CAAC,mBAAmB,CAAC,CAAC,MAAM,GAAG,CAAC,EAAE,CAAC;QACjD,MAAM,CAAC,gBAAgB,CAAC,GAAG,mBAAmB,CAAC;IAChD,CAAC;IAED,iEAAiE;IACjE,IAAI,aAAa,EAAE,SAAS,EAAE,CAAC;QAC9B,MAAM,CAAC,SAAS,GAAG,aAAa,CAAC,SAAS,CAAC;IAC5C,CAAC;IAED,OAAO,EAAE,MAAM,EAAE,YAAY,EAAE,OAAO,EAAE,aAAa,EAAE,MAAM,EAAE,MAAM,EAAE,CAAC;AACzE,CAAC"}
+{"version":3,"file":"config-layer.js","sourceRoot":"","sources":["../../../src/extensions/forgecli/config-layer.ts"],"names":[],"mappings":"AAAA,OAAO,KAAK,EAAE,MAAM,SAAS,CAAC;AAC9B,OAAO,SAAS,MAAM,KAAK,CAAC;AAC5B,OAAO,MAAM,MAAM,yBAAyB,CAAC,OAAO,IAAI,EAAE,MAAM,EAAE,CAAC;AACnE,OAAO,EAAE,mBAAmB,EAAE,oBAAoB,EAAE,MAAM,kBAAkB,CAAC;AAE7E,4DAA4D;AAC5D,wDAAwD;AACxD,MAAM,GAAG,GAAI,SAAiB,CAAC,OAAO,EAAE,GAAG,IAAK,SAAiB,CAAC,GAAG,IAAI,SAAS,CAAC;AAiEnF,MAAM,GAAG,GAAG,IAAI,GAAG,CAAC,EAAE,SAAS,EAAE,IAAI,EAAE,CAAC,CAAC;AACzC,MAAM,QAAQ,GAAG,GAAG,CAAC,OAAO,CAAC,MAAM,CAAC,CAAC;AAErC,SAAS,cAAc,CACtB,GAAY,EACZ,KAAa;IAEb,MAAM,EAAE,GAAG,QAAQ,CAAC,GAAG,CAAC,CAAC;IACzB,IAAI,CAAC,EAAE,EAAE,CAAC;QACT,MAAM,QAAQ,GACb,QAAQ,CAAC,MAAM;YACd,EAAE,GAAG,CAAC,CAAC,CAA8C,EAAE,EAAE,CAAC,GAAG,CAAC,CAAC,YAAY,IAAI,GAAG,IAAI,CAAC,CAAC,OAAO,EAAE,CAAC;aACjG,IAAI,CAAC,IAAI,CAAC,IAAI,SAAS,CAAC;QAC3B,OAAO,EAAE,KAAK,EAAE,KAAK,EAAE,KAAK,EAAE,aAAa,KAAK,yBAAyB,QAAQ,EAAE,EAAE,CAAC;IACvF,CAAC;IACD,OAAO,EAAE,KAAK,EAAE,IAAI,EAAE,IAAI,EAAE,GAAmC,EAAE,CAAC;AACnE,CAAC;AAED,SAAS,YAAY,CAAC,QAAgB;IACrC,IAAI,CAAC;QACJ,OAAO,IAAI,CAAC,KAAK,CAAC,EAAE,CAAC,YAAY,CAAC,QAAQ,EAAE,OAAO,CAAC,CAAC,CAAC;IACvD,CAAC;IAAC,OAAO,IAAa,EAAE,CAAC;QACxB,OAAO,IAAI,CAAC;IACb,CAAC;AACF,CAAC;AAED,MAAM,UAAU,iBAAiB,CAAC,GAAW;IAC5C,MAAM,MAAM,GAAa,EAAE,CAAC;IAE5B,MAAM,UAAU,GAAG,mBAAmB,EAAE,CAAC;IACzC,MAAM,WAAW,GAAG,oBAAoB,CAAC,GAAG,CAAC,CAAC;IAE9C,IAAI,YAAY,GAAwB,IAAI,CAAC;IAC7C,IAAI,aAAa,GAAyB,IAAI,CAAC;IAE/C,MAAM,SAAS,GAAG,YAAY,CAAC,UAAU,CAAC,CAAC;IAC3C,IAAI,SAAS,KAAK,IAAI,EAAE,CAAC;QACxB,MAAM,MAAM,GAAG,cAAc,CAAC,SAAS,EAAE,QAAQ,CAAC,CAAC;QACnD,IAAI,MAAM,CAAC,KAAK,EAAE,CAAC;YAClB,YAAY,GAAG,MAAM,CAAC,IAAI,CAAC;QAC5B,CAAC;aAAM,CAAC;YACP,MAAM,CAAC,IAAI,CAAC,MAAM,CAAC,KAAK,CAAC,CAAC;QAC3B,CAAC;IACF,CAAC;IAED,MAAM,UAAU,GAAG,YAAY,CAAC,WAAW,CAAC,CAAC;IAC7C,IAAI,UAAU,KAAK,IAAI,EAAE,CAAC;QACzB,MAAM,MAAM,GAAG,cAAc,CAAC,UAAU,EAAE,SAAS,CAAC,CAAC;QACrD,IAAI,MAAM,CAAC,KAAK,EAAE,CAAC;YAClB,aAAa,GAAG,MAAM,CAAC,IAAI,CAAC;QAC7B,CAAC;aAAM,CAAC;YACP,MAAM,CAAC,IAAI,CAAC,MAAM,CAAC,KAAK,CAAC,CAAC;QAC3B,CAAC;IACF,CAAC;IAED,yEAAyE;IACzE,MAAM,mBAAmB,GAAqB;QAC7C,GAAG,CAAC,YAAY,EAAE,CAAC,gBAAgB,CAAC,IAAI,EAAE,CAAC;QAC3C,GAAG,CAAC,aAAa,EAAE,CAAC,gBAAgB,CAAC,IAAI,EAAE,CAAC;KAC5C,CAAC;IAEF,MAAM,MAAM,GAAiB;QAC5B,OAAO,EAAE,YAAY;QACrB,QAAQ,EAAE,aAAa;KACvB,CAAC;IAEF,IAAI,MAAM,CAAC,IAAI,CAAC,mBAAmB,CAAC,CAAC,MAAM,GAAG,CAAC,EAAE,CAAC;QACjD,MAAM,CAAC,gBAAgB,CAAC,GAAG,mBAAmB,CAAC;IAChD,CAAC;IAED,iEAAiE;IACjE,IAAI,aAAa,EAAE,SAAS,EAAE,CAAC;QAC9B,MAAM,CAAC,SAAS,GAAG,aAAa,CAAC,SAAS,CAAC;IAC5C,CAAC;IAGD,OAAO,EAAE,MAAM,EAAE,YAAY,EAAE,OAAO,EAAE,aAAa,EAAE,MAAM,EAAE,MAAM,EAAE,CAAC;AACzE,CAAC"}

package/dist/extensions/forgecli/context-governor-compaction.d.ts

@@ -0,0 +1,83 @@
+import type { ExtensionFactory } from "@earendil-works/pi-coding-agent";
+/**
+ * Structured Forge facts extracted from messagesToSummarize.
+ * All fields are arrays of strings for serialization into the compaction summary.
+ */
+export interface ForgeFactSummary {
+    /** FORGE-X-Y / FORGE-X-Y-TN patterns extracted from message text. */
+    storeIds: string[];
+    /** Lines containing [x] or [ ] checkbox patterns (Markdown task lists). */
+    acStateLines: string[];
+    /** Lines matching → <status> or update-status ... status <value>. */
+    transitionLines: string[];
+    /** File refs: engineering/, .forge/, *.ts/*.md/*.cjs/*.json paths. */
+    fileRefs: string[];
+    /** Text blocks containing [FRICTION] or type:friction. */
+    frictionBlocks: string[];
+}
+/**
+ * Options for buildForgeCompactionFactory.
+ */
+export interface ForgeCompactionOptions {
+    /**
+     * Absolute path to the project CWD (for warm-tier summary file lookup).
+     * When omitted, warm-tier merge is skipped unless summaryReader is provided.
+     */
+    cwd?: string;
+    /**
+     * Phase key for summary filename resolution (e.g. "architect/plan").
+     * When omitted, warm-tier merge is skipped.
+     */
+    phaseKey?: string;
+    /**
+     * Task/entity ID for summary path resolution (e.g. "FORGE-S30-T09").
+     * When omitted, warm-tier merge is skipped.
+     */
+    entityId?: string;
+    /**
+     * Sprint ID for summary path resolution (e.g. "FORGE-S30").
+     * When omitted, warm-tier merge is skipped.
+     */
+    sprintId?: string;
+    /**
+     * Injected summary reader (test seam). Receives the resolved summary
+     * file path (empty string when path resolution is skipped) and returns
+     * the raw JSON string or null. Defaults to fs.readFileSync.
+     * Must not throw — return null on any failure.
+     */
+    summaryReader?: (filePath: string) => string | null;
+}
+/**
+ * Extract structured Forge facts from an array of message-like objects.
+ *
+ * Pure function — no fs I/O, no LLM calls, provider-neutral.
+ * Accepts any array (unknown[]) to be safe against varying pi message shapes.
+ * Text content is extracted from `.content[].text` (assistant messages)
+ * and from direct string entries.
+ *
+ * @param messagesToSummarize  Array of message-like objects from preparation.
+ * @returns ForgeFactSummary with all extracted patterns.
+ */
+export declare function extractForgeFacts(messagesToSummarize: unknown[]): ForgeFactSummary;
+/**
+ * Build an ExtensionFactory that registers a session_before_compact handler
+ * returning a deterministically-composed CompactionResult.
+ *
+ * The handler:
+ * 1. Validates that event.preparation is present and well-formed.
+ * 2. Extracts Forge facts from event.preparation.messagesToSummarize
+ *    (no LLM call, provider-neutral).
+ * 3. Reads the warm-tier {PHASE}-SUMMARY.json if opts provide path context,
+ *    or invokes opts.summaryReader("") as a test seam.
+ * 4. Assembles a compact structured summary string.
+ * 5. Returns { compaction: { summary, firstKeptEntryId, tokensBefore } }.
+ * 6. Returns undefined on any error (IL7 — lets pi compact normally).
+ *
+ * Pack 07: reads summary files but never writes .forge/store/.
+ * IL10: no pi-mono edits, no dispatch contract changes.
+ * NOT wired into index.ts/run-task.ts — deferred to T07 production integration.
+ *
+ * @param opts  ForgeCompactionOptions (default: empty — no warm-tier).
+ * @returns ExtensionFactory for passing to DefaultResourceLoader.extensionFactories.
+ */
+export declare function buildForgeCompactionFactory(opts?: ForgeCompactionOptions): ExtensionFactory;