@entelligentsia/forgecli 0.11.3 → 0.19.0

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

@@ -1,9 +1,313 @@
 {
-  "0.44.7": {
-    "version": "0.44.8",
+  "0.51.2": {
+    "version": "0.51.3",
+    "date": "2026-05-23",
+    "notes": "Workflow prose updated to reference forge_artifact tool for all phase artifact reads/writes. Eliminates manual path construction — models use typed tool calls with entity ID resolution and JSON summary schema validation.",
+    "target": "workflows:all-phase-workflows,workflows:_fragments/store-cli-verbs",
+    "regenerate": [
+      "workflows:plan_task",
+      "workflows:review_plan",
+      "workflows:implement_plan",
+      "workflows:review_code",
+      "workflows:validate_task",
+      "workflows:architect_approve",
+      "workflows:fix_bug",
+      "workflows:collator_agent",
+      "workflows:_fragments/store-cli-verbs"
+    ],
+    "breaking": false,
+    "manual": []
+  },
+  "0.51.1": {
+    "version": "0.51.2",
+    "date": "2026-05-23",
+    "notes": "S25 post-refactor regression fixes: (A) store-cli-verbs.md — explicit 4-arg update-status syntax; (B) implement workflow — two-step plan-approved→implementing→implemented transition; (C/D) collator workflow — no-set-summary Iron Law + WRITEBACK-SUMMARY.json Finalize step.",
+    "target": "workflows:implement_plan,workflows:collator_agent,workflows:_fragments/store-cli-verbs",
+    "regenerate": [
+      "workflows:implement_plan",
+      "workflows:collator_agent",
+      "workflows:_fragments/store-cli-verbs"
+    ],
+    "breaking": false,
+    "manual": []
+  },
+  "0.51.0": {
+    "version": "0.51.1",
+    "date": "2026-05-23",
+    "notes": "FORGE-S25-T28 — Guardrails CI consolidation. Adds --check mode to build-manifest.cjs and build-enum-catalog.cjs (non-destructive drift detection; exits 1 when structure-manifest.json or enum-catalog.json/transitions/*.json are stale). Wires manifest-drift + enum-catalog-drift gates into plugin-ci.yml. Adds forge/forge/CLAUDE.md documenting the four CI gates.",
+    "target": "tools:build-manifest",
+    "regenerate": [
+      "tools:build-manifest",
+      "tools:build-enum-catalog"
+    ],
+    "breaking": false,
+    "manual": []
+  },
+  "0.50.0": {
+    "version": "0.50.1",
+    "date": "2026-05-23",
+    "notes": "FORGE-S25-T26 — Catalog generator + plugin consumers. Adds build-enum-catalog.cjs emitting forge/schemas/enum-catalog.json + forge/schemas/transitions/{task,sprint,bug}.json from T25 ADR canonical FSM tables. Canonicalizes store-cli.cjs TASK_TRANSITIONS/SPRINT_TRANSITIONS/BUG_TRANSITIONS to T25 ADR (D-T-1..D-T-9, D-S-1..D-S-4, D-B-1). Narrows FAILED_STATES: removes blocked, plan-revision-required, code-revision-required (all transitions are now explicit in the tables). Extends substitute-placeholders.cjs with {{ENUM:entity.field}} placeholder support (resolves to comma-separated schema enum values). Adds @catalogSync annotation to hooks/lib/common.cjs:FORGE_COMMAND_PATTERNS + fills 15 missing command patterns; syncs inline copy in hooks/triage-error.cjs. build-manifest.cjs gains post-step to regenerate enum-catalog on every manifest rebuild. gen-integrity.cjs tracks new catalog + transition files. New tests: build-enum-catalog.test.cjs (14 cases), store-cli-transitions.test.cjs (9 regression cases, D-T-* / D-S-* / D-B-*). integrity.json regenerated.",
+    "target": "schemas:enum-catalog",
+    "regenerate": [
+      "schemas:enum-catalog",
+      "schemas:transitions",
+      "tools:build-enum-catalog",
+      "tools:store-cli",
+      "tools:substitute-placeholders",
+      "tools:build-manifest",
+      "tools:gen-integrity",
+      "hooks:triage-error",
+      "hooks:lib/common"
+    ],
+    "breaking": false,
+    "manual": []
+  },
+  "0.49.0": {
+    "version": "0.50.0",
+    "date": "2026-05-23",
+    "notes": "FORGE-S25-T15 — hooks:h5-polish. Drop mtime sentinel in post-init.cjs (H-5c); add logSwallowedError helper to hooks/lib/common.cjs (H-5b); interpolate CLAUDE_PLUGIN_ROOT into forge-permissions.cjs node-tool rule (H-5d); reduce check-update.cjs HTTPS timeout 5s→2s (H-5a); complete hooks/README.md swallowed-error policy section. integrity.json regenerated.",
+    "target": "hooks:h5-polish",
+    "regenerate": [],
+    "breaking": false,
+    "manual": []
+  },
+  "0.48.2": {
+    "version": "0.49.0",
+    "date": "2026-05-23",
+    "notes": "FORGE-S25-T14 — hooks/*.js → *.cjs rename + extract hooks/lib/{plugin-detection,update-url,update-msg}.cjs + REGISTRY private. Closes H-2, H-3, H rename. gen-integrity.cjs updated to glob .cjs. integrity.json regenerated. forge-cli/scripts/build-payload.cjs hook filter updated from .js to .cjs (cross-repo).",
+    "regenerate": [],
+    "breaking": false,
+    "manual": []
+  },
+  "0.48.1": {
+    "version": "0.48.2",
+    "date": "2026-05-23",
+    "notes": "FORGE-S25-T13 — Release-time URL rewrite strategy for plugin.json (S-12), structure-manifest.json product-manager edge fix (S-7), additionalProperties CI gate (S-4/N-S-2), schema-evolution-policy ADR. Adds rewrite-plugin-urls.cjs tool (--target main|release) for release workflow automation. Fixes build-manifest.cjs parseMetaDeps to filter non-generated personas (product-manager, orchestrator) from workflow edges. Regenerates structure-manifest.json. Adds schema-additionalProperties.test.cjs CI gate asserting every *.schema.json has root additionalProperties:false. Sets plugin.json URLs to main-branch raw GitHub content.",
+    "regenerate": [
+      "schemas:structure-manifest"
+    ],
+    "breaking": false,
+    "manual": []
+  },
+  "0.48.0": {
+    "version": "0.48.1",
+    "date": "2026-05-23",
+    "notes": "Fix preflight-gate sprint directory slug resolution. When a sprint directory has a slug suffix (e.g. 'FORGE-S25-foundation-refactor' for sprintId 'FORGE-S25'), the gate was using the bare sprintId as the directory path, causing artifact-not-found failures even when the artifact existed under the slugged directory. Adds resolveSprintArtifactDir() (exported) that scans engineering/sprints/ for an exact match then a '<sprintId>-*' prefix match, analogous to resolveTaskArtifactDir(). resolveTaskArtifactDir() gains an optional resolvedSprintDir parameter. CLI shim resolves the sprint dir before resolving the task dir and uses it for the {sprint} substitution.",
+    "regenerate": [],
+    "breaking": false,
+    "manual": []
+  },
+  "0.47.2": {
+    "version": "0.48.0",
+    "date": "2026-05-22",
+    "notes": "FORGE-S25-T10 — extract _fragments/{store-write-verification,iron-laws,generation-instructions}.md + backfills. Closes CM-1, CM-2, CM-3, CM-4, CM-6, N-CM-4, N-CM-5. Three new canonical fragment files added to meta/workflows/_fragments/ and mirrored to init/base-pack/workflows/_fragments/. The 9-line Store-Write Verification block (byte-identical across 9 workflows) replaced with a single comment marker; 3 variant workflows (sprint-plan, collate, enhance) retain inline text with inline note. iron-laws.md and generation-instructions.md are template-guide fragments (CM-2/CM-3/CM-6 closed-as-documented, not closed-as-deduplicated — duplication stays inline, fragments document the canonical structure; see doc/decisions/meta-fragment-includes.md). Iron Laws backfilled into 3 previously missing workflows (meta-migrate, meta-retrospective, meta-sprint-intake). Generation Instructions backfilled into 2 missing workflows (meta-enhance, meta-migrate). meta-review-plan: ## Generation Notes renamed to ## Generation Instructions. Intentional-omission comments added for meta-quiz-agent and meta-review-sprint-completion. FRAGMENT_MAP in build-manifest.cjs updated with 3 new entries (now 9 total). Byte budgets in phase-frontmatter.test.cjs lowered for files where SWV block was removed: meta-validate (5888→5376), meta-update-plan (3584→3072), meta-update-implementation (4096→3584); other 6 files remain within existing budgets. All 1513 plugin tests pass. Regeneration required: workflows and _fragments.",
+    "regenerate": [
+      "workflows:_fragments",
+      "workflows:commit_task",
+      "workflows:implement_plan",
+      "workflows:review_plan",
+      "workflows:update_implementation",
+      "workflows:approve_task",
+      "workflows:update_plan",
+      "workflows:review_implementation",
+      "workflows:validate_task",
+      "workflows:plan_task",
+      "workflows:architect_sprint_plan",
+      "workflows:collator_agent",
+      "workflows:enhance",
+      "workflows:fix_bug",
+      "workflows:orchestrate_task",
+      "workflows:migrate_structural",
+      "workflows:sprint_retrospective",
+      "workflows:architect_sprint_intake",
+      "workflows:quiz_agent"
+    ],
+    "breaking": false,
+    "manual": [
+      "Run /forge:update to receive the 3 new _fragments/ files and updated workflow files that now carry fragment reference markers instead of verbatim Store-Write Verification blocks.",
+      "CM-2/CM-3/CM-6 (Iron Laws and Generation Instructions duplication) are closed-as-documented via the template-guide pattern — the prose remains inline in each workflow. No manual deduplication needed."
+    ]
+  },
+  "0.47.1": {
+    "version": "0.47.2",
+    "date": "2026-05-22",
+    "notes": "FORGE-S25-T07 — extract lib/frontmatter.cjs (CRLF normalization), lib/slug.cjs (maxLen=30), lib/fsutil.cjs. Closes findings N-T-3, N-T-4, T-5. lib/frontmatter.cjs: canonical YAML frontmatter extractor normalizing all line endings (CRLF/CR/mixed) to LF on read — resolves silent divergence between build-base-pack.cjs and substitute-placeholders.cjs. lib/slug.cjs: deriveSlug(title, {maxLen=30}) with trailing-hyphen trim — closes slug truncation divergence between seed-store.cjs (truncated at 30) and store-facade.cjs (no truncation). lib/fsutil.cjs: ensureDir/isFile/isDirectory — consolidates 4 inline mkdirSync sites. One-shot migration script: tools/migrate-slug-maxlen.cjs (dry-run by default; --apply renames KB directories for any bug whose title exceeds 30 chars). forge-cli build-payload.cjs LIB_ALLOWLIST updated with frontmatter.cjs, slug.cjs, fsutil.cjs. Decision doc: doc/decisions/lib-extraction-contract.md.",
+    "regenerate": [
+      "tools:seed-store",
+      "tools:store-facade",
+      "tools:build-base-pack",
+      "tools:substitute-placeholders"
+    ],
+    "breaking": false,
+    "manual": [
+      "Run `node forge/forge/tools/migrate-slug-maxlen.cjs` to check for long-title bug entities that may have slug changes under maxLen=30. If affected entities are reported, run with --apply to rename KB directories."
+    ]
+  },
+  "0.47.0": {
+    "version": "0.47.1",
+    "date": "2026-05-22",
+    "notes": "FORGE-S25-T06 — extract lib/json-io.cjs + lib/schema-loader.cjs (memoized). Closes findings T-1, T-10, H-4d, N-T-2. Creates forge/forge/tools/lib/json-io.cjs (readJson/writeJson shared primitives extracted from FSImpl in store.cjs) and forge/forge/tools/lib/schema-loader.cjs (memoized 4-path search chain: project → in-tree → plugin-installed → forge-cli bundled .schemas/; extracted from _getSchemas() in store-cli.cjs). Migrates four consumers: tools/store.cjs (FSImpl._readJson/_writeJson now delegate to lib/json-io.cjs), tools/lib/store-facade.cjs (_loadDir, getEntity, loadForgeConfig inline JSON.parse calls replaced with readJson), tools/store-cli.cjs (_getSchemas() body replaced with loadSchemas() wrapper — memoization and 4-path chain live in schema-loader.cjs; dead _schemas variable removed), hooks/validate-write.js (inline loadSchema() replaced with resolveSchemaLoader()+loadSchemas() — gains the bundled .schemas/ path that the previous inline implementation was missing). Adds unit tests: json-io.test.cjs (7 cases), schema-loader.test.cjs (7 cases), store-facade.test.cjs (9 cases). Full plugin test suite 1516/1516 passing. forge-cli build-payload.cjs LIB_ALLOWLIST updated with json-io.cjs + schema-loader.cjs; npm run build passes; both files confirmed in dist/forge-payload/tools/lib/. MINIMAL_REQUIRED is now canonical in schema-loader.cjs (exported); store-cli.cjs retains its own copy for the exported symbol surface (backward-compat). resetSchemaCache() exported for test isolation only. Additive, non-breaking — no schema changes, no workflow regeneration needed.",
+    "regenerate": [
+      "tools:store-facade",
+      "tools:store-cli",
+      "hooks:validate-write"
+    ],
+    "breaking": false,
+    "manual": [
+      "After /forge:update, the new lib/json-io.cjs and lib/schema-loader.cjs files will be installed alongside the updated tools. No manual steps needed for standard installs.",
+      "forge-cli users: rebuild the forge-cli bundle (npm run build in forge-cli/) to pick up the two new lib files in the forge-cli bundled payload."
+    ]
+  },
+  "0.46.2": {
+    "version": "0.47.0",
+    "date": "2026-05-22",
+    "notes": "FORGE-S25-T12 schema hygiene — extract schemas/_defs/phaseSummary.schema.json (single-source for task + bug phase-summary shape; superset includes the bug-only `route` field used by meta-fix-bug.md triage). Refactor task.schema.json + bug.schema.json `summaries.*` slots to external $ref into the shared _defs file; drop inline $defs.phaseSummary from both (proven equivalent — bug `route` field now lives in the shared definition). Upgrade config.schema.json $schema to draft 2020-12 + HTTPS $id (https://github.com/Entelligentsia/agentic-skills/forge/config.schema.json) — body already 2020-12-compatible. Add root additionalProperties:false to config.schema.json — live dogfooded config validates clean, so no manual strip step is needed for known-good consumers. Port rich content from sdlc-config.schema.json into config.schema.json (pipelines definition, calibrationHistory, sprint.execution, pipeline.skipPhases + includeTokenDataInBugReports, commands.syntaxCheck object form, mode description) so config.schema.json becomes the single canonical source. DELETE forge/sdlc-config.schema.json outright (FORGE-S25-T12 / S-6) — three plugin consumers rewritten to schemas/config.schema.json in the same task: commands/health.md:57, init/sdlc-init.md:83, init/smoke-test.md:26+114. forge-cli's write-guard already loaded config.schema.json. Pre-commit grep across forge/forge/ + forge-cli/src/ confirmed zero live consumers of sdlc-config.schema.json (vision/*.md historical design docs only). Fix migrations.json typos schemas:events -> schemas:event at entries 0.43.12 and 0.43.11 (third occurrence at 0.45.0 was already correct). Remove stale schemas:update-check-cache target from 0.40.2 (FORGE-S25-T12 N-S-1; never resolvable — update-check-cache is a runtime cache, not a schema; documented via notes_addendum on the 0.40.2 entry). PREREQUISITE shared-surface change in forge-cli (paired same-commit): migration-engine.ts `schemas` branch in resolveCategory now walks .schemas/ recursively and preserves relative subdir structure under .forge/schemas/, so the new _defs/ subtree actually ships to user installs via /forge:update. forge-cli build-payload.cjs schema copy loop likewise recursive so the bundle carries _defs/phaseSummary.schema.json. Test surface: forge-cli adds migration-engine-defs.test.ts (5 cases, test-first) + migration-engine-dryrun.test.ts (2 cases, F-5 behavioural). Plugin tests stay 1492 green; forge-cli tests stay green (3 pre-existing unrelated doctor.test.ts failures from local auth env). Additive: no record field changes (phaseSummary $ref resolves to the same shape); store validation unchanged (validate-store.cjs validates top-level fields only, does not traverse $ref).",
+    "regenerate": [
+      "schemas",
+      "commands:health",
+      "init:sdlc-init",
+      "init:smoke-test"
+    ],
+    "breaking": false,
+    "manual": [
+      "If any project carries non-canonical keys at the root of .forge/config.json, the tightened additionalProperties:false will fail validation under the new draft-2020-12 schema. Inspect the live config and remove unknown root keys before /forge:update completes. Live dogfooded configs validate clean — this step only applies to hand-edited installs.",
+      "After /forge:update, manually delete `.forge/sdlc-config.schema.json` if present — it is the now-removed sibling schema; the regenerate mechanism only writes, it does not prune. No tooling reads it post-migration."
+    ]
+  },
+  "0.46.1": {
+    "version": "0.46.2",
+    "date": "2026-05-22",
+    "notes": "chore: FORGE-S25-T01 — plugin test baseline + no-skip CI gate. Adds `forge/tools/check-no-skipped-tests.cjs` (fails on committed it.skip / describe.skip / test.skip / it.only / describe.only / test.only / xit / xdescribe under forge/tools/__tests__ and forge/hooks/__tests__; warn-only secondary scan for FIXME:skip / TODO:re-enable so reminder comments cannot self-trip the gate; self-excludes its own paired test which carries literal marker fixtures). Expands `npm test` glob to `forge/tools/__tests__/*.test.cjs forge/hooks/__tests__/*.test.cjs` so hook failures can no longer hide outside CI. Lands `forge/.github/workflows/plugin-ci.yml` (Node 20, single job: skip-gate -> npm test -> manifest regen -> verify-integrity; no `npm ci` until T28 adds devDependencies + lockfile, marked with TODO(FORGE-S25-T28)). Deletes stale duplicate hook tests `check-update.test.js` and `forge-permissions.test.js` (canonical `.cjs` counterparts live in tools/__tests__/; grep proved zero callers outside docs/security/). Renames surviving hook tests post-init.test.js / post-sprint.test.js / validate-write.test.js to .test.cjs for layout uniformity (hook source `.js -> .cjs` rename deferred to T14). Adds `enhancement` to the store-cli emit RESERVED_GLOB so post-init/post-sprint hooks' enhancement-trigger events stop being silently dropped by the FK check — root-cause fix for the two pre-existing hook test failures. Adds `npm run lint:no-skip` script. Documents the no-skipped-tests policy in `forge/CLAUDE.md` Script Test Suite section. Full plugin suite now 1492/1492 (was 1437; +55 — hook suite + skip-gate + enhancement FK regression). Additive, non-breaking — no schema change, no workflow regeneration needed.",
+    "regenerate": [
+      "tools:check-no-skipped-tests",
+      "tools:store-cli",
+      "workflows:plugin-ci-tmp-smoke-job"
+    ],
+    "breaking": false,
+    "manual": []
+  },
+  "0.46.0": {
+    "version": "0.46.1",
+    "date": "2026-05-22",
+    "notes": "build: regenerate base-pack/workflows/enhance.md from meta sources to ship the FORGE-S24 SKILL-CURATION Phase 2 pipeline. The 0.45.1–0.45.7 entries declared `workflows:enhance` in their `regenerate` lists, but the meta→base-pack derivation (node tools/build-base-pack.cjs) was not re-run during the sprint, so the installable workflow stayed at the pre-S24 algorithm and downstream projects migrating to 0.46.0 received a stale workflow that lacked queue-drain (step 1a), recurrence scoring, delete-candidate detection (step 5b), compression gate (step 5b.5), and the LLM-judge step (step 5c). This patch bump regenerates the base-pack copy (init/base-pack/workflows/enhance.md — 280→600 lines, 20 S24 markers landed) and forces a re-copy on any project sitting at 0.46.0 by declaring `workflows:enhance` here. No plugin source change beyond the regenerated workflow file. Additive, non-breaking.",
+    "regenerate": [
+      "workflows:enhance"
+    ],
+    "breaking": false,
+    "manual": []
+  },
+  "0.45.7": {
+    "version": "0.46.0",
+    "date": "2026-05-22",
+    "notes": "chore: FORGE-S24 SKILL-CURATION sprint completion — gated rollout marker (FORGE-S24-T12). No plugin source change in this bump; the seven preceding entries (0.45.1 → 0.45.7) carry the actual SKILL-CURATION machinery: `skill_usage` event variant (T01, 0.45.1), proposal op classification (T02, 0.45.2), recurrence scoring (T04, 0.45.3), delete-candidate detection (T05, 0.45.4), LLM-judge rubric (T03, 0.45.5), compression gate (T06, 0.45.6), and queue-drain (T07, 0.45.7). T12 lands the gated-rollout contract on the forge-cli side via `forgeCli.skillCuration.enabled` (default OFF) — the four forge-cli modules (T08 skill-retriever, T09 skill-usage-tracker, T10 skill-curator-subagent, T11 friction-emit) no-op at entry when the flag is off, so a flag-off run is byte-identical to pre-FORGE-S24 behaviour. This plugin-side minor bump (0.45.7 → 0.46.0) is the convergent terminal marker for the sprint: it signals to operators running `/forge:update` that the full SKILL-CURATION pipeline has shipped end-to-end, and pairs with the forge-cli 0.13.4 → 0.14.0 bump that lands the rollout flag. No regeneration is required (no manifest entry change, no workflow change, no schema change in this bump alone — those landed in 0.45.1–0.45.7). Operators who want to enable the pipeline must (1) upgrade forge-cli to 0.14.0+ AND (2) set `forgeCli.skillCuration.enabled: true` in their project config at `<cwd>/.pi/forge-cli/config.json` (or the env override `FORGE_CLI_SKILL_CURATION_ENABLED=1` for one-shot operator use). Until both conditions hold, the new event variants and friction subkinds remain emitter-silent — the plugin schema continues to accept them on receipt, so a delayed forge-cli upgrade is non-blocking. Additive, non-breaking.",
+    "regenerate": [],
+    "breaking": false,
+    "manual": []
+  },
+  "0.45.6": {
+    "version": "0.45.7",
+    "date": "2026-05-22",
+    "notes": "feat: queue drain at sprint close — per-task curator → batched review (FORGE-S24-T07). Adds `forge/tools/queue-drain.cjs` exporting `bodyHash(body)` (sha256 hex digest, UTF-8), `dedupeKey(proposal)` (`<op>|<target_path>|<sha256(diff_body)>` composite), `dedupeProposals(proposals)` (first-seen-wins, no-mutation), `queuePathFor({queueRoot, sprintId, taskId, ts})` (canonical `.forge/enhancement-proposals/queue/<sprintId>/<taskId>-<ts>.json` path), `appendToQueue({queueRoot, sprintId, taskId, ts, proposals})` (writes one file per curator run; throws if path exists — append-only invariant per AC1), and `drainQueue({queueRoot, sprintId})` (returns `{proposals, files, errors}` after deduping the sprint sub-dir; empty-safe when queue missing per AC5; skips malformed JSON and reports them via `errors`; deterministic lexicographic file ordering ⇒ chronological because of the ts suffix). Per-task curators (T10) append proposals to the queue throughout the sprint without collision (AC2 — distinct ts per call); Phase 2 reads the queue once at sprint close, dedupes by `{op, target_path, body-hash}` (AC3), and merges the queued proposals with the friction-synthesised ones, then feeds a SINGLE batched array through recurrence (T04) → delete-candidate detection (T05) → compression gate (T06) → judge (T03) — one prompt per sprint, not one per task (AC4, paper §3.2.1 grouped reward). `meta/workflows/meta-enhance.md` Phase 2 gains step 1a (drain queue) and step-5 merge sub-block; the zero-input guard now checks both friction events AND queued proposals before exiting cleanly with `frictionCount:0,queuedCount:0`. The drain is read-only — Phase 2 never deletes queue files; operators triage them during retrospective. Test-first per Iron Law 2: `queue-drain.test.cjs` (19 cases — exports surface, bodyHash sha256 contract + empty-body digest + collision contract, dedupeKey AC3 composite + field-sensitivity, dedupeProposals dedup + order-preservation + no-mutation + empty + non-array, queuePathFor AC1 canonical layout + input validation x3, appendToQueue AC1 fresh-file write + AC2 no-collision + append-only refusal, drainQueue AC5 empty/missing safety + AC3 multi-file dedup merge + AC4 single-batch output + sprint scoping + input validation x2 + malformed-JSON resilience) landed before the helper. Pure helpers; fs-touching helpers are `appendToQueue` and `drainQueue` only. Full suite 1437/1437 (was 1418; +19). Additive, non-breaking.",
+    "regenerate": [
+      "tools:queue-drain",
+      "workflows:enhance"
+    ],
+    "breaking": false,
+    "manual": []
+  },
+  "0.45.5": {
+    "version": "0.45.6",
+    "date": "2026-05-22",
+    "notes": "feat: compression gate — reject >20% growth without 3+ frictions (FORGE-S24-T06). Adds `forge/tools/compression-gate.cjs` exporting `GROWTH_THRESHOLD` (0.20), `MIN_SUPPORTING_FRICTIONS` (3), `evaluateGrowth({currentBody, newBody}) -> {currentBytes, newBytes, growthRatio}`, `evaluateProposal({proposal, currentBody, newBody, supportingFrictionCount}) -> {admit, reason, growthRatio, currentBytes, newBytes, supportingFrictionCount, threshold, minSupportingFrictions, op}`, and `filterProposals({proposals, currentBodyFor, newBodyFor, supportingFrictionCountFor}) -> {admitted, rejected}`. The gate runs in `meta/workflows/meta-enhance.md` Phase 2 as new step 5b.5 BEFORE the LLM judge (5c) — cheap deterministic filter first. Only `update_skill` proposals are gated; `insert_skill` and `delete_skill` pass through unconditionally (insert bloat is the judge's `body_under_2kb` axis; delete only shrinks). Growth is measured byte-wise via `Buffer.byteLength(body, 'utf8')` on the new body that would land after applying the proposal's diff. Threshold comparison is strict (>0.20) so ties at exactly 20% admit. Default supporting friction count = `proposal.sourceFrictionIds.length`; the caller may override via `supportingFrictionCountFor(proposal)` when the policy is to count frictions citing the same skill across the sprint. Updates on an empty current body yield `growthRatio: Infinity` and the friction-support rule still applies; shrinks (negative growth) admit unconditionally. Rejected proposals are persisted to the same `phase2-<timestamp>-rejections.json` sibling that the T03 judge writes, with reason `compression_gate_growth_unsupported` and the full evaluation record alongside the original proposal — every drop (gate or judge) stays traceable. Closes the unbounded-growth failure mode of SkillOS — pasting pages of trajectory copy-paste to 'patch' a friction now requires real recurrence evidence. Test-first per Iron Law 2: `compression-gate.test.cjs` (25 cases — GROWTH_THRESHOLD/MIN_SUPPORTING_FRICTIONS constants, evaluateGrowth shape, UTF-8 multibyte byte counting, empty-current-body Infinity ratio, AC1 0-friction rejection, AC2 3-friction admission, 2-friction insufficiency, AC5 exact-20% strict admission, under-threshold admission, sourceFrictionIds fallback, shrink admission, AC4 insert_skill/delete_skill pass-through, input validation x5, filterProposals AC6 ordering/partition, empty input, no-mutation invariant, callback contracts, supportingFrictionCountFor override) landed before the helper. Pure module; no fs access; no LLM call. Full suite 1418/1418 (was 1393; +25). Additive, non-breaking.",
+    "regenerate": [
+      "tools:compression-gate",
+      "workflows:enhance"
+    ],
+    "breaking": false,
+    "manual": []
+  },
+  "0.45.4": {
+    "version": "0.45.5",
+    "date": "2026-05-22",
+    "notes": "feat: LLM-judge step in Phase 2 — Sonnet rubric, drop <3/5 (FORGE-S24-T03). Adds `forge/tools/judge-proposal.cjs` exporting `RUBRIC_AXES` (frozen 5-axis tuple: specificity, when_not_to_use, no_trajectory_copy_paste, body_under_2kb, cites_friction), `scoreProposal(proposal) -> { axes, average }` (deterministic per-axis 0..5 scorer), and `decideJudgement({ axes }) -> { verdict, average, axes, reason }` (pure aggregator: verdict === 'drop' iff average < 3, strict; ties at 3.0 keep). The rubric is single-sourced in this helper — Sonnet's role is to apply the same axes and emit scores that the helper then validates and aggregates; in the absence of an LLM call the deterministic scorer is the fallback. `decideJudgement` fails loud on missing or out-of-range axes (RangeError) so a malformed score sheet never silently coerces into a verdict. `meta/workflows/meta-enhance.md` Phase 2 gains step 5c calling `scoreProposal` + `decideJudgement` for every proposal between delete-candidate detection (5b) and artifact write (6); kept proposals continue to step 6, dropped proposals are persisted to a sibling `phase2-<timestamp>-rejections.json` carrying the original proposal alongside `{ verdict, average, axes, reason }` so every rejection is traceable for retro review (AC3). Per-axis heuristics: specificity scores deep paths, named (non-generic) skill files, non-trivial rationales, and recurrence trails; when_not_to_use checks for the literal phrase; no_trajectory_copy_paste flags long verbatim runs or unbroken non-whitespace blocks >= 400 bytes; body_under_2kb gates on `Buffer.byteLength(diff_body,'utf8') <= 2048`; cites_friction rewards `sourceFrictionIds.length` >= 1, boosting for multi-citation and recurrence. Consumes recurrence data from T04 in the specificity and cites_friction axes — proposals that recurred across multiple tasks score higher. Test-first per Iron Law 2: `judge-proposal.test.cjs` (13 cases — rubric-axes shape, 5/5 keep fixture, 1/5 drop fixture, body byte boundary at exactly 2048, zero-citation suppression, phrase-presence binary, AC6 explicit 2.8/5 drop fixture, keep + drop end-to-end decisions, exact-3.0 boundary keeps, missing-axis RangeError, out-of-range RangeError) landed before the helper. Pure module; no fs access; no LLM call. Full suite 1393/1393 (was 1380; +13). Additive, non-breaking.",
+    "regenerate": [
+      "tools:judge-proposal",
+      "workflows:enhance"
+    ],
+    "breaking": false,
+    "manual": []
+  },
+  "0.45.3": {
+    "version": "0.45.4",
+    "date": "2026-05-22",
+    "notes": "feat: delete-candidate detection — 3-sprint zero-use (FORGE-S24-T05). Adds `forge/tools/delete-candidate-detector.cjs` exporting `scanZeroUse({events, sprintOrder, windowSize})` and `buildDeleteProposals({events, sprintOrder, windowSize, targetPathFor})`. The detector scans `skill_usage` events across the trailing `windowSize` (default 3) sprints; any skill with at least one in-window observation AND zero `retrieved` AND zero `used` qualifies as a delete candidate. Skills with zero in-window observations are explicitly NOT proposed — that case is indistinguishable from a newly-added skill that hasn't been loaded yet. `meta/workflows/meta-enhance.md` Phase 2 gains step 5b calling `buildDeleteProposals` between recurrence annotation (step 5a) and artifact write (step 6). Each delete proposal carries `op: 'delete_skill'`, `target_path` resolved via the supplied `targetPathFor(skillId)` callback, a diff body and rationale that name the cold skill and the observed sprints, `sourceFrictionIds: []` (usage-derived, not friction-derived), `window_size`, `window_sprint_ids`, plus neutral `recurrence_count: 1` and `recurrence_task_ids: []` so the proposal shape stays uniform with the rest of the Phase 2 array. Carry-over caveat documented in the workflow: the trailing-3-sprint window only becomes meaningful once 3 sprints have elapsed since `skill_usage` emission landed in T01 (0.45.1); short-history runs produce advisory rather than authoritative deletes. This is the only mechanism by which the skill repository shrinks, completing the three-op classification rollout from T02 (insert/update were already in play). Test-first per Iron Law 2: `delete-candidate-detector.test.cjs` (16 cases — three-sprint zero-use baseline, retrieved=true disqualification, used=true disqualification, trailing-window guard against pre-window usage, default windowSize 3, configurable windowSize, never-observed-in-window suppression, empty events, friction-event filtering, short-history carry-over case, no-mutation invariant, multi-skill output, deterministic ordering, callback contract, plus AC restatement cases) landed before the detector. Pure module; no fs access. Full suite 1380/1380 (was 1364; +16). Additive, non-breaking.",
+    "regenerate": [
+      "tools:delete-candidate-detector",
+      "workflows:enhance"
+    ],
+    "breaking": false,
+    "manual": []
+  },
+  "0.45.2": {
+    "version": "0.45.3",
+    "date": "2026-05-22",
+    "notes": "feat: cross-task replay scoring — recurrence boost (FORGE-S24-T04). Adds `forge/tools/replay-scoring.cjs` exporting `computeRecurrence({events, subkind, skillId, fromTaskId, taskOrder})` and `annotateProposals(proposals, frictionEvents, taskOrder)`. For each Phase 2 enrichment proposal synthesised from a friction event at task `t`, the annotator scans tasks `t+1..N` in the same sprint for friction events matching the same `(subkind, evidence.skillId)` pair and stamps `recurrence_count` (>= 1, includes the origin task) and `recurrence_task_ids` (taskOrder-sorted) onto the proposal. Forward-only scan: earlier tasks before `fromTaskId` are excluded. Proposals without resolvable `sourceFrictionIds` (eventId not in the friction set, or the resolved event lacks subkind/evidence.skillId) receive a neutral `recurrence_count: 1` and empty `recurrence_task_ids: []`. `meta/workflows/meta-enhance.md` Phase 2 gains step 5a calling `annotateProposals` between synthesis (step 5) and artifact write (step 6); the step 5 contract is tightened to require `sourceFrictionIds` to carry every contributing eventId so the recurrence scan can resolve provenance. `forge/schemas/proposal.schema.json` gains optional `recurrence_count` (integer minimum:1) and `recurrence_task_ids` (array of strings) properties — additive only, both fields are optional, `additionalProperties: false` continues to reject unknown keys. Feeds T03 (judge) so specificity scoring can boost frictions that recurred across multiple tasks. Test-first per Iron Law 2: `replay-scoring.test.cjs` (11 cases — AC3 three-task recurrence, single-task baseline, forward-only-direction guard, subkind mismatch rejection, skillId mismatch rejection, intra-task dedup, fromTaskId-outside-taskOrder fallback, missing-evidence guard, full annotateProposals happy path, unresolved-provenance neutral case, no-mutation invariant) landed before the helper. Full suite 1364/1364 (was 1353; +11). Additive, non-breaking.",
+    "regenerate": [
+      "tools:replay-scoring",
+      "schemas:proposal",
+      "workflows:enhance"
+    ],
+    "breaking": false,
+    "manual": []
+  },
+  "0.45.1": {
+    "version": "0.45.2",
+    "date": "2026-05-22",
+    "notes": "feat: Phase 2 proposal op classification (FORGE-S24-T02). Adds `forge/schemas/proposal.schema.json` and `forge/tools/proposal-normalize.cjs`. The new schema enumerates `op` ∈ {insert_skill, update_skill, delete_skill} with required `target_path` + `diff_body`; `additionalProperties: false` rejects unknown fields. `meta/workflows/meta-enhance.md` Phase 2 (steps 5–6) now requires every enrichment proposal to carry this triplet and writes a machine-readable `phase2-<timestamp>.json` alongside the existing markdown artifact. Back-compat: legacy proposals without `op` are normalised to `insert_skill` via `proposal-normalize.cjs:normaliseProposal()` — downstream consumers route through the helper explicitly so normalisation is auditable. Foundation for T03 (judge), T05 (delete-candidate detection), T06 (compression gate), T07 (queue drain). Test-first per Iron Law 2: `proposal-schema.test.cjs` (6 cases including missing-op rejection, unknown-op rejection, additionalProperties:false, and the legacy normalisation contract) landed before the schema. Full suite 1353/1353. Additive, non-breaking.",
+    "regenerate": [
+      "schemas:proposal"
+    ],
+    "breaking": false,
+    "manual": []
+  },
+  "0.45.0": {
+    "version": "0.45.1",
+    "date": "2026-05-22",
+    "notes": "feat: event.schema.json — new `skill_usage` event variant (FORGE-S24-T01, plan 08 Phase B). Adds `skill_usage` to the `type` enum and a conditional allOf branch requiring {skillId, retrieved, used, tool_call_success_rate, retrieval_score}. Top-level numeric properties (`tool_call_success_rate`, `retrieval_score`) carry [0,1] declarative bounds; `skillId` is `minLength: 1`. The root `additionalProperties: false` gate continues to reject unknown fields on every variant. Foundation for Sprint S24 SKILL-CURATION: T02 emits, T04 retrieval-score correlation, T05 delete-candidate detection, T08 replay scoring all consume records of this type. No code path change to validate-store.cjs — the existing validateRecord() handles the new allOf branch via the same machinery used for friction / sprint-complete / sprint-halted variants. Additive, non-breaking: existing event records remain valid. Note on target version: TASK_PROMPT requested v0.45.0 but that tag already shipped (snapshot-replay change); bumping to 0.45.1 is the minimum forward step.",
+    "regenerate": [
+      "schemas:event"
+    ],
+    "breaking": false,
+    "manual": []
+  },
+  "0.44.10": {
+    "version": "0.45.0",
+    "date": "2026-05-21",
+    "notes": "feat: Approach A — snapshot replay (forge#107). manage-versions gains a new replay subcommand that restores user-enhanced files captured by /forge:enhance Phase 2 snapshots after /forge:regenerate writes fresh base-pack content. Fulfills layer 3 of the composition contract (Working Artifact = base + snapshot + user_enhancements) declared at manage-versions.cjs:13. regenerate.md updated to invoke replay per category (personas, skills, workflows, templates) between subagent generation and manifest record. Overlay semantics: user-enhanced files retain captured content; later snapshots win on collision. Pairs with v0.44.10 (forge#108 archive-path fix) which made layer 2 functional in the first place.",
+    "regenerate": [
+      "commands:regenerate",
+      "tools:manage-versions"
+    ],
+    "breaking": false,
+    "manual": []
+  },
+  "0.44.9": {
+    "version": "0.44.10",
+    "date": "2026-05-21",
+    "notes": "fix: manage-versions add-snapshot now archives files correctly when --enhanced-elements paths include the .forge/ prefix (forge#108). Previously, every archive directory has been created empty since basePackVersion 0.43.3 — layer 2 of the composition contract was silently a no-op. Tool now strips a leading .forge/ from each element path before joining; both .forge/-relative (e.g. personas/X.md) and project-root-relative (.forge/personas/X.md) forms accepted. Unblocks forge#107 (Approach A — snapshot replay). Pure tool fix.",
+    "regenerate": [
+      "tools:manage-versions"
+    ],
+    "breaking": false,
+    "manual": []
+  },
+  "0.44.8": {
+    "version": "0.44.9",
     "date": "2026-05-21",
-    "notes": "fix: meta-enhance.md — add phase-routing guidance to command table; add zero-friction guard (skip steps 3-10; emit event with frictionCount=0); renumber Phase 2 steps 2-9 to 3-10 to align with zero-friction guard.",
-    "regenerate": ["workflows:enhance"],
+    "notes": "fix: /forge:regenerate personas + skills silently overwrote manual modifications (forge#106 / FORGE-BUG-037). Pre-write generation-manifest check added to both single-file and full-rebuild paths in commands/regenerate.md, mirroring the workflows + templates pattern. Closes asymmetric modification-detection across the four structural-element categories. Markdown-only fix.",
+    "regenerate": [
+      "commands:regenerate"
+    ],
     "breaking": false,
     "manual": []
   },
@@ -11,7 +315,9 @@
     "version": "0.44.7",
     "date": "2026-05-21",
     "notes": "fix: build-persona-pack.cjs schema mismatch — tool now accepts both base-pack (no frontmatter) and meta (YAML frontmatter) persona files; derives id/role/summary/responsibilities/outputs/file_ref from content for base-pack; derives file_ref from path for base-pack skills; throws (no empty-pack write) when both dirs are empty.",
-    "regenerate": ["tools:build-persona-pack"],
+    "regenerate": [
+      "tools:build-persona-pack"
+    ],
     "breaking": false,
     "manual": []
   },
@@ -31,7 +337,10 @@
     "version": "0.44.5",
     "date": "2026-05-21",
     "notes": "Migration apply path — runMigrations() deterministic engine + /forge:update integration (FORGE-S23-T01). Adds forge-cli migration-engine.ts: semver-range traversal [from, to) on keys, per-category resolver (84 unique category strings), idempotency ledger at .forge/applied-migrations.json, always-on schema refresh post-pass, fileOps forward-compat, path-traversal defense. The /forge:update command now prompts to apply migrations after npm upgrade; FORGE_NON_INTERACTIVE=1 auto-applies. update_plan and plan_task workflows reference migration application steps.",
-    "regenerate": ["workflows:update_plan", "workflows:plan_task"],
+    "regenerate": [
+      "workflows:update_plan",
+      "workflows:plan_task"
+    ],
     "breaking": false,
     "manual": []
   },
@@ -39,7 +348,9 @@
     "version": "0.44.4",
     "date": "2026-05-19",
     "notes": "Supervisor persona gains a top-level Iron Law forbidding `store-cli update-status` writes from any review phase. The workflow-level guard at meta-review-plan.md:76 and meta-review-implementation.md:82 (\"Bug mode — NO status write\") already existed; this is the persona-level reinforcement. Surfaced during FORGE-BUG-003 re-run testing of the forge-cli stale-ctx fix, where a supervisor subagent attempted `update-status bug FORGE-BUG-003 status plan-approved` against a bug already in terminal `fixed` state. store-cli correctly rejected the illegal transition; the persona update is defense-in-depth so the model stops attempting the write at all.",
-    "regenerate": ["personas:supervisor"],
+    "regenerate": [
+      "personas:supervisor"
+    ],
     "breaking": false,
     "manual": []
   },
@@ -47,7 +358,10 @@
     "version": "0.44.3",
     "date": "2026-05-19",
     "notes": "Add `route` (enum [A, B]) to phaseSummary in bug.schema.json and the mirrored PHASE_SUMMARY_SCHEMA constant in store-cli.cjs. Required so triage subagents can record the fix-bug pipeline route decision via set-bug-summary. EMG-BUG-001 v0.44.2 first run failed with `route: undeclared field` because the schema's additionalProperties:false rejected the new field. Optional, triage-only by convention; non-triage phases ignore it.",
-    "regenerate": ["tools:store-cli", "schemas:bug"],
+    "regenerate": [
+      "tools:store-cli",
+      "schemas:bug"
+    ],
     "breaking": false,
     "manual": []
   },
@@ -55,7 +369,9 @@
     "version": "0.44.2",
     "date": "2026-05-19",
     "notes": "parse-gates.cjs now accepts `n/a` as a valid `after <phase> = <verdict>` directive value, matching read-verdict.cjs § ALLOWED_VERDICTS. EMBERGLOW-BUG-001 (v0.44.1 second run) halted at preflight exit 2 (gate misconfigured) because the new fix-bug meta uses `after triage = n/a` (legitimate for setup phases that produce verdict: \"n/a\") and the parser hardcoded the verdict set to {approved, revision}. Test added covering n/a parsing.",
-    "regenerate": ["tools:parse-gates"],
+    "regenerate": [
+      "tools:parse-gates"
+    ],
     "breaking": false,
     "manual": []
   },
@@ -63,7 +379,9 @@
     "version": "0.44.1",
     "date": "2026-05-19",
     "notes": "Rename the triage route field from summaries.triage.path to summaries.triage.route to avoid collision with bug.path (artifact directory). Symptom from v0.44.0 first run on emberglow (EMBERGLOW-BUG-001): triage subagent wrote `\"path\": \"A\"` to the bug record, overwriting the artifact directory, causing TRIAGE.md to land under .forge/store/bugs/ instead of engineering/bugs/. Field is now `route`. The fix-bug meta carries a 'Field-naming caution' callout citing the regression so future readers understand why route is named route, not path.",
-    "regenerate": ["workflows:fix_bug"],
+    "regenerate": [
+      "workflows:fix_bug"
+    ],
     "breaking": false,
     "manual": [
       "If any bug at EMBERGLOW-BUG-001 vintage carries `path: \"A\"` or `path: \"B\"`, restore its real artifact directory before regeneration: FORGE_ALLOW_FORCE=1 node .forge/tools/store-cli.cjs write bug '{...corrected JSON with path: \"engineering/bugs/{slug}\"...}'"
@@ -129,7 +447,7 @@
   "0.43.15": {
     "version": "0.43.16",
     "date": "2026-05-15",
-    "notes": "Sprint finalization ceremony (Plan 12). Add sprint-complete and sprint-halted event variants to event.schema.json with conditional requireds via allOf/if/then. Loosen top-level required (move taskId/phase/iteration into task-scoped allOf branch). Gate workflow finalize step-4 on verdict (Approved \u2192 completed; Revision Required + partial \u2192 partially-completed; Revision Required + complete \u2192 no transition). Update validate-store.cjs allOf if/then interpreter to support enum predicates alongside const. Pairs with forge-cli v0.6.6.",
+    "notes": "Sprint finalization ceremony (Plan 12). Add sprint-complete and sprint-halted event variants to event.schema.json with conditional requireds via allOf/if/then. Loosen top-level required (move taskId/phase/iteration into task-scoped allOf branch). Gate workflow finalize step-4 on verdict (Approved → completed; Revision Required + partial → partially-completed; Revision Required + complete → no transition). Update validate-store.cjs allOf if/then interpreter to support enum predicates alongside const. Pairs with forge-cli v0.6.6.",
     "regenerate": [
       "schemas:event",
       "workflows:architect_review_sprint_completion"
@@ -140,7 +458,7 @@
   "0.43.14": {
     "version": "0.43.15",
     "date": "2026-05-14",
-    "notes": "Slice-2 fragment-sweep completion. v0.43.14 introduced the orchestrator-emits-everything contract and surgically rewrote the five phase workflows (plan/review-plan/implement/validate/commit) plus their meta sources, but 16 other workflows \u2014 every other base-pack workflow body \u2014 still carried the pre-Slice-2 'Emit the complete event ... via store-cli emit' instruction and 'Execute Token Reporting' step in their Finalize blocks. Any subagent reading those workflows would faithfully reproduce the exact hallucination class Slice 2 was built to kill (LLM-fabricated model/provider strings). This patch removes those two lines from every remaining workflow \u2014 meta sources (meta-approve, meta-update-implementation, meta-review-implementation, meta-review-sprint-completion, meta-sprint-intake, meta-sprint-plan, meta-collate, meta-update-plan, meta-fix-bug, meta-retrospective) and base-pack mirrors (architect_sprint_plan, sprint_retrospective, architect_approve, collator_agent, architect_review_sprint_completion, fix_bug, update_implementation, architect_sprint_intake, update_plan, review_code). Replaced with the canonical 'Do NOT emit a phase event yourself; the orchestrator (or kickoff handler) owns event emission' directive. Also swept the friction-emit code block in meta-fix-bug.md and base-pack/fix_bug.md to point at friction-emit.cjs (matches the pattern shipped for meta-orchestrate in v0.43.14). For workflows that are kickoff-only standalones today (sprint-intake, sprint-plan, collate, retrospective, review-sprint-completion), removing the hardcoded emit means honest-absence of event coverage until the corresponding forge-cli kickoff handlers learn to emit on the LLM's behalf \u2014 a follow-up item. Tests: 1202 pass.",
+    "notes": "Slice-2 fragment-sweep completion. v0.43.14 introduced the orchestrator-emits-everything contract and surgically rewrote the five phase workflows (plan/review-plan/implement/validate/commit) plus their meta sources, but 16 other workflows — every other base-pack workflow body — still carried the pre-Slice-2 'Emit the complete event ... via store-cli emit' instruction and 'Execute Token Reporting' step in their Finalize blocks. Any subagent reading those workflows would faithfully reproduce the exact hallucination class Slice 2 was built to kill (LLM-fabricated model/provider strings). This patch removes those two lines from every remaining workflow — meta sources (meta-approve, meta-update-implementation, meta-review-implementation, meta-review-sprint-completion, meta-sprint-intake, meta-sprint-plan, meta-collate, meta-update-plan, meta-fix-bug, meta-retrospective) and base-pack mirrors (architect_sprint_plan, sprint_retrospective, architect_approve, collator_agent, architect_review_sprint_completion, fix_bug, update_implementation, architect_sprint_intake, update_plan, review_code). Replaced with the canonical 'Do NOT emit a phase event yourself; the orchestrator (or kickoff handler) owns event emission' directive. Also swept the friction-emit code block in meta-fix-bug.md and base-pack/fix_bug.md to point at friction-emit.cjs (matches the pattern shipped for meta-orchestrate in v0.43.14). For workflows that are kickoff-only standalones today (sprint-intake, sprint-plan, collate, retrospective, review-sprint-completion), removing the hardcoded emit means honest-absence of event coverage until the corresponding forge-cli kickoff handlers learn to emit on the LLM's behalf — a follow-up item. Tests: 1202 pass.",
     "regenerate": [
       "workflows:fix_bug",
       "workflows:update_plan",
@@ -160,7 +478,7 @@
   "0.43.13": {
     "version": "0.43.14",
     "date": "2026-05-14",
-    "notes": "Telemetry contract Slice 2 \u2014 orchestrator-emits-everything. Slice 1 (v0.43.13) added `provider` as required and moved cost out of the schema, but subagents were still hand-building 14-field event JSON containing runtime facts (model, provider, eventId, timestamps, iteration) and hallucinating them (HLO-S01-T05 evidence: events carried `provider:\"anthropic\"`/`model:\"claude-sonnet-4-20250514\"` while the subagent actually ran on `glm-5.1:cloud`). Slice 2 makes runtime attribution the orchestrator's responsibility end-to-end. Plugin-side changes: (1) workflow fragments `_fragments/event-emission-schema.md` and `_fragments/friction-emit.md` rewritten in both meta/ and init/base-pack/ \u2014 replace 'build a 14-field event JSON' instructions with 'write {PHASE}-SUMMARY.json; the orchestrator emits the event'. ALL hardcoded example model strings removed (the source of pattern-copy hallucination). (2) Phase meta workflows (meta-plan-task, meta-review-plan, meta-implement, meta-validate, meta-commit) and their base-pack mirrors (plan_task, review_plan, implement_plan, validate_task, commit_task) drop the `Emit the complete event ... via store-cli emit` line and the `Execute Token Reporting` step \u2014 subagents now only write SUMMARY and return. (3) meta-orchestrate.md + base-pack/orchestrate_task.md Event Emission and Friction Emit sections rewritten: orchestrator owns emission; friction is recorded by subagents via the new `friction-emit.cjs` tool which appends judgement-only records to `.forge/cache/FRICTION-{workflow}.jsonl`, drained and stamped with runtime attribution by the orchestrator. (4) New tool `forge/forge/tools/friction-emit.cjs` \u2014 judgement-only CLI that refuses any runtime-attribution flag (--model, --provider, --eventId, timestamps, tokens). (5) New tool `forge/forge/tools/backfill-provider.cjs` \u2014 one-shot helper for the 0.43.13 manual[] item (stamps provider:\"unknown\" on legacy events missing the field; sidecars skipped). Both tools shipped test-first per Iron Law 2. Slice 2 runtime emit site lives in forge-cli (run-task.ts) \u2014 see forge-cli v0.6.5 changelog. Tests: 1202 pass.",
+    "notes": "Telemetry contract Slice 2 — orchestrator-emits-everything. Slice 1 (v0.43.13) added `provider` as required and moved cost out of the schema, but subagents were still hand-building 14-field event JSON containing runtime facts (model, provider, eventId, timestamps, iteration) and hallucinating them (HLO-S01-T05 evidence: events carried `provider:\"anthropic\"`/`model:\"claude-sonnet-4-20250514\"` while the subagent actually ran on `glm-5.1:cloud`). Slice 2 makes runtime attribution the orchestrator's responsibility end-to-end. Plugin-side changes: (1) workflow fragments `_fragments/event-emission-schema.md` and `_fragments/friction-emit.md` rewritten in both meta/ and init/base-pack/ — replace 'build a 14-field event JSON' instructions with 'write {PHASE}-SUMMARY.json; the orchestrator emits the event'. ALL hardcoded example model strings removed (the source of pattern-copy hallucination). (2) Phase meta workflows (meta-plan-task, meta-review-plan, meta-implement, meta-validate, meta-commit) and their base-pack mirrors (plan_task, review_plan, implement_plan, validate_task, commit_task) drop the `Emit the complete event ... via store-cli emit` line and the `Execute Token Reporting` step — subagents now only write SUMMARY and return. (3) meta-orchestrate.md + base-pack/orchestrate_task.md Event Emission and Friction Emit sections rewritten: orchestrator owns emission; friction is recorded by subagents via the new `friction-emit.cjs` tool which appends judgement-only records to `.forge/cache/FRICTION-{workflow}.jsonl`, drained and stamped with runtime attribution by the orchestrator. (4) New tool `forge/forge/tools/friction-emit.cjs` — judgement-only CLI that refuses any runtime-attribution flag (--model, --provider, --eventId, timestamps, tokens). (5) New tool `forge/forge/tools/backfill-provider.cjs` — one-shot helper for the 0.43.13 manual[] item (stamps provider:\"unknown\" on legacy events missing the field; sidecars skipped). Both tools shipped test-first per Iron Law 2. Slice 2 runtime emit site lives in forge-cli (run-task.ts) — see forge-cli v0.6.5 changelog. Tests: 1202 pass.",
     "regenerate": [
       "fragments:event-emission-schema",
       "fragments:friction-emit",
@@ -176,15 +494,15 @@
     ],
     "breaking": false,
     "manual": [
-      "Run `node $FORGE_ROOT/tools/backfill-provider.cjs` once on existing installs to stamp `provider:\"unknown\"` on legacy events missing the field \u2014 this is the helper promised in 0.43.13 manual[]. After backfill, all event reads should validate cleanly."
+      "Run `node $FORGE_ROOT/tools/backfill-provider.cjs` once on existing installs to stamp `provider:\"unknown\"` on legacy events missing the field — this is the helper promised in 0.43.13 manual[]. After backfill, all event reads should validate cleanly."
     ]
   },
   "0.43.12": {
     "version": "0.43.13",
     "date": "2026-05-14",
-    "notes": "Telemetry contract fix (Slice 1) \u2014 refactors the token-usage capture pipeline from a subagent self-probe (which never worked: pi runtime has no `/cost` probe, and the workflow's `tokenSource: \"missing\"` writes were rejected by the schema enum [reported, estimated] causing 8 schema_drift errors per HLO-S01-T04 run) to an orchestrator-owned model. Three changes: (1) event.schema.json adds `provider` as a required field \u2014 same model is priced differently across providers (Anthropic direct vs Bedrock vs Vertex; ZAI cloud vs self-host) and cost is unattributable without it; auto-populated via new discoverProvider() helper from FORGE_PROVIDER / CLAUDE_CODE_PROVIDER env vars, falling back to \"unknown\" rather than guessing. (2) Dropped `estimatedCostUSD` from event + event-sidecar schemas entirely \u2014 cost is derived at collate time from (provider, model, tokens) via tools/lib/pricing.cjs, keeping the dataset truthful when pricing changes. (3) Rewrote meta/workflows/_fragments/finalize.md AND init/base-pack/workflows/_fragments/finalize.md to delete the broken `/cost` probe + `\"missing\"` write instructions; new rule: subagents MUST NOT write token sidecars; orchestrator owns telemetry and emits the canonical event with provider-reported usage. If runtime doesn't surface usage, fields are omitted (honest absence beats placeholder zeros). collate.cjs drops the `missing` bucket from tokenSourceCounts \u2014 token-less events surface as husks instead. Tool changes: store-cli.cjs (CANONICAL_TOKEN_FIELDS + SIDECAR_ACCEPTED_FIELDS adjusted, --provider flag added on record-usage, --estimated-cost-usd flag explicitly rejected with helpful error, discoverProvider() exported); estimate-usage.cjs (removed PRICE_PER_1M heuristic table + DEFAULT_PRICE_PER_1M \u2014 returns only inputTokens/outputTokens/tokenSource); collate.cjs (cost recomputed via pricing.cjs is now the only source). Slice 2 (forge-cli runtime emit site) will wire the orchestrator emit path that consumes this contract \u2014 out of scope here. Tests: 1173 pass, 1 pre-existing FRAGMENT_MAP failure unrelated to this slice. No `.forge/` or `engineering/` edits.",
+    "notes": "Telemetry contract fix (Slice 1) — refactors the token-usage capture pipeline from a subagent self-probe (which never worked: pi runtime has no `/cost` probe, and the workflow's `tokenSource: \"missing\"` writes were rejected by the schema enum [reported, estimated] causing 8 schema_drift errors per HLO-S01-T04 run) to an orchestrator-owned model. Three changes: (1) event.schema.json adds `provider` as a required field — same model is priced differently across providers (Anthropic direct vs Bedrock vs Vertex; ZAI cloud vs self-host) and cost is unattributable without it; auto-populated via new discoverProvider() helper from FORGE_PROVIDER / CLAUDE_CODE_PROVIDER env vars, falling back to \"unknown\" rather than guessing. (2) Dropped `estimatedCostUSD` from event + event-sidecar schemas entirely — cost is derived at collate time from (provider, model, tokens) via tools/lib/pricing.cjs, keeping the dataset truthful when pricing changes. (3) Rewrote meta/workflows/_fragments/finalize.md AND init/base-pack/workflows/_fragments/finalize.md to delete the broken `/cost` probe + `\"missing\"` write instructions; new rule: subagents MUST NOT write token sidecars; orchestrator owns telemetry and emits the canonical event with provider-reported usage. If runtime doesn't surface usage, fields are omitted (honest absence beats placeholder zeros). collate.cjs drops the `missing` bucket from tokenSourceCounts — token-less events surface as husks instead. Tool changes: store-cli.cjs (CANONICAL_TOKEN_FIELDS + SIDECAR_ACCEPTED_FIELDS adjusted, --provider flag added on record-usage, --estimated-cost-usd flag explicitly rejected with helpful error, discoverProvider() exported); estimate-usage.cjs (removed PRICE_PER_1M heuristic table + DEFAULT_PRICE_PER_1M — returns only inputTokens/outputTokens/tokenSource); collate.cjs (cost recomputed via pricing.cjs is now the only source). Slice 2 (forge-cli runtime emit site) will wire the orchestrator emit path that consumes this contract — out of scope here. Tests: 1173 pass, 1 pre-existing FRAGMENT_MAP failure unrelated to this slice. No `.forge/` or `engineering/` edits.",
     "regenerate": [
-      "schemas:events",
+      "schemas:event",
       "schemas:event-sidecar",
       "fragments:finalize",
       "tools:store-cli",
@@ -194,14 +512,14 @@
     ],
     "breaking": false,
     "manual": [
-      "Existing event records on disk that lack `provider` will fail strict validation. On re-running collate or any read path that validates events, stamp legacy records with `provider: \"unknown\"` \u2014 a one-shot backfill helper will ship in a follow-up patch. New events emitted by `store-cli emit` auto-populate `provider` via FORGE_PROVIDER env var or fall back to \"unknown\".",
+      "Existing event records on disk that lack `provider` will fail strict validation. On re-running collate or any read path that validates events, stamp legacy records with `provider: \"unknown\"` — a one-shot backfill helper will ship in a follow-up patch. New events emitted by `store-cli emit` auto-populate `provider` via FORGE_PROVIDER env var or fall back to \"unknown\".",
       "`estimatedCostUSD` is no longer accepted on event or event-sidecar records. Existing records on disk that carry the field will fail strict validation; collate's recomputation path (lib/pricing.cjs) is now authoritative."
     ]
   },
   "0.43.11": {
     "version": "0.43.12",
     "date": "2026-05-14",
-    "notes": "build-base-pack.cjs + build-manifest.cjs allowlist bug \u2014 fragments added to meta/workflows/_fragments/ after the allowlists were last edited never reached init/base-pack/workflows/_fragments/, so the user-facing bundle silently dropped them. Discovered while debugging HLO-S01-T03 plan-phase friction in the testbench: store-cli verb fumble (#95) and event-shape iteration (#87) persisted after /forge:regenerate because store-cli-verbs.md and friction-emit.md were missing from the regenerated `.forge/workflows/_fragments/` even though the workflow body referenced them. Fix: both build-base-pack.cjs (fragment copy loop + expected-files validator) and build-manifest.cjs (FRAGMENT_MAP) now enumerate fragments dynamically from `meta/workflows/_fragments/*.md` instead of from hardcoded lists. Added parity assertion in build-base-pack.test.cjs that base-pack `_fragments/` must equal meta `_fragments/` exactly. Also bumped base-pack-byte-budget overrides for plan_task.md (5120\u21925632), implement_plan.md (5120\u21925888), validate_task.md (4096\u21924608) to absorb the now-included fragment references. Discovered blind spot: the replay-friction harness validates meta-source, not base-pack output \u2014 #95 PASSed in HLO-S01 without ever generating the user-facing fragment. Manifest fragment count 4 \u2192 6 (store-cli-verbs.md + friction-emit.md now shipped).",
+    "notes": "build-base-pack.cjs + build-manifest.cjs allowlist bug — fragments added to meta/workflows/_fragments/ after the allowlists were last edited never reached init/base-pack/workflows/_fragments/, so the user-facing bundle silently dropped them. Discovered while debugging HLO-S01-T03 plan-phase friction in the testbench: store-cli verb fumble (#95) and event-shape iteration (#87) persisted after /forge:regenerate because store-cli-verbs.md and friction-emit.md were missing from the regenerated `.forge/workflows/_fragments/` even though the workflow body referenced them. Fix: both build-base-pack.cjs (fragment copy loop + expected-files validator) and build-manifest.cjs (FRAGMENT_MAP) now enumerate fragments dynamically from `meta/workflows/_fragments/*.md` instead of from hardcoded lists. Added parity assertion in build-base-pack.test.cjs that base-pack `_fragments/` must equal meta `_fragments/` exactly. Also bumped base-pack-byte-budget overrides for plan_task.md (5120→5632), implement_plan.md (5120→5888), validate_task.md (4096→4608) to absorb the now-included fragment references. Discovered blind spot: the replay-friction harness validates meta-source, not base-pack output — #95 PASSed in HLO-S01 without ever generating the user-facing fragment. Manifest fragment count 4 → 6 (store-cli-verbs.md + friction-emit.md now shipped).",
     "regenerate": [
       "tools:build-base-pack",
       "tools:build-manifest",
@@ -215,7 +533,7 @@
   "0.43.10": {
     "version": "0.43.11",
     "date": "2026-05-13",
-    "notes": "HLO-S01 friction-fix sweep \u2014 batched migration covering 10 fixes surfaced by the 2026-05-13 dogfood run on /home/boni/src/forge-testbench/hello/ (umbrella forge#93). All non-breaking; each verified by the replay-friction harness (engineering/runbooks/hlo-s01/ in forge-engineering). Fixes: (a) #78/#76 meta-review-plan: `review-approved` \u2192 `plan-approved` so the review\u2192plan-approved status flip matches the FSM; (b) #80 widen `event.type` enum to cover task-implemented, plan-complete, review-passed and the rest of the emitted set; (c) #79 task FSM permits `planned \u2192 implemented` (was illegal, breaking run-task phase 4 writeback); (d) #96 inline FSM transition table into plan_task / review_plan / implement_plan workflow prose so subagents read state machine inline, not from a sibling fragment; (e) #95 embed store-cli verb cheat-sheet into all run-task / fix-bug phase workflows via new shared `_fragments/store-cli-verbs.md` \u2014 eliminates `forge_store` invocation hallucinations; (f) #84 replace `/cost` slash-command pre-flight in implement/validate/update-implementation with a runtime-conditional probe ({{RUNTIME_COST_CMD}}) \u2014 fixes hard-fail when /cost is unavailable in the runtime; (g) #94 surface resolved `commands.test` (placeholder substitution) in workflow bodies, not just frontmatter \u2014 subagents now see the actual test command; (h) #87 gate `--force` behind `FORGE_ALLOW_FORCE` env in store-cli AND inline canonical event-shape into every workflow emit line (was two-bug pair: LLM-bypass + event mismatch); (i) #82 commit_task no longer hardcodes 'Claude' as Co-author \u2014 uses runtime principal; (j) forge-cli#5 forge-tools piece \u2014 native `--task-suffix` / `--sprint-suffix` flags on store-cli short-form resolution. Row 8 (forge#86 kickoff-shim markers in review_plan/review_code) was already covered by the 0.43.5 wave-2 migration \u2014 no new sub-target needed. forge#7 deferred (SKIPPED: needs live FORGE_DEBUG capture). Also bumped per-file byte budgets in phase-frontmatter.test.cjs across all nine subagent-targeted meta-workflow files (e.g. meta-plan-task 5500\u21926912, meta-implement 5500\u21927168, meta-update-plan 3072\u21923584) \u2014 same precedent as the 0.43.6 wave: legitimate friction-fix growth from #95 cheat-sheet + #96 FSM table + #87 event-shape + #84 cost probe + #94 commands.test inlined across phases. Budgets sized to current bytes + ~10% headroom, 512B-aligned.",
+    "notes": "HLO-S01 friction-fix sweep — batched migration covering 10 fixes surfaced by the 2026-05-13 dogfood run on /home/boni/src/forge-testbench/hello/ (umbrella forge#93). All non-breaking; each verified by the replay-friction harness (engineering/runbooks/hlo-s01/ in forge-engineering). Fixes: (a) #78/#76 meta-review-plan: `review-approved` → `plan-approved` so the review→plan-approved status flip matches the FSM; (b) #80 widen `event.type` enum to cover task-implemented, plan-complete, review-passed and the rest of the emitted set; (c) #79 task FSM permits `planned → implemented` (was illegal, breaking run-task phase 4 writeback); (d) #96 inline FSM transition table into plan_task / review_plan / implement_plan workflow prose so subagents read state machine inline, not from a sibling fragment; (e) #95 embed store-cli verb cheat-sheet into all run-task / fix-bug phase workflows via new shared `_fragments/store-cli-verbs.md` — eliminates `forge_store` invocation hallucinations; (f) #84 replace `/cost` slash-command pre-flight in implement/validate/update-implementation with a runtime-conditional probe ({{RUNTIME_COST_CMD}}) — fixes hard-fail when /cost is unavailable in the runtime; (g) #94 surface resolved `commands.test` (placeholder substitution) in workflow bodies, not just frontmatter — subagents now see the actual test command; (h) #87 gate `--force` behind `FORGE_ALLOW_FORCE` env in store-cli AND inline canonical event-shape into every workflow emit line (was two-bug pair: LLM-bypass + event mismatch); (i) #82 commit_task no longer hardcodes 'Claude' as Co-author — uses runtime principal; (j) forge-cli#5 forge-tools piece — native `--task-suffix` / `--sprint-suffix` flags on store-cli short-form resolution. Row 8 (forge#86 kickoff-shim markers in review_plan/review_code) was already covered by the 0.43.5 wave-2 migration — no new sub-target needed. forge#7 deferred (SKIPPED: needs live FORGE_DEBUG capture). Also bumped per-file byte budgets in phase-frontmatter.test.cjs across all nine subagent-targeted meta-workflow files (e.g. meta-plan-task 5500→6912, meta-implement 5500→7168, meta-update-plan 3072→3584) — same precedent as the 0.43.6 wave: legitimate friction-fix growth from #95 cheat-sheet + #96 FSM table + #87 event-shape + #84 cost probe + #94 commands.test inlined across phases. Budgets sized to current bytes + ~10% headroom, 512B-aligned.",
     "regenerate": [
       "workflows:plan_task",
       "workflows:review_plan",
@@ -223,7 +541,7 @@
       "workflows:validate_task",
       "workflows:update_implementation",
       "workflows:commit_task",
-      "schemas:events",
+      "schemas:event",
       "tools:store-cli",
       "fragments:store-cli-verbs",
       "tools:integrity"
@@ -234,7 +552,7 @@
   "0.43.9": {
     "version": "0.43.10",
     "date": "2026-05-13",
-    "notes": "Verdict-source refactor: preflight-gate `after <phase>` predicates now read structured verdicts from store.task.summaries.<canonical>.verdict (and task.status for approve), not regex-parse markdown. New module forge/tools/read-verdict.cjs centralises the phase.role \u2192 canonical-summary-key mapping (mirrors VALID_SUMMARY_PHASES) and the approve-via-status sentinel. Eliminates three classes of recurring bugs: (a) forge#91 (approve phase markdown-vs-store mismatch), (b) forge-cli#11 (review-code \u2192 code_review key reversal), (c) the underscore-swap defensive fallback dance in run-task.ts (still present, now redundant). Removed: forge/tools/parse-verdict.cjs and its test (no consumers remaining). preflight()'s `verdictSources` parameter and the `resolveVerdictSources` helper are gone \u2014 `after` reads live from state.task / state.bug directly. The `**Verdict:**` line in review markdown is now a human breadcrumb only; the byte-budget lint asserting its presence is retained but documented as advisory. meta-approve.md updated to clarify the markdown line is not load-bearing. Live testbench HLO-S01-T01 commit preflight: EXIT=0 via the new store path. +11 read-verdict unit tests, +2 preflight tests (approve via status; revision in store).",
+    "notes": "Verdict-source refactor: preflight-gate `after <phase>` predicates now read structured verdicts from store.task.summaries.<canonical>.verdict (and task.status for approve), not regex-parse markdown. New module forge/tools/read-verdict.cjs centralises the phase.role → canonical-summary-key mapping (mirrors VALID_SUMMARY_PHASES) and the approve-via-status sentinel. Eliminates three classes of recurring bugs: (a) forge#91 (approve phase markdown-vs-store mismatch), (b) forge-cli#11 (review-code → code_review key reversal), (c) the underscore-swap defensive fallback dance in run-task.ts (still present, now redundant). Removed: forge/tools/parse-verdict.cjs and its test (no consumers remaining). preflight()'s `verdictSources` parameter and the `resolveVerdictSources` helper are gone — `after` reads live from state.task / state.bug directly. The `**Verdict:**` line in review markdown is now a human breadcrumb only; the byte-budget lint asserting its presence is retained but documented as advisory. meta-approve.md updated to clarify the markdown line is not load-bearing. Live testbench HLO-S01-T01 commit preflight: EXIT=0 via the new store path. +11 read-verdict unit tests, +2 preflight tests (approve via status; revision in store).",
     "regenerate": [
       "tools:preflight-gate",
       "tools:read-verdict",
@@ -256,7 +574,7 @@
   "0.43.7": {
     "version": "0.43.8",
     "date": "2026-05-13",
-    "notes": "preflight-gate.cjs: gate-less phases now pass through (exit 0) instead of escalating (exit 2). Some run-task phases are intentionally gate-less by design \u2014 writeback (collator regen) has no predecessor verdict to check. The previous semantic conflated `phase not declared in any workflow` and `workflow declares no gate block for phase` with `misconfiguration` (exit 2), causing live regression at phase 7 (writeback) of /forge:run-task HLO-S01-T01: `\u00d7 preflight gate escalated for phase writeback (exit 2); manual intervention required`. Both `no workflow declares phase` and `no gate block for declared phase` now exit 0 with an informational stderr note. Exit 2 stays reserved for real argument / parse errors (unchanged). +1 regression test (sibling case: workflow exists, no gate block).",
+    "notes": "preflight-gate.cjs: gate-less phases now pass through (exit 0) instead of escalating (exit 2). Some run-task phases are intentionally gate-less by design — writeback (collator regen) has no predecessor verdict to check. The previous semantic conflated `phase not declared in any workflow` and `workflow declares no gate block for phase` with `misconfiguration` (exit 2), causing live regression at phase 7 (writeback) of /forge:run-task HLO-S01-T01: `× preflight gate escalated for phase writeback (exit 2); manual intervention required`. Both `no workflow declares phase` and `no gate block for declared phase` now exit 0 with an informational stderr note. Exit 2 stays reserved for real argument / parse errors (unchanged). +1 regression test (sibling case: workflow exists, no gate block).",
     "regenerate": [
       "tools:preflight-gate"
     ],
@@ -266,7 +584,7 @@
   "0.43.6": {
     "version": "0.43.7",
     "date": "2026-05-13",
-    "notes": "Pack-06 materialization-marker regression fix, third (final) wave + structural lint. Adds Iron Laws + Store-Write Verification sections (plus persona-load step and `forge_store` token) to the remaining six meta workflows that subagent-target the run-task / fix-bug pipeline: meta-validate.md, meta-approve.md, meta-collate.md, meta-commit.md, meta-update-plan.md, meta-update-implementation.md. Live testbench surfaced the gap at phase 5 (validate) of /forge:run-task: kickoff shim hard-failed with `\u00d7 workflow regression: Store-Write Verification not found in validate_task.md`. Three waves (0.43.2 plan/implement, 0.43.5 review-plan/review-code, 0.43.6 validate/approve/collate/commit/update-plan/update-impl) is the cost of discovering one phase at a time. Encoded a regression lint in base-pack-byte-budget.test.cjs (`phase files carry kickoff-shim markers`) that asserts all four markers across every PHASE_FILE \u2014 future drop-throughs fail the build, not the smoke test. Also bumped per-file byte budgets for meta-validate.md (4096\u21925120), meta-approve.md / meta-commit.md (3072\u21924096). See forge#? (this entry's GH issue).",
+    "notes": "Pack-06 materialization-marker regression fix, third (final) wave + structural lint. Adds Iron Laws + Store-Write Verification sections (plus persona-load step and `forge_store` token) to the remaining six meta workflows that subagent-target the run-task / fix-bug pipeline: meta-validate.md, meta-approve.md, meta-collate.md, meta-commit.md, meta-update-plan.md, meta-update-implementation.md. Live testbench surfaced the gap at phase 5 (validate) of /forge:run-task: kickoff shim hard-failed with `× workflow regression: Store-Write Verification not found in validate_task.md`. Three waves (0.43.2 plan/implement, 0.43.5 review-plan/review-code, 0.43.6 validate/approve/collate/commit/update-plan/update-impl) is the cost of discovering one phase at a time. Encoded a regression lint in base-pack-byte-budget.test.cjs (`phase files carry kickoff-shim markers`) that asserts all four markers across every PHASE_FILE — future drop-throughs fail the build, not the smoke test. Also bumped per-file byte budgets for meta-validate.md (4096→5120), meta-approve.md / meta-commit.md (3072→4096). See forge#? (this entry's GH issue).",
     "regenerate": [
       "workflows:validate_task",
       "workflows:architect_approve",
@@ -281,7 +599,7 @@
   "0.43.5": {
     "version": "0.43.6",
     "date": "2026-05-13",
-    "notes": "preflight-gate.cjs artifact-dir resolution fix. Two compounding bugs surfaced when a sprint dir contained an artifact directory named exactly `<taskId>` (no `-<slug>` suffix \u2014 modern convention). (1) resolveTaskArtifactDir Pass 1 required `entry.startsWith(taskId + '-')`, rejecting exact-match entries. Pass 2's `<sprintId>-` prefix matcher also didn't apply when taskId already embeds sprintId (e.g. taskId=`HLO-S01-T01`, sprintId=`S01`). resolveTaskArtifactDir returned null. (2) The fallback then set `taskArtifactPath = taskRecord.path` directly \u2014 but `taskRecord.path` is the primary source FILE (e.g. `TASK_PROMPT.md`), not a directory. Predecessor-review resolution then appended `PLAN_REVIEW.md` to the file path, producing bogus paths like `.../TASK_PROMPT.md/PLAN_REVIEW.md` (ENOTDIR), failing every `after <phase>` gate. Fix: Pass 1 now also accepts `entry === taskId`; fallback dirname()s task.path when it has a file extension. Live testbench regression: phase 3 (implement) of `/forge:run-task HLO-S01-T01` was hard-failing preflight. After patch, EXIT=0. See forge#?.",
+    "notes": "preflight-gate.cjs artifact-dir resolution fix. Two compounding bugs surfaced when a sprint dir contained an artifact directory named exactly `<taskId>` (no `-<slug>` suffix — modern convention). (1) resolveTaskArtifactDir Pass 1 required `entry.startsWith(taskId + '-')`, rejecting exact-match entries. Pass 2's `<sprintId>-` prefix matcher also didn't apply when taskId already embeds sprintId (e.g. taskId=`HLO-S01-T01`, sprintId=`S01`). resolveTaskArtifactDir returned null. (2) The fallback then set `taskArtifactPath = taskRecord.path` directly — but `taskRecord.path` is the primary source FILE (e.g. `TASK_PROMPT.md`), not a directory. Predecessor-review resolution then appended `PLAN_REVIEW.md` to the file path, producing bogus paths like `.../TASK_PROMPT.md/PLAN_REVIEW.md` (ENOTDIR), failing every `after <phase>` gate. Fix: Pass 1 now also accepts `entry === taskId`; fallback dirname()s task.path when it has a file extension. Live testbench regression: phase 3 (implement) of `/forge:run-task HLO-S01-T01` was hard-failing preflight. After patch, EXIT=0. See forge#?.",
     "regenerate": [
       "tools:preflight-gate"
     ],
@@ -291,7 +609,7 @@
   "0.43.4": {
     "version": "0.43.5",
     "date": "2026-05-13",
-    "notes": "Pack-06 materialization-marker regression fix, second wave. Adds Iron Laws + Store-Write Verification sections (plus `.forge/personas/supervisor.md` persona-load step and `forge_store` tokens) to meta-review-plan.md and meta-review-implementation.md so generated review_plan.md and review_code.md carry the four markers required by forge-cli /forge:run-task's per-phase kickoff shim. Without these markers, every fresh init since 0.43.2 has shipped review-plan / review-code workflows that hard-fail phase 2 (and phase 4) of /forge:run-task with `\u00d7 workflow regression: Store-Write Verification not found ...`. Root cause: 0.43.2 patched meta-plan-task.md and meta-implement.md, but the symmetric review metas were missed. Side-effect: per-file byte budgets bumped for review_plan.md / review_code.md (4096\u21925120) and meta-review-plan.md / meta-review-implementation.md (3200/4200\u21924500/5500) to fit the marker blocks. See forge#85.",
+    "notes": "Pack-06 materialization-marker regression fix, second wave. Adds Iron Laws + Store-Write Verification sections (plus `.forge/personas/supervisor.md` persona-load step and `forge_store` tokens) to meta-review-plan.md and meta-review-implementation.md so generated review_plan.md and review_code.md carry the four markers required by forge-cli /forge:run-task's per-phase kickoff shim. Without these markers, every fresh init since 0.43.2 has shipped review-plan / review-code workflows that hard-fail phase 2 (and phase 4) of /forge:run-task with `× workflow regression: Store-Write Verification not found ...`. Root cause: 0.43.2 patched meta-plan-task.md and meta-implement.md, but the symmetric review metas were missed. Side-effect: per-file byte budgets bumped for review_plan.md / review_code.md (4096→5120) and meta-review-plan.md / meta-review-implementation.md (3200/4200→4500/5500) to fit the marker blocks. See forge#85.",
     "regenerate": [
       "workflows:review_plan",
       "workflows:review_code"
@@ -312,7 +630,7 @@
   "0.43.2": {
     "version": "0.43.3",
     "date": "2026-05-10",
-    "notes": "Adds workflows/enhance.md to base-pack (FORGE-S20-T04 sprint-completion gap fix). meta-enhance.md now generates init/base-pack/workflows/enhance.md via the standard transformWorkflow path; build-base-pack expects 20 workflow files (was 19); enhance.md ships with Iron Laws + Store-Write Verification + forge_store + engineer.md markers required by the forge-cli /forge:enhance kickoff shim. Without this file, /forge:enhance hard-failed every fresh init with `\u00d7 forge:enhance \u2014 workflow not found at .forge/workflows/enhance.md`. enhance.md is orchestrator-only audience and exempt from the 4KB phase-file byte budget. Pairs with forge-cli v0.5.7.",
+    "notes": "Adds workflows/enhance.md to base-pack (FORGE-S20-T04 sprint-completion gap fix). meta-enhance.md now generates init/base-pack/workflows/enhance.md via the standard transformWorkflow path; build-base-pack expects 20 workflow files (was 19); enhance.md ships with Iron Laws + Store-Write Verification + forge_store + engineer.md markers required by the forge-cli /forge:enhance kickoff shim. Without this file, /forge:enhance hard-failed every fresh init with `× forge:enhance — workflow not found at .forge/workflows/enhance.md`. enhance.md is orchestrator-only audience and exempt from the 4KB phase-file byte budget. Pairs with forge-cli v0.5.7.",
     "regenerate": [
       "workflows:enhance"
     ],
@@ -322,7 +640,7 @@
   "0.43.1": {
     "version": "0.43.2",
     "date": "2026-05-10",
-    "notes": "Pack-06 materialization-marker regression fix. Adds Iron Laws + Store-Write Verification sections (plus persona-load step and forge_store token) to meta-plan-task.md and meta-implement.md so generated plan_task.md and implement_plan.md carry the four markers required by forge-cli /forge:plan and /forge:implement kickoff shims. Without these markers, every fresh init produced workflows that hard-failed on dispatch with `\u00d7 workflow regression: Store-Write Verification not found` (and three siblings: Iron Laws, forge_store, persona file path). Root cause: forge-cli FORGE-S20-T04/T05/T06 added kickoff-shim materialization preconditions but never updated the corresponding meta sources or base-pack regen. Side-effect: bumps base-pack byte budget for plan_task.md/implement_plan.md from 4096\u21925120 (per-file overrides) and meta-plan-task/meta-implement from 4096\u21925500 to fit the marker blocks. Pairs with forge-cli v0.5.6.",
+    "notes": "Pack-06 materialization-marker regression fix. Adds Iron Laws + Store-Write Verification sections (plus persona-load step and forge_store token) to meta-plan-task.md and meta-implement.md so generated plan_task.md and implement_plan.md carry the four markers required by forge-cli /forge:plan and /forge:implement kickoff shims. Without these markers, every fresh init produced workflows that hard-failed on dispatch with `× workflow regression: Store-Write Verification not found` (and three siblings: Iron Laws, forge_store, persona file path). Root cause: forge-cli FORGE-S20-T04/T05/T06 added kickoff-shim materialization preconditions but never updated the corresponding meta sources or base-pack regen. Side-effect: bumps base-pack byte budget for plan_task.md/implement_plan.md from 4096→5120 (per-file overrides) and meta-plan-task/meta-implement from 4096→5500 to fit the marker blocks. Pairs with forge-cli v0.5.6.",
     "regenerate": [
       "workflows:plan_task",
       "workflows:implement_plan"
@@ -333,7 +651,7 @@
   "0.43.0": {
     "version": "0.43.1",
     "date": "2026-05-10",
-    "notes": "Direct-exec contract patch. Replaces all `/forge:store ...` slash-command references in init/base-pack/workflows/*.md (and _fragments/) with the canonical `node \"$FORGE_ROOT/tools/store-cli.cjs\" ...` direct-cjs form already used by meta/workflows/*.md. Pairs with forge-cli v0.5.1 (system-prompt tool-discipline block, kickoff-prompt rewrites, and bin fast-path for `forge {store|collate|validate-store|store-query} ...`). Root cause: cartographer testbench observed haiku-4-5 burning 26-220s per `bash forge store ...` shell-out \u2014 each invocation spawned a fresh pi/agent loop. Fix: prescriptive system prompt + canonical workflow text + bin fast-path. Existing `/forge:store` materialized workflows remain functional under the bin fast-path; no manual migration required for projects on v0.43.0.",
+    "notes": "Direct-exec contract patch. Replaces all `/forge:store ...` slash-command references in init/base-pack/workflows/*.md (and _fragments/) with the canonical `node \"$FORGE_ROOT/tools/store-cli.cjs\" ...` direct-cjs form already used by meta/workflows/*.md. Pairs with forge-cli v0.5.1 (system-prompt tool-discipline block, kickoff-prompt rewrites, and bin fast-path for `forge {store|collate|validate-store|store-query} ...`). Root cause: cartographer testbench observed haiku-4-5 burning 26-220s per `bash forge store ...` shell-out — each invocation spawned a fresh pi/agent loop. Fix: prescriptive system prompt + canonical workflow text + bin fast-path. Existing `/forge:store` materialized workflows remain functional under the bin fast-path; no manual migration required for projects on v0.43.0.",
     "regenerate": [
       "workflows:base-pack-store-cli-form"
     ],
@@ -343,7 +661,7 @@
   "0.42.0": {
     "version": "0.43.0",
     "date": "2026-05-10",
-    "notes": "FORGE-S20 Sprint A \u2014 Friction emit channel + foundation. T00 lands the writer side of the friction channel: event.schema.json gains `type:\"friction\"` enum with conditional required {workflow, persona, issue} via a JSON-Schema `allOf if/then` block; validate-store.cjs gains a minimal `allOf if/then required` interpreter; five meta-workflows (implement, fix-bug, validate, plan-task, orchestrate) now carry an explicit Friction Emit section describing trigger conditions and the canonical flat-payload `node \"$FORGE_ROOT/tools/store-cli.cjs\" emit` shape. T01 narrows the optional slots reserved by T00: `subkind` is constrained to a frozen enum (skill_unused|skill_failed|skill_missing|skill_stale|skill_redundant) plus a reserved `^x_[a-z_]+$` experimental namespace (no migration required for x_*), encoded as a single combined regex pattern; `evidence` is shaped into a closed object (trajectory_excerpt:string, tool_errors:string[], retrieval_score:number 0..1, skillId:string ref); validate-store.cjs gains a minimal `pattern` interpreter on string fields. Unblocks Plan 08 Phase B (dynamic skill curation): /forge:enhance --phase 2 reader has been waiting for typed writers since S13-T08. Non-breaking: events without `type` continue to validate exactly as before, and T00-shaped friction events without subkind/evidence remain valid because those slots are not in the friction allOf then-required block.",
+    "notes": "FORGE-S20 Sprint A — Friction emit channel + foundation. T00 lands the writer side of the friction channel: event.schema.json gains `type:\"friction\"` enum with conditional required {workflow, persona, issue} via a JSON-Schema `allOf if/then` block; validate-store.cjs gains a minimal `allOf if/then required` interpreter; five meta-workflows (implement, fix-bug, validate, plan-task, orchestrate) now carry an explicit Friction Emit section describing trigger conditions and the canonical flat-payload `node \"$FORGE_ROOT/tools/store-cli.cjs\" emit` shape. T01 narrows the optional slots reserved by T00: `subkind` is constrained to a frozen enum (skill_unused|skill_failed|skill_missing|skill_stale|skill_redundant) plus a reserved `^x_[a-z_]+$` experimental namespace (no migration required for x_*), encoded as a single combined regex pattern; `evidence` is shaped into a closed object (trajectory_excerpt:string, tool_errors:string[], retrieval_score:number 0..1, skillId:string ref); validate-store.cjs gains a minimal `pattern` interpreter on string fields. Unblocks Plan 08 Phase B (dynamic skill curation): /forge:enhance --phase 2 reader has been waiting for typed writers since S13-T08. Non-breaking: events without `type` continue to validate exactly as before, and T00-shaped friction events without subkind/evidence remain valid because those slots are not in the friction allOf then-required block.",
     "regenerate": [
       "events:friction-emit",
       "events:friction-subkind",
@@ -362,7 +680,7 @@
   "0.41.0": {
     "version": "0.42.0",
     "date": "2026-05-10",
-    "notes": "Release-routine catch-up bump. No code changes. Promotes v0.40.3 (substitute-placeholders --target pi) and v0.41.0 (store-cli describe/template + validate hint) cumulatively to skillforge marketplace under a single tag. Users on v0.40+ \u2192 /forge:update is non-breaking. Users on <v0.40 still need the v0.40.0 manual migration path (run /forge:update then /forge:migrate per v0.40.0 entry).",
+    "notes": "Release-routine catch-up bump. No code changes. Promotes v0.40.3 (substitute-placeholders --target pi) and v0.41.0 (store-cli describe/template + validate hint) cumulatively to skillforge marketplace under a single tag. Users on v0.40+ → /forge:update is non-breaking. Users on <v0.40 still need the v0.40.0 manual migration path (run /forge:update then /forge:migrate per v0.40.0 entry).",
     "regenerate": [],
     "breaking": false,
     "manual": []
@@ -370,7 +688,7 @@
   "0.40.3": {
     "version": "0.41.0",
     "date": "2026-05-09",
-    "notes": "Add store-cli describe/template subcommands and validate.js error hint (FORGE-BUG-029-friction). describe <entity> prints raw JSON Schema; template <entity> prints canonical sample with required fields populated. validateRecord errors now include a hint pointing to template/describe when entity is known. Reduces write\u2192reject\u2192retry friction on weak/non-Anthropic models. No breaking changes.",
+    "notes": "Add store-cli describe/template subcommands and validate.js error hint (FORGE-BUG-029-friction). describe <entity> prints raw JSON Schema; template <entity> prints canonical sample with required fields populated. validateRecord errors now include a hint pointing to template/describe when entity is known. Reduces write→reject→retry friction on weak/non-Anthropic models. No breaking changes.",
     "regenerate": [
       "tools:store-cli",
       "tools:lib:validate"
@@ -409,11 +727,11 @@
       "workflows:migrate_structural",
       "workflows:_fragments",
       "schemas:config",
-      "schemas:update-check-cache",
       "schemas:structure-manifest"
     ],
     "breaking": false,
-    "manual": []
+    "manual": [],
+    "notes_addendum": "removed schemas:update-check-cache target — not a schema (runtime cache only); the target was never resolvable. Removed by FORGE-S25-T12 (N-S-1)."
   },
   "0.40.0": {
     "version": "0.40.1",
@@ -429,7 +747,7 @@
   "0.32.0": {
     "version": "0.40.0",
     "date": "2026-05-02",
-    "notes": "Base-pack init with progressive enhancement (S13 \u2014 T02\u2013T06 + T08\u2013T10 + T11 friction reconciliation). Replaces multi-minute LLM cold-start init with a deterministic 4-phase pipeline (Collect \u2192 Discover \u2192 Materialize \u2192 Register, ~30\u201345s). Working artefacts ship as a base-pack with {{KEY}} placeholders; init substitutes from config.json + project-context.json (no LLM in materialization). New project-context.json schema (T02), substitute-placeholders.cjs tool (T03), 4-phase sdlc-init.md (T04), versioned structural snapshots in structure-versions.json (T05), npm run build-base-pack regeneration script (T06), enhancement agent skill at meta/workflows/meta-enhance.md and commands/enhance.md (T08), post-init + post-sprint hooks (T09), migration agent at meta/workflows/meta-migrate.md (T10), and bucket-A friction fixes (T11) covering forge#71 (7 sub-bugs in /forge:update) and forge#72 (preflight-gate workflow shadowing). Breaking: --fast aliases to default; init-progress.json is now 4-phase; structure-versions.json + project-context.json are net-new files; manage-versions.cjs is now the gateway for snapshot writes.",
+    "notes": "Base-pack init with progressive enhancement (S13 — T02–T06 + T08–T10 + T11 friction reconciliation). Replaces multi-minute LLM cold-start init with a deterministic 4-phase pipeline (Collect → Discover → Materialize → Register, ~30–45s). Working artefacts ship as a base-pack with {{KEY}} placeholders; init substitutes from config.json + project-context.json (no LLM in materialization). New project-context.json schema (T02), substitute-placeholders.cjs tool (T03), 4-phase sdlc-init.md (T04), versioned structural snapshots in structure-versions.json (T05), npm run build-base-pack regeneration script (T06), enhancement agent skill at meta/workflows/meta-enhance.md and commands/enhance.md (T08), post-init + post-sprint hooks (T09), migration agent at meta/workflows/meta-migrate.md (T10), and bucket-A friction fixes (T11) covering forge#71 (7 sub-bugs in /forge:update) and forge#72 (preflight-gate workflow shadowing). Breaking: --fast aliases to default; init-progress.json is now 4-phase; structure-versions.json + project-context.json are net-new files; manage-versions.cjs is now the gateway for snapshot writes.",
     "regenerate": [
       "workflows:orchestrate_task",
       "workflows:fix_bug",
@@ -465,10 +783,10 @@
     ],
     "breaking": true,
     "manual": [
-      "Init flow is now 4 phases (Collect \u2192 Discover \u2192 Materialize \u2192 Register). --fast and --full both run the same deterministic pipeline; existing init-progress.json checkpoints from 12-phase runs are deleted automatically on resume.",
+      "Init flow is now 4 phases (Collect → Discover → Materialize → Register). --fast and --full both run the same deterministic pipeline; existing init-progress.json checkpoints from 12-phase runs are deleted automatically on resume.",
       "structure-versions.json and project-context.json are net-new files at .forge/. Existing installations without them are migrated by /forge:migrate (T10).",
-      "Existing users on v0.28\u2013v0.30.x: run /forge:update to install the new tools and workflows, then /forge:migrate to synthesise project-context.json from existing .forge/ artefacts. /forge:migrate archives the pre-migration .forge/ contents to .forge/archive/pre-migration/.",
-      "After /forge:update, run /forge:update-tools to install the three new schemas (project-context.schema.json, structure-versions.schema.json, project-overlay.schema.json) into .forge/schemas/. /forge:update does not regenerate schemas \u2014 this is by design (T11 forge#71-bug3); /forge:update-tools is the dedicated path for schema installation.",
+      "Existing users on v0.28–v0.30.x: run /forge:update to install the new tools and workflows, then /forge:migrate to synthesise project-context.json from existing .forge/ artefacts. /forge:migrate archives the pre-migration .forge/ contents to .forge/archive/pre-migration/.",
+      "After /forge:update, run /forge:update-tools to install the three new schemas (project-context.schema.json, structure-versions.schema.json, project-overlay.schema.json) into .forge/schemas/. /forge:update does not regenerate schemas — this is by design (T11 forge#71-bug3); /forge:update-tools is the dedicated path for schema installation.",
       "After /forge:update-tools, run /forge:health to verify integrity.json and snapshot v0 register cleanly.",
       "T11 fixes: /forge:update Step 1 baseline derivation now uses localVersion ?? migratedFrom ?? LOCAL_VERSION; preflight-gate.cjs no longer requires --workflow workaround for orchestrate_task; integrity.json regenerated from current hashes (no false-positive on /forge:health post-update)."
     ]
@@ -476,7 +794,7 @@
   "0.31.0": {
     "version": "0.32.0",
     "date": "2026-05-01",
-    "notes": "Init flow rewrite (T04): replace 12-phase init with 4-phase model (Collect \u2192 Discover \u2192 Materialize \u2192 Register). forge/commands/init.md and forge/init/sdlc-init.md fully rewritten. Phase 3 calls substitute-placeholders.cjs to produce fully functional workflows (no stubs). Phase 4 writes structure-versions.json at .forge/structure-versions.json (T05 stub), generation-manifest.json, persona-pack.json, context-pack.md/json, init-context.json/md, store seed, update-check cache, and invokes refresh-kb-links. --fast and --full flags accepted as no-ops (both run identical 4-phase flow). Old 12-phase checkpoint files deleted automatically on resume.",
+    "notes": "Init flow rewrite (T04): replace 12-phase init with 4-phase model (Collect → Discover → Materialize → Register). forge/commands/init.md and forge/init/sdlc-init.md fully rewritten. Phase 3 calls substitute-placeholders.cjs to produce fully functional workflows (no stubs). Phase 4 writes structure-versions.json at .forge/structure-versions.json (T05 stub), generation-manifest.json, persona-pack.json, context-pack.md/json, init-context.json/md, store seed, update-check cache, and invokes refresh-kb-links. --fast and --full flags accepted as no-ops (both run identical 4-phase flow). Old 12-phase checkpoint files deleted automatically on resume.",
     "regenerate": [],
     "breaking": false,
     "manual": []
@@ -492,7 +810,7 @@
   "0.29.0": {
     "version": "0.30.0",
     "date": "2026-05-01",
-    "notes": "Prompt-efficiency structural cut (T01_6): (1) phase meta sources split by audience \u2014 orchestrate_task/fix_bug carry audience:orchestrator-only, all phase files carry audience:subagent with context: block; (2) PROJECT_OVERLAY replaces mandatory MASTER_INDEX.md reads \u2014 build-overlay.cjs materialises a \u22641kB task-scoped index slice injected by the orchestrator; architecture_block is now conditional on phase.context.architecture; (3) store-cli success-path stdout is now silent \u2014 pass --verbose for legacy JSON echo; (4) new _fragments/finalize.md carries the /cost sidecar contract; (5) review-code and validate phases default to diff-first read mode. Breaking: store-cli JSON stdout no longer emitted on success.",
+    "notes": "Prompt-efficiency structural cut (T01_6): (1) phase meta sources split by audience — orchestrate_task/fix_bug carry audience:orchestrator-only, all phase files carry audience:subagent with context: block; (2) PROJECT_OVERLAY replaces mandatory MASTER_INDEX.md reads — build-overlay.cjs materialises a ≤1kB task-scoped index slice injected by the orchestrator; architecture_block is now conditional on phase.context.architecture; (3) store-cli success-path stdout is now silent — pass --verbose for legacy JSON echo; (4) new _fragments/finalize.md carries the /cost sidecar contract; (5) review-code and validate phases default to diff-first read mode. Breaking: store-cli JSON stdout no longer emitted on success.",
     "regenerate": [
       "workflows:orchestrate_task",
       "workflows:fix_bug",
@@ -518,7 +836,7 @@
   "0.28.1": {
     "version": "0.29.0",
     "date": "2026-04-29",
-    "notes": "Security hardening (FORGE-BUG-016): fix 5 critical findings from security scan v0.28.0. (1) Bulk permission escalation: persist only matched rule instead of all 31 rules. (2) Remove node -e/p auto-approve \u2014 arbitrary code execution requires explicit approval. (3) Add domain allowlist for update URLs. (4) Block prototype pollution (__proto__/constructor/prototype) in getByPath/setByPath. (5) Add path traversal guard to cmdProgress/cmdProgressClear. Also scopes broad wildcards (touch, rmdir, rm -f) and adds require.main guard to forge-permissions.js.",
+    "notes": "Security hardening (FORGE-BUG-016): fix 5 critical findings from security scan v0.28.0. (1) Bulk permission escalation: persist only matched rule instead of all 31 rules. (2) Remove node -e/p auto-approve — arbitrary code execution requires explicit approval. (3) Add domain allowlist for update URLs. (4) Block prototype pollution (__proto__/constructor/prototype) in getByPath/setByPath. (5) Add path traversal guard to cmdProgress/cmdProgressClear. Also scopes broad wildcards (touch, rmdir, rm -f) and adds require.main guard to forge-permissions.js.",
     "regenerate": [
       "hooks:forge-permissions",
       "hooks:check-update",
@@ -527,7 +845,7 @@
     ],
     "breaking": true,
     "manual": [
-      "node -e one-liners will now prompt for approval \u2014 this is intentional. Run /forge:update to refresh hooks and tools."
+      "node -e one-liners will now prompt for approval — this is intentional. Run /forge:update to refresh hooks and tools."
     ]
   },
   "0.27.1": {
@@ -571,7 +889,7 @@
     ],
     "breaking": false,
     "manual": [
-      "Restart Claude Code after updating for the new hook to take effect. On first Forge command, approve each permission prompt once \u2014 they will persist for future sessions."
+      "Restart Claude Code after updating for the new hook to take effect. On first Forge command, approve each permission prompt once — they will persist for future sessions."
     ]
   },
   "0.24.2": {
@@ -690,14 +1008,14 @@
   "0.17.1": {
     "version": "0.18.0",
     "date": "2026-04-19",
-    "notes": "Write-boundary schema enforcement. New PreToolUse hook (hooks/validate-write.js) intercepts Write/Edit/MultiEdit against Forge-owned paths under .forge/store/ and validates the proposed contents against the matching schema \u2014 task, sprint, bug, feature, event, event-sidecar, collation-state, and progress-log entries. Three new schemas added (event-sidecar, progress-entry, collation-state). store-cli gains schema enforcement on the four previously unvalidated write paths (sidecar emit, sidecar merge, progress append, collation-state write). Shared validator extracted to tools/lib/validate.js and reused by both the hook and store-cli. Emergency bypass via FORGE_SKIP_WRITE_VALIDATION=1, which also appends an audit line to the affected sprint's progress.log.",
+    "notes": "Write-boundary schema enforcement. New PreToolUse hook (hooks/validate-write.js) intercepts Write/Edit/MultiEdit against Forge-owned paths under .forge/store/ and validates the proposed contents against the matching schema — task, sprint, bug, feature, event, event-sidecar, collation-state, and progress-log entries. Three new schemas added (event-sidecar, progress-entry, collation-state). store-cli gains schema enforcement on the four previously unvalidated write paths (sidecar emit, sidecar merge, progress append, collation-state write). Shared validator extracted to tools/lib/validate.js and reused by both the hook and store-cli. Emergency bypass via FORGE_SKIP_WRITE_VALIDATION=1, which also appends an audit line to the affected sprint's progress.log.",
     "regenerate": [
       "hooks",
       "schemas"
     ],
     "breaking": false,
     "manual": [
-      "Run /forge:update to install the new write-boundary hook. Any existing tooling that writes malformed JSON to .forge/store/ will now be rejected at write time \u2014 fix the data, don't bypass the hook."
+      "Run /forge:update to install the new write-boundary hook. Any existing tooling that writes malformed JSON to .forge/store/ will now be rejected at write time — fix the data, don't bypass the hook."
     ]
   },
   "0.17.0": {
@@ -750,7 +1068,7 @@
   "0.14.0": {
     "version": "0.14.1",
     "date": "2026-04-18",
-    "notes": "collate now generates Sprint, Task, and Bug INDEX.md files \u2014 closes broken knowledge graph links from MASTER_INDEX.md. refresh-kb-links skill gains KB integrity check that warns when INDEX files are missing.",
+    "notes": "collate now generates Sprint, Task, and Bug INDEX.md files — closes broken knowledge graph links from MASTER_INDEX.md. refresh-kb-links skill gains KB integrity check that warns when INDEX files are missing.",
     "regenerate": [],
     "breaking": false,
     "manual": []
@@ -766,7 +1084,7 @@
   "0.13.0": {
     "version": "0.13.1",
     "date": "2026-04-18",
-    "notes": "Tomoshibi Oracle warns before config changes that require regeneration \u2014 project.prefix change now shows impact and exact follow-up command before [Y/n] prompt.",
+    "notes": "Tomoshibi Oracle warns before config changes that require regeneration — project.prefix change now shows impact and exact follow-up command before [Y/n] prompt.",
     "regenerate": [],
     "breaking": false,
     "manual": []
@@ -803,7 +1121,7 @@
   "0.12.3": {
     "version": "0.12.4",
     "date": "2026-04-17",
-    "notes": "Fast-mode capability announcement: every materialise round (per-workflow stub trigger or /forge:materialize --all) now emits a 2-line summary like '\u3007 Forge is currently in fast mode \u00b7 5% capabilities generated (2 of 41) \u2014 this round will lift capabilities to 29% (12 of 41, +10 artifact(s))'. Silent on full installs. New ensure-ready.cjs subcommands: --capabilities, --capabilities-after, --announce.",
+    "notes": "Fast-mode capability announcement: every materialise round (per-workflow stub trigger or /forge:materialize --all) now emits a 2-line summary like '〇 Forge is currently in fast mode · 5% capabilities generated (2 of 41) — this round will lift capabilities to 29% (12 of 41, +10 artifact(s))'. Silent on full installs. New ensure-ready.cjs subcommands: --capabilities, --capabilities-after, --announce.",
     "regenerate": [],
     "breaking": false,
     "manual": []
@@ -811,7 +1129,7 @@
   "0.12.2": {
     "version": "0.12.3",
     "date": "2026-04-17",
-    "notes": "Visual onboarding character: hero banners and per-phase/step badges across /forge:init, /forge:update, /forge:regenerate, /forge:health (and light touch on /forge:config and /forge:materialize). banners.cjs gains progressBar, subtitle, phaseHeader, plain-mode (NO_COLOR / non-tty / --plain). Backwards-compatible \u2014 all existing API + emits still work; new visuals are additive.",
+    "notes": "Visual onboarding character: hero banners and per-phase/step badges across /forge:init, /forge:update, /forge:regenerate, /forge:health (and light touch on /forge:config and /forge:materialize). banners.cjs gains progressBar, subtitle, phaseHeader, plain-mode (NO_COLOR / non-tty / --plain). Backwards-compatible — all existing API + emits still work; new visuals are additive.",
     "regenerate": [],
     "breaking": false,
     "manual": []
@@ -879,7 +1197,7 @@
   "0.10.0": {
     "version": "0.10.1",
     "date": "2026-04-16",
-    "notes": "Fix: quiz_agent.md was missing from new inits \u2014 add meta-quiz-agent.md so Phase 7 generates the KB knowledge-check workflow.",
+    "notes": "Fix: quiz_agent.md was missing from new inits — add meta-quiz-agent.md so Phase 7 generates the KB knowledge-check workflow.",
     "regenerate": [
       "workflows"
     ],
@@ -889,7 +1207,7 @@
   "0.9.18": {
     "version": "0.10.0",
     "date": "2026-04-16",
-    "notes": "0.9.x \u2192 0.10.0 \u2014 Tomoshibi agent (\u706f): coding-agent instruction files linked to Forge KB and workflows; KB folder name configurable at init pre-flight (paths.engineering); forge:init Phase 12, forge:update Step 7, meta-collate Finalize. Full 0.9.x cycle: store custodian gateway, named-agent IPC with phase banners and Monitor streaming, orchestrator context compaction, banner library, calibrate command, add-task, health improvements, structure manifest, BUG-008/009 fixes.",
+    "notes": "0.9.x → 0.10.0 — Tomoshibi agent (灯): coding-agent instruction files linked to Forge KB and workflows; KB folder name configurable at init pre-flight (paths.engineering); forge:init Phase 12, forge:update Step 7, meta-collate Finalize. Full 0.9.x cycle: store custodian gateway, named-agent IPC with phase banners and Monitor streaming, orchestrator context compaction, banner library, calibrate command, add-task, health improvements, structure manifest, BUG-008/009 fixes.",
     "regenerate": [
       "workflows",
       "commands",
@@ -903,7 +1221,7 @@
   "0.9.17": {
     "version": "0.10.0",
     "date": "2026-04-16",
-    "notes": "0.9.x \u2192 0.10.0 \u2014 see 0.9.18 entry.",
+    "notes": "0.9.x → 0.10.0 — see 0.9.18 entry.",
     "regenerate": [
       "workflows",
       "commands",
@@ -917,7 +1235,7 @@
   "0.9.16": {
     "version": "0.10.0",
     "date": "2026-04-16",
-    "notes": "0.9.x \u2192 0.10.0 \u2014 see 0.9.18 entry.",
+    "notes": "0.9.x → 0.10.0 — see 0.9.18 entry.",
     "regenerate": [
       "workflows",
       "commands",
@@ -931,7 +1249,7 @@
   "0.9.15": {
     "version": "0.10.0",
     "date": "2026-04-16",
-    "notes": "0.9.x \u2192 0.10.0 \u2014 see 0.9.18 entry.",
+    "notes": "0.9.x → 0.10.0 — see 0.9.18 entry.",
     "regenerate": [
       "workflows",
       "commands",
@@ -945,7 +1263,7 @@
   "0.9.14": {
     "version": "0.10.0",
     "date": "2026-04-16",
-    "notes": "0.9.x \u2192 0.10.0 \u2014 see 0.9.18 entry.",
+    "notes": "0.9.x → 0.10.0 — see 0.9.18 entry.",
     "regenerate": [
       "workflows",
       "commands",
@@ -959,7 +1277,7 @@
   "0.9.13": {
     "version": "0.10.0",
     "date": "2026-04-16",
-    "notes": "0.9.x \u2192 0.10.0 \u2014 see 0.9.18 entry.",
+    "notes": "0.9.x → 0.10.0 — see 0.9.18 entry.",
     "regenerate": [
       "workflows",
       "commands",
@@ -973,7 +1291,7 @@
   "0.9.12": {
     "version": "0.10.0",
     "date": "2026-04-16",
-    "notes": "0.9.x \u2192 0.10.0 \u2014 see 0.9.18 entry.",
+    "notes": "0.9.x → 0.10.0 — see 0.9.18 entry.",
     "regenerate": [
       "workflows",
       "commands",
@@ -987,7 +1305,7 @@
   "0.9.11": {
     "version": "0.10.0",
     "date": "2026-04-16",
-    "notes": "0.9.x \u2192 0.10.0 \u2014 see 0.9.18 entry.",
+    "notes": "0.9.x → 0.10.0 — see 0.9.18 entry.",
     "regenerate": [
       "workflows",
       "commands",
@@ -1001,7 +1319,7 @@
   "0.9.10": {
     "version": "0.10.0",
     "date": "2026-04-16",
-    "notes": "0.9.x \u2192 0.10.0 \u2014 see 0.9.18 entry.",
+    "notes": "0.9.x → 0.10.0 — see 0.9.18 entry.",
     "regenerate": [
       "workflows",
       "commands",
@@ -1015,7 +1333,7 @@
   "0.9.9": {
     "version": "0.10.0",
     "date": "2026-04-16",
-    "notes": "0.9.x \u2192 0.10.0 \u2014 see 0.9.18 entry.",
+    "notes": "0.9.x → 0.10.0 — see 0.9.18 entry.",
     "regenerate": [
       "workflows",
       "commands",
@@ -1029,7 +1347,7 @@
   "0.9.8": {
     "version": "0.10.0",
     "date": "2026-04-16",
-    "notes": "0.9.x \u2192 0.10.0 \u2014 see 0.9.18 entry.",
+    "notes": "0.9.x → 0.10.0 — see 0.9.18 entry.",
     "regenerate": [
       "workflows",
       "commands",
@@ -1043,7 +1361,7 @@
   "0.9.7": {
     "version": "0.10.0",
     "date": "2026-04-16",
-    "notes": "0.9.x \u2192 0.10.0 \u2014 see 0.9.18 entry.",
+    "notes": "0.9.x → 0.10.0 — see 0.9.18 entry.",
     "regenerate": [
       "workflows",
       "commands",
@@ -1057,7 +1375,7 @@
   "0.9.6": {
     "version": "0.10.0",
     "date": "2026-04-16",
-    "notes": "0.9.x \u2192 0.10.0 \u2014 see 0.9.18 entry.",
+    "notes": "0.9.x → 0.10.0 — see 0.9.18 entry.",
     "regenerate": [
       "workflows",
       "commands",
@@ -1071,7 +1389,7 @@
   "0.9.5": {
     "version": "0.10.0",
     "date": "2026-04-16",
-    "notes": "0.9.x \u2192 0.10.0 \u2014 see 0.9.18 entry.",
+    "notes": "0.9.x → 0.10.0 — see 0.9.18 entry.",
     "regenerate": [
       "workflows",
       "commands",
@@ -1085,7 +1403,7 @@
   "0.9.4": {
     "version": "0.10.0",
     "date": "2026-04-16",
-    "notes": "0.9.x \u2192 0.10.0 \u2014 see 0.9.18 entry.",
+    "notes": "0.9.x → 0.10.0 — see 0.9.18 entry.",
     "regenerate": [
       "workflows",
       "commands",
@@ -1099,7 +1417,7 @@
   "0.9.3": {
     "version": "0.10.0",
     "date": "2026-04-16",
-    "notes": "0.9.x \u2192 0.10.0 \u2014 see 0.9.18 entry.",
+    "notes": "0.9.x → 0.10.0 — see 0.9.18 entry.",
     "regenerate": [
       "workflows",
       "commands",
@@ -1113,7 +1431,7 @@
   "0.9.2": {
     "version": "0.10.0",
     "date": "2026-04-16",
-    "notes": "0.9.x \u2192 0.10.0 \u2014 see 0.9.18 entry.",
+    "notes": "0.9.x → 0.10.0 — see 0.9.18 entry.",
     "regenerate": [
       "workflows",
       "commands",
@@ -1127,7 +1445,7 @@
   "0.9.1": {
     "version": "0.10.0",
     "date": "2026-04-16",
-    "notes": "0.9.x \u2192 0.10.0 \u2014 see 0.9.18 entry.",
+    "notes": "0.9.x → 0.10.0 — see 0.9.18 entry.",
     "regenerate": [
       "workflows",
       "commands",
@@ -1141,7 +1459,7 @@
   "0.9.0": {
     "version": "0.10.0",
     "date": "2026-04-16",
-    "notes": "0.9.x \u2192 0.10.0 \u2014 see 0.9.18 entry.",
+    "notes": "0.9.x → 0.10.0 — see 0.9.18 entry.",
     "regenerate": [
       "workflows",
       "commands",
@@ -1155,7 +1473,7 @@
   "0.8.10": {
     "version": "0.9.0",
     "date": "2026-04-15",
-    "notes": "0.8.x \u2192 0.9.0 \u2014 Store Custodian: deterministic store gateway (store-cli.cjs), 16 meta-workflows migrated from direct writes to custodian, sprint schema gains goal and features fields. Full 0.8.x cycle: Sprint S06 cap, slug-aware directory discovery, ghost event fix, collate purge-events, init migration baseline stamp, workflow canonical naming, effort: frontmatter, fix sprint-plan and forge:update Step 4.",
+    "notes": "0.8.x → 0.9.0 — Store Custodian: deterministic store gateway (store-cli.cjs), 16 meta-workflows migrated from direct writes to custodian, sprint schema gains goal and features fields. Full 0.8.x cycle: Sprint S06 cap, slug-aware directory discovery, ghost event fix, collate purge-events, init migration baseline stamp, workflow canonical naming, effort: frontmatter, fix sprint-plan and forge:update Step 4.",
     "regenerate": [
       "workflows",
       "commands",
@@ -1169,7 +1487,7 @@
   "0.8.9": {
     "version": "0.9.0",
     "date": "2026-04-15",
-    "notes": "0.8.x \u2192 0.9.0 \u2014 see 0.8.10 entry.",
+    "notes": "0.8.x → 0.9.0 — see 0.8.10 entry.",
     "regenerate": [
       "workflows",
       "commands",
@@ -1183,7 +1501,7 @@
   "0.8.8": {
     "version": "0.9.0",
     "date": "2026-04-15",
-    "notes": "0.8.x \u2192 0.9.0 \u2014 see 0.8.10 entry.",
+    "notes": "0.8.x → 0.9.0 — see 0.8.10 entry.",
     "regenerate": [
       "workflows",
       "commands",
@@ -1197,7 +1515,7 @@
   "0.8.7": {
     "version": "0.9.0",
     "date": "2026-04-15",
-    "notes": "0.8.x \u2192 0.9.0 \u2014 see 0.8.10 entry.",
+    "notes": "0.8.x → 0.9.0 — see 0.8.10 entry.",
     "regenerate": [
       "workflows",
       "commands",
@@ -1211,7 +1529,7 @@
   "0.8.6": {
     "version": "0.9.0",
     "date": "2026-04-15",
-    "notes": "0.8.x \u2192 0.9.0 \u2014 see 0.8.10 entry.",
+    "notes": "0.8.x → 0.9.0 — see 0.8.10 entry.",
     "regenerate": [
       "workflows",
       "commands",
@@ -1225,7 +1543,7 @@
   "0.8.5": {
     "version": "0.9.0",
     "date": "2026-04-15",
-    "notes": "0.8.x \u2192 0.9.0 \u2014 see 0.8.10 entry.",
+    "notes": "0.8.x → 0.9.0 — see 0.8.10 entry.",
     "regenerate": [
       "workflows",
       "commands",
@@ -1239,7 +1557,7 @@
   "0.8.4": {
     "version": "0.9.0",
     "date": "2026-04-15",
-    "notes": "0.8.x \u2192 0.9.0 \u2014 see 0.8.10 entry.",
+    "notes": "0.8.x → 0.9.0 — see 0.8.10 entry.",
     "regenerate": [
       "workflows",
       "commands",
@@ -1253,7 +1571,7 @@
   "0.8.3": {
     "version": "0.9.0",
     "date": "2026-04-15",
-    "notes": "0.8.x \u2192 0.9.0 \u2014 see 0.8.10 entry.",
+    "notes": "0.8.x → 0.9.0 — see 0.8.10 entry.",
     "regenerate": [
       "workflows",
       "commands",
@@ -1267,7 +1585,7 @@
   "0.8.2": {
     "version": "0.9.0",
     "date": "2026-04-15",
-    "notes": "0.8.x \u2192 0.9.0 \u2014 see 0.8.10 entry.",
+    "notes": "0.8.x → 0.9.0 — see 0.8.10 entry.",
     "regenerate": [
       "workflows",
       "commands",
@@ -1281,7 +1599,7 @@
   "0.8.1": {
     "version": "0.9.0",
     "date": "2026-04-15",
-    "notes": "0.8.x \u2192 0.9.0 \u2014 see 0.8.10 entry.",
+    "notes": "0.8.x → 0.9.0 — see 0.8.10 entry.",
     "regenerate": [
       "workflows",
       "commands",
@@ -1295,7 +1613,7 @@
   "0.8.0": {
     "version": "0.9.0",
     "date": "2026-04-15",
-    "notes": "0.8.x \u2192 0.9.0 \u2014 see 0.8.10 entry.",
+    "notes": "0.8.x → 0.9.0 — see 0.8.10 entry.",
     "regenerate": [
       "workflows",
       "commands",
@@ -1309,7 +1627,7 @@
   "0.7.11": {
     "version": "0.8.0",
     "date": "2026-04-14",
-    "notes": "0.7.x \u2192 0.8.0 \u2014 Sprint S06: orchestrator persona noun-based lookup, meta-workflows purged of inline Persona sections, forge:regenerate includes personas, sprint schema path field, slug-aware seed-store/collate/validate-store. Full 0.7.x cycle: Japanese nature persona palette, orchestrator announcements, ghost event fix, false breaking-change suppression, validate-store slug and filesystem checks.",
+    "notes": "0.7.x → 0.8.0 — Sprint S06: orchestrator persona noun-based lookup, meta-workflows purged of inline Persona sections, forge:regenerate includes personas, sprint schema path field, slug-aware seed-store/collate/validate-store. Full 0.7.x cycle: Japanese nature persona palette, orchestrator announcements, ghost event fix, false breaking-change suppression, validate-store slug and filesystem checks.",
     "regenerate": [
       "workflows",
       "commands",
@@ -1322,7 +1640,7 @@
   "0.7.10": {
     "version": "0.8.0",
     "date": "2026-04-14",
-    "notes": "0.7.x \u2192 0.8.0 \u2014 see 0.7.11 entry.",
+    "notes": "0.7.x → 0.8.0 — see 0.7.11 entry.",
     "regenerate": [
       "workflows",
       "commands",
@@ -1335,7 +1653,7 @@
   "0.7.9": {
     "version": "0.8.0",
     "date": "2026-04-14",
-    "notes": "0.7.x \u2192 0.8.0 \u2014 see 0.7.11 entry.",
+    "notes": "0.7.x → 0.8.0 — see 0.7.11 entry.",
     "regenerate": [
       "workflows",
       "commands",
@@ -1348,7 +1666,7 @@
   "0.7.8": {
     "version": "0.8.0",
     "date": "2026-04-14",
-    "notes": "0.7.x \u2192 0.8.0 \u2014 see 0.7.11 entry.",
+    "notes": "0.7.x → 0.8.0 — see 0.7.11 entry.",
     "regenerate": [
       "workflows",
       "commands",
@@ -1361,7 +1679,7 @@
   "0.7.7": {
     "version": "0.8.0",
     "date": "2026-04-14",
-    "notes": "0.7.x \u2192 0.8.0 \u2014 see 0.7.11 entry.",
+    "notes": "0.7.x → 0.8.0 — see 0.7.11 entry.",
     "regenerate": [
       "workflows",
       "commands",
@@ -1374,7 +1692,7 @@
   "0.7.6": {
     "version": "0.8.0",
     "date": "2026-04-14",
-    "notes": "0.7.x \u2192 0.8.0 \u2014 see 0.7.11 entry.",
+    "notes": "0.7.x → 0.8.0 — see 0.7.11 entry.",
     "regenerate": [
       "workflows",
       "commands",
@@ -1387,7 +1705,7 @@
   "0.7.5": {
     "version": "0.8.0",
     "date": "2026-04-14",
-    "notes": "0.7.x \u2192 0.8.0 \u2014 see 0.7.11 entry.",
+    "notes": "0.7.x → 0.8.0 — see 0.7.11 entry.",
     "regenerate": [
       "workflows",
       "commands",
@@ -1400,7 +1718,7 @@
   "0.7.4": {
     "version": "0.8.0",
     "date": "2026-04-14",
-    "notes": "0.7.x \u2192 0.8.0 \u2014 see 0.7.11 entry.",
+    "notes": "0.7.x → 0.8.0 — see 0.7.11 entry.",
     "regenerate": [
       "workflows",
       "commands",
@@ -1413,7 +1731,7 @@
   "0.7.3": {
     "version": "0.8.0",
     "date": "2026-04-14",
-    "notes": "0.7.x \u2192 0.8.0 \u2014 see 0.7.11 entry.",
+    "notes": "0.7.x → 0.8.0 — see 0.7.11 entry.",
     "regenerate": [
       "workflows",
       "commands",
@@ -1426,7 +1744,7 @@
   "0.7.2": {
     "version": "0.8.0",
     "date": "2026-04-14",
-    "notes": "0.7.x \u2192 0.8.0 \u2014 see 0.7.11 entry.",
+    "notes": "0.7.x → 0.8.0 — see 0.7.11 entry.",
     "regenerate": [
       "workflows",
       "commands",
@@ -1439,7 +1757,7 @@
   "0.7.1": {
     "version": "0.8.0",
     "date": "2026-04-14",
-    "notes": "0.7.x \u2192 0.8.0 \u2014 see 0.7.11 entry.",
+    "notes": "0.7.x → 0.8.0 — see 0.7.11 entry.",
     "regenerate": [
       "workflows",
       "commands",
@@ -1452,7 +1770,7 @@
   "0.7.0": {
     "version": "0.8.0",
     "date": "2026-04-14",
-    "notes": "0.7.x \u2192 0.8.0 \u2014 see 0.7.11 entry.",
+    "notes": "0.7.x → 0.8.0 — see 0.7.11 entry.",
     "regenerate": [
       "workflows",
       "commands",
@@ -1465,7 +1783,7 @@
   "0.6.13": {
     "version": "0.7.0",
     "date": "2026-04-13",
-    "notes": "0.6.x \u2192 0.7.0 \u25b3 Breaking \u2014 Portability migration: legacy model: fields \u2192 structured requirements blocks (3D Agent Model); grounding and descriptive pathing (ID-description folder naming, absolute path injection). Full 0.6.x cycle: distribution-aware update URLs, QA validate phase, store.cjs facade, collate fixes, skillforge git-subdir.",
+    "notes": "0.6.x → 0.7.0 △ Breaking — Portability migration: legacy model: fields → structured requirements blocks (3D Agent Model); grounding and descriptive pathing (ID-description folder naming, absolute path injection). Full 0.6.x cycle: distribution-aware update URLs, QA validate phase, store.cjs facade, collate fixes, skillforge git-subdir.",
     "regenerate": [
       "workflows",
       "commands",
@@ -1481,7 +1799,7 @@
   "0.6.12": {
     "version": "0.7.0",
     "date": "2026-04-13",
-    "notes": "0.6.x \u2192 0.7.0 \u2014 see 0.6.13 entry.",
+    "notes": "0.6.x → 0.7.0 — see 0.6.13 entry.",
     "regenerate": [
       "workflows",
       "commands",
@@ -1497,7 +1815,7 @@
   "0.6.11": {
     "version": "0.7.0",
     "date": "2026-04-13",
-    "notes": "0.6.x \u2192 0.7.0 \u2014 see 0.6.13 entry.",
+    "notes": "0.6.x → 0.7.0 — see 0.6.13 entry.",
     "regenerate": [
       "workflows",
       "commands",
@@ -1513,7 +1831,7 @@
   "0.6.10": {
     "version": "0.7.0",
     "date": "2026-04-13",
-    "notes": "0.6.x \u2192 0.7.0 \u2014 see 0.6.13 entry.",
+    "notes": "0.6.x → 0.7.0 — see 0.6.13 entry.",
     "regenerate": [
       "workflows",
       "commands",
@@ -1529,7 +1847,7 @@
   "0.6.9": {
     "version": "0.7.0",
     "date": "2026-04-13",
-    "notes": "0.6.x \u2192 0.7.0 \u2014 see 0.6.13 entry.",
+    "notes": "0.6.x → 0.7.0 — see 0.6.13 entry.",
     "regenerate": [
       "workflows",
       "commands",
@@ -1545,7 +1863,7 @@
   "0.6.8": {
     "version": "0.7.0",
     "date": "2026-04-13",
-    "notes": "0.6.x \u2192 0.7.0 \u2014 see 0.6.13 entry.",
+    "notes": "0.6.x → 0.7.0 — see 0.6.13 entry.",
     "regenerate": [
       "workflows",
       "commands",
@@ -1561,7 +1879,7 @@
   "0.6.7": {
     "version": "0.7.0",
     "date": "2026-04-13",
-    "notes": "0.6.x \u2192 0.7.0 \u2014 see 0.6.13 entry.",
+    "notes": "0.6.x → 0.7.0 — see 0.6.13 entry.",
     "regenerate": [
       "workflows",
       "commands",
@@ -1577,7 +1895,7 @@
   "0.6.6": {
     "version": "0.7.0",
     "date": "2026-04-13",
-    "notes": "0.6.x \u2192 0.7.0 \u2014 see 0.6.13 entry.",
+    "notes": "0.6.x → 0.7.0 — see 0.6.13 entry.",
     "regenerate": [
       "workflows",
       "commands",
@@ -1593,7 +1911,7 @@
   "0.6.5": {
     "version": "0.7.0",
     "date": "2026-04-13",
-    "notes": "0.6.x \u2192 0.7.0 \u2014 see 0.6.13 entry.",
+    "notes": "0.6.x → 0.7.0 — see 0.6.13 entry.",
     "regenerate": [
       "workflows",
       "commands",
@@ -1609,7 +1927,7 @@
   "0.6.4": {
     "version": "0.7.0",
     "date": "2026-04-13",
-    "notes": "0.6.x \u2192 0.7.0 \u2014 see 0.6.13 entry.",
+    "notes": "0.6.x → 0.7.0 — see 0.6.13 entry.",
     "regenerate": [
       "workflows",
       "commands",
@@ -1625,7 +1943,7 @@
   "0.6.3": {
     "version": "0.7.0",
     "date": "2026-04-13",
-    "notes": "0.6.x \u2192 0.7.0 \u2014 see 0.6.13 entry.",
+    "notes": "0.6.x → 0.7.0 — see 0.6.13 entry.",
     "regenerate": [
       "workflows",
       "commands",
@@ -1641,7 +1959,7 @@
   "0.6.2": {
     "version": "0.7.0",
     "date": "2026-04-13",
-    "notes": "0.6.x \u2192 0.7.0 \u2014 see 0.6.13 entry.",
+    "notes": "0.6.x → 0.7.0 — see 0.6.13 entry.",
     "regenerate": [
       "workflows",
       "commands",
@@ -1657,7 +1975,7 @@
   "0.6.1": {
     "version": "0.7.0",
     "date": "2026-04-13",
-    "notes": "0.6.x \u2192 0.7.0 \u2014 see 0.6.13 entry.",
+    "notes": "0.6.x → 0.7.0 — see 0.6.13 entry.",
     "regenerate": [
       "workflows",
       "commands",
@@ -1673,7 +1991,7 @@
   "0.6.0": {
     "version": "0.7.0",
     "date": "2026-04-13",
-    "notes": "0.6.x \u2192 0.7.0 \u2014 see 0.6.13 entry.",
+    "notes": "0.6.x → 0.7.0 — see 0.6.13 entry.",
     "regenerate": [
       "workflows",
       "commands",
@@ -1689,7 +2007,7 @@
   "0.5.9": {
     "version": "0.6.0",
     "date": "2026-04-09",
-    "notes": "0.5.x \u2192 0.6.0 \u2014 Feature tier: Feature entity (feature.schema.json, .forge/store/features/), feature_id in sprint/task schemas, collate generates features/ registry, health reports per-feature coverage, docs/concepts/ added. Full 0.5.x cycle: fix-bug as true orchestrator, validate-store null handling, collate FORGE_ROOT fix, update UX improvements, canary source detection.",
+    "notes": "0.5.x → 0.6.0 — Feature tier: Feature entity (feature.schema.json, .forge/store/features/), feature_id in sprint/task schemas, collate generates features/ registry, health reports per-feature coverage, docs/concepts/ added. Full 0.5.x cycle: fix-bug as true orchestrator, validate-store null handling, collate FORGE_ROOT fix, update UX improvements, canary source detection.",
     "regenerate": [
       "workflows",
       "commands",
@@ -1701,7 +2019,7 @@
   "0.5.8": {
     "version": "0.6.0",
     "date": "2026-04-09",
-    "notes": "0.5.x \u2192 0.6.0 \u2014 see 0.5.9 entry.",
+    "notes": "0.5.x → 0.6.0 — see 0.5.9 entry.",
     "regenerate": [
       "workflows",
       "commands",
@@ -1713,7 +2031,7 @@
   "0.5.7": {
     "version": "0.6.0",
     "date": "2026-04-09",
-    "notes": "0.5.x \u2192 0.6.0 \u2014 see 0.5.9 entry.",
+    "notes": "0.5.x → 0.6.0 — see 0.5.9 entry.",
     "regenerate": [
       "workflows",
       "commands",
@@ -1725,7 +2043,7 @@
   "0.5.6": {
     "version": "0.6.0",
     "date": "2026-04-09",
-    "notes": "0.5.x \u2192 0.6.0 \u2014 see 0.5.9 entry.",
+    "notes": "0.5.x → 0.6.0 — see 0.5.9 entry.",
     "regenerate": [
       "workflows",
       "commands",
@@ -1737,7 +2055,7 @@
   "0.5.5": {
     "version": "0.6.0",
     "date": "2026-04-09",
-    "notes": "0.5.x \u2192 0.6.0 \u2014 see 0.5.9 entry.",
+    "notes": "0.5.x → 0.6.0 — see 0.5.9 entry.",
     "regenerate": [
       "workflows",
       "commands",
@@ -1749,7 +2067,7 @@
   "0.5.4": {
     "version": "0.6.0",
     "date": "2026-04-09",
-    "notes": "0.5.x \u2192 0.6.0 \u2014 see 0.5.9 entry.",
+    "notes": "0.5.x → 0.6.0 — see 0.5.9 entry.",
     "regenerate": [
       "workflows",
       "commands",
@@ -1761,7 +2079,7 @@
   "0.5.3": {
     "version": "0.6.0",
     "date": "2026-04-09",
-    "notes": "0.5.x \u2192 0.6.0 \u2014 see 0.5.9 entry.",
+    "notes": "0.5.x → 0.6.0 — see 0.5.9 entry.",
     "regenerate": [
       "workflows",
       "commands",
@@ -1773,7 +2091,7 @@
   "0.5.2": {
     "version": "0.6.0",
     "date": "2026-04-09",
-    "notes": "0.5.x \u2192 0.6.0 \u2014 see 0.5.9 entry.",
+    "notes": "0.5.x → 0.6.0 — see 0.5.9 entry.",
     "regenerate": [
       "workflows",
       "commands",
@@ -1785,7 +2103,7 @@
   "0.5.1": {
     "version": "0.6.0",
     "date": "2026-04-09",
-    "notes": "0.5.x \u2192 0.6.0 \u2014 see 0.5.9 entry.",
+    "notes": "0.5.x → 0.6.0 — see 0.5.9 entry.",
     "regenerate": [
       "workflows",
       "commands",
@@ -1797,7 +2115,7 @@
   "0.5.0": {
     "version": "0.6.0",
     "date": "2026-04-09",
-    "notes": "0.5.x \u2192 0.6.0 \u2014 see 0.5.9 entry.",
+    "notes": "0.5.x → 0.6.0 — see 0.5.9 entry.",
     "regenerate": [
       "workflows",
       "commands",
@@ -1809,7 +2127,7 @@
   "0.4.1": {
     "version": "0.5.0",
     "date": "2026-04-06",
-    "notes": "0.4.x \u2192 0.5.0 \u2014 Japanese-style marks (\u3007\u25b3\u00d7\ud83c\udf31\ud83c\udf3f\u26f0\ufe0f) across all output, agent personas with symbols, command renames (plan/review-plan/review-code), generation-manifest tool, engineering/tools/ eliminated (all tools from $FORGE_ROOT/tools/), paths.forgeRoot and paths.customCommands added to config schema.",
+    "notes": "0.4.x → 0.5.0 — Japanese-style marks (〇△×🌱🌿⛰️) across all output, agent personas with symbols, command renames (plan/review-plan/review-code), generation-manifest tool, engineering/tools/ eliminated (all tools from $FORGE_ROOT/tools/), paths.forgeRoot and paths.customCommands added to config schema.",
     "regenerate": [
       "workflows",
       "commands"
@@ -1820,7 +2138,7 @@
   "0.4.0": {
     "version": "0.5.0",
     "date": "2026-04-06",
-    "notes": "0.4.x \u2192 0.5.0 \u2014 see 0.4.1 entry. If upgrading from 0.4.0 directly, first run: node engineering/tools/manage-config.cjs pipeline backfill-models",
+    "notes": "0.4.x → 0.5.0 — see 0.4.1 entry. If upgrading from 0.4.0 directly, first run: node engineering/tools/manage-config.cjs pipeline backfill-models",
     "regenerate": [
       "workflows",
       "commands"
@@ -1831,7 +2149,7 @@
   "0.3.15": {
     "version": "0.4.0",
     "date": "2026-04-05",
-    "notes": "0.3.x \u2192 0.4.0 \u25b3 Breaking \u2014 Pre-built CJS tools shipped (collate, seed-store, validate-store, manage-config); revision loop fix; context accumulation fix (BUG-001); error triage hook; graceful error handling. Full 0.3.x cycle included.",
+    "notes": "0.3.x → 0.4.0 △ Breaking — Pre-built CJS tools shipped (collate, seed-store, validate-store, manage-config); revision loop fix; context accumulation fix (BUG-001); error triage hook; graceful error handling. Full 0.3.x cycle included.",
     "regenerate": [
       "workflows",
       "commands",
@@ -1845,7 +2163,7 @@
   "0.3.14": {
     "version": "0.4.0",
     "date": "2026-04-05",
-    "notes": "0.3.x \u2192 0.4.0 \u2014 see 0.3.15 entry.",
+    "notes": "0.3.x → 0.4.0 — see 0.3.15 entry.",
     "regenerate": [
       "workflows",
       "commands",
@@ -1859,7 +2177,7 @@
   "0.3.13": {
     "version": "0.4.0",
     "date": "2026-04-05",
-    "notes": "0.3.x \u2192 0.4.0 \u2014 see 0.3.15 entry.",
+    "notes": "0.3.x → 0.4.0 — see 0.3.15 entry.",
     "regenerate": [
       "workflows",
       "commands",
@@ -1873,7 +2191,7 @@
   "0.3.12": {
     "version": "0.4.0",
     "date": "2026-04-05",
-    "notes": "0.3.x \u2192 0.4.0 \u2014 see 0.3.15 entry.",
+    "notes": "0.3.x → 0.4.0 — see 0.3.15 entry.",
     "regenerate": [
       "workflows",
       "commands",
@@ -1887,7 +2205,7 @@
   "0.3.11": {
     "version": "0.4.0",
     "date": "2026-04-05",
-    "notes": "0.3.x \u2192 0.4.0 \u2014 see 0.3.15 entry.",
+    "notes": "0.3.x → 0.4.0 — see 0.3.15 entry.",
     "regenerate": [
       "workflows",
       "commands",
@@ -1901,7 +2219,7 @@
   "0.3.10": {
     "version": "0.4.0",
     "date": "2026-04-05",
-    "notes": "0.3.x \u2192 0.4.0 \u2014 see 0.3.15 entry.",
+    "notes": "0.3.x → 0.4.0 — see 0.3.15 entry.",
     "regenerate": [
       "workflows",
       "commands",
@@ -1915,7 +2233,7 @@
   "0.3.9": {
     "version": "0.4.0",
     "date": "2026-04-05",
-    "notes": "0.3.x \u2192 0.4.0 \u2014 see 0.3.15 entry.",
+    "notes": "0.3.x → 0.4.0 — see 0.3.15 entry.",
     "regenerate": [
       "workflows",
       "commands",
@@ -1929,7 +2247,7 @@
   "0.3.8": {
     "version": "0.4.0",
     "date": "2026-04-05",
-    "notes": "0.3.x \u2192 0.4.0 \u2014 see 0.3.15 entry.",
+    "notes": "0.3.x → 0.4.0 — see 0.3.15 entry.",
     "regenerate": [
       "workflows",
       "commands",
@@ -1943,7 +2261,7 @@
   "0.3.7": {
     "version": "0.4.0",
     "date": "2026-04-05",
-    "notes": "0.3.x \u2192 0.4.0 \u2014 see 0.3.15 entry.",
+    "notes": "0.3.x → 0.4.0 — see 0.3.15 entry.",
     "regenerate": [
       "workflows",
       "commands",
@@ -1957,7 +2275,7 @@
   "0.3.6": {
     "version": "0.4.0",
     "date": "2026-04-05",
-    "notes": "0.3.x \u2192 0.4.0 \u2014 see 0.3.15 entry.",
+    "notes": "0.3.x → 0.4.0 — see 0.3.15 entry.",
     "regenerate": [
       "workflows",
       "commands",
@@ -1971,7 +2289,7 @@
   "0.3.5": {
     "version": "0.4.0",
     "date": "2026-04-05",
-    "notes": "0.3.x \u2192 0.4.0 \u2014 see 0.3.15 entry.",
+    "notes": "0.3.x → 0.4.0 — see 0.3.15 entry.",
     "regenerate": [
       "workflows",
       "commands",
@@ -1985,7 +2303,7 @@
   "0.3.4": {
     "version": "0.4.0",
     "date": "2026-04-05",
-    "notes": "0.3.x \u2192 0.4.0 \u2014 see 0.3.15 entry.",
+    "notes": "0.3.x → 0.4.0 — see 0.3.15 entry.",
     "regenerate": [
       "workflows",
       "commands",
@@ -1999,7 +2317,7 @@
   "0.3.3": {
     "version": "0.4.0",
     "date": "2026-04-05",
-    "notes": "0.3.x \u2192 0.4.0 \u2014 see 0.3.15 entry.",
+    "notes": "0.3.x → 0.4.0 — see 0.3.15 entry.",
     "regenerate": [
       "workflows",
       "commands",
@@ -2013,7 +2331,7 @@
   "0.3.2": {
     "version": "0.4.0",
     "date": "2026-04-05",
-    "notes": "0.3.x \u2192 0.4.0 \u2014 see 0.3.15 entry.",
+    "notes": "0.3.x → 0.4.0 — see 0.3.15 entry.",
     "regenerate": [
       "workflows",
       "commands",
@@ -2027,7 +2345,7 @@
   "0.3.1": {
     "version": "0.4.0",
     "date": "2026-04-05",
-    "notes": "0.3.x \u2192 0.4.0 \u2014 see 0.3.15 entry.",
+    "notes": "0.3.x → 0.4.0 — see 0.3.15 entry.",
     "regenerate": [
       "workflows",
       "commands",
@@ -2041,7 +2359,7 @@
   "0.3.0": {
     "version": "0.4.0",
     "date": "2026-04-05",
-    "notes": "0.3.x \u2192 0.4.0 \u2014 see 0.3.15 entry.",
+    "notes": "0.3.x → 0.4.0 — see 0.3.15 entry.",
     "regenerate": [
       "workflows",
       "commands",
@@ -2062,4 +2380,4 @@
     "breaking": false,
     "manual": []
   }
-}
+}