mindforge-cc 11.9.2 → 11.9.4

package/bin/validate-config.js

@@ -8,15 +8,55 @@
 'use strict';
 
 const fs = require('fs');
+const path = require('path');
 
 // The one bracket-aware MINDFORGE.md reader (see bin/utils/mindforge-params.js).
 const { readParams } = require('./utils/mindforge-params');
 
+// The config belongs to the CALLER, so it stays relative to cwd.
 const CONFIG_PATH  = process.argv[2] || 'MINDFORGE.md';
-const SCHEMA_PATH  = '.mindforge/MINDFORGE-SCHEMA.json';
+
+/**
+ * The schema belongs to the FRAMEWORK, so it is resolved from __dirname first.
+ *
+ * This was the bare relative `'.mindforge/MINDFORGE-SCHEMA.json'`, which only ever resolved
+ * because bin/mindforge-cli.js pinned the child's cwd to MindForge's own install directory. That
+ * pin is what made `security-scan` validate the vendor's MINDFORGE.md and report
+ * `✅ valid — 43 settings configured` over any caller's config. Removing the pin without anchoring
+ * the schema here would have swapped one broken outcome for another: every consumer with a real
+ * MINDFORGE.md would hit the `not found` branch below and exit 0 having validated NOTHING. Measured
+ * that exact regression on a fixture — `ℹ️ MINDFORGE-SCHEMA.json not found — skipping schema
+ * validation`, rc=0 — which is why the two changes ship together.
+ *
+ * Every check in this file is schema-driven (required, recommended, type, minimum, maximum, enum,
+ * pattern, nonOverridable). There is no schema-free validation path, so a missing schema is not a
+ * degraded check, it is no check.
+ *
+ * Package-relative first, cwd-relative second, because the two supported install shapes put the
+ * schema in different places:
+ *   - `npx mindforge-cc` — runs from node_modules/mindforge-cc/, where .mindforge/ ships. Fixed.
+ *   - a copied bin/ tree — the installer copies bin/ but creates no .mindforge/, verified on a
+ *     clean `--claude --local` install. There the schema is genuinely absent and the honest skip
+ *     below is the correct outcome; the cwd fallback still finds one if the project has its own.
+ */
+function resolveSchemaPath() {
+  const candidates = [
+    path.join(__dirname, '..', '.mindforge', 'MINDFORGE-SCHEMA.json'),
+    path.join(process.cwd(), '.mindforge', 'MINDFORGE-SCHEMA.json'),
+  ];
+  return candidates.find((p) => fs.existsSync(p)) || candidates[0];
+}
+
+const SCHEMA_PATH = resolveSchemaPath();
 
 if (!fs.existsSync(CONFIG_PATH)) {
-  console.log('ℹ️  MINDFORGE.md not found — using all defaults. Create one to customise.');
+  // Name the path actually looked for, and where. This said "MINDFORGE.md not found" verbatim even
+  // when argv[2] supplied a different file, so `validate-config.js custom-config.md` reported a
+  // missing MINDFORGE.md — a message about a file the caller never mentioned. It cost real time
+  // during this change: a test failure was diagnosed as "a defaultArgs positional shadowed argv[2]"
+  // when the truth was simply that the named file was not in the working directory.
+  console.log(`ℹ️  ${CONFIG_PATH} not found in ${process.cwd()} — using all defaults. `
+    + 'Create one to customise.');
   process.exit(0);
 }
 

package/bin/wizard/setup-wizard.js

@@ -6,7 +6,10 @@ const readline = require('readline');
 const detector = require('./environment-detector');
 const generator = require('./config-generator');
 
-const VERSION = require('../../package.json').version;
+// Resolved by package NAME, not by relative path: in an install `../../package.json` is the
+// consumer's manifest, so the wizard displayed the host app's version as MindForge's.
+const { resolveMindforgeVersion } = require('../utils/mindforge-version');
+const VERSION = resolveMindforgeVersion({ fromDir: __dirname }).version;
 const ARGS = process.argv.slice(2);
 const IS_INTERACTIVE =
   !ARGS.some((a) => ['--claude', '--antigravity', '--all', '--help'].includes(a)) &&

package/bin/wizard/theme.js

@@ -106,7 +106,15 @@ const Theme = {
     console.log(`  ${this.colors.dim('│')}    ${this.colors.bold('Environment')}: ${this.colors.cyan(runtime)} (${this.colors.dim(scope)})                         ${this.colors.dim('│')}`);
     console.log(`  ${this.colors.dim('│')}                                                                        ${this.colors.dim('│')}`);
     console.log(`  ${this.colors.dim('│')}    ${this.colors.bold('Next steps:')}                                                   ${this.colors.dim('│')}`);
-    console.log(`  ${this.colors.dim('│')}      ${this.colors.bold('mindforge-cc init')}   ${this.colors.dim('— Initialize your first workspace')}      ${this.colors.dim('│')}`);
+    // Was `mindforge-cc init`, which does not exist. mindforge-cc takes flags only and silently
+    // ignored the positional, so obeying this line re-ran the installer against whatever directory
+    // the user was standing in: measured 1,836 files written into an empty temp dir, exit 0, and
+    // this same panel printed again — so it loops. `/mindforge:init-project` is the real command and
+    // the install has just placed it in the harness, so the instruction now names something the
+    // user actually has. bin/install.js rejects stray positionals too: a wrong instruction and a
+    // silent acceptance of it are two separate defects, and fixing either alone leaves a trap.
+    // Padding keeps the visible width at 65 so the box border still lines up.
+    console.log(`  ${this.colors.dim('│')}      ${this.colors.bold('/mindforge:init-project')}  ${this.colors.dim('— Initialize your workspace')}       ${this.colors.dim('│')}`);
     console.log(`  ${this.colors.dim('│')}      ${this.colors.bold('/mindforge:help')}    ${this.colors.dim('— Explore the command suite')}        ${this.colors.dim('│')}`);
     console.log(`  ${this.colors.dim('│')}                                                                        ${this.colors.dim('│')}`);
     console.log(`  ${this.colors.dim('├' + '─'.repeat(boxWidth) + '╯')}\n`);

package/changelogs/index.json

@@ -1,5 +1,7 @@
 {
   "versions": [
+    "11.9.3",
+    "11.9.2",
     "11.9.1",
     "11.9.0",
     "11.8.3",
@@ -47,8 +49,8 @@
     "6.5.0",
     "6.4.0",
     "6.3.0",
-    "6.2.0",
     "6.2.0-alpha",
+    "6.2.0",
     "6.1.0-alpha",
     "6.0.0-alpha",
     "5.9.0",
@@ -60,8 +62,8 @@
     "5.3.0",
     "5.2.0",
     "5.1.0",
-    "5.0.0-alpha.2",
     "5.0.0-alpha.1",
+    "5.0.0-alpha.2",
     "4.3.0",
     "4.1.0",
     "4.0.0",
@@ -76,17 +78,17 @@
     "2.1.2",
     "2.1.1",
     "2.1.0",
-    "2.0.0",
-    "2.0.0-alpha.12",
-    "2.0.0-alpha.11",
-    "2.0.0-alpha.10",
     "2.0.0-alpha.9",
     "2.0.0-alpha.8",
-    "2.0.0-alpha.7",
-    "2.0.0-alpha.4",
-    "2.0.0-alpha.3",
+    "2.0.0",
+    "2.0.0-alpha.10",
     "2.0.0-alpha.2",
     "2.0.0-alpha.1",
+    "2.0.0-alpha.11",
+    "2.0.0-alpha.7",
+    "2.0.0-alpha.12",
+    "2.0.0-alpha.3",
+    "2.0.0-alpha.4",
     "1.0.5",
     "1.0.4",
     "1.0.3",

package/changelogs/v11.9.3.md

@@ -0,0 +1,204 @@
+# Changelog
+
+## [11.9.3] — 2026-08-21 — Honesty: gates that can fail, commands that run, a release path that is checked
+
+Patch release. No new features. Twenty-one fixes, and they all turned out to be the
+same defect: **an instrument reported success while doing nothing.** Gates that could
+not fail, tests satisfied by a comment, docs describing capabilities with no code
+behind them, commands printing success while performing no action, and a publish path
+that no check ever touched.
+
+Contains behaviour changes under a patch bump — several of the things being fixed were
+bugs that a consumer could have been relying on. Read BREAKING before upgrading if you
+script against the CLI or the installer.
+
+> **Corrected after release.** Three measured numbers in this entry were wrong and are fixed above:
+> the count of places `--status`/`--stop` were documented (removed rather than re-guessed — it reads 4,
+> 9 or 15 depending on how you count, which is the argument against stating it); the eslint total, which
+> was 199 on the author's machine and **190** on a clean clone, because 9 problems came from an
+> untracked local directory; and "four releases behind", which is **three** (11.8.3 → 11.9.0 → 11.9.1 →
+> 11.9.2). Found by an adversarial audit of this changelog against the published artifact. A release
+> arguing that measured numbers should be reproducible has to hold its own notes to that standard.
+
+### BREAKING
+
+Each of these is a bug fix whose correct behaviour differs from the shipped behaviour.
+
+- **Routed CLI commands now act on YOUR project, not MindForge's own checkout.**
+  `bin/mindforge-cli.js` passed `cwd: ROOT` to every routed command, so `mindforge
+  classify` diffed MindForge's repository instead of yours, and `mindforge health`
+  inspected MindForge's `node_modules`. Measured across all 27 routed commands: 7
+  changed behaviour, all in the correct direction, none regressed. If you parsed output
+  that happened to describe MindForge itself, it now describes your project. (#201)
+
+- **`npx mindforge-cc install` — and any other positional argument — now exits 1.**
+  The installer takes flags only and silently ignored stray words, so
+  `npx mindforge-cc install` appeared to work while installing nothing configured.
+  It now refuses with the correct form. `--runtime`'s value token is still accepted.
+  Use `npx mindforge-cc --claude --local`. (#202)
+
+- **`mindforge verify` now SKIPS unavailable stages instead of failing them.** A project
+  with no ESLint config, no test script or no `bin/verify-audit.js` was reported as
+  FAILING those stages rather than as not having them. If your CI relied on a non-zero
+  exit in those cases, it will now pass. A run in which every stage skipped prints a
+  "NOTHING WAS VERIFIED" banner rather than a clean bill of health. (#204)
+
+- **`scripts/sync-version.js` now exits non-zero when the plugin build artifacts are
+  stale.** A bump used to report `✅ every derivable channel is at <version>` and exit 0
+  while leaving `npm test` red. If you script this, handle the new exit code — it means
+  "run the build chain it just printed". (#211)
+
+- **A self-install no longer writes over your tracked files.** Running the installer
+  inside a MindForge checkout printed that it was skipping and then overwrote 149
+  tracked files, including `CLAUDE.md`, `.claude/**`, `.agent/**` and `.mindforge/**`.
+  The skip is now honoured for local scope. (#200)
+
+- **Releases must be tagged on a commit reachable from `main`.** The release workflow
+  now refuses a tag that is not an ancestor of `origin/main`. The documented flow is
+  develop → release → main; tagging elsewhere previously published, with provenance
+  attesting to that tree. (#216)
+
+### Fixed
+
+**Installer**
+
+- A self-install claimed to skip and then overwrote 149 tracked files. The gate is now
+  scope-aware (`isSelfInstall() && scope === 'local'`). (#200)
+- Every `--global` install reported failure on a correct run: `verifyInstall` demanded
+  six `bin/**` paths regardless of scope, so a global install ended
+  `❌ 6 of 12 required file(s) missing` and exit 1, with a `--force` retry that could
+  not help. A global install writes 389 files to `$HOME/.claude` and, deliberately,
+  zero to `bin/`. (#210)
+- 11 of 27 routed CLI verbs died on `MODULE_NOT_FOUND` in a real install: the router
+  shipped but 6 of the scripts it dispatches to did not. `coreFiles` grew from 2 entries
+  to 8. (#210)
+- Two leaks: `/tmp` staging files left behind on abandoned runs, and developer runtime
+  state (`celestial.db`, `.browser-daemon-token`) copied into consumer projects.
+  `SENSITIVE_EXCLUDE` now covers both. (#210)
+- The forge commands overwrote three `mindforge` commands of the same name. (#197)
+- The documented default install did not deliver the CLI it documents. (#196)
+
+**Versioning and release**
+
+- `sync-version.js --fetch-sha` hashed npm's 404 error body. For an unpublished version
+  the registry answers `{"error":"Not found"}` and `curl -sL` exits 0, so the digest
+  written into the Homebrew formula was the SHA-256 of that error text — the same
+  constant for every unpublished version — and `--check` then passed. Now `curl -fsSL`
+  plus a gzip magic-byte check, and it refuses rather than writing a digest no artifact
+  can match. (#203)
+- The Homebrew formula may now LAG canonical but never LEAD it. Requiring equality
+  before publishing required something impossible: the digest is the hash of a tarball
+  that does not exist yet, and `npm test` blocked the publish that would have made it
+  satisfiable. (#208)
+- Semver comparison is numeric per component. Lexicographically, `11.10.0` reads as
+  *behind* `11.9.2` — wrong on exactly the first release past a `.9` minor. (#208)
+- Three version channels had no writer at all, so `npm test` failed on every bump and
+  the documented remedy could not fix it: `mcp-server/server.json` (both keys, matched
+  by identifier), `AGENTS.md`, and `sdk/README.md`'s second shape. (#207, #211)
+- **No channel covered a document a user receives.** `SECURITY.md` — the security policy
+  at the root of the published package — said "Current version: 11.9.0", and
+  getting-started, faq, troubleshooting, user-guide and sdk-reference all titled
+  themselves v11.9.0: three releases stale, while every npm manifest was correct.
+  `--check` was green throughout, because a channel that does not exist cannot drift.
+  Structural markers now track canonical; narrative measurements deliberately do not.
+  (#211)
+- A bump is not finished when `sync-version.js` exits. Two tracked artifacts are gated
+  against `package.json` and only a build can write them —
+  `plugins/mindforge/.claude-plugin/plugin.json` and
+  `plugins/mindforge/mcp/dist/index.js`. They are now reported under
+  `🔨 REQUIRE A BUILD` with the exact three-command chain, which nothing had documented.
+  (#211)
+- `sync-version.js` reported "a channel is AHEAD of canonical" whenever its exit code
+  was non-zero for any reason, so the `--fetch-sha` refusal for an unpublished tarball
+  claimed the formula LEADS canonical in the same run that printed "DEFERRED until after
+  publish (behind, not ahead)". (#211)
+- `changelogs/index.json`, which `bin/updater/changelog-fetcher.js` reads as the
+  authoritative version list, was missing 11.9.2. (#218)
+
+**Publishing**
+
+- **The tag push that publishes was exempt from every gate.** Publishing is triggered by
+  exactly one event — a `v*` tag push — and the repository's only ruleset targets
+  branches, so its six required checks applied to nothing on the path that ships. GitHub
+  cannot attach required status checks to a tag. A `preflight` job now gates it. (#216)
+- The `stable` npm dist-tag was moved by hand, or not at all — it sat three releases
+  behind `latest` (11.8.3 against 11.9.2, via 11.9.0 and 11.9.1), so `npm i mindforge-cc@stable` delivered a
+  build with none of the 11.9.x fixes. The release workflow now moves it as its final
+  step: forward-only, prereleases skipped, and verified against npm's uncached dist-tags
+  endpoint rather than the CDN-cached packument. (#216)
+
+**Dashboard**
+
+- `--status` and `--stop` were documented across the harness roots and the docs and implemented
+  nowhere; both
+  printed nothing and exited 0. Now implemented, before `express` is required, so they
+  work without the dependency installed. (#206)
+- `--stop` identified the target by the SHAPE of its command line, which matched any
+  `node <anything>/dashboard/server.js` — verified against
+  `node /var/www/unrelated_app/dashboard/server.js`. It now resolves the script's
+  realpath and compares it to its own. (#206)
+- `--status` printed a port it could not know: the PID file records only the pid, so it
+  reported whatever port that invocation happened to receive. Measured, `--status` on a
+  server started with `--port 7466` printed "port 7339". (#206)
+
+**Memory**
+
+- Every abandoned exit left a full copy of the database on disk — 1.8 GB of orphaned
+  `.tmp` files. (#199)
+- The SDK's WebSocket client took the caller's process down on a failed reconnect. (#191)
+
+**Verification**
+
+- `mindforge verify`'s lint stage used `--max-warnings=0`, which made it impossible to
+  pass in the repository it ships from: on a clean clone `npx eslint .` reports 190 problems /
+  0 errors / 190 warnings, so `verify` reported a lint FAILURE on a tree that is green by the
+  project's own contract. Aligned with the project's definition; errors still fail. (#204)
+- `temporal cleanup` printed "🧹 Cleaning up old temporal snapshots..." and
+  "✅ Cleanup complete." with no cleanup between them. Now wired to
+  `TemporalHub.gc({maxSnapshots: 50, maxAgeDays: 30})` with `--dry-run` and honest
+  counts, including zero. (#209)
+
+**Documentation that named things that do not exist**
+
+- The protocol files instructed the agent to run `soul-engine.js` and
+  `shard-controller.js`, neither of which exists anywhere in the package. Those steps
+  are reasoning protocols and now say so. (#205)
+- Fifteen phantom `/mindforge:` slash commands in shipped docs. A reader following
+  `docs/user-guide.md` typed `/mindforge:personas --list` and got nothing. They were not
+  typos: `.agent/workflows/` holds 130 tracked files using those exact names — an old
+  target layout, committed and orphaned, shipping zero files. (#209)
+- Four documented CLI invocations could not be run, each verified by running it:
+  `npx mindforge-cc@latest install` (exit 1), `mindforge-cli.js dashboard` (exit 1),
+  `npx mindforge auto` in a shipped engine doc (`auto` is a slash command, never a CLI
+  verb), and `@mindforge <verb>`, a syntax that exists nowhere. (#213)
+- `workflow` is the most-documented CLI verb in the project and works, but appeared in
+  neither `--help` nor the "Available commands" list, so a user who mistyped it was told
+  it does not exist. (#213)
+- Root `CLAUDE.md` named `bin/hooks/mindforge-context-monitor.js`; the file is under
+  `.agent/hooks/`. (#214)
+
+### Added
+
+- **`preflight` job on the release workflow.** Asserts the tagged commit is an ancestor
+  of `origin/main`, then runs the six gates a tag push never saw, with the publish job
+  behind `needs:`. (#216)
+- **Automatic `stable` dist-tag movement**, forward-only and verified. (#216)
+- **`node bin/dashboard/server.js --status` / `--stop`.** Not CLI verbs —
+  `mindforge-cli.js dashboard` does not route. (#206)
+- **`mindforge temporal cleanup --dry-run`.** (#209)
+- New regression gates, each falsified by mutation before being trusted:
+  `tests/protocol-claims.test.js` (no exemption list, deliberately — a name-keyed
+  allowlist was shown to excuse the exact defect it was written for), the shipped-doc
+  phantom-command gate, the CLI-verb gate, the authority-doc `.js` gate, the
+  version-channel round trips, and assertions that the release preflight itself cannot
+  be silently removed.
+
+### Notes for operators
+
+- `npm run version:check` is the offline drift check. A bump is finished only when
+  `sync-version.js` exits 0 — if it prints `🔨 REQUIRE A BUILD`, run the three commands
+  it names and commit both regenerated files.
+- Releases are now gated on being tagged from `main`. One residual, inherent to
+  tag-triggered workflows: a tag push resolves the workflow from the TAGGED ref, so a
+  tag placed on a commit predating this release runs that commit's workflow and is
+  ungated.

package/changelogs/v11.9.4.md

@@ -0,0 +1,155 @@
+# Changelog
+
+## [11.9.4] — 2026-08-22 — Delivery: the gates register, the tarball matches its tag, three packages attested
+
+Patch release. 11.9.3 argued that an instrument must not report success while doing
+nothing. 11.9.4 is what an adversarial audit of the **published** 11.9.3 artifact found
+when that standard was applied to the delivery itself: **enforcement that installed and
+then declined to register, a tarball that could not be reproduced from its own tag, and a
+README that understated what shipped.**
+
+Every finding here came from measuring the published package in a confined environment —
+not from reading the repository. That distinction is the whole content of this release.
+
+### BREAKING
+
+- **The installer now registers hooks on projects where it previously declined.** If you
+  install into a project that has an ancestor directory containing a `.claude`, MindForge
+  now writes `.claude/settings.json` (merging append-only into any existing file) instead
+  of skipping. On a machine that has ever run Claude Code, `~/.claude` makes that
+  essentially every project — so most installs go from **0 registered hooks to 8**. Three
+  of them can block a tool call. If you were relying on the installer being inert here,
+  it no longer is; `.mindforge/hook-registration.json` records exactly what was written,
+  and the previous settings file is backed up under `.mindforge/backups/`. (#224)
+
+### Fixed
+
+**Hook registration — the gates shipped installed but inert**
+
+- **`register()` skipped whenever any ancestor held a `.claude` directory.** Measured
+  against the published 11.9.3 tarball, confined HOME, `~/.claude` as the only ancestor:
+  **11 hook scripts installed, 0 registered, no settings file written.** The gates that
+  the shipped `CLAUDE.md` calls MANDATORY were copied in and left unreachable. Same
+  sandbox on 11.9.4: **8 registered, installer preflight executed 7 of 8 and verified all
+  3 deny-class hooks returning exit 2** before keeping the file. (#224)
+
+  The reason it printed — *"the harness will read `<ancestor>/.claude/settings.json`, not
+  this directory"* — was wrong three separate ways:
+
+  1. `~/.claude/settings.json` is the **user tier**, applied in addition to the project
+     tier. Its existence carries no information about whether a project file is read, so
+     the condition that suppressed the gates was satisfied by an ordinary laptop.
+  2. For a genuine project ancestor the claim is false too — that file is not read
+     either. Verified with a natural experiment: an ancestor two levels up carried a
+     `PreToolUse` Bash hook appending a marker to a log; across a dozen tool calls with
+     the inner directory as the project root, the log was never created. Skipping did not
+     deliver the gates elsewhere. It delivered them nowhere.
+  3. The git-boundary guard was **dead code**. `stop` was the git toplevel while the walk
+     began at `dirname(projectRoot)`, so when toplevel equalled projectRoot the stop
+     condition could never be true and the walk ran to the filesystem root every time.
+     The boundary meant to keep the check local is why it reached `$HOME`.
+
+  It now warns and registers anyway: a registration that turns out inert costs nothing and
+  becomes live when the harness is launched there, whereas a skip is guaranteed inert. The
+  check additionally requires a real `settings.json` **file** — the old one accepted any
+  directory named `.claude`, and the one it hit in practice held only markdown. (#224)
+
+- **The installer's only failure-path pointer led nowhere.** It told anyone whose hooks
+  were not registered to "see `docs/troubleshooting.md`", where the word *hook* appeared
+  **0** times. That file now carries the section the message names, separating "not
+  registered" from "registered but not live", and including a copy-paste payload that
+  drives a hook directly so a broken hook can be told apart from an unwired one. (#224)
+
+**Release artifacts**
+
+- **The published tarball could not be reproduced from its tag.**
+  `.mindforge/memory/sync-manifest.json` — gitignored, written at runtime by
+  `bin/memory/semantic-hub.js` — was **1 of 1979** shipped files not tracked at
+  `v11.9.3`, so provenance attested to a tree containing a file the repository does not
+  contain. With a `files[]` allowlist, a **directory** entry ships its contents regardless
+  of `.gitignore`; `files[]` already carried a negation for `pattern-library.jsonl` for
+  exactly this reason, and the manifest's entire content is the sync record *for that
+  already-excluded file*. (#225)
+
+- **`mindforge-sdk` is published again, with provenance.** It sat at **11.8.0** on npm
+  while `sync-version.js` kept `sdk/package.json` at canonical — seven releases of
+  disagreement (11.8.1 through 11.9.3, none published) that nothing detected, because
+  `version:check` verifies the tracked file and not what the registry serves. It was also
+  the only one of the three packages with **no attestation**. The release workflow now
+  publishes it with `--provenance`, after the two proven publishes and before the GitHub
+  Release, so the newest step cannot cost the others their artifacts.
+
+- **The Homebrew formula carries the real 11.9.3 digest.** Verified against an independent
+  measurement rather than the tool's own output, and explicitly confirmed not to be the
+  SHA-256 of npm's 21-byte `{"error":"Not found"}` body — the constant #203 used to write
+  for every unpublished version. (#223)
+
+**Honesty about what is enforced**
+
+- **The README understated the product.** "What is actually enforced" still declared that
+  **no install channel registers hooks**, with a `No / No` table, and stated that the
+  plugin channel's dispatcher crashes on every fire. Measured: the plugin's
+  `scripts/lib/` exists, all **14** path tokens in `plugins/mindforge/hooks/hooks.json`
+  resolve under the plugin root, and driving the dispatcher by hand returns **exit 2** for
+  `mindforge-block-no-verify` and `mindforge-config-protection`. A document that
+  under-claims a security capability is the same defect as one that over-claims it —
+  either way it describes a system that is not the one shipped. Now stated per channel,
+  with the four cases that remain deliberately unenforced and the three liveness
+  preconditions outside MindForge's control. (#225)
+
+**Defects the published-artifact audit found (#222)**
+
+- The **v11.9.3 release page shipped empty**: `changelog-fetcher.js --latest` exits 0
+  while writing zero bytes, so the `||` fallback never fired and a 195-line changelog
+  reached nobody. The step now prefers the in-tree changelog and fails on an empty body.
+- A **shipped CI snippet told users to `npx` a package we do not own**.
+  `npx mindforge …` resolves to an unrelated third-party package; in a fresh runner it is
+  fetched and unpacked, install scripts and all, inside a job holding `MINDFORGE_TOKEN`.
+  Now pinned with `--package=mindforge-cc`.
+- The **version-source gate missed a live defect twice**. `mindforge health` printed
+  `RELEASE v0.4.2` and `Current : v11.9.3` twenty-six lines apart in a project declaring
+  0.4.2, and produced `Unexpected end of JSON input` with no manifest at all — the verb
+  whose job is verifying installation integrity misreporting the installation. Widening
+  the gate surfaced two more of the same shape, one of which bound the **wrong** version
+  silently into approval records, which is worse than no binding because the check still
+  returns a verdict.
+- `mindforge approve` died with ENOENT on any non-Node project. Absent values are now
+  recorded as `null` rather than invented.
+
+**Test infrastructure**
+
+- `tests/production.test.js` carried the uncommitted diff into its clone with
+  `git diff HEAD` (which includes staged files) but committed it with `commit -a` (which
+  stages only modified and deleted **tracked** files). So any commit **adding** a file
+  under `bin/` or `tests/` left the clone dirty and failed the gate's own cleanliness
+  assertion — reintroducing precisely the `--no-verify` pressure that carry exists to
+  avoid, for the one case it did not cover.
+
+### Added
+
+New regression gates, each falsified by reinstating the exact defect and confirming RED,
+with every touched file restored byte-exact afterwards:
+
+- `tests/hook-registration-ancestor.test.js` — six properties, the first of which asserts
+  the ancestor detector fires at all, so the other five cannot pass by never triggering.
+- `every shipped file is tracked in git` — property-based, no name list. It cannot fail on
+  a clean clone, which is how the real leak survived CI, so it is paired with a second
+  test that plants the runtime state in a throwaway clone and then packs.
+- `all three published packages publish with provenance` — counts the `npm publish`
+  invocations rather than matching one, because a single-match regex was satisfied by
+  either of the two packages that already had an attestation while the SDK had none. Also
+  asserts the SDK step is idempotent and ordered after the proven publishes.
+
+### Notes for operators
+
+- **These fixes change installer behaviour on almost every project.** After upgrading,
+  check `.mindforge/hook-registration.json` to see what was registered, and restart the
+  harness — hooks are snapshotted at session start.
+- A registered hook is only *live* if the harness has been restarted, the project is
+  trusted in the harness, and `CLAUDE_PROJECT_DIR` is set with `node` on the hook PATH.
+  None of those three are in MindForge's control; the last is a deliberate trade against a
+  fail-closed shell tail that was measured denying benign commands on a fresh clone.
+- Two gaps remain that require repository settings rather than code, and are recorded
+  rather than claimed fixed: there is no `v*` **tag ruleset** restricting who may create
+  the ref that triggers publishing, and `NPM_TOKEN` is a long-lived repository secret with
+  no GitHub environment in front of it.

package/docs/References/config-reference.md

@@ -33,8 +33,11 @@ and be followed by `=`. Prose bullets that merely mention `[KEY]` are not parsed
 Three more are **recommended** — absent ones produce a warning, not an error:
 `[COST_WARN_USD]`, `[COST_HARD_LIMIT_USD]`, `[BLOCK_ON_SECURITY]`.
 
-> `[COST_HARD_LIMIT_USD]` is **declared but not enforced** as of 11.9.2. Do not rely on it as a
-> spend control; see the CHANGELOG.
+> `[COST_HARD_LIMIT_USD]` is **enforced from 11.9.3** (it was declared but inert in 11.9.2).
+> `preflight()` refuses the model call once today's ledger spend plus the call estimate reaches
+> the limit. Because the key is *recommended* rather than *required*, an absent key — or an
+> explicit `0` — leaves the cap off; a present-but-unparseable value is a hard error
+> (`COST_LIMIT_MISCONFIGURED`), not a silent bypass.
 
 ---
 

package/docs/References/sdk-api.md

@@ -2,7 +2,7 @@
 
 ## Package
 
-`@mindforge/sdk`
+`mindforge-sdk`
 
 ## Exports
 

package/docs/Templates/Codebase/architecture.md

@@ -146,7 +146,7 @@ Template for `.mindforge/codebase/ARCHITECTURE.md` - captures conceptual code or
 
 **CLI Command Execution:**
 
-1. User runs: `mindforge new-project`
+1. User runs: `mytool new-project`
 2. Commander parses args and flags
 3. Command handler invoked (`src/commands/new-project.ts`)
 4. Handler calls service methods (`src/services/project.ts` → `create()`)

package/docs/commands-reference.md

@@ -131,13 +131,12 @@ High-fidelity behaviors ported from the Superpowers library and hardened for pro
 
 | Command | Description |
 | :--- | :--- |
-| `/mindforge:brainstorming` | Deep exploratory protocol for intent clarification and architectural ideation. |
-| `/mindforge:swarm-execution` | Wave-based implemention for independent, non-conflicting tasks. |
-| `/mindforge:parallel-mesh` | Orchestrates a mesh of agent waves with automated dependency compaction. |
+| *(protocol, not a command)* | Wave-based implementation for independent tasks — see `.mindforge/engine/swarm-controller.md`. |
+| *(protocol, not a command)* | Mesh of agent waves with dependency compaction — see `.mindforge/engine/wave-executor.md`. |
 | `/mindforge:workspace` | Manages isolated development environments via git worktrees with smart safety checks. |
-| `/mindforge:tdd` | Strict Test-Driven Development (Red-Green-Refactor) with automated test generation. |
+| `/mindforge:skill-tdd` | Strict Test-Driven Development (Red-Green-Refactor) with automated test generation. |
 | `/mindforge:debug` | Systematic debugging using persistent state tracking and Root Cause Analysis. |
-| `/mindforge:verify-work` | Multi-level truth verification protocol (substance, existence, wiring). |
+| `/mindforge:verify-phase` | Multi-level truth verification protocol (substance, existence, wiring). |
 | `/mindforge:retrospective` | Facilitates structured team retrospectives with objective telemetry and metrics. |
 
 ---

package/docs/faq.md

@@ -1,4 +1,4 @@
-# MindForge FAQ (v11.9.0)
+# MindForge FAQ (v11.9.4)
 
 ## Is MindForge tied to Claude only?
 No. MindForge supports Claude Code and Antigravity. Install with `--claude`,
@@ -55,13 +55,21 @@ The `deep-research` workflow was removed before the v11.8.0 release (the superpo
 ## Version & Stability
 
 **Q: What version is current?**
-v11.9.0 — verify with `node bin/mindforge-cli.js --version`
+v11.9.4 — verify with `node bin/mindforge-cli.js --version`
 
 **Q: Is v11.9.0 production-stable?**
 Yes. The IQ200 deep-audit (258 discrete checks across 14 dimensions) shows 258/258 passing. 0 CVEs, 0 test failures, 0 ESLint errors, 0 TypeScript errors.
 
-**Q: What npm dist-tags point to v11.9.0?**
-Both `latest` and `stable`: `npx mindforge-cc@stable` or `npx mindforge-cc@latest`
+**Q: Which npm dist-tag should I install?**
+`latest` is every published release, including patches. `stable` tracks the newest
+non-prerelease and is moved by the release workflow as its final step — forward only, so it
+never regresses to an older version. Prerelease builds keep their own `rc` and `alpha` tags and
+never become `stable`. Use `npx mindforge-cc@latest` unless you specifically want to lag a
+release behind. Check what each points at right now with `npm dist-tag ls mindforge-cc`.
+
+> This answer deliberately names no version. It previously claimed `latest` and `stable` both
+> pointed at v11.9.0; measured, they were 11.9.2 and 11.8.3 — neither. A documented invariant
+> survives releases, a documented value does not.
 
 ## Known Limitations
 
@@ -72,4 +80,16 @@ Spawn dispatch is not yet implemented in v11.9.0. Use `/mindforge:auto` or `/min
 Tier-3 trust uses in-process key simulation in v11.9.0 — this is intentional and safe. `SECURITY_TIER_3_SIMULATED = true` is the documented v11.x behavior. Hardware TPM/HSM is planned for v12.x.
 
 **Q: What is the test coverage?**
-95/97 tests passing (0 failures, 2 permanently env-skipped). Line coverage ~66% — gaps are in `bin/source-loader.js` and `scripts/ci/validate-assets.js`. Target is 80% for v11.9.0.
+134 test files: 132 pass, 0 failures, 2 env-dependent skips (`browser.test.js` needs a Chromium
+daemon, `sre-integration.test.js` needs git worktree support and a clean tree).
+
+The enforced floor is **30% lines**, gated in CI by the `mindforge-quality` job
+(`npx c8 --check-coverage --lines 30 --exclude 'plugins/**' --exclude 'mcp-server/dist/**'`).
+The measured figure is printed by that job and deliberately not restated here. The previous
+answer to this question was wrong in three ways at once — a test count from a much smaller
+suite, a stale coverage figure, and two named coverage gaps that were no longer the gaps — and
+it stayed wrong because none of it was checked by anything. `tests/doc-count-claims.test.js`
+now pins every count this file does state.
+
+Both `--exclude` flags are load-bearing: without them c8 measured the generated `plugins/` tree
+and `mcp-server/dist/` esbuild output, which understated real coverage substantially.

package/docs/getting-started.md

@@ -1,4 +1,4 @@
-# MindForge — Getting Started (v11.9.0)
+# MindForge — Getting Started (v11.9.4)
 
 This guide gets you from zero to a working MindForge project in under five minutes.
 
@@ -54,7 +54,13 @@ Run the MindForge MCP server (`mindforge-mcp-server`) over stdio — it exposes
 claude mcp add mindforge -- npx -y mindforge-mcp-server
 ```
 
-This server is also published to the [MCP Registry](https://registry.modelcontextprotocol.io) as `io.github.sairam0424/mindforge` (currently `11.9.0`, marked latest).
+This server is also published to the [MCP Registry](https://registry.modelcontextprotocol.io) as
+`io.github.sairam0424/mindforge`. **The registry entry lags this package** — it is republished
+manually, so check what it actually serves before relying on it:
+`curl -s 'https://registry.modelcontextprotocol.io/v0/servers?search=io.github.sairam0424/mindforge'`.
+To pin a known version instead, install `mindforge-mcp-server` from npm directly. (The previous
+wording named a specific version and marked it latest; both were wrong in both directions, which
+is why this now describes how to check rather than asserting a number.)
 
 ### 4. Homebrew
 
@@ -108,7 +114,7 @@ Or use slash commands: `/mindforge:wf-code-audit`
 ## Your First 5 Minutes with MindForge
 
 1. **Verify install:** `node bin/mindforge-cli.js health`
-2. **Check version:** `node bin/mindforge-cli.js --version` (should print `11.9.0`)
+2. **Check version:** `node bin/mindforge-cli.js --version` (should print `11.9.4`)
 3. **List workflows:** `node bin/mindforge-cli.js workflow list`
 4. **Run first slash command:** Open Claude Code → `/mindforge:status`
 5. **Onboard your codebase:** Open Claude Code → `/mindforge:wf-onboard-codebase`
@@ -140,4 +146,4 @@ MindForge operates on a high-velocity 4-pillar lifecycle:
 
 - Explore the [User Guide](user-guide.md) for advanced features.
 - Switch to a specialized [Persona](PERSONAS.md) for target tasks.
-- Join the community: `/mindforge:join-discord`.
+- Join the community: https://github.com/sairam0424/MindForge/issues.