mindforge-cc 11.9.2 → 11.9.4

package/docs/sdk-reference.md

@@ -2,8 +2,8 @@
 
 ## Overview
 
-The `@mindforge/sdk` package provides a programmatic TypeScript API for integrating
-MindForge into tools, dashboards, and CI pipelines. Import from `@mindforge/sdk`.
+The `mindforge-sdk` package provides a programmatic TypeScript API for integrating
+MindForge into tools, dashboards, and CI pipelines. Import from `mindforge-sdk`.
 
 ```typescript
 import {
@@ -11,14 +11,14 @@ import {
   MindForgeEventStream,
   MindForgeMemory,
   commands,
-} from '@mindforge/sdk';
+} from 'mindforge-sdk';
 ```
 
-Current SDK version: `11.9.0`
+Current SDK version: `11.9.4`
 
 ---
 
-## SDK Exports (v11.9.0)
+## SDK Exports (v11.9.4)
 
 ```javascript
 const {
@@ -28,7 +28,7 @@ const {
   commands,               // Command registry
   batch,                  // Batch execution
   MindForgeMemory,        // Memory interface
-  VERSION                 // '11.9.0'
+  VERSION                 // '11.9.4'
 } = require('mindforge-sdk');
 // or: import { MindForgeClient, VERSION } from 'mindforge-sdk';
 ```
@@ -417,6 +417,14 @@ cd sdk && npm install && npm run build
 
 ## Installation
 ```bash
-npm install mindforge-sdk@11.9.1
+npm install mindforge-sdk
 # or: npx mindforge-cc@stable  # installs SDK as part of the framework
 ```
+
+> **`mindforge-sdk` is versioned independently of the framework.** The release workflow
+> (`.github/workflows/mindforge-release.yml`) publishes `mindforge-cc` and
+> `mindforge-mcp-server` only — it has no `sdk` steps — so `sdk/package.json`'s version
+> tracks the monorepo while the published package does not. At the time of writing the
+> latest published SDK is **11.8.0** (`npm view mindforge-sdk versions`), even though the
+> in-repo `sdk/package.json` reads 11.9.2. Install it unpinned, as above; pinning it to a
+> framework version yields `E404 No match found for version …`.

package/docs/troubleshooting.md

@@ -1,4 +1,4 @@
-# MindForge Troubleshooting (v11.9.0)
+# MindForge Troubleshooting (v11.9.4)
 
 This page lists common issues and fast fixes. If you get stuck, start with
 `/mindforge:health`.
@@ -117,15 +117,19 @@ rerun migration. See `.mindforge/audit/AUDIT-SCHEMA.md` for expected format.
 
 ### Protocol Step 0 fails to activate
 **Symptom:** Commands proceed without activating `_extended` skills.
-**Fix:** Run `/mindforge:neural-orchestrator --reset`. Ensure all `_extended` skills are present in `.agent/skills/`.
+**Fix:** Ensure all `_extended` skills are present in `.agent/skills/`, then start a fresh session so the
+skill loader re-reads them. There is no orchestrator reset command.
 
 ### Context drift in Parallel Mesh
 **Symptom:** Parallel agents making conflicting decisions.
-**Fix:** Run `/mindforge:parallel-mesh --sync`. This forces a global state re-synchronization across all active worker identities.
+**Fix:** Re-synchronise by re-reading `.planning/HANDOFF.json` and `.planning/auto-state.json` before the
+next wave — the mesh protocol is described in `.mindforge/engine/wave-executor.md`. It is a protocol you
+follow, not a command.
 
 ### Workspace isolation failure
 **Symptom:** Conflicts between feature branches or dirty worktree.
-**Fix:** Run `/mindforge:workspace-isolated --cleanup`. Use `/mindforge:health --repair` if `.git/worktrees/` is corrupt.
+**Fix:** Run `/mindforge:workspace` to inspect worktree state. Use `/mindforge:health --repair` if
+`.git/worktrees/` is corrupt.
 
 ---
 
@@ -133,7 +137,7 @@ rerun migration. See `.mindforge/audit/AUDIT-SCHEMA.md` for expected format.
 If the above doesn’t resolve it:
 - Review `docs/user-guide.md`
 - Check `docs/security/SECURITY.md` for security issues
-- Open a GitHub issue or join the Discord: `/mindforge:join-discord`
+- Open a GitHub issue: https://github.com/sairam0424/MindForge/issues
 - **Architecture**: `docs/architecture/V5-ENTERPRISE.md`
 - **Commands**: `docs/commands-reference.md`
 - **Personas**: `docs/PERSONAS.md`
@@ -203,4 +207,59 @@ All tests must be run from the MindForge project root: `cd /path/to/MindForge &&
 
 **Symptom:** `--version` flag reports "Unknown command" on installs older than v11.9.0.
 
-**Fix:** Upgrade to v11.9.0: `npx mindforge-cc@latest install`
+**Fix:** Upgrade: `npx mindforge-cc@latest --claude --local`
+
+---
+
+## Hooks are installed but nothing is blocked
+
+**Symptom:** The hook scripts are present under `.claude/hooks/`, but a command that should be denied
+— say `git commit --no-verify` — runs normally.
+
+Hooks have two separate failure modes: **not registered** (no config names them) and **registered but
+not live** (the config exists, the harness has not applied it). Check them in that order.
+
+**1. Was registration attempted, and what did it decide?** The installer prints one line for every
+outcome, and writes a receipt:
+
+```
+cat .mindforge/hook-registration.json
+```
+
+`registered: false` there carries the reason. Registration is deliberately narrow: Claude Code only,
+`--local` only, non-Windows. A self-install inside a MindForge checkout also declines, because that
+repo maintains its own tracked config.
+
+**2. Restart the harness.** Claude Code snapshots hooks at session start, so a registration performed
+during an open session is not live in it. This is the single most common cause.
+
+**3. Confirm the project is trusted.** User-tier and project-tier settings are applied independently:
+`~/.claude/settings.json` is the user tier and applies to every session, while
+`<project>/.claude/settings.json` is the project tier and needs the project itself to be trusted.
+Measured on one machine: the user-tier hooks fired on every tool call while the project-tier hooks in
+the same session did not, and that project's entry in `~/.claude.json` had
+`hasTrustDialogAccepted: false`. Accept the trust prompt for the directory, then use `/hooks` to
+confirm the entries are listed.
+
+**4. Drive the hook directly** to separate "the hook is broken" from "the hook is not wired". This
+takes the harness out of the loop entirely — a deny-class hook must exit **2**:
+
+```bash
+echo '{"hook_event_name":"PreToolUse","tool_name":"Bash","cwd":"'"$PWD"'","tool_input":{"command":"git commit --no-verify -m x"}}' \
+  | node .claude/hooks/run-with-flags.js mindforge-block-no-verify .claude/hooks/mindforge-block-no-verify.js minimal,standard,strict
+echo "exit=$?"
+```
+
+Exit 2 with a `BLOCKED:` line on stderr means the hook works and the problem is registration or
+trust. Exit 0 with the payload echoed back means the dispatcher could not load the script — check
+that the second path exists under `.claude/hooks/`.
+
+**5. If you launch the harness somewhere else, install there too.** Project settings are read from the
+directory the harness starts in; they are **not** inherited from a parent directory. An ancestor
+project having its own `.claude/settings.json` does not make its hooks apply here, and does not stop
+these from applying — the installer warns when it sees one, and still registers.
+
+**Known residual:** if `CLAUDE_PROJECT_DIR` is unset, or `node` is not on the hook PATH, the
+registered commands exit 1 and the gate is simply absent — the same position as not installing. This
+is a deliberate trade: a fail-closed shell tail was measured denying benign commands on a fresh
+clone.

package/docs/user-guide.md

@@ -1,8 +1,8 @@
-# MindForge User Guide (v11.9.0)
+# MindForge User Guide (v11.9.4)
 
 This guide gets you from install to productive, with the minimum needed to run MindForge in a real project.
 
-> **v11.9.0 Stats:** 35 workflows · 221 slash commands · 232 engine skills · 216 personas · 0 CVEs · 258/258 IQ200 checks passing
+> **v11.9.4 Stats:** 35 workflows · 221 slash commands · 232 engine skills · 216 personas · 0 CVEs · 258/258 IQ200 checks passing
 
 ## Prerequisites
 
@@ -44,7 +44,7 @@ mindforge health          # Verify project integrity
 mindforge security-scan   # Run security checks
 mindforge headless        # Run agent in non-interactive mode
 mindforge --verbose ...   # Enable verbose output for debugging
-mindforge --version       # Print installed version (e.g. 11.9.0) and exit 0
+mindforge --version       # Print installed version (e.g. 11.9.4) and exit 0
 ```
 
 Use `--verbose` (or `-v`) on any command for detailed diagnostic output. Use `--version` (or `-V`) to print the installed version and exit.
@@ -127,7 +127,7 @@ MindForge features 211 specialized personas. Each persona is optimized for a spe
 To switch personas or see the full list:
 
 ```bash
-/mindforge:personas --list
+ls .mindforge/personas/            # 216 persona briefs; there is no personas command
 ```
 
 ---
@@ -137,7 +137,7 @@ To switch personas or see the full list:
 For complex tasks that require minimal intervention:
 
 ```bash
-/mindforge:autonomous --phase [N]
+/mindforge:auto --phase [N]
 ```
 
 Use the **Steer** command to guide logic without stopping execution:
@@ -153,7 +153,7 @@ Use the **Steer** command to guide logic without stopping execution:
 Observe your agent waves, token spend, and milestone progress in real-time.
 
 ```bash
-/mindforge:dashboard --start --open
+/mindforge:dashboard --open
 ```
 
 The dashboard provides a premium web interface at `http://localhost:7339`.
@@ -179,7 +179,7 @@ Extend MindForge by learning from documentation or authoring custom protocols.
 
 ```bash
 /mindforge:learn https://docs.nextjs.org "nextjs-mastery"
-/mindforge:skill-creation # Author a new high-fidelity protocol
+/mindforge:skills-index   # browse the catalogue; author new skills per the guide in CLAUDE.md
 ```
 
 ---
@@ -189,7 +189,7 @@ Extend MindForge by learning from documentation or authoring custom protocols.
 MindForge features automated PR creation and commit management.
 
 ```bash
-/mindforge:pr-branch "feature/auth-refactor"
+git switch -c feature/auth-refactor   # no pr-branch command; use git, then /mindforge:pr-review
 /mindforge:ship --auto-pr
 ```
 
@@ -202,7 +202,7 @@ MindForge provides mission-critical resilience and sovereign reasoning for enter
 ### Multi-Cloud Arbitrage
 MindForge automatically hedges against provider outages and optimizes for cost/latency.
 ```bash
-/mindforge:settings --cloud-arbitrage on
+# settings live in MINDFORGE.md as [KEY] = value; edit it, then run `mindforge security-scan`
 ```
 
 ### Sovereign Reason Enclaves (SRE)
@@ -214,8 +214,8 @@ Tier 3 (Principal) agents execute reasoning in isolated enclaves to protect sens
 ### Dynamic Human-Agent Handover & Temporal Steering (Pillar VII)
 NEXUS enables sub-second state reconstruction and **Hindsight Injection**. When an agent drifts, roll back its logic via the Dashboard's **Temporal Slider** and inject a steering vector to re-orient the wave.
 ```bash
-/mindforge:temporal status     # View active reasoning snapshots
-/mindforge:temporal inject [ID] # Manual CLI-based hindsight
+mindforge temporal status      # View active reasoning snapshots (a CLI command)
+mindforge temporal inject [ID] # Manual CLI-based hindsight
 ```
 
 ### Agentic Revenue Operations (AgRevOps) (Pillar VIII)
@@ -239,7 +239,7 @@ The **Enterprise Expansion** introduces 14 hardened protocols from the Superpowe
 
 Activate the mesh for any session:
 ```bash
-/mindforge:neural-orchestrator
+# the orchestrator layer is a protocol in .mindforge/engine/, not a command
 ```
 
 ---
@@ -260,7 +260,7 @@ Keep your framework current with the latest personas and library updates:
 
 MindForge allows you to "time-travel" through your agent's reasoning.
 
-1.  **Launch the Dashboard**: `/mindforge:dashboard --start --open`
+1.  **Launch the Dashboard**: `/mindforge:dashboard --open`
 2.  **Navigate to 'Temporal'**: Use the horizontal slider to scrub through reasoning snapshots.
 3.  **Inspect State**: View the exact memory, file diffs, and thought chain at that point in space-time.
 4.  **Inject Hindsight**: If you see a logic error, use the **Hindsight Injector** form to roll back and provide a corrective "Steering Vector."
@@ -283,4 +283,4 @@ Monitor your project's economic performance in real-time via the **RevOps Hub**.
 - **USP & Roadmap**: `docs/usp-features.md`
 - **Commands**: `docs/commands-reference.md`
 - **Troubleshooting**: `docs/troubleshooting.md`
-- **Discord**: `/mindforge:join-discord`
+- **Issues**: https://github.com/sairam0424/MindForge/issues

package/examples/sdk-integration/README.md

@@ -1,6 +1,6 @@
 # SDK Integration Example
 
-Demonstrates basic usage of the `@mindforge/sdk` package.
+Demonstrates basic usage of the `mindforge-sdk` package.
 
 ## Prerequisites
 

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "mindforge-cc",
-  "version": "11.9.2",
-  "description": "MindForge \u2014 Sovereign Agentic Intelligence Framework. Sovereign Stability: Production-Hardened Agentic Intelligence (v11)",
+  "version": "11.9.4",
+  "description": "MindForge — Sovereign Agentic Intelligence Framework. Sovereign Stability: Production-Hardened Agentic Intelligence (v11)",
   "bin": {
     "mindforge-cc": "bin/install.js",
     "mindforge": "bin/mindforge-cli.js"
@@ -29,6 +29,7 @@
     ".mindforge/intelligence/",
     ".mindforge/memory/",
     "!.mindforge/memory/pattern-library.jsonl",
+    "!.mindforge/memory/sync-manifest.json",
     ".mindforge/metrics/",
     "!.mindforge/metrics/token-usage.jsonl",
     ".mindforge/models/",
@@ -62,12 +63,16 @@
     "coverage": "npx c8 node tests/run-all.js",
     "lint": "eslint .",
     "harness:audit": "node bin/harness-audit.js",
+    "harness:gate": "node bin/harness-audit.js --min-score 76 --fail-on-findings",
+    "harness:gate:install": "node scripts/ci/harness-gate-install.js",
     "harness:compliance": "node bin/installer/harness-adapter-compliance.js --check",
     "release:ready": "node bin/utils/readiness-gate.js release",
+    "version:check": "node scripts/sync-version.js --check",
     "validate:assets": "node scripts/ci/validate-assets.js",
     "eval:retrieval": "node bin/eval/eval-harness.js --set golden-set-retrieval.json --min-recall 0.55",
     "commit": "cz",
-    "prepare": "husky"
+    "prepare": "husky",
+    "verify:pinning": "node scripts/ci/verify-action-pinning.js"
   },
   "keywords": [
     "claude-code",

package/subagents/.claude-plugin/marketplace.json

@@ -6,7 +6,7 @@
   },
   "metadata": {
     "version": "1.0.3",
-    "description": "Curated collection of 154 specialized Claude Code subagents organized into 10 focused categories"
+    "description": "Curated collection of 164 specialized Claude Code subagents organized into 10 focused categories"
   },
   "plugins": [
     {

package/.mindforge/memory/sync-manifest.json

@@ -1,6 +0,0 @@
-{
-  "pattern-library.jsonl": {
-    "lastSync": "2026-08-16T19:50:41.118Z",
-    "localCount": 1
-  }
-}

package/bin/dashboard/approval-handler.js

@@ -1,136 +0,0 @@
-/**
- * MindForge v2 — Approval Handler
- * Handles POST /api/approve/:id — approve or reject governance requests.
- * Reads/writes APPROVAL-*.json files in .planning/approvals/
- */
-'use strict';
-
-const fs   = require('fs');
-const path = require('path');
-
-// Paths resolved lazily for testing
-const getPaths = () => ({
-  approvals: path.join(process.cwd(), '.planning', 'approvals'),
-  audit:     path.join(process.cwd(), '.planning', 'AUDIT.jsonl'),
-});
-
-/**
- * Process an approval decision from the dashboard.
- * @param {string} approvalId - The APPROVAL UUID
- * @param {string} decision   - 'approve' or 'reject'
- * @param {string} comment    - Optional comment
- * @param {string} approver   - Approver identifier (email or name)
- * @returns {{ success, decision, message }}
- */
-function processDecision(approvalId, decision, comment, approver, confirmationId = null) {
-  // Input validation
-  if (!approvalId || typeof approvalId !== 'string') {
-    return { success: false, error: 'Invalid approval ID' };
-  }
-
-  // Sanitize approvalId — only allow UUID characters
-  if (!/^[a-f0-9-]{36}$/.test(approvalId)) {
-    return { success: false, error: 'Malformed approval ID format' };
-  }
-
-  if (!['approve', 'reject'].includes(decision)) {
-    return { success: false, error: 'Decision must be "approve" or "reject"' };
-  }
-
-  // Find the approval file
-  const paths    = getPaths();
-  const filePath = path.join(paths.approvals, `APPROVAL-${approvalId}.json`);
-  if (!fs.existsSync(filePath)) {
-    return { success: false, error: `Approval not found: ${approvalId}` };
-  }
-
-  let approval;
-  try {
-    approval = JSON.parse(fs.readFileSync(filePath, 'utf8'));
-  } catch {
-    return { success: false, error: 'Cannot parse approval file' };
-  }
-
-  // Validate approval is still pending
-  if (approval.status !== 'pending') {
-    return { success: false, error: `Approval already ${approval.status}` };
-  }
-
-  // Check expiry
-  if (approval.expires_at && new Date(approval.expires_at) < new Date()) {
-    return { success: false, error: 'Approval has expired' };
-  }
-
-  // TIER 3 CONFIRMATION — require typing the plan ID
-  if (approval.tier === 3 && decision === 'approve') {
-    const expectedConfirmation = `${approval.phase}-${approval.plan}`;
-    if (!confirmationId || confirmationId.trim() !== expectedConfirmation) {
-      return {
-        success: false,
-        error: `Tier 3 approval requires typing the plan ID "${expectedConfirmation}" to confirm.`,
-        confirmation_required: true,
-        expected: expectedConfirmation,
-        tier3_warning: 'This is a Tier 3 change (auth/payment/PII). Review the code diff before approving.',
-      };
-    }
-  }
-
-  // Write AUDIT entry FIRST (before updating file)
-  writeAuditEntry({
-    id:          require('crypto').randomBytes(8).toString('hex'),
-    timestamp:   new Date().toISOString(),
-    event:       decision === 'approve' ? 'approval_granted' : 'approval_rejected',
-    approval_id: approvalId,
-    tier:        approval.tier,
-    phase:       approval.phase,
-    plan:        approval.plan,
-    resolved_by: approver || 'dashboard',
-    comment:     comment || null,
-    agent:       'mindforge-dashboard',
-    session_id:  'dashboard',
-  });
-
-  // Update approval file
-  const updated = {
-    ...approval,
-    status:       decision === 'approve' ? 'approved' : 'rejected',
-    resolved_at:  new Date().toISOString(),
-    resolved_by:  approver || 'dashboard',
-    comment:      comment || null,
-    resolution_channel: 'mindforge-dashboard',
-  };
-
-  fs.writeFileSync(filePath, JSON.stringify(updated, null, 2));
-
-  return {
-    success:     true,
-    decision,
-    approval_id: approvalId,
-    tier:        approval.tier,
-    message:     `${approval.tier === 3 ? 'Tier 3' : 'Tier 2'} approval ${decision}d for Plan ${approval.phase}-${approval.plan}`,
-  };
-}
-
-function writeAuditEntry(entry) {
-  try {
-    const paths = getPaths();
-    if (!fs.existsSync(path.dirname(paths.audit))) return;
-    // UC-04b: unified, hash-chained, durable append into the single verifiable chain.
-    const { appendAuditEntrySync } = require('../autonomous/audit-writer');
-    appendAuditEntrySync(paths.audit, entry);
-  } catch { /* ignore AUDIT write failures */ }
-}
-
-function listApprovals() {
-  const paths = getPaths();
-  if (!fs.existsSync(paths.approvals)) return [];
-  return fs.readdirSync(paths.approvals)
-    .filter(f => f.startsWith('APPROVAL-') && f.endsWith('.json'))
-    .map(f => {
-      try { return JSON.parse(fs.readFileSync(path.join(paths.approvals, f), 'utf8')); }
-      catch { return null; }
-    })
-    .filter(Boolean);
-}
-
-module.exports = { processDecision, listApprovals };