mindforge-cc 8.1.1 → 8.2.0

package/.mindforge/mirrors/mirror-sre-776a1cf9/.agent/mindforge/status.md

@@ -0,0 +1,113 @@
+---
+description: Display a rich dashboard of the current project state.
+---
+
+# MindForge — Status Command
+# Usage: /mindforge:status
+
+Display a rich dashboard of the current project state.
+Pull data from STATE.md, AUDIT.jsonl, REQUIREMENTS.md, and the phases directory.
+
+## Dashboard sections
+
+### Section 1 — Project header
+```
+━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
+⚡ MindForge Status — [Project Name]
+━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
+  Last updated : [STATE.md last updated timestamp]
+  Current phase: Phase [N] — [phase description]
+  Status       : [status from STATE.md]
+```
+
+### Section 2 — Phase progress
+```
+Phase Progress
+───────────────────────────────────────────────────────
+  Phase 1  [████████████████████] 100% — Complete ✅
+  Phase 2  [████████░░░░░░░░░░░░]  40% — In progress
+  Phase 3  [░░░░░░░░░░░░░░░░░░░░]   0% — Not started
+  Phase 4  [░░░░░░░░░░░░░░░░░░░░]   0% — Not started
+```
+Calculate percentage from: tasks with SUMMARY files / total tasks in phase.
+Count ONLY SUMMARY files that contain `Status: Completed ✅` (or `Status` + `Completed`).
+Do not count failed tasks as progress.
+If VERIFICATION.md is missing for a phase: label it "In progress" not "0% verified".
+
+### Section 3 — Requirements coverage
+Read REQUIREMENTS.md and count:
+- Total v1 requirements
+- Requirements with a passing test (from VERIFICATION.md files)
+- Requirements implemented but untested
+- Requirements not yet started
+
+```
+Requirements (v1)
+───────────────────────────────────────────────────────
+  Total        : [N]
+  ✅ Done + tested  : [N]
+  ⚠️  Done, no test : [N]
+  🔴 Not started   : [N]
+```
+
+### Section 4 — Recent activity (from AUDIT.jsonl)
+Read the last 10 entries from AUDIT.jsonl and display:
+```
+Recent Activity
+───────────────────────────────────────────────────────
+  [timestamp]  task_completed  Plan 03: User API endpoints ✅
+  [timestamp]  task_completed  Plan 02: Product model ✅
+  [timestamp]  task_started    Plan 03: User API endpoints
+  [timestamp]  task_completed  Plan 01: User model ✅
+  [timestamp]  context_compaction  Phase 2, Plan 03 (72% context)
+```
+If AUDIT.jsonl is empty or missing, display:
+```
+Recent Activity
+───────────────────────────────────────────────────────
+  No activity logged yet. Activity will appear here
+  after running /mindforge:execute-phase.
+```
+
+### Section 5 — Open issues
+Check for:
+- Any open SECURITY-REVIEW files with CRITICAL or HIGH findings
+- Any BUGS.md files with open issues
+- Any failed tasks in WAVE-REPORT files
+- Any blockers in STATE.md
+
+```
+Open Issues
+───────────────────────────────────────────────────────
+  🔴 CRITICAL: [if any — from SECURITY-REVIEW]
+  🟠 HIGH:     [if any]
+  ✅ No open issues
+```
+
+### Section 7 — Sovereign Intelligence
+```
+Sovereign Intelligence (v6.2.0-alpha)
+───────────────────────────────────────────────────────
+  🛡️  PQAS Security : [ACTIVE | PASSIVE] (Dilithium-5)
+  🎯  Proactive Homing: [ENABLED | DISABLED]
+  🧠  Drift Recovery : [N] remediation events
+  🧬  Biometric Gate : [LOCKED | BYPASSED]
+```
+- PQAS Status: Check if `bin/governance/quantum-crypto.js` exists and if `PolicyEngine.js` has `highRiskBypass` enabled.
+- Proactive Homing: Check if `bin/autonomous/intent-harvester.js` is active in `AutoRunner.js`.
+
+━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
+```
+
+## Data sources (in priority order)
+1. STATE.md — authoritative for current status
+2. AUDIT.jsonl — authoritative for history
+3. REQUIREMENTS.md — authoritative for scope
+4. VERIFICATION.md files — authoritative for test coverage
+5. WAVE-REPORT files — authoritative for execution history
+6. HANDOFF.json — authoritative for session state
+
+## Performance notes
+- For recent activity, read only the last 500 bytes of AUDIT.jsonl:
+  `tail -c 500 .planning/AUDIT.jsonl | [parse last complete JSON objects]`
+- For requirement counts, count lines starting with `| FR-` instead of parsing the whole file.

package/.mindforge/mirrors/mirror-sre-776a1cf9/.agent/mindforge/steer.md

@@ -0,0 +1,17 @@
+---
+description: Injects mid-execution guidance into the running autonomous engine.
+---
+
+# /mindforge:steer "[instruction]"
+
+**Purpose**: Injects mid-execution guidance into the running autonomous engine.
+Steering guidance is applied at the next task boundary to course-correct MindForge.
+
+## Usage
+- `/mindforge:steer "Use the new logger in all created files"`
+- `/mindforge:steer --task 3-05 "This plan is too broad, focus on login only"`
+- `/mindforge:steer --cancel` (Clears the steering queue)
+
+## Precedence
+- Steering instructions take precedence over the original `PLAN-N-MM.md` actions.
+- Steering cannot override core security constraints or governance gates.

package/.mindforge/mirrors/mirror-sre-776a1cf9/.agent/mindforge/sync-confluence.md

@@ -0,0 +1,15 @@
+---
+description: Publish approved planning artifacts to Confluence. Usage:
+---
+
+Publish approved planning artifacts to Confluence. Usage:
+`/mindforge:sync-confluence [--architecture] [--phase N] [--milestone name]`
+
+## Behaviour
+- verify Confluence availability through `connection-manager.md`
+- publish idempotently by existing page title or page ID
+- never publish secrets, raw approval notes, or raw audit logs
+- log success, skip, or failure to AUDIT
+
+Publishing failures are non-fatal and create a pending manual action in
+ `STATE.md`.

package/.mindforge/mirrors/mirror-sre-776a1cf9/.agent/mindforge/sync-jira.md

@@ -0,0 +1,16 @@
+---
+description: Synchronise MindForge phase and plan metadata to Jira. Usage:
+---
+
+Synchronise MindForge phase and plan metadata to Jira. Usage:
+`/mindforge:sync-jira [--phase N] [--plan M]`
+
+## Behaviour
+- verify Jira availability through `connection-manager.md`
+- create or update Epic and Story mappings in `.planning/jira-sync.json`
+- use dynamic transition lookup, never hardcoded IDs
+- preserve manual Jira edits
+- log all actions to AUDIT
+
+Integration failures are non-fatal and should be written to `STATE.md` for
+ manual retry.

package/.mindforge/mirrors/mirror-sre-776a1cf9/.agent/mindforge/tokens.md

@@ -0,0 +1,12 @@
+---
+description: Display token consumption profile and efficiency analysis.
+---
+
+# MindForge — Token Usage Command
+# Usage: /mindforge:tokens [--phase N] [--session ID] [--window short|medium|long] [--optimise]
+
+## Purpose
+Display token consumption profile and efficiency analysis.
+Helps identify where tokens are being spent and how to reduce waste.
+
+## Default output (no flags — last 5 sessions)

package/.mindforge/mirrors/mirror-sre-776a1cf9/.agent/mindforge/ui-phase.md

@@ -0,0 +1,34 @@
+---
+name: mindforge:ui-phase
+description: Generate a UI Design Contract (UI-SPEC.md) for the current phase
+argument-hint: [N]
+allowed-tools:
+  - view_file
+  - write_to_file
+  - list_dir
+---
+
+<objective>
+Generate a detailed UI design contract (UI-SPEC.md) for a frontend development phase to ensure consistent spacing, typography, color palettes, and accessibility standards before implementation.
+</objective>
+
+<execution_context>
+.claude/commands/mindforge/ui-phase.md
+</execution_context>
+
+<context>
+Arguments: $ARGUMENTS (The phase number [N], optional)
+Configuration: MINDFORGE.md `UI_PHASE_ACCESSIBILITY_STANDARD`
+State: Resolves the phase from STATE.md if N is not provided.
+</context>
+
+<process>
+1. **Identify Phase**: Get the current or targeted phase number.
+2. **Read Inputs**: Read `REQUIREMENTS.md` and `DESIGN_SYSTEM.md`.
+3. **Generate UI-SPEC.md**:
+    - Define component-level spacing and layout for the phase.
+    - Specify required colors and typography from the design system.
+    - List accessibility requirements (WCAG level).
+4. **Finalize**: Write `UI-SPEC.md` to the phase's planning directory or the root `.planning/`.
+5. **Confirm**: Provide a link to the user for review.
+</process>

package/.mindforge/mirrors/mirror-sre-776a1cf9/.agent/mindforge/ui-review.md

@@ -0,0 +1,36 @@
+---
+name: mindforge:ui-review
+description: Perform a retroactive visual audit of implemented UI against the DESIGN_SYSTEM.md and UI-SPEC.md
+argument-hint: [N]
+allowed-tools:
+  - view_file
+  - write_to_file
+  - read_browser_page
+  - open_browser_url
+---
+
+<objective>
+Perform a retroactive, multi-pillar visual audit of implemented UI features against the defined Design System and UI-SPEC.md to ensure pixel-perfect fidelity and accessibility compliance.
+</objective>
+
+<execution_context>
+.claude/commands/mindforge/ui-review.md
+</execution_context>
+
+<context>
+Arguments: $ARGUMENTS (The phase number [N], optional)
+Sources: `DESIGN_SYSTEM.md`, `UI-SPEC.md`, and the live application UI.
+</context>
+
+<process>
+1. **Identify Target**: Determine the phase to review.
+2. **Audit Application**:
+    - Use the browser tool to inspect the implemented features.
+    - Compare against the `UI-SPEC.md` for spacing, colors, and layout.
+    - Audit for accessibility (ARIA labels, contrast, keyboard navigation).
+3. **Generate UI-REVIEW.md**:
+    - Grade each pillar (Layout, Color, Typography, etc.).
+    - List specific "Needs Work" items.
+    - Provide "Approved" status if all criteria are met.
+4. **Finalize**: Notify the user of the audit results.
+</process>

package/.mindforge/mirrors/mirror-sre-776a1cf9/.agent/mindforge/update.md

@@ -0,0 +1,46 @@
+---
+description: Check for and apply MindForge framework updates in a safe, scope-preserving way.
+---
+
+# MindForge — Update Command
+# Usage: /mindforge:update [--apply] [--force] [--check] [--skip-changelog]
+
+## Purpose
+Check for and apply MindForge framework updates in a safe, scope-preserving way.
+
+## Execution flow
+
+### 1. Version check
+Execute `bin/updater/self-update.js` `checkAndUpdate()`.
+Always show: current version, latest version, update type (major/minor/patch).
+
+### 2. Changelog display (unless --skip-changelog)
+Fetch and display the relevant CHANGELOG.md section.
+For major updates: prefix with ⚠️ BREAKING CHANGES notice.
+Limit display to 3,000 characters — link to full CHANGELOG for the rest.
+
+### 3. Confirmation gate (unless --apply)
+Without --apply: show update info, stop. Do not modify any files.
+Message: "To apply this update: /mindforge:update --apply"
+
+### 4. Apply (with --apply)
+a. Detect original install scope (local vs global, claude vs antigravity)
+b. Read schema_version from HANDOFF.json (captures current version BEFORE update)
+c. Run `npx mindforge-cc@[latest] --[runtime] --[scope]`
+d. Run migration: `node bin/migrations/migrate.js` with captured schema_version
+e. Run /mindforge:health to verify update succeeded
+
+### 5. Post-update health check
+If health errors: surface them immediately with specific fix instructions.
+Common post-update issue: CLAUDE.md and .agent/CLAUDE.md drifted → auto-repair.
+
+## Error scenarios and recovery
+
+| Error | Recovery |
+|---|---|
+| npm registry unreachable | Message: "Check internet. Manual: npm info mindforge-cc version" |
+| Update download fails | Retry once, then suggest manual: `npx mindforge-cc@latest` |
+| Migration fails | Restored from backup automatically. Run /mindforge:migrate manually. |
+| Install scope detection fails | Prompt user: "Is your install global or local?" |
+
+## AUDIT entry

package/.mindforge/mirrors/mirror-sre-776a1cf9/.agent/mindforge/validate-phase.md

@@ -0,0 +1,31 @@
+---
+name: mindforge:validate-phase
+description: Audit the current phase for requirement coverage and test gaps
+argument-hint: [N]
+allowed-tools:
+  - view_file
+  - list_dir
+---
+
+<objective>
+Audit a completed project phase to ensure every requirement has been addressed and that corresponding automated tests have been implemented and are passing.
+</objective>
+
+<execution_context>
+.claude/commands/mindforge/validate-phase.md
+</execution_context>
+
+<context>
+Arguments: $ARGUMENTS (The phase number [N], optional)
+Knowledge: `STATE.md`, `REQUIREMENTS.md`, and the codebase test suite.
+</context>
+
+<process>
+1. **Identify Phase**: Resolve the targeted phase.
+2. **Cross-reference**:
+    - List all requirements in `REQUIREMENTS.md` marked for this phase.
+    - Verify implementation of each requirement in the code.
+    - Check for the existence of passing tests for each requirement.
+3. **Analyze Gaps**: Identify any "orphaned" requirements or features missing tests.
+4. **Report Findings**: Summarize coverage and call out specific gaps to the user.
+</process>

package/.mindforge/mirrors/mirror-sre-776a1cf9/.agent/mindforge/verify-phase.md

@@ -0,0 +1,66 @@
+---
+description: Human acceptance testing for a completed phase. Usage: /mindforge:verify-phase [N]
+---
+
+Human acceptance testing for a completed phase. Usage: /mindforge:verify-phase [N]
+
+## Pre-check
+`.planning/phases/[N]/VERIFICATION.md` must exist.
+If it does not: instruct the user to run /mindforge:execute-phase [N] first.
+
+## Step 1 — Extract testable deliverables
+Read REQUIREMENTS.md and the phase PLAN files.
+Generate a list of testable deliverables — things the user can actually check.
+
+Format each as a clear, actionable test instruction:
+"Navigate to /login and submit a form with a valid email and password.
+ You should be redirected to /dashboard within 2 seconds."
+
+## Step 2 — Walk through each deliverable
+Present one at a time. After each:
+"Please test this now and tell me: pass ✅ or fail ❌ — and describe what you saw."
+
+Wait for the user's response before proceeding to the next.
+
+## Step 3 — Handle failures
+If the user reports a failure:
+1. Ask: "What exactly happened? (error message, wrong behaviour, nothing happened)"
+2. Spawn a debug subagent with: the failure description, the relevant PLAN file,
+   and the relevant source files. Instruct it to find the root cause.
+3. Create a fix plan: `.planning/phases/[N]/FIX-PLAN-[N]-[NN].md`
+   using the same XML format as regular plans.
+4. Ask the user: "Fix plan created. Run /mindforge:execute-phase [N] again
+   to apply the fixes?"
+
+## Step 4 — Write UAT record
+Write `.planning/phases/[N]/UAT.md`:
+
+```markdown
+# UAT — Phase [N]
+
+## Tester
+[User name or "developer"]
+
+## Date
+[ISO 8601 date]
+
+## Results
+
+| # | Deliverable                        | Result | Notes                  |
+|---|------------------------------------|--------|------------------------|
+| 1 | [description]                      | ✅     | [what was observed]    |
+| 2 | [description]                      | ❌     | [what went wrong]      |
+
+## Overall status
+All passed ✅ / Issues found — fix plans created ❌
+
+## Sign-off
+[Passed / Pending fixes]
+```
+
+## Step 5 — Update state if all pass
+If all deliverables pass:
+Update STATE.md: phase N = verified and signed off.
+Tell the user:
+"✅ Phase [N] verified and signed off.
+ Run /mindforge:ship [N] to create the release PR."

package/.mindforge/mirrors/mirror-sre-776a1cf9/.agent/mindforge/workspace.md

@@ -0,0 +1,33 @@
+---
+description: Monorepo workspace management.
+---
+
+# MindForge — Workspace Command
+# Usage: /mindforge:workspace [detect|list|plan phase N|test]
+
+Monorepo workspace management.
+
+## detect
+Run workspace detector from `.mindforge/monorepo/workspace-detector.md`.
+Write WORKSPACE-MANIFEST.json.
+Report: workspace type, packages found, dependency order.
+
+## list
+Read WORKSPACE-MANIFEST.json and display package list:
+```
+Workspace: Turborepo (4 packages)
+  packages/shared    → @myapp/shared   (lib, 0 dependents)
+  apps/api           → @myapp/api      (api, depends on: shared)
+  apps/web           → @myapp/web      (web, depends on: shared, api)
+  apps/mobile        → @myapp/mobile   (mobile, depends on: shared)
+Execution order: shared → api → (web, mobile in parallel)
+```
+
+## plan phase N
+Create a phase plan that spans multiple packages.
+Uses cross-package-planner.md to determine package execution order.
+Each PLAN file includes a `<package>` and `<working-dir>` field.
+
+## test
+Run tests across all packages in dependency order.
+Report per-package test results and aggregate coverage.

package/.mindforge/mirrors/mirror-sre-776a1cf9/.agent/mindforge/workstreams.md

@@ -0,0 +1,35 @@
+---
+name: mindforge:workstreams
+description: Manage parallel feature tracks with isolated state
+argument-hint: [list|create|switch|status|complete]
+allowed-tools:
+  - list_dir
+  - view_file
+  - write_to_file
+  - run_command
+---
+
+<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/.mindforge/mirrors/mirror-sre-776a1cf9/.agent/settings.json

@@ -0,0 +1,42 @@
+{
+  "hooks": {
+    "SessionStart": [
+      {
+        "hooks": [
+          {
+            "type": "command",
+            "command": "node .agent/hooks/mindforge-check-update.js"
+          },
+          {
+            "type": "command",
+            "command": "node .agent/hooks/mindforge-session-init_extended.js"
+          }
+        ]
+      }
+    ],
+    "AfterTool": [
+      {
+        "matcher": "Bash|Edit|Write|MultiEdit|Agent|Task",
+        "hooks": [
+          {
+            "type": "command",
+            "command": "node .agent/hooks/mindforge-context-monitor.js",
+            "timeout": 10
+          }
+        ]
+      }
+    ],
+    "BeforeTool": [
+      {
+        "matcher": "Write|Edit",
+        "hooks": [
+          {
+            "type": "command",
+            "command": "node .agent/hooks/mindforge-prompt-guard.js",
+            "timeout": 5
+          }
+        ]
+      }
+    ]
+  }
+}

package/.mindforge/mirrors/mirror-sre-776a1cf9/.agent/skills/mindforge-add-backlog/SKILL.md

@@ -0,0 +1,72 @@
+---
+name: mindforge-add-backlog
+description: Add an idea to the backlog parking lot (999.x numbering)
+---
+
+
+<objective>
+Add a backlog item to the roadmap using 999.x numbering. Backlog items are
+unsequenced ideas that aren't ready for active planning — they live outside
+the normal phase sequence and accumulate context over time.
+</objective>
+
+<process>
+
+1. **Read ROADMAP.md** to find existing backlog entries:
+   ```bash
+   cat .planning/ROADMAP.md
+   ```
+
+2. **Find next backlog number:**
+   ```bash
+   NEXT=$(node ".agent/bin/mindforge-tools.cjs" phase next-decimal 999 --raw)
+   ```
+   If no 999.x phases exist, start at 999.1.
+
+3. **Create the phase directory:**
+   ```bash
+   SLUG=$(node ".agent/bin/mindforge-tools.cjs" generate-slug "$ARGUMENTS")
+   mkdir -p ".planning/phases/${NEXT}-${SLUG}"
+   touch ".planning/phases/${NEXT}-${SLUG}/.gitkeep"
+   ```
+
+4. **Add to ROADMAP.md** under a `## Backlog` section. If the section doesn't exist, create it at the end:
+
+   ```markdown
+   ## Backlog
+
+   ### Phase {NEXT}: {description} (BACKLOG)
+
+   **Goal:** [Captured for future planning]
+   **Requirements:** TBD
+   **Plans:** 0 plans
+
+   Plans:
+   - [ ] TBD (promote with /mindforge-review-backlog when ready)
+   ```
+
+5. **Commit:**
+   ```bash
+   node ".agent/bin/mindforge-tools.cjs" commit "docs: add backlog item ${NEXT} — ${ARGUMENTS}" --files .planning/ROADMAP.md ".planning/phases/${NEXT}-${SLUG}/.gitkeep"
+   ```
+
+6. **Report:**
+   ```
+   ## 📋 Backlog Item Added
+
+   Phase {NEXT}: {description}
+   Directory: .planning/phases/{NEXT}-{slug}/
+
+   This item lives in the backlog parking lot.
+   Use /mindforge-discuss-phase {NEXT} to explore it further.
+   Use /mindforge-review-backlog to promote items to active milestone.
+   ```
+
+</process>
+
+<notes>
+- 999.x numbering keeps backlog items out of the active phase sequence
+- Phase directories are created immediately, so /mindforge-discuss-phase and /mindforge-plan-phase work on them
+- No `Depends on:` field — backlog items are unsequenced by definition
+- Sparse numbering is fine (999.1, 999.3) — always uses next-decimal
+</notes>

package/.mindforge/mirrors/mirror-sre-776a1cf9/.agent/skills/mindforge-add-phase/SKILL.md

@@ -0,0 +1,39 @@
+---
+name: mindforge-add-phase
+description: Add phase to end of current milestone in roadmap
+---
+
+
+<objective>
+Add a new integer phase to the end of the current milestone in the roadmap.
+
+Routes to the add-phase workflow which handles:
+- Phase number calculation (next sequential integer)
+- Directory creation with slug generation
+- Roadmap structure updates
+- STATE.md roadmap evolution tracking
+</objective>
+
+<execution_context>
+@.agent/workflows/mindforge-add-phase.md
+</execution_context>
+
+<context>
+Arguments: $ARGUMENTS (phase description)
+
+Roadmap and state are resolved in-workflow via `init phase-op` and targeted tool calls.
+</context>
+
+<process>
+**Follow the add-phase workflow** from `@.agent/workflows/mindforge-add-phase.md`.
+
+The workflow handles all logic including:
+1. Argument parsing and validation
+2. Roadmap existence checking
+3. Current milestone identification
+4. Next phase number calculation (ignoring decimals)
+5. Slug generation from description
+6. Phase directory creation
+7. Roadmap entry insertion
+8. STATE.md updates
+</process>

package/.mindforge/mirrors/mirror-sre-776a1cf9/.agent/skills/mindforge-add-tests/SKILL.md

@@ -0,0 +1,28 @@
+---
+name: mindforge-add-tests
+description: Generate tests for a completed phase based on UAT criteria and implementation
+---
+
+<objective>
+Generate unit and E2E tests for a completed phase, using its SUMMARY.md, CONTEXT.md, and VERIFICATION.md as specifications.
+
+Analyzes implementation files, classifies them into TDD (unit), E2E (browser), or Skip categories, presents a test plan for user approval, then generates tests following RED-GREEN conventions.
+
+Output: Test files committed with message `test(phase-{N}): add unit and E2E tests from add-tests command`
+</objective>
+
+<execution_context>
+@.agent/workflows/mindforge-add-tests.md
+</execution_context>
+
+<context>
+Phase: $ARGUMENTS
+
+@.planning/STATE.md
+@.planning/ROADMAP.md
+</context>
+
+<process>
+Execute the add-tests workflow from @.agent/workflows/mindforge-add-tests.md end-to-end.
+Preserve all workflow gates (classification approval, test plan approval, RED-GREEN verification, gap reporting).
+</process>