mindforge-cc 6.1.0-alpha → 6.2.0

package/.agent/bin/lib/commands.cjs

@@ -547,8 +547,8 @@ function cmdProgressRender(cwd, format, raw) {
     const bar = '\u2588'.repeat(filled) + '\u2591'.repeat(barWidth - filled);
     let out = `# ${milestone.version} ${milestone.name}\n\n`;
     out += `**Progress:** [${bar}] ${totalSummaries}/${totalPlans} plans (${percent}%)\n\n`;
-    out += `| Phase | Name | Plans | Status |\n`;
-    out += `|-------|------|-------|--------|\n`;
+    out += '| Phase | Name | Plans | Status |\n';
+    out += '|-------|------|-------|--------|\n';
     for (const p of phases) {
       out += `| ${p.number} | ${p.name} | ${p.summaries}/${p.plans} | ${p.status} |\n`;
     }
@@ -923,8 +923,8 @@ function cmdStats(cwd, format, raw) {
       out += `**Requirements:** ${requirementsComplete}/${requirementsTotal} complete\n`;
     }
     out += '\n';
-    out += `| Phase | Name | Plans | Completed | Status |\n`;
-    out += `|-------|------|-------|-----------|--------|\n`;
+    out += '| Phase | Name | Plans | Completed | Status |\n';
+    out += '|-------|------|-------|-----------|--------|\n';
     for (const p of phases) {
       out += `| ${p.number} | ${p.name} | ${p.plans} | ${p.summaries} | ${p.status} |\n`;
     }

package/.agent/bin/lib/state.cjs

@@ -723,7 +723,7 @@ function stripFrontmatter(content) {
   // Handles CRLF line endings and multiple stacked blocks (corruption recovery).
   // Greedy: keeps stripping ---...--- blocks separated by optional whitespace.
   let result = content;
-  // eslint-disable-next-line no-constant-condition
+   
   while (true) {
     const stripped = result.replace(/^\s*---\r?\n[\s\S]*?\r?\n---\s*/, '');
     if (stripped === result) break;

package/.agent/bin/lib/verify.cjs

@@ -778,14 +778,14 @@ function cmdValidateHealth(cwd, options, raw) {
             }
             // Generate minimal STATE.md from ROADMAP.md structure
             const milestone = getMilestoneInfo(cwd);
-            let stateContent = `# Session State\n\n`;
-            stateContent += `## Project Reference\n\n`;
-            stateContent += `See: .planning/PROJECT.md\n\n`;
-            stateContent += `## Position\n\n`;
+            let stateContent = '# Session State\n\n';
+            stateContent += '## Project Reference\n\n';
+            stateContent += 'See: .planning/PROJECT.md\n\n';
+            stateContent += '## Position\n\n';
             stateContent += `**Milestone:** ${milestone.version} ${milestone.name}\n`;
-            stateContent += `**Current phase:** (determining...)\n`;
-            stateContent += `**Status:** Resuming\n\n`;
-            stateContent += `## Session Log\n\n`;
+            stateContent += '**Current phase:** (determining...)\n';
+            stateContent += '**Status:** Resuming\n\n';
+            stateContent += '## Session Log\n\n';
             stateContent += `- ${new Date().toISOString().split('T')[0]}: STATE.md regenerated by /mindforge-health --repair\n`;
             writeStateMd(statePath, stateContent, cwd);
             repairActions.push({ action: repair, success: true, path: 'STATE.md' });

package/.agent/bin/mindforge-tools.cjs

@@ -532,7 +532,7 @@ async function runCommand(command, args, cwd, raw) {
       break;
     }
 
-    case "config-set-model-profile": {
+    case 'config-set-model-profile': {
       config.cmdConfigSetModelProfile(cwd, args[1], raw);
       break;
     }

package/.agent/hooks/mindforge-context-monitor.js

@@ -143,7 +143,7 @@ process.stdin.on('end', () => {
 
     const output = {
       hookSpecificOutput: {
-        hookEventName: process.env.GEMINI_API_KEY ? "AfterTool" : "PostToolUse",
+        hookEventName: process.env.GEMINI_API_KEY ? 'AfterTool' : 'PostToolUse',
         additionalContext: message
       }
     };

package/.agent/hooks/mindforge-session-init_extended.js

@@ -16,16 +16,16 @@ function run() {
     
     // Check for MindForge registry for additional info if needed
     const registryPath = path.join(projectRoot, 'MINDFORGE.md');
-    let registryWarning = "";
+    let registryWarning = '';
     if (!fs.existsSync(registryPath)) {
-        registryWarning = "\n\n[WARNING]: MINDFORGE.md Parameter Registry not found. Architectural integrity may be degraded.";
+        registryWarning = '\n\n[WARNING]: MINDFORGE.md Parameter Registry not found. Architectural integrity may be degraded.';
     }
 
-    const sessionContext = "<EXTREMELY_IMPORTANT>\nYou have MindForge Swarm Intelligence.\n\n**Below is the full content of your 'mindforge-neural-orchestrator' skill - your introduction to using skills. For all other skills, use the 'Skill' tool:**\n\n" + skillContent + registryWarning + "\n</EXTREMELY_IMPORTANT>";
+    const sessionContext = '<EXTREMELY_IMPORTANT>\nYou have MindForge Swarm Intelligence.\n\n**Below is the full content of your \'mindforge-neural-orchestrator\' skill - your introduction to using skills. For all other skills, use the \'Skill\' tool:**\n\n' + skillContent + registryWarning + '\n</EXTREMELY_IMPORTANT>';
 
     const output = {
       hookSpecificOutput: {
-        hookEventName: "SessionStart",
+        hookEventName: 'SessionStart',
         additionalContext: sessionContext
       },
       // Fallback for other platforms

package/.agent/hooks/mindforge-workflow-guard.js

@@ -77,7 +77,7 @@ process.stdin.on('end', () => {
     // not in a subagent context. Inject advisory warning.
     const output = {
       hookSpecificOutput: {
-        hookEventName: "PreToolUse",
+        hookEventName: 'PreToolUse',
         additionalContext: `⚠️ WORKFLOW ADVISORY: You're editing ${path.basename(filePath)} directly without a MindForge command. ` +
           'This edit will not be tracked in STATE.md or produce a SUMMARY.md. ' +
           'Consider using /mindforge:fast for trivial fixes or /mindforge:quick for larger changes ' +

package/.agent/mindforge/debug.md

@@ -12,6 +12,9 @@ Systematic debugging using the Debug Specialist persona with full RCA protocol.
 Load `.mindforge/personas/debug-specialist.md` immediately.
 This command runs entirely in that persona for its full duration.
 
+## Step 0 — Initial Intelligence Check
+Read `AGENTS_LEARNING.md` before intake. Check the "Mistakes Observed" and "Anti-Patterns" sections to see if this issue matches a known historical failure.
+
 ## Step 1 — Intake
 
 Ask the user:

package/.agent/mindforge/execute-phase.md

@@ -106,6 +106,7 @@ After all tasks in wave complete:
    - Stop. Ask user how to proceed.
 3. If tests pass:
    - Report: "Wave [W] complete. All [X] tasks passed. Tests passing. ✅"
+   - Run `/mindforge:record-learning` if any architectural "Aha!" moments or significant anti-patterns were discovered during this wave.
    - Write WAVE-REPORT update
 
 ## Step 4 — Phase-level verification
@@ -139,6 +140,11 @@ Run /mindforge:verify-phase [N] for human acceptance testing.
 
 Update HANDOFF.json with completed phase info.
 
+## Step 5.1 — Final Intelligence Sync
+1. Read `AGENTS_LEARNING.md` one last time.
+2. Run `/mindforge:record-learning` to capture the final phase-level learnings (Mistakes discovered during UAT, architectural refinements).
+3. Commit `AGENTS_LEARNING.md` if updated.
+
 Write final AUDIT entry:
 ```json
 {

package/.agent/mindforge/learning.md

@@ -0,0 +1,20 @@
+---
+description: Consult or initialize the project agentic learning memory - AGENTS_LEARNING.md
+---
+
+# /mindforge:learning [init]
+
+Consult the project's persistent engineering memory to avoid past mistakes and follow established best practices.
+
+## Usage
+
+- `/mindforge:learning`: Displays the current learning status and path to the learning file.
+- `/mindforge:learning init`: Initializes a new `AGENTS_LEARNING.md` in the project root if it doesn't already exist.
+
+## Why use this?
+Before starting any significant implementation or refactor, you MUST consult the learning memory. It contains project-specific "Anti-Patterns" to avoid and "Best Practices" that have been proven in this specific system.
+
+## Example
+1. Run `/mindforge:learning` to find where the learning file is.
+2. Read the file to understand recent architectural shifts or discovered failure scenarios.
+3. If the project is new, run `/mindforge:learning init` to scaffold the memory.

package/.agent/mindforge/plan-phase.md

@@ -11,11 +11,12 @@ Read PROJECT.md, REQUIREMENTS.md, ARCHITECTURE.md, and STATE.md before proceedin
 ## Pre-read (before any questions or planning)
 
 Read these files in order:
-1. `.planning/PROJECT.md`
-2. `.planning/REQUIREMENTS.md`
-3. `.planning/ARCHITECTURE.md`
-4. `.planning/STATE.md`
-5. `.planning/phases/phase-[N]/CONTEXT.md` (if it exists)
+1. `AGENTS_LEARNING.md` (MUST READ to avoid repeating past mistakes)
+2. `.planning/PROJECT.md`
+3. `.planning/REQUIREMENTS.md`
+4. `.planning/ARCHITECTURE.md`
+5. `.planning/STATE.md`
+6. `.planning/phases/phase-[N]/CONTEXT.md` (if it exists)
 
 ### If CONTEXT.md exists for phase [N]:
 This means `/mindforge:discuss-phase [N]` was already run.
@@ -62,8 +63,9 @@ Spawn a research subagent with this context only:
 Instruct it to investigate:
 1. Best available libraries for this phase's requirements (with version numbers)
 2. Common pitfalls and anti-patterns for this tech domain
-3. Relevant architectural patterns (with tradeoffs)
-4. Any known security considerations specific to this domain
+3. Project-specific anti-patterns from `AGENTS_LEARNING.md`
+4. Relevant architectural patterns (with tradeoffs)
+5. Any known security considerations specific to this domain
 
 Write findings to `.planning/phases/phase-[N]/RESEARCH.md`.
 

package/.agent/mindforge/record-learning.md

@@ -0,0 +1,22 @@
+---
+description: Append a new Learning Entry to the Evolution Log in AGENTS_LEARNING.md
+---
+
+# /mindforge:record-learning
+
+Append a new Learning Entry to the `Evolution Log`. Recording learnings regularly is a MANDATORY practice to build project intelligence.
+
+## Usage
+
+`/mindforge:record-learning`
+
+This command initiates a session-end recording. You should provide details on:
+- **Context**: What task was being performed.
+- **Mistake**: What went wrong.
+- **Root Cause**: Why it happened.
+- **Fix**: What was done.
+- **Prevention Rule**: Rule to avoid this in the future.
+- **Category**: (Best Practice, Anti-Pattern, Bug Fix, Architecture).
+
+## Example
+Run after a complex debugging session to capture the root cause and the specific engineering oversight to prevent it from happening again.

package/.agent/mindforge/retrospective.md

@@ -13,6 +13,7 @@ Facilitate a structured retrospective with objective metrics + qualitative insig
 3. Write retrospective artifact in `.planning/phases/...` or `.planning/milestones/...`.
 4. Create follow-up tasks/tickets for action items.
 5. Update metrics with retrospective-completed event.
+6. Run `/mindforge:record-learning` to sync any new architectural "Aha!" moments or significant anti-patterns discovered during this phase/milestone.
 
 ## Step 5 — Apply learnings to MINDFORGE.md
 Ask explicitly:

package/.agent/mindforge/ship.md

@@ -49,6 +49,12 @@ npm audit --audit-level=high
 
 If any gate fails: stop. Report the failures. Do not proceed to PR creation.
 
+## Step 2.1 — Final Intelligence Audit
+1. Read `AGENTS_LEARNING.md` for this project.
+2. Verify if any new architectural patterns, anti-patterns, or mistakes from this phase were recorded.
+3. If not: Run `/mindforge:record-learning` now to capture them before shipping.
+4. Commit `AGENTS_LEARNING.md` if updated.
+
 ## Step 3 — Create PR description
 Generate a complete PR description:
 
@@ -78,6 +84,7 @@ Generate a complete PR description:
 
 ### Checklist
 - [x] CHANGELOG.md updated
+- [x] AGENTS_LEARNING.md updated with phase-specific insights
 - [x] All tests pass
 - [x] No linter errors
 - [x] UAT signed off

package/.claude/CLAUDE.md

@@ -1,4 +1,4 @@
-# MindForge — Unified Protocol Engine (v4.0.0-alpha.swarm)
+# 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.
 
@@ -41,11 +41,18 @@ You are a **Dynamic Multi-Agent Swarm (Agentic Mesh)**. Your mission is to execu
 - **Shipping**: `mindforge-ship_extended`.
 - **Verification**: `mindforge-verify-work_extended`.
 
-### 5. The Temporal Vision Loop (Hindsight)
-**IF** verification fails **OR** deep bug suspected:
-1. Invoke `hindsight-injector.js`.
-2. Pull the "Last Known Good" state from the Temporal Hub.
-3. Execute `mindforge:repair` if drift is detected.
+### 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.
 
 ---
 
@@ -54,9 +61,11 @@ You are a **Dynamic Multi-Agent Swarm (Agentic Mesh)**. Your mission is to execu
 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.
+- [ ] **Audit Always**: Write a JSONL entry for every significant session event. All entries must be Merkle-linked.
 
 ---
 

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

@@ -1,30 +1,22 @@
 ---
-name: mindforge:approve
-description: Process pending approvals and emergency overrides
-argument-hint: [approval-id] [--approve|--reject] [--reason "..."] [--emergency]
-allowed-tools:
-  - list_dir
-  - view_file
-  - write_to_file
+description: Process pending approvals and emergency overrides. Usage:
 ---
 
-<objective>
-Manage the governance layer by reviewing and confirming high-tier architectural or security changes, ensuring all sensitive operations have explicit human authorization.
-</objective>
+Process pending approvals and emergency overrides. Usage:
+`/mindforge:approve [approval-id] [--approve|--reject] [--reason "..."] [--emergency]`
 
-<execution_context>
-.claude/commands/mindforge/approve.md
-</execution_context>
+## Listing approvals
+Scan `.planning/approvals/` and show only files with `status: pending` unless
+ the user explicitly asks for historical records.
 
-<context>
-Storage: .planning/approvals/
-Governance Config: INTEGRATIONS-CONFIG.md
-</context>
+## 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
 
-<process>
-1. **List**: Scan for pending approval requests and present them to the user.
-2. **Identity Verification**: Confirm the user's identity via git config or environment.
-3. **Audit Eligibility**: Verify the user has sufficient permissions for the requested tier.
-4. **Record Verdict**: Update the approval file with status, timestamp, and the provided reason.
-5. **Emergency Override**: If `--emergency` is used, bypass standard checks if the identity matches the pre-defined emergency approver list.
-</process>
+## 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 +1,34 @@
 ---
-name: mindforge:audit
-description: Query the .planning/AUDIT.jsonl log by phase, event, date, or severity
-argument-hint: [filters]
-allowed-tools:
-  - run_command
-  - view_file
-  - list_dir
+description: Query .planning/AUDIT.jsonl by phase, event, date, severity, integration, or
 ---
 
-<objective>
-Provide a structured interface to query and validate the project's audit logs, ensuring accountability and traceability of all agent actions and system events.
-</objective>
+Query `.planning/AUDIT.jsonl` by phase, event, date, severity, integration, or
+ agent. Usage: `/mindforge:audit [filters]`
 
-<execution_context>
-.claude/commands/mindforge/audit.md
-</execution_context>
+## Supported options
+- `--phase N`
+- `--event NAME`
+- `--agent NAME`
+- `--severity LEVEL`
+- `--date YYYY-MM-DD`
+- `--summary`
+- `--verify`
+- `--export PATH`
 
-<context>
-Storage: .planning/AUDIT.jsonl
-Archive: .planning/audit-archive/
-Filters: --phase, --event, --agent, --severity, --date, --summary, --verify, --export
-</context>
+## Summary mode
+Summarise counts by event, severity, integration, and phase.
+Entries with `"phase": null` are reported as `project-level`, not dropped.
 
-<process>
-1. **Parse Filters**: Identify the search criteria (phase, event, severity, etc.).
-2. **Execute Query**:
-    - Use `grep` or `jq` (if available via bash) to filter the JSONL file.
-    - If `--summary`: Aggregate counts by event and severity.
-    - If `--verify`: Check for JSON validity and chronological integrity.
-3. **Handle Large Logs**: If the log exceeds 10,000 lines, rotate it to the archive directory.
-4. **Export (Optional)**: If `--export` is used, write filtered results to the target path (ensuring project boundary safety).
-5. **Display**: Present the filtered log or summary to the user.
-</process>
+## 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,33 +1,26 @@
 ---
-name: mindforge:auto
-description: Start the MindForge Autonomous Execution Engine
-argument-hint: [Phase N] [--resume] [--headless] [--dry-run]
-allowed-tools:
-  - run_command
-  - list_dir
-  - view_file
-  - write_to_file
+description: Starts the MindForge Autonomous Execution Engine for the
 ---
 
-<objective>
-Execute a planned phase entirely unattended, coordinating wave fulfillment, self-repair of minor failures, and compliance gating while maintaining a persistent state checkpoint.
-</objective>
+# /mindforge:auto [Phase N]
 
-<execution_context>
-.claude/commands/mindforge/auto.md
-</execution_context>
+**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.
 
-<context>
-Storage: HANDOFF.json checkpoints.
-Governance: Auto-approves Tier 1/2; Escalates Tier 3.
-Notifications: Requires Slack/Discord webhooks for mission-critical alerts.
-</context>
+## 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)
 
-<process>
-1. **Boot**: Load the specifies phase or resume from the last known checkpoint in `HANDOFF.json`.
-2. **Wave Engine**: Execute the DAG of tasks sequentially or in parallel based on dependencies.
-3. **Self-Repair**: Automatically attempt to retry or decompose tasks that encounter recoverable errors.
-4. **Gating**: Evaluate compliance gates between waves. Escalates to human for Tier 3 changes.
-5. **Persistence**: Save state after every successful tool call or task completion.
-6. **Finalize**: Shift status to "Verify Pending" once all waves are complete.
-</process>
+## 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,30 +1,37 @@
 ---
-name: mindforge:benchmark
-description: Measure skill effectiveness and project metrics over time
-argument-hint: [--skill skill-name] [--compare skill-a skill-b]
-allowed-tools:
-  - view_file
-  - list_dir
+description: Measure skill effectiveness over time.
 ---
 
-<objective>
-Analyze command and skill performance by correlating usage data with verify pass rates and project quality scores, facilitating data-driven decisions on tool improvements.
-</objective>
+# MindForge — Benchmark Command
+# Usage: /mindforge:benchmark [--skill skill-name] [--compare skill-a skill-b]
 
-<execution_context>
-.claude/commands/mindforge/benchmark.md
-</execution_context>
+Measure skill effectiveness over time.
 
-<context>
-Sources: AUDIT.jsonl, skill-usage.jsonl
-Metrics: Pass rate, load frequency, anti-pattern reduction, quality lift.
-</context>
+## 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?
 
-<process>
-1. **Gather Data**: Extract usage and outcome logs for the target skill(s).
-2. **Calculate Trends**: Determine pass rate vs baseline and session quality improvement.
-3. **Generate Assessment**:
-    - For single skill: Provide a usage distribution and quality lift report.
-    - For comparison: Provide a head-to-head comparison on cost and effectiveness.
-4. **Recommendation**: Advise on whether to keep, improve, or deprecate the targeted skills.
-</process>
+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,28 +1,30 @@
 ---
-name: mindforge:browse
-description: Control the persistent MindForge browser daemon for visual verification
-argument-hint: <url | action>
-allowed-tools:
-  - open_browser_url
-  - run_command
+description: @mindforge browse <url | action>
 ---
 
-<objective>
-Enable the agent to interact with web interfaces, maintain persistent sessions, and perform visual audits of UI changes using an automated browser daemon.
-</objective>
+# /mindforge:browse
 
-<execution_context>
-.claude/commands/mindforge/browse.md
-</execution_context>
+## Usage
+`@mindforge browse <url | action>`
 
-<context>
-Security: Daemon binds to 127.0.0.1. Sessions are gitignored.
-State: Supports cookie/localStorage persistence via named sessions.
-</context>
+## Description
+Controls the persistent MindForge browser daemon. 
+Maintains session state (cookies/localStorage) for the AI.
 
-<process>
-1. **Control Daemon**: Start, stop, or query the health/active sessions of the browser daemon.
-2. **Session Management**: Switch between browser contexts or import sessions from the host (Chrome/Arc).
-3. **Navigate & Interact**: Load URLs, click selectors, and type text into input fields.
-4. **Verify**: Capture screenshots of the current viewport for visual confirmation.
-</process>
+## 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,32 +1,22 @@
 ---
-name: mindforge:complete-milestone
-description: Archive a completed milestone and prepare the next version
-argument-hint: <name> <version>
-allowed-tools:
-  - list_dir
-  - view_file
-  - write_to_file
-  - run_command
+description: Archive a completed milestone, generate a release report, and prepare the next
 ---
 
-<objective>
-Finalize a project milestone by summarizing shipped value, archiving phase artifacts, and preparing the environment for the next development cycle.
-</objective>
+Archive a completed milestone, generate a release report, and prepare the next
+ milestone. Usage: `/mindforge:complete-milestone <name> <version>`
 
-<execution_context>
-.claude/commands/mindforge/complete-milestone.md
-</execution_context>
+## Step 1 — Validate milestone completion
+Ensure every included phase is verified and has no pending blocking approvals.
 
-<context>
-Validation: Ensures all included phases are verified and have no pending approvals.
-Storage: Moves phase files to a milestone-specific archive.
-</context>
+## Step 2 — Generate milestone report
+Summarise shipped phases, notable changes, risks, approvals, and unresolved
+ follow-ups.
 
-<process>
-1. **Validate**: Confirm every phase in the milestone is signed off and verified.
-2. **Summarize**: Generate a MILESTONE-REPORT with shipped functionality, risks, and follow-ups.
-3. **Archive**: Move the included `.planning/phases/` directories to a persistent milestone archive.
-4. **Tag**: Create a git release tag for the milestone.
-5. **State Reset**: Update `STATE.md` to reflect the milestone completion and target the next version.
-6. **Audit**: Log `milestone_completed` event.
-</process>
+## 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.