mindforge-cc 11.9.7 → 11.9.9

package/bin/installer-core.js

@@ -636,13 +636,16 @@ async function install(runtime, scope, options = {}) {
     const assetMappings = [
       { key: 'skillsSubdir',   src: src('.agent', 'skills'),      label: 'skills' },
       { key: 'hooksSubdir',    src: src('.agent', 'hooks'),       label: 'hooks' },
-      { key: 'personasSubdir', src: src('.mindforge', 'personas'), label: 'personas' },
       // NB: on-disk dirs are capitalized (docs/References, docs/Templates). macOS is
       // case-insensitive so lowercase used to "work" locally, but npm/Linux is
       // case-sensitive — the lookup silently missed in production (UC: REFERENCES 0).
       { key: 'docsSubdir',     src: src('docs', 'References'),    label: 'references' },
       { key: 'docsSubdir',     src: src('docs', 'Templates'),     label: 'templates' }
     ];
+    // Mirrors the real copy logic in Section 2.1: personas are skipped under --minimal.
+    if (!minimal) {
+      assetMappings.push({ key: 'personasSubdir', src: src('.mindforge', 'personas'), label: 'personas' });
+    }
 
     assetMappings.forEach(asset => {
       const subDir = cfg[asset.key];
@@ -813,17 +816,25 @@ async function install(runtime, scope, options = {}) {
     }
   }
 
-  // ── 2.1 Install Enterprise Assets (Skills, Hooks, Personas) ─────────────────
+  // ── 2.1 Install Enterprise Assets (Skills, Hooks, Personas, Docs, Memory, Plugins) ──
   if (scope === 'local' && !selfInstall) {
     const assetTypes = [
       { key: 'skillsSubdir',   src: src('.agent', 'skills'),      label: 'skills' },
       { key: 'hooksSubdir',    src: src('.agent', 'hooks'),       label: 'hooks' },
-      { key: 'personasSubdir', src: src('.mindforge', 'personas'), label: 'personas' },
       { key: 'docsSubdir',     src: src('docs', 'References'),    label: 'references' },
       { key: 'docsSubdir',     src: src('docs', 'Templates'),     label: 'templates' },
       { key: 'memorySubdir',   src: src('.mindforge', 'memory'),   label: 'memory' },
       { key: 'pluginsSubdir',  src: src('.mindforge', 'plugins'),  label: 'plugins' }
     ];
+    // 'personas' is gated on !minimal, not removed: this copy into <runtime>/personas/ (e.g.
+    // .claude/personas/) is a real, tested, documented per-harness asset delivery contract
+    // (bin/installer/harness-adapter-compliance.js's ADAPTER_RECORDS asserts a >=218-file floor
+    // here for every harness except copilot), not dead/unused. The bug was that it ran
+    // unconditionally regardless of --minimal, undermining --minimal's "no persona library"
+    // promise (README.md, docs/getting-started.md) by shipping the full persona set anyway.
+    if (!minimal) {
+      assetTypes.push({ key: 'personasSubdir', src: src('.mindforge', 'personas'), label: 'personas' });
+    }
 
     assetTypes.forEach(asset => {
       const subDir = cfg[asset.key];
@@ -882,7 +893,10 @@ async function install(runtime, scope, options = {}) {
       if (minimal) {
         const minimalEntries = new Set([
           'MINDFORGE-SCHEMA.json',
-          'engine', 'org', 'governance', 'integrations', 'personas', 'skills', 'team'
+          // 'personas' deliberately excluded: --minimal's whole point is "no persona library"
+          // (README.md, docs/getting-started.md). It was accidentally left in this allowlist,
+          // so a --minimal install shipped the full 216-persona set anyway.
+          'engine', 'org', 'governance', 'integrations', 'skills', 'team'
         ]);
         fsu.ensureDir(forgeDst);
         for (const entry of fs.readdirSync(forgeSrc, { withFileTypes: true })) {
@@ -1079,6 +1093,13 @@ async function install(runtime, scope, options = {}) {
       // install-manifests/install-state pair, which are build- and CI-side and have no business in a
       // consumer project.
       'bin/installer/hook-registration.js',
+      // A thin (12-line) entry point whose only require is bin/governance/audit-verifier.js, which
+      // already ships unconditionally via sovereignEngines above -- so this adds zero new surface,
+      // just the one file consumers need to actually run "node bin/verify-audit.js" themselves.
+      // Previously gated behind --with-utils for no functional reason: CLAUDE.md documents
+      // "node bin/verify-audit.js" as a top-level command, not a --with-utils-only one, and a
+      // fresh default install had the doc but not the script.
+      'bin/verify-audit.js',
     ];
     coreFiles.forEach(rel => {
       const srcFile = src(...rel.split('/'));
@@ -1327,19 +1348,55 @@ async function run(args) {
     bannerVersion = require('./utils/mindforge-version').resolveMindforgeVersion(process.cwd()).version;
   } catch { /* a banner must never be the reason health cannot run */ }
 
-  // Print header and brand manifest
+  const runtimes = runtime === 'all'
+    ? Object.keys(RUNTIMES)
+    : runtime.split(',').map((r) => r.trim()).filter(Boolean);
+
+  const unknownRuntimes = runtimes.filter((rt) => !RUNTIMES[rt]);
+  if (unknownRuntimes.length) {
+    console.error(
+      `Unknown runtime(s): ${unknownRuntimes.join(', ')}. Valid: ${Object.keys(RUNTIMES).join(', ')}, all`
+    );
+    process.exit(1);
+  }
+
   // Print header and brand manifest
   Theme.printHeader(bannerVersion);
   Theme.printBrandManifest();
-  // Check for updates only
+  // `health` (routed here via --check — bin/mindforge-cli.js:33-37) advertises itself as "Verify
+  // project health and installation integrity". Until now it only did the first half — this
+  // npm-registry lookup — and returned before touching a single file on disk. Measured: in a fresh
+  // --claude --local install with bin/governance/policy-engine.js deleted by hand, `mindforge health`
+  // printed only "vX.Y.Z is the latest version" and exited 0 — the missing file was invisible to the
+  // one command whose job is to say so.
+  //
+  // verifyInstall() already exists as the real per-runtime file check (used by install() at :1144,
+  // see its own comment for why it was dead code before that). Reusing it here for a project's
+  // EXISTING install — rather than inventing a second checker — means both callers agree on what
+  // "installed" means.
   if (isCheck) {
     const { checkAndUpdate } = require('./updater/self-update');
     await checkAndUpdate({ apply: false });
+
+    let anyMissing = false;
+    for (const rt of runtimes) {
+      const cfg = RUNTIMES[rt];
+      const rtBaseDir = resolveBaseDir(rt, scope);
+      const rtCmdsDir = norm(path.join(rtBaseDir, cfg.commandsSubdir));
+      const verification = verifyInstall(rtBaseDir, rtCmdsDir, rt, scope);
+      if (verification.ok) {
+        Theme.printResolved(c.bold(`${rt} (${scope}): install verified (${verification.checked} required files present)`));
+      } else {
+        anyMissing = true;
+        console.error(`\n  ❌  ${rt} (${scope}): install verification failed — ${verification.missing.length} of ` +
+          `${verification.checked} required file(s) missing:`);
+        verification.missing.forEach(f => console.error(`      ${f}`));
+      }
+    }
+    if (anyMissing) process.exit(1);
     return;
   }
 
-  const runtimes = runtime === 'all' ? Object.keys(RUNTIMES) : [runtime];
-
   for (const rt of runtimes) {
     if (isUninstall)  await uninstall(rt, scope, options);
     else if (isUpdate) await install(rt, scope, { ...options, isUpdate: true });

package/bin/mindforge-cli.js

@@ -41,11 +41,11 @@ const COMMANDS = {
   },
   'pr-review': {
     script: 'bin/review/cross-review-engine.js',
-    description: 'Run standard PR review logic'
+    description: 'Alias for cross-review -- runs the same 2-model adversarial review engine'
   },
   'cross-review': {
     script: 'bin/review/cross-review-engine.js',
-    description: 'Run advanced cross-model review'
+    description: 'Run the 2-model adversarial cross-review engine (architect + security auditor)'
   },
   'classify': {
     script: 'bin/change-classifier.js',

package/bin/verify-audit.js

@@ -3,7 +3,13 @@
 const { verifyAuditChain } = require('./governance/audit-verifier');
 const auditPath = process.argv[2] || '.planning/AUDIT.jsonl';
 const result = verifyAuditChain(auditPath);
-if (result.valid) {
+if (result.missing) {
+  // Not a break: a project that has never written an audit entry has no chain to break. Measured
+  // before this branch existed: an absent log printed "❌ audit chain BROKEN at entry 0: unreadable:
+  // ENOENT..." and exited 1 — indistinguishable from real tamper detection to a brand-new user.
+  process.stdout.write(`ℹ️  no audit log yet at ${auditPath} — one will be created on first audited action\n`);
+  process.exit(0);
+} else if (result.valid) {
   process.stdout.write(`✅ audit chain valid: ${result.count} entries\n`);
   process.exit(0);
 } else {

package/bin/wizard/theme.js

@@ -76,7 +76,7 @@ const Theme = {
     console.log(`  ${this.colors.dim('│')}`);
     console.log(`  ${this.colors.dim('│')}  ${this.colors.cyan('⭐ HELP US GROW:')}`);
     console.log(`  ${this.colors.dim('│')}    - GitHub:  ${this.colors.dim('https://github.com/sairam0424/MindForge')}`);
-    console.log(`  ${this.colors.dim('│')}    - Discord: ${this.colors.dim('https://discord.gg/mindforge')}`);
+    console.log(`  ${this.colors.dim('│')}    - Discussions: ${this.colors.dim('https://github.com/sairam0424/MindForge/discussions')}`);
     console.log(`  ${this.colors.dim('│')}    - Docs:    ${this.colors.dim('https://github.com/sairam0424/MindForge#documentation')}`);
     console.log(`  ${this.colors.dim('│')}`);
     console.log(`  ${this.colors.dim('—'.repeat(80))}\n`);

package/changelogs/v11.9.8.md

@@ -0,0 +1,51 @@
+# Changelog
+
+## [11.9.8] — 2026-09-21 — What the README claims, verified line by line
+
+Patch release. v11.9.7's README rewrite got a literal, end-to-end audit: every command it
+documents actually run — real `npx` installs, a real Homebrew install/uninstall cycle, a
+real `npm i mindforge-sdk`, live registry checks — instead of re-reading the prose. 113
+claims checked: 98 held up, 14 didn't, 1 couldn't be verified either way. All 14 confirmed
+failures are fixed here.
+
+### Fixed
+
+**Two real bugs, not just docs**
+
+- `--runtime claude,cursor` (or any comma-separated runtime list) crashed the installer
+  outright ("Cannot read properties of undefined (reading 'localDir')"). `--all` already
+  expanded into a real multi-runtime loop; a comma-separated `--runtime` value was never
+  split into it, so it was looked up as the literal key `RUNTIMES['claude,cursor']`, which
+  doesn't exist. Fixed, plus a graceful "Unknown runtime(s)" exit for typos instead of a raw
+  crash.
+- `--minimal` claimed "no persona library" but shipped all 216 personas anyway — the
+  `minimalEntries` allowlist in `bin/installer-core.js` explicitly included `'personas'`.
+  Removed.
+
+**Twelve documentation inaccuracies**
+
+- Removed a `[--ads]` flag hint on `/mindforge:plan-phase` that was never wired into the
+  live command spec — it only exists in a much larger, never-ported legacy workflow file.
+- Reworded the bare `npx mindforge-cc@latest` "auto-detects your runtime" claim: real
+  detection only runs inside the interactive TTY wizard (and even there it's a pre-selected
+  default you still confirm); every non-interactive invocation (CI, piped stdin, scripted)
+  hardcodes `--claude`.
+- Disclosed that `/mindforge:health --repair` is documented in the command spec but not
+  wired into the CLI backing path — the flag is silently dropped, output is byte-identical
+  to plain `health`.
+- Fixed `/mindforge:tokens --profile` — that flag doesn't exist; swapped in a real one
+  (`--optimise`) and listed the actual flag set.
+- Disclosed that `node bin/mindforge-cli.js spawn <persona>` is a v1.0 stub that exits 1
+  with "NOT IMPLEMENTED", not a working scripted path.
+- Corrected the License section's copyright holder to match `LICENSE` exactly.
+- Fixed the architecture diagram's skill count: only 232 of the 355 skills live under
+  `.mindforge/` (engine tier); the other 123 are under `.agent/skills/` (extended tier).
+- Corrected `bin/`'s "~22K LOC" claim to the measured ~32K raw / ~25K stripped-of-comments.
+- Narrowed the Config reference doc-table row — that doc never mentions
+  `.mindforge/config.json`.
+- Reworded the Threat model doc-table row — that file is explicitly historical (v1.0.0-era),
+  not re-reviewed against v11.x, and redirects to `SECURITY.md`.
+- Reworded the USP-features doc-table row — that file has zero competitor comparison
+  content; it's the same honesty pass applied to MindForge's own features.
+- Disclosed that the `mindforge-plugin-*` namespace has zero packages published under it
+  today.

package/changelogs/v11.9.9.md

@@ -0,0 +1,59 @@
+# Changelog
+
+## [11.9.9] — 2026-09-23 — Release-readiness audit: 5 CRITICAL + 9 HIGH findings fixed
+
+Patch release. An 8-agent audit workflow tested every MindForge surface (slash commands,
+skills, personas, subagents, dynamic workflows, CLI/MCP, live install/verify/health) as a
+release gate before shipping to real external users. Every finding was independently
+re-verified against live code/commands before fixing, not trusted from the audit report
+alone.
+
+### Fixed
+
+**CRITICAL**
+
+- Removed the `godmode` skill entirely — a real, complete LLM jailbreak toolkit that was
+  shipping unconditionally in the published npm tarball, undisclosed anywhere in the docs.
+- Rewrote `help.md`/`status.md`/`health.md`/`security-scan.md`: they claimed
+  PQAS/biometric-bypass/lattice-crypto signature verification was "active by default,"
+  directly contradicted by `quantum-crypto.js`'s own comments (simulated, off by default).
+- Fixed `--minimal`: a second, unguarded persona-copy path in `installer-core.js` shipped
+  the full 218-file persona set regardless of `--minimal`. Gated on `!minimal` rather than
+  removed outright — the copy is a real, tested per-harness delivery contract, confirmed
+  against `harness-adapter-compliance.js`'s `ADAPTER_RECORDS`.
+- Fixed `security-scan.md`'s "Sovereign Integrity Check," which called a CLI flag on a
+  module with no CLI entrypoint (always exits 0) — a CRITICAL gate that could never fail.
+  Replaced with the one real check (policy-engine tamper detection).
+- Disclosed `bin/engine/skill-loader.js` as dead code (4 lines, zero callers). The real
+  trigger-matching mechanism is an LLM-followed protocol spec
+  (`.mindforge/engine/skills/loader.md`), not deterministic code.
+
+**HIGH**
+
+- `install-skill.md`: documented the literal action token (`install`/`register`/`audit`)
+  `bin/skill-registry.js` deliberately requires with no default.
+- `marketplace.md`: disclosed that zero published packages exist today; labeled sample
+  output as illustrative, not reproducible.
+- `status.md`: fixed a nonexistent-file reference (`AutoRunner.js` -> the real
+  `bin/autonomous/auto-runner.js`).
+- `pr-review`/`cross-review`: was an unqualified alias with descriptions implying different
+  behavior — now honestly documented as the same 2-model adversarial review engine.
+- 8 dynamic-workflow scripts (`feature-planner`, `tdd-sprint`, `onboard-codebase`,
+  `incident-response`, `release-prep`, `perf-optimize`, `refactor-plan`,
+  `verification-loop`): added null-guards after every dependent `agent()` call, matching
+  the pattern ~27 other scripts already use.
+- `MANIFEST.md`: registered 32 engine-tier skills that existed on disk but were never
+  listed in the registration source of truth (`systematic-debugging`,
+  `test-driven-development`, and 30 others).
+- 3 MF-series personas (`mf-tool`, `mf-memory`, `mf-executor`): replaced fictional tool
+  grants (`Database`, `API`, `task_boundary`, `commit_memory`,
+  `multi_replace_file_content`) with the real Claude Code tool vocabulary.
+- `swarm-templates.json`: reconciled 11 dangling persona references (2 fixed by name
+  correction, 9 removed with no real equivalent); updated `docs/PERSONAS.md`'s
+  `data-privacy-engineer` writeup to match the real `privacy-engineer.md` persona it now
+  points to.
+- `health` command: wired to `verifyInstall()` so it actually checks installation
+  integrity instead of only an npm-version lookup.
+- `AUDIT.jsonl`: distinguished "no audit log yet" from "chain broken" so a brand-new
+  install doesn't report a false BROKEN status; shipped `verify-audit.js` by default (its
+  only dependencies already shipped unconditionally).

package/docs/References/commands.md

@@ -36,7 +36,7 @@ the complete, verified list.
 | `/mindforge:note` | `note <text> [list|promote N]` | Zero-friction idea capture and todo promotion | v2.0.0 |
 | `/mindforge:quick` | `quick` | Run a small, single-task plan without a full phase | |
 | `/mindforge:status` | `status` | Show current phase, plan status, and next action | |
-| `/mindforge:health` | `health [--repair]` | Validate installation and repair drift | |
+| `/mindforge:health` | `health` | Validate installation. `--repair` is documented but not wired into the CLI backing path — it's silently ignored, byte-identical to plain `health`. | |
 | `/mindforge:review` | `review [N]` | Run a structured review pass for a phase | |
 | `/mindforge:debug` | `debug [plan-id]` | Debug a failed plan with root-cause workflow | |
 | `/mindforge:add-backlog` | `add-backlog <desc>` | Park ideas in 999.x "parking lot" | v2.0.0 |
@@ -70,7 +70,7 @@ the complete, verified list.
 | `/mindforge:metrics` | `metrics [--phase N]` | Compute quality and throughput metrics | |
 | `/mindforge:profile-team` | `profile-team` | Generate team skill and ownership profile | |
 | `/mindforge:benchmark` | `benchmark [--skill X]` | Measure skill effectiveness | |
-| `/mindforge:tokens` | `tokens [--profile] [--summary]` | Token usage profiling and optimisation | |
+| `/mindforge:tokens` | `tokens [--phase N] [--session ID] [--window short\|medium\|long] [--optimise]` | Token usage profiling and optimisation (`--profile`/`--summary` don't exist) | |
 
 ### Integrations & distribution
 

package/docs/References/config-reference.md

@@ -24,7 +24,7 @@ and be followed by `=`. Prose bullets that merely mention `[KEY]` are not parsed
 
 | Key | Example |
 | :--- | :--- |
-| `[VERSION]` | `11.9.2` — must match `^\d+\.\d+\.\d+$` |
+| `[VERSION]` | `11.9.8` — must match `^\d+\.\d+\.\d+$` |
 | `[REACTIVE_MODE]` | `true` |
 | `[PLANNER]` | `claude-opus-4-7` |
 | `[EXECUTOR]` | `claude-sonnet-4-6` |
@@ -56,6 +56,9 @@ for older configs.
 | `[VERIFIER]` | `VERIFIER_MODEL` | Testing and UAT verification. | `claude-sonnet-4-6` |
 | `[SECURITY]` | `SECURITY_MODEL` | Sensitive security scanning. | `claude-opus-4-7` |
 | `[DEBUG]` | — | Debugging and root-cause analysis. | `claude-opus-4-7` |
+| `[RESEARCH]` | `RESEARCH_MODEL` | Domain research during planning. | `gemini-2.5-pro` |
+| `[QA]` | `QA_MODEL` | Quality-assurance / test-writing tasks. | `claude-sonnet-4-6` |
+| `[QUICK]` | `QUICK_MODEL` | Tier-1 budget-biased tasks. | — |
 
 **Values are free-form strings** — the schema does not constrain them to a list, so a new model
 id works without a framework upgrade. The ids shipped in `MINDFORGE.md` today are
@@ -91,13 +94,15 @@ than editing your registry to satisfy it.
 
 These settings control the `/mindforge:auto` engine's behavior and performance.
 
+> [!WARNING]
+> `AUTONOMOUS_MODE_ENABLED`, `STUCK_DETECTION_TIMEOUT_MS`, `STEERING_CHECK_INTERVAL_MS`, and
+> `NODE_REPAIR_ENABLED` do not appear anywhere in `.mindforge/MINDFORGE-SCHEMA.json`, and nothing
+> in `bin/autonomous/` reads them — they are not currently configurable keys. Only the two rows
+> below are real.
+
 | Key | Description | Default |
 | :--- | :--- | :--- |
-| `AUTONOMOUS_MODE_ENABLED` | Global toggle for autonomous task execution. | `true` |
 | `MAX_TASKS_PER_PHASE` | Limit on task expansion during planning. | `15` |
-| `STUCK_DETECTION_TIMEOUT_MS` | Time before an agent is considered "looping" or stuck. | `300000` |
-| `STEERING_CHECK_INTERVAL_MS` | How often the engine checks for user guidance. | `5000` |
-| `NODE_REPAIR_ENABLED` | If true, the engine attempts to self-heal on failures. | `true` |
 | `COMPACTION_THRESHOLD_PCT` | The context usage percentage at which to trigger compaction. | `70` |
 
 ---
@@ -111,8 +116,7 @@ Define the rules that code must follow to pass the `VERIFY` phase.
 | `MIN_TEST_COVERAGE_PCT` | Required test coverage for any new module. | `80` |
 | `MAX_FUNCTION_LINES` | Maximum lines allowed for a single function. | `40` |
 | `MAX_CYCLOMATIC_COMPLEXITY` | Maximum complexity score (McCune) allowed. | `10` |
-| `BLOCK_ON_MEDIUM_SECURITY` | Fail the gate if any medium security findings exist. | `true` |
-| `ANTIPATTERN_SENSITIVITY` | Frequency at which suspicious patterns are flagged. | `0.7` |
+| `BLOCK_ON_MEDIUM_SECURITY_FINDINGS` | Fail the gate if any medium security findings exist. | `true` |
 
 ---
 
@@ -136,37 +140,18 @@ Control reasoning snapshot retention for the Temporal Steering system.
 | Key | Description | Default |
 | :--- | :--- | :--- |
 | `temporal.max_snapshots` | Maximum number of reasoning snapshots retained per session. | `50` |
-| `temporal.max_age_days` | Snapshots older than this value (in days) are auto-pruned. | `30` |
-
----
-
-## 6. Rate Limiting (v11.0.0+)
-
-Configure request rate limits for the dashboard and API endpoints.
-
-| Key | Description | Default |
-| :--- | :--- | :--- |
-| `rate_limiting.dashboard_rpm` | Maximum requests per minute to dashboard endpoints. | `120` |
-
----
-
-## 7. Session Configuration (v11.0.0+)
-
-Control session token behaviour for dashboard authentication.
-
-| Key | Description | Default |
-| :--- | :--- | :--- |
-| `session.token_expiry_hours` | Hours before a dashboard bearer token expires. | `24` |
+| `temporal.max_age_days` | Snapshots older than this value (in days) are auto-pruned. | `7` |
 
 ---
 
-## 8. Wave Execution (v11.0.0+)
-
-Tune parallel wave execution behaviour.
+## 6. Rate Limiting, Session Configuration, Wave Execution
 
-| Key | Description | Default |
-| :--- | :--- | :--- |
-| `wave_execution.max_concurrency` | Maximum number of tasks executed in parallel within a wave. | `6` |
+> [!WARNING]
+> `rate_limiting.dashboard_rpm`, `session.token_expiry_hours`, and
+> `wave_execution.max_concurrency` are not present in the current `.mindforge/config.json` and
+> nothing in the live `bin/` runtime reads them. The first two only ever existed as one-time
+> values written by a historical migration (`bin/migrations/10.7.0-to-11.0.0.js`); the third
+> doesn't appear anywhere in the codebase. Do not rely on setting any of these three today.
 
 ---
 
@@ -181,4 +166,4 @@ To ensure enterprise safety, several rules **cannot** be disabled via `MINDFORGE
 5. **Critical Security Blocks:** High/Critical findings *will* block the `SHIP` command.
 
 > [!WARNING]
-> Attempting to disable these rules in your configuration will result in a silent enforcement of the defaults. See [ADR-013](../adr/ADR-013-immutable-governance.md) for architectural details.
+> Attempting to disable these rules in your configuration will result in a silent enforcement of the defaults.

package/docs/References/sdk-api.md

@@ -1,4 +1,4 @@
-# MindForge SDK API — Reference (v2.0.0-alpha.4)
+# MindForge SDK API — Reference (v11.9.8)
 
 ## Package
 
@@ -9,11 +9,17 @@
 From `sdk/src/index.ts`:
 
 - `MindForgeClient`
-- `MindForgeEventStream`
-- `commands`
+- `MindForgeEventStream` — SSE-based event stream (see below)
+- `WebSocketEventStream` — WebSocket-based alternative; requires a global `WebSocket` (Node 22+,
+  a browser, or the optional `ws` package assigned to `globalThis.WebSocket` — the SDK declares
+  no runtime dependencies, so nothing is installed for you)
+- `commands` — slash-command string builders
+- `batch(commands: string[])` — joins an array of command strings with `&&`
 - `MindForgeMemory`
 - Types: `MindForgeConfig`, `PhaseResult`, `TaskResult`, `SecurityFinding`,
-  `GateResult`, `HealthReport`, `HealthIssue`, `MindForgeEvent`, `CommandOptions`
+  `GateResult`, `HealthReport`, `HealthIssue`, `MindForgeEvent`, `CommandOptions`,
+  `AuditLogEntry`, `WaveExecutionResult`, `MigrationResult`, `StreamChunk`,
+  `StreamingExecutionResult`, `BatchExecutionRequest`, `BatchExecutionResult`
 - `VERSION`
 
 ## MindForgeClient

package/docs/References/skills-api.md

@@ -13,12 +13,13 @@ Skills are domain knowledge packs loaded on demand. They are stored as
 ```
 
 ## SKILL.md schema (frontmatter)
-Required fields:
+Required fields, enforced by `scripts/ci/validate-assets.js` and `tests/skills-platform.test.js`:
 - `name`: string (stable in 1.x.x)
-- `description`: string
-- `triggers`: array of keywords
 - `version`: semver string
-- `owner`: string (team or org)
+- `status`: string (e.g. `stable`)
+- `triggers`: comma-separated keyword string, minimum 10 terms, unique across all engine skills
+
+`description` and `owner` are commonly present but are **not** enforced as required fields.
 
 Optional fields:
 - `scope`: `core | org | project`
@@ -30,8 +31,9 @@ Example:
 ---
 name: security-review
 version: 1.0.0
+status: stable
 description: Secure coding review checklist and threat modeling prompts
-triggers: ["auth", "payment", "pii", "encryption"]
+triggers: auth, payment, pii, encryption, secrets, credential, oauth, token, session, permission
 owner: mindforge-core
 scope: core
 ---
@@ -53,5 +55,5 @@ Skills can be published to the npm registry under `mindforge-skill-*`.
 See `docs/skills-publishing-guide.md` for full workflow.
 
 ## Stability contract
-As of v1.0.0, the `name` values of the 10 core skills are stable. New optional
-fields may be added in minor versions; removals require a major version bump.
+As of v1.0.0, the `name` values of the 232 engine-tier skills (`.mindforge/skills/`) are stable.
+New optional fields may be added in minor versions; removals require a major version bump.

package/docs/commands-reference.md

@@ -171,8 +171,8 @@ mindforge <command> [options]
 | `security-scan` | Validate configuration and run security checks |
 | `health` | Verify project health and installation integrity |
 | `headless` | Run MindForge agent in headless (non-interactive) mode |
-| `pr-review` | Run standard PR review logic |
-| `cross-review` | Run advanced cross-model architecture review |
+| `pr-review` | Alias for `cross-review` — same 2-model adversarial review engine |
+| `cross-review` | Run the 2-model adversarial cross-review engine (architect + security auditor) |
 | `classify` | Classify changes into governance tiers |
 | `approve` | Generate a governance approval signature to unblock Tier 3 gates |
 | `validate-skill` | Run Level 1 & 2 validation on a SKILL.md file |

package/docs/faq.md

@@ -1,4 +1,4 @@
-# MindForge FAQ (v11.9.7)
+# MindForge FAQ (v11.9.9)
 
 ## Is MindForge tied to Claude only?
 No. MindForge supports Claude Code and Antigravity. Install with `--claude`,
@@ -39,7 +39,7 @@ Plugins are preferred for sharing and versioning.
 
 ## Dynamic Workflows
 
-**Q: How many workflows does MindForge v11.9.0 include?**
+**Q: How many workflows does MindForge include?**
 35 pre-built multi-agent workflows across 5 tiers: Research (5), Dev (14), Ops (6), Intelligence (7), Beast (3).
 
 **Q: How do I run a workflow?**
@@ -55,10 +55,13 @@ The `deep-research` workflow was removed before the v11.8.0 release (the superpo
 ## Version & Stability
 
 **Q: What version is current?**
-v11.9.7 — verify with `node bin/mindforge-cli.js --version`
+v11.9.9 — 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: Was v11.9.0 production-stable?**
+At that release: yes, by the IQ200 deep-audit (258 discrete checks across 14 dimensions),
+258/258 passing, 0 CVEs, 0 test failures, 0 ESLint errors, 0 TypeScript errors. That was a
+one-time, point-in-time audit rather than a repeated gate, so it is not re-run per release —
+see "What is the test coverage?" below for the number that is.
 
 **Q: Which npm dist-tag should I install?**
 `latest` is every published release, including patches. `stable` tracks the newest
@@ -74,10 +77,10 @@ release behind. Check what each points at right now with `npm dist-tag ls mindfo
 ## Known Limitations
 
 **Q: Why does `spawn architect` exit with an error?**
-Spawn dispatch is not yet implemented in v11.9.0. Use `/mindforge:auto` or `/mindforge:next` from Claude Code instead.
+Spawn dispatch is a v1.0 stub — still not implemented as of v11.9.8. Use `/mindforge:auto` or `/mindforge:next` from Claude Code instead.
 
 **Q: Why does ZTAI show a Tier-3 warning?**
-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.
+Tier-3 trust uses in-process key simulation in v11.x. `bin/governance/ztai-manager.js` warns on this itself: key material resides in the Node.js heap, not hardware-isolated — do not use Tier-3 trust for production credential workflows. `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?**
 140 test files: 137 pass, 0 failures, 3 env-dependent skips (`browser.test.js` and

package/docs/getting-started.md

@@ -1,4 +1,4 @@
-# MindForge — Getting Started (v11.9.7)
+# MindForge — Getting Started (v11.9.9)
 
 This guide gets you from zero to a working MindForge project in under five minutes.
 
@@ -17,7 +17,8 @@ MindForge ships across several channels. Pick the one that matches how you work
 Zero-config setup that scaffolds the full framework:
 
 ```bash
-# Recommended (auto-detects your runtime)
+# Interactive wizard (TTY only) -- pre-selects a detected runtime, you confirm it.
+# Non-interactive/CI/piped invocations skip the wizard and default to --claude.
 npx mindforge-cc@latest
 
 # Antigravity (local development)
@@ -29,6 +30,11 @@ npx mindforge-cc@latest --claude --local
 
 After installation, the `mindforge` CLI command is available for runtime operations (health checks, security scans, headless execution, etc.).
 
+If a `CLAUDE.md` already exists in the target directory, the installer backs it up
+(`CLAUDE.md.backup-<timestamp>`) before writing its own — check that backup if you had custom
+content there. Hooks are snapshotted by Claude Code at session start, so if the harness was
+already open during install, restart it before expecting a newly-registered hook to fire.
+
 **Global install** (system-wide `/mindforge` commands for your primary AI coding runtime):
 
 ```bash
@@ -106,7 +112,7 @@ MindForge adapts to your existing engineering environment via runtime flags:
 
 **Run any workflow:**
 ```bash
-node bin/mindforge-cli.js workflow list              # browse all 32
+node bin/mindforge-cli.js workflow list              # browse all 35
 node bin/mindforge-cli.js workflow info code-audit   # details + phases
 ```
 Or use slash commands: `/mindforge:wf-code-audit`
@@ -114,7 +120,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.7`)
+2. **Check version:** `node bin/mindforge-cli.js --version` (should print `11.9.9`)
 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`

package/docs/sdk-reference.md

@@ -14,11 +14,11 @@ import {
 } from 'mindforge-sdk';
 ```
 
-Current SDK version: `11.9.7`
+Current SDK version: `11.9.9`
 
 ---
 
-## SDK Exports (v11.9.7)
+## SDK Exports (v11.9.9)
 
 ```javascript
 const {
@@ -28,7 +28,7 @@ const {
   commands,               // Command registry
   batch,                  // Batch execution
   MindForgeMemory,        // Memory interface
-  VERSION                 // '11.9.7'
+  VERSION                 // '11.9.9'
 } = require('mindforge-sdk');
 // or: import { MindForgeClient, VERSION } from 'mindforge-sdk';
 ```

package/docs/security/SECURITY.md

@@ -0,0 +1,14 @@
+# MindForge — Security Policy
+
+> This file used to duplicate the repo's security policy and had drifted out of sync (it was
+> still listing a `5.x.x`/`4.x.x`/`< 4.0.0` support table years behind the real `11.x` line). The
+> canonical, kept-current security policy — supported versions, vulnerability reporting process,
+> and the full "Security Features" / "Known Mitigations & Limitations" breakdown — lives at the
+> repo root: **[`/SECURITY.md`](../../SECURITY.md)**. Read that file, not this one.
+
+For the outward agentic-harness threat model (prompt injection, poisoned config/hooks/MCP,
+supply-chain risk in skills/agents, sandboxing) see
+**[`/MINDFORGE-AGENTIC-SECURITY.md`](../../MINDFORGE-AGENTIC-SECURITY.md)**.
+
+For the current, honestly-labeled status of Zero-Trust Agentic Identity specifically, see
+**[ZTAI Overview](./ZTAI-OVERVIEW.md)** — read its status banner first.