mindforge-cc 9.0.0 → 10.0.0

package/.agent/workflows/mindforge:workstreams.md

@@ -1,27 +0,0 @@
----
-description: Manage parallel feature tracks with isolated state
----
-<objective>
-Enable developers to work on multiple features or bugs concurrently within the same codebase without state collision. Provides isolated tracking for each "workstream".
-</objective>
-
-<execution_context>
-.claude/commands/mindforge/workstreams.md
-</execution_context>
-
-<context>
-Arguments: $ARGUMENTS (Switch subcommand)
-Storage: .planning/workstreams/
-State: Each workstream maintains its own subset of `STATE.md` or a local context file.
-</context>
-
-<process>
-1. **Route Subcommand**:
-    - `list`: Show all active and archived workstreams in `.planning/workstreams/`.
-    - `create <name>`: Initialize a new workstream directory and baseline state.
-    - `switch <name>`: Update the global pointer in `STATE.md` to the targeted workstream.
-    - `status`: Show the current active workstream and its progress.
-2. **Manage Isolation**:
-    - When switching, ensure current work is saved or stashed if necessary.
-3. **Confirm**: Success/Failure status message to user.
-</process>

package/.agent/workflows/publish-release.md

@@ -1,36 +0,0 @@
----
-description: Publish a new version of MindForge to npm
----
-
-# MindForge Publishing Workflow
-
-This workflow automates the pre-verification and publishing of MindForge.
-
-## Pre-Flight Checks
-
-1. Verify structural integrity
-// turbo
-npm test
-
-2. Check package contents
-// turbo
-npm pack --dry-run
-
-## Publish Execution
-
-**Note**: If this is a prerelease (alpha, beta, rc), you must specify the tag.
-
-3. Publish to npm
-```bash
-# For stable:
-npm publish --access public
-
-# For alpha:
-npm publish --tag alpha --access public
-```
-
-4. Create Git Tag
-```bash
-git tag v$(node -p "require('./package.json').version")
-git push origin --tags
-```

package/.claude/CLAUDE.md

@@ -1,102 +0,0 @@
-# MindForge — Unified Protocol Engine (v5.10.0-NEXUS)
-
-# MASTER DIRECTIVE: Every session MUST begin by loading the Parameter Registry (MINDFORGE.md) and activating the `mindforge-neural-orchestrator` layer.
-
----
-
-## 🎯 MISSION STATEMENT
-
-You are a **Dynamic Multi-Agent Swarm (Agentic Mesh)**. Your mission is to execute project objectives via parallel specialist clusters, ensuring architectural integrity and zero-trust verification.
-
----
-
-## 🛠️ CORE PROTOCOLS (The "How")
-
-### 1. Swarm Dynamic Orchestration (V4)
-**IF** task complexity/impact is high **OR** cross-disciplinary logic is required:
-1.  Invoke `SwarmController` and activate `mindforge-swarm-execution`.
-2.  Spawn task-specific ephemeral specialist cluster (AIEngineering, Security, etc.).
-3.  Inject knowledge patches via `PersonaFactory` (Context7).
-4.  Execute parallel mesh waves via `WaveExecutor` guided by `mindforge-parallel-mesh_extended`.
-5.  Consolidate mesh findings into a single `SWARM-SUMMARY`.
-
-### 2. The Sharded Memory Loop (SRD)
-**IF** context ≥ 70% **OR** starting a new task:
-1. Initialize `shard-controller.js`.
-2. Rotate context per the Tri-Tier strategy (Hot/Warm/Cold).
-3. Inject only sharded relevant data into the active buffer.
-
-### 3. The Adversarial Decision Loop (ADS)
-**BEFORE** committing any architectural change:
-1. Spawn Red-Team/Blue-Team debate contexts.
-2. Run `soul-engine.js` on the proposed diff.
-3. **STOP** if SOUL Score < `[MIN_SOUL_SCORE]` from MINDFORGE.md.
-
-### 4. Standard Extended Protocols (Quality Gates)
-**MANDATORY**: For specific workflows, activate the corresponding `_extended` protocol:
-- **Planning**: `mindforge-plan-phase_extended` + `mindforge-brainstorming`.
-- **Execution**: `mindforge-execute-phase_extended`.
-- **Debugging**: `mindforge-debug_extended` (Scientific RCA).
-- **TDD**: `mindforge-tdd_extended` (Red-Green-Refactor).
-- **Shipping**: `mindforge-ship_extended`.
-- **Verification**: `mindforge-verify-work_extended`.
-
-### 5. The Temporal Vision Loop (Hindsight & Steering)
-**IF** verification fails **OR** deep bug suspected **OR** manual correction needed:
-1. Invoke the **MindForge Dashboard (localhost:7339)** and navigate to the **Temporal** tab.
-2. Use the **Temporal Slider** to identify the exact divergence point in the reasoning history.
-3. Inject a **Hindsight Steering Vector** via the dashboard to rollback state and re-trigger optimization.
-4. Verify the `auto-state.json` status has transitioned to `awaiting_regeneration`.
-
-### 6. AgRevOps Governance (Pillar VIII)
-**MANDATORY for all Enterprise-tier sessions**:
-1. Monitor the **AgRevOps Hub** on the dashboard for real-time ROI tracking ($100/hr mapping).
-2. Validate the **Security Health Score** (must remain > 85).
-3. Check the **Velocity Forecaster** for milestone completion ETAs.
-
----
-
-## SESSION START PROTOCOL (The "Gates")
-
-Prioritize based on `[REACTIVE_MODE]` in MINDFORGE.md. These are the **Quality gates**:
-
-- [ ] **Load Config**: Read PROJECT.md, STATE.md, and **MINDFORGE.md**.
-- [ ] **Nexus Sync**: Ensure `NexusTracer` singleton is initialized and active.
-- [ ] **AgRevOps Check**: Verify ROI trends and Security Health Score via `/api/revops`.
-- [ ] **PLAN-FIRST RULE**: Never code without a verified XML plan.
-- [ ] **Verify First**: Never task-complete without successful `<verify>` output.
-- [ ] **Audit Always**: Write a JSONL entry for every significant session event. All entries must be Merkle-linked.
-
----
-
-## ⚡ COMMAND SUITE
-
-- `/mindforge:next` — Primary auto-discovery.
-- `/mindforge:auto` — Reactive engine start.
-- `/mindforge:brainstorming` — Creative & architectural exploration.
-- `/mindforge:history` — Temporal Hub access.
-- `/mindforge:status` — Project health & sharding state.
-- `/mindforge:audit` — Day 4 governance access.
-
----
-
-## 🛡️ CRITICAL SECURITY & AUTO-TRIGGER
-
-Any change to `Auth/Payment/PII/Uploads` triggers an automatic **Security Persona** lock (**SECURITY AUTO-TRIGGER**). **Tier 3** changes require manual overhead.
-
-1. Read `security-reviewer.md`.
-2. Run `mindforge:security-scan` PRE-COMMIT.
-3. Fail if any Medium+ findings are unaddressed.
-
----
-
-## ✍️ IDENTITY
-
-Adopt the Principal AI persona. Be instruction-dense, unambiguous, and architectural.
-
-**Source of Truth Hierarchy**:
-
-1. SOUL.md (Sovereign Identity — Behavioral OS)
-2. MINDFORGE.md (Parameter Registry)
-3. .agent/CLAUDE.md (Protocols)
-4. `.mindforge/` (Framework Binary Logic)

package/.claude/commands/forge/help.md

@@ -1,7 +0,0 @@
-Show all available FORGE commands and what they do.
-
-List every .md file in .claude/commands/forge/ and display:
-- Command name (filename without extension)
-- First line of the file as its description
-
-Format as a clean table. Also remind the user to read CLAUDE.md if they haven't yet.

package/.claude/commands/forge/init-project.md

@@ -1,32 +0,0 @@
-Initialize a new project under the FORGE framework.
-
-Follow these steps in order:
-
-1. Ask the user these questions one at a time (wait for each answer before asking the next):
-   - What is this project? (1-2 sentence description)
-   - Who is the target user?
-   - What is the core problem it solves?
-   - What tech stack do you want to use? (or "help me decide")
-   - What is absolutely NOT in scope for v1?
-   - What does success look like at the end of v1?
-
-2. If the user said "help me decide" on tech stack, ask 3 clarifying questions then recommend a stack with brief reasoning.
-
-3. Create `.planning/PROJECT.md` with:
-   - Project name and one-line description
-   - Problem statement
-   - Target user
-   - Tech stack (with brief rationale for each choice)
-   - v1 scope (what's in)
-   - Out of scope (what's explicitly not in v1)
-   - Success criteria
-
-4. Create `.planning/STATE.md` with:
-   - Status: Project initialized
-   - Current phase: None (not started)
-   - Last action: Project initialization
-   - Next step: Run /forge:plan-phase 1
-
-5. Create `.planning/REQUIREMENTS.md` (blank template with sections)
-
-6. Tell the user: "Project initialized. Run /forge:plan-phase 1 to begin planning your first phase."

package/.claude/commands/forge/plan-phase.md

@@ -1,30 +0,0 @@
-Plan a phase of the project. Usage: /forge:plan-phase [N]
-
-If N is not provided, check STATE.md for the current phase and use that.
-
-Steps:
-1. Read PROJECT.md, REQUIREMENTS.md, and STATE.md.
-2. Ask the user: "Describe what phase [N] should accomplish in 2-3 sentences."
-3. Ask: "Are there any specific implementation decisions you've already made for this phase?"
-4. Spawn a research subagent: Read the project's tech stack from PROJECT.md and research the best patterns, libraries, and pitfalls for implementing this phase. Write findings to `.planning/phases/phase-[N]/RESEARCH.md`.
-5. Create 3-6 atomic task plans in `.planning/phases/phase-[N]/`. Each PLAN file must use this XML format:
-```xml
-<plan>
-  <task>Task name</task>
-  <files>
-    specific/file/paths/to/touch.ts
-  </files>
-  <instructions>
-    Precise implementation instructions. Include:
-    - Which library to use and why (mention specific version if relevant)
-    - Any gotchas or anti-patterns to avoid
-    - The exact approach, not just "implement X"
-  </instructions>
-  <verify>Specific command or check that confirms this task is done</verify>
-  <done>One sentence definition of done for this task</done>
-</plan>
-```
-
-6. Check each plan against REQUIREMENTS.md. If a plan implements something out of scope, revise it.
-7. Update STATE.md: current phase = N, status = "Phase [N] planned, ready to execute"
-8. Tell the user: "Phase [N] has [X] task plans ready. Run /forge:execute-phase [N] to begin execution."

package/.claude/commands/mindforge/add-backlog.md

@@ -1,32 +0,0 @@
----
-name: mindforge:add-backlog
-description: Capture ideas in a "parking lot" to keep them out of the active phase sequence
-argument-hint: <description>
-allowed-tools:
-  - view_file
-  - write_to_file
-  - replace_file_content
-  - multi_replace_file_content
----
-
-<objective>
-Capture an idea, task, or feature request in a "parking lot" section of the ROADMAP.md to prevent it from cluttering the active development phases.
-</objective>
-
-<execution_context>
-.claude/commands/mindforge/add-backlog.md
-</execution_context>
-
-<context>
-Arguments: $ARGUMENTS (The description of the backlog item)
-Target File: ROADMAP.md
-State: Uses 999.x numbering scheme for backlog items.
-</context>
-
-<process>
-1. **Read ROADMAP.md**: Locate the `## Backlog` or `## Future Milestones` section.
-2. **Initialize if missing**: If no backlog section exists, create `## Backlog` at the end of the file.
-3. **Determine numbering**: Find the last `999.x` item. If none, start with `999.1`.
-4. **Append item**: Add the new backlog item with the determined number and the provided description.
-5. **Confirm**: Notify the user that the item has been parked in the backlog.
-</process>

package/.claude/commands/mindforge/agent.md

@@ -1,31 +0,0 @@
----
-name: mindforge:agent
-description: Spawn or invoke a specialized enterprise persona from the MindForge library
-argument-hint: "[persona-name] [prompt]"
-allowed-tools:
-  - list_dir
-  - view_file
----
-
-<objective>
-Provide an on-demand mechanism to "spawn" any of the 13+ standardized MindForge personas. This allows the user to switch the AI assistant's context, role, and process to a specific specialized mode (e.g., Roadmapper, Security Reviewer, Analyst).
-</objective>
-
-<execution_context>
-.claude/commands/mindforge/agent.md
-</execution_context>
-
-<context>
-Personas Directory: `.mindforge/personas/`
-State: Loads the persona's XML-tagged structure into the active system context.
-</context>
-
-<process>
-1. **List Personas**: If no arguments are provided, list all available `.md` files in `.mindforge/personas/` with their name and description (parsed from YAML).
-2. **Load Persona**: If a name is provided:
-    - Locate `.mindforge/personas/[name].md`.
-    - Read the file content.
-    - Present the persona's role and success criteria to the user.
-3. **Switch Mode**: Instruct the AI (through the current session context) to adopt the role, philosophy, and process defined in the loaded file.
-4. **Initial Task**: If a prompt is provided as the second argument, immediately execute that prompt using the newly adopted persona.
-</process>

package/.claude/commands/mindforge/approve.md

@@ -1,22 +0,0 @@
----
-description: Process pending approvals and emergency overrides. Usage:
----
-
-Process pending approvals and emergency overrides. Usage:
-`/mindforge:approve [approval-id] [--approve|--reject] [--reason "..."] [--emergency]`
-
-## Listing approvals
-Scan `.planning/approvals/` and show only files with `status: pending` unless
- the user explicitly asks for historical records.
-
-## Standard approval flow
-1. Read the approval file
-2. Confirm current identity from `git config user.email` or `$USER`
-3. Validate approver eligibility from `INTEGRATIONS-CONFIG.md`
-4. Record approval or rejection with timestamp and reason
-
-## Emergency overrides
-Emergency override requires the `--emergency` flag.
-Read `EMERGENCY_APPROVERS` from `INTEGRATIONS-CONFIG.md` and deny the request if
- the current identity is not listed. Document that git-config-based identity is
- a convenience layer, not a high-assurance identity proof.

package/.claude/commands/mindforge/audit.md

@@ -1,34 +0,0 @@
----
-description: Query .planning/AUDIT.jsonl by phase, event, date, severity, integration, or
----
-
-Query `.planning/AUDIT.jsonl` by phase, event, date, severity, integration, or
- agent. Usage: `/mindforge:audit [filters]`
-
-## Supported options
-- `--phase N`
-- `--event NAME`
-- `--agent NAME`
-- `--severity LEVEL`
-- `--date YYYY-MM-DD`
-- `--summary`
-- `--verify`
-- `--export PATH`
-
-## Summary mode
-Summarise counts by event, severity, integration, and phase.
-Entries with `"phase": null` are reported as `project-level`, not dropped.
-
-## Verify mode
-Validate JSONL shape and chronological ordering.
-Timestamp comparison may use string comparison because ISO-8601 UTC timestamps
- with a `Z` suffix sort lexicographically.
-
-## Archive rotation
-If the active audit log exceeds 10,000 lines, rotate it into
- `.planning/audit-archive/` before continuing heavy writes. Rotation must never
- delete history; it archives then resets the active file.
-
-## Export safety
-Validate export paths stay inside the project directory. If a path traversal or
- unsafe destination is requested, export into `.planning/` instead.

package/.claude/commands/mindforge/auto.md

@@ -1,26 +0,0 @@
----
-description: Starts the MindForge Autonomous Execution Engine for the
----
-
-# /mindforge:auto [Phase N]
-
-**Purpose**: Starts the MindForge Autonomous Execution Engine for the
-specified phase. The agent will execute all waves, handle repairs, and
-perform compliance gates without requiring human confirmation.
-
-## Usage
-- `/mindforge:auto --phase 3` (Standard unattended mode)
-- `/mindforge:auto --resume` (Resumes from last checkpoint)
-- `/mindforge:auto --headless` (CI/CD optimized output)
-- `/mindforge:auto --dry-run` (Show the wave DAG and plan without executing)
-
-## Behavior
-- **Zero-Interaction**: Auto-approves Tier 1/2 changes if gates pass.
-- **Self-Repair**: Tries RETRY/DECOMPOSE before asking for help.
-- **Checkpointing**: Constant state persistence in `HANDOFF.json`.
-- **Governance**: ESCALATES on Tier 3 changes (Auth/Payment/PII).
-
-## Environment Variables
-- `AUTO_MODE_TIMEOUT_MINUTES`: Default 120.
-- `AUTO_PUSH_ON_WAVE_COMPLETE`: Default false.
-- `SLACK_WEBHOOK_URL`: Required for notifications.

package/.claude/commands/mindforge/benchmark.md

@@ -1,37 +0,0 @@
----
-description: Measure skill effectiveness over time.
----
-
-# MindForge — Benchmark Command
-# Usage: /mindforge:benchmark [--skill skill-name] [--compare skill-a skill-b]
-
-Measure skill effectiveness over time.
-
-## Single skill benchmark
-For a named skill, analyse AUDIT.jsonl and skill-usage.jsonl:
-- How many times was the skill loaded this month?
-- What is the verify pass rate for tasks where this skill was loaded?
-- Are there anti-patterns less common after this skill is loaded?
-- What is the average session quality score when this skill is active?
-
-Report:
-```
-Skill Benchmark: security-review v1.0.0
-────────────────────────────────────────
-Usage (last 30 days): 47 task loads
-Trigger distribution: text match 68%, file-path 22%, file-name 10%
-Verify pass rate:     91% (vs. 84% baseline without this skill)
-Security findings:    8 HIGH caught (0 CRITICAL missed in tasks using this skill)
-Session quality lift: +6.2 points average when loaded
-
-Assessment: HIGH VALUE — clear quality improvement signal
-```
-
-## Skill comparison
-Compare two skills head-to-head:
-- Load frequency
-- Verify pass rate improvement
-- Anti-pattern detection rate
-- Context budget cost (token estimate)
-
-Helps decide: should you keep both skills, or deprecate the lower-performer?

package/.claude/commands/mindforge/browse.md

@@ -1,30 +0,0 @@
----
-description: @mindforge browse <url | action>
----
-
-# /mindforge:browse
-
-## Usage
-`@mindforge browse <url | action>`
-
-## Description
-Controls the persistent MindForge browser daemon. 
-Maintains session state (cookies/localStorage) for the AI.
-
-## Actions
-| Action | Description |
-|---|---|
-| `--start` | Initialize browser daemon |
-| `--stop` | Kill browser daemon |
-| `--status` | Show daemon health and active sessions |
-| `--session <name>` | Switch browser context |
-| `--import-session <name> --from <browser>` | Import cookies from host browser (chrome, arc, etc) |
-| `<url>` | Navigate the current page to URL |
-| `click <selector>` | Trigger click event |
-| `type <sel> <text>` | Fill input field |
-| `screenshot` | Capture current viewport |
-
-## Security
-- Daemon binds to `127.0.0.1` only.
-- Session files are gitignored.
-- Use only for debugging and visual verification.

package/.claude/commands/mindforge/complete-milestone.md

@@ -1,22 +0,0 @@
----
-description: Archive a completed milestone, generate a release report, and prepare the next
----
-
-Archive a completed milestone, generate a release report, and prepare the next
- milestone. Usage: `/mindforge:complete-milestone <name> <version>`
-
-## Step 1 — Validate milestone completion
-Ensure every included phase is verified and has no pending blocking approvals.
-
-## Step 2 — Generate milestone report
-Summarise shipped phases, notable changes, risks, approvals, and unresolved
- follow-ups.
-
-## Step 3 — Archive milestone artifacts
-Archive only the phases included in the milestone, not the entire
- `.planning/phases/` directory. Preserve history in the archive while keeping
- active planning files available in place.
-
-## Step 4 — Release metadata
-Create the release tag, update `STATE.md` with milestone summary, and mark the
- project ready for the next version.

package/.claude/commands/mindforge/costs.md

@@ -1,15 +0,0 @@
----
-description: Real-time cost tracking for all AI model usage.
----
-
-# MindForge v2 — Costs Command
-# Usage: /mindforge:costs [--phase N] [--session ID] [--window 7d]
-
-## Purpose
-Real-time cost tracking for all AI model usage.
-Enforce daily budgets and see per-model spend.
-
-## Metrics
-- Total spend: $X.XX
-- Daily limit usage: XX%
-- Per-model breakdown (Tokens/Cost)

package/.claude/commands/mindforge/cross-review.md

@@ -1,21 +0,0 @@
----
-description: Get the same code diff reviewed by multiple AI models simultaneously.
----
-
-# MindForge v2 — Cross-Review Command
-# Usage: /mindforge:cross-review [--phase N] [--models list] [--focus area]
-
-## Purpose
-Get the same code diff reviewed by multiple AI models simultaneously.
-Claude finds what Claude finds. GPT-4o finds what GPT-4o finds.
-Consensus findings = high confidence issues.
-
-## Round 1: Primary (Claude)
-Senior architect review.
-
-## Round 2: Adversarial (GPT-4o)
-Critical security and edge case review.
-
-## Synthesis
-Consensus detector filters findings.
-Verdict is gating for `/mindforge:ship`.

package/.claude/commands/mindforge/dashboard.md

@@ -1,102 +0,0 @@
----
-description: Start the MindForge real-time web dashboard — a live observability UI for the
----
-
-# MindForge v2 — Dashboard Command
-# Usage: /mindforge:dashboard [--port 7339] [--open] [--stop] [--status]
-# Version: v2.0.0-alpha.5
-
-## Purpose
-Start the MindForge real-time web dashboard — a live observability UI for the
-entire team. Shows execution progress, quality metrics, pending approvals,
-knowledge graph, and team activity without requiring CLI access.
-
-## Design
-The dashboard is a localhost-only web server:
-- No build step — single HTML file, no bundler, no npm packages on client
-- No authentication — binding to 127.0.0.1 is the security model
-- Live updates via Server-Sent Events — no WebSocket library needed
-- Designed for screensharing at standups, not external access
-
-## Usage
-
-### Start the dashboard
-```
-/mindforge:dashboard
-→ Dashboard running at: http://localhost:7339
-→ Press CTRL+C to stop (or /mindforge:dashboard --stop)
-```
-
-### Start and open in browser
-```
-/mindforge:dashboard --open
-→ Opens http://localhost:7339 in your default browser
-```
-
-### Custom port
-```
-/mindforge:dashboard --port 7340
-→ Useful if 7339 is already in use
-```
-
-### Stop the dashboard
-```
-/mindforge:dashboard --stop
-→ Finds the running dashboard process (from PID file) and sends SIGTERM
-```
-
-### Check dashboard status
-```
-/mindforge:dashboard --status
-→ Checks if dashboard is running, shows port and PID
-→ Also shows: http://localhost:7339/api/status
-```
-
-## Dashboard pages
-
-### Activity (default)
-- Phase name, auto mode status (RUNNING/PAUSED/ESCALATED/IDLE)
-- Wave progress bar (tasks completed / total)
-- Live AUDIT event feed with color-coded event types
-- Steering input: send guidance to auto mode without touching the CLI
-
-### Quality Metrics
-- Session quality score trend (last 20 sessions)
-- Verify pass rate over time
-- Security findings by severity (CRITICAL/HIGH/MEDIUM/LOW)
-- Cost per session trend
-
-### Approvals
-- All pending Tier 2/3 governance requests
-- [Approve] and [Reject] buttons — no CLI needed for approval
-- Tier, phase/plan, description, time since requested, expiry warning
-- Recent approval history
-
-### Knowledge
-- Search the knowledge graph from the browser
-- Entries filtered by confidence, type, tags
-- Color-coded by knowledge type
-
-### Team
-- Active developers (by git email, from AUDIT.jsonl)
-- What each person is working on (last task)
-- File conflict warnings (two developers recently touching the same file)
-
-## Security rules
-1. Never expose the dashboard on 0.0.0.0 — localhost only
-2. Never forward the port externally (no ngrok, no port forwarding)
-3. For remote team visibility: screenshare your browser instead
-4. The dashboard shows project details including code patterns and decisions
-
-## Integration with auto mode
-When `/mindforge:auto` is running and the dashboard is open:
-- Activity feed updates live as tasks complete
-- Wave progress bar advances in real-time
-- Any escalations appear immediately with red indicator
-- The Steering input is active — inject guidance without a second terminal
-
-## AUDIT entry
-```json
-{ "event": "dashboard_started", "port": 7339, "pid": 12345 }
-{ "event": "dashboard_stopped", "pid": 12345 }
-```