mindforge-cc 9.0.0 → 10.0.1

package/.agent/workflows/mindforge-audit-milestone.md

@@ -1,332 +0,0 @@
-<purpose>
-Verify milestone achieved its definition of done by aggregating phase verifications, checking cross-phase integration, and assessing requirements coverage. Reads existing VERIFICATION.md files (phases already verified during execute-phase), aggregates tech debt and deferred gaps, then spawns integration checker for cross-phase wiring.
-</purpose>
-
-<required_reading>
-Read all files referenced by the invoking prompt's execution_context before starting.
-</required_reading>
-
-<process>
-
-## 0. Initialize Milestone Context
-
-```bash
-INIT=$(node ".agent/bin/mindforge-tools.cjs" init milestone-op)
-if [[ "$INIT" == @file:* ]]; then INIT=$(cat "${INIT#@file:}"); fi
-```
-
-Extract from init JSON: `milestone_version`, `milestone_name`, `phase_count`, `completed_phases`, `commit_docs`.
-
-Resolve integration checker model:
-```bash
-integration_checker_model=$(node ".agent/bin/mindforge-tools.cjs" resolve-model mindforge-integration-checker --raw)
-```
-
-## 1. Determine Milestone Scope
-
-```bash
-# Get phases in milestone (sorted numerically, handles decimals)
-node ".agent/bin/mindforge-tools.cjs" phases list
-```
-
-- Parse version from arguments or detect current from ROADMAP.md
-- Identify all phase directories in scope
-- Extract milestone definition of done from ROADMAP.md
-- Extract requirements mapped to this milestone from REQUIREMENTS.md
-
-## 2. Read All Phase Verifications
-
-For each phase directory, read the VERIFICATION.md:
-
-```bash
-# For each phase, use find-phase to resolve the directory (handles archived phases)
-PHASE_INFO=$(node ".agent/bin/mindforge-tools.cjs" find-phase 01 --raw)
-# Extract directory from JSON, then read VERIFICATION.md from that directory
-# Repeat for each phase number from ROADMAP.md
-```
-
-From each VERIFICATION.md, extract:
-- **Status:** passed | gaps_found
-- **Critical gaps:** (if any — these are blockers)
-- **Non-critical gaps:** tech debt, deferred items, warnings
-- **Anti-patterns found:** TODOs, stubs, placeholders
-- **Requirements coverage:** which requirements satisfied/blocked
-
-If a phase is missing VERIFICATION.md, flag it as "unverified phase" — this is a blocker.
-
-## 3. Spawn Integration Checker
-
-With phase context collected:
-
-Extract `MILESTONE_REQ_IDS` from REQUIREMENTS.md traceability table — all REQ-IDs assigned to phases in this milestone.
-
-```
-Task(
-  prompt="Check cross-phase integration and E2E flows.
-
-Phases: {phase_dirs}
-Phase exports: {from SUMMARYs}
-API routes: {routes created}
-
-Milestone Requirements:
-{MILESTONE_REQ_IDS — list each REQ-ID with description and assigned phase}
-
-MUST map each integration finding to affected requirement IDs where applicable.
-
-Verify cross-phase wiring and E2E user flows.",
-  subagent_type="mindforge-integration-checker",
-  model="{integration_checker_model}"
-)
-```
-
-## 4. Collect Results
-
-Combine:
-- Phase-level gaps and tech debt (from step 2)
-- Integration checker's report (wiring gaps, broken flows)
-
-## 5. Check Requirements Coverage (3-Source Cross-Reference)
-
-MUST cross-reference three independent sources for each requirement:
-
-### 5a. Parse REQUIREMENTS.md Traceability Table
-
-Extract all REQ-IDs mapped to milestone phases from the traceability table:
-- Requirement ID, description, assigned phase, current status, checked-off state (`[x]` vs `[ ]`)
-
-### 5b. Parse Phase VERIFICATION.md Requirements Tables
-
-For each phase's VERIFICATION.md, extract the expanded requirements table:
-- Requirement | Source Plan | Description | Status | Evidence
-- Map each entry back to its REQ-ID
-
-### 5c. Extract SUMMARY.md Frontmatter Cross-Check
-
-For each phase's SUMMARY.md, extract `requirements-completed` from YAML frontmatter:
-```bash
-for summary in .planning/phases/*-*/*-SUMMARY.md; do
-  node ".agent/bin/mindforge-tools.cjs" summary-extract "$summary" --fields requirements_completed --pick requirements_completed
-done
-```
-
-### 5d. Status Determination Matrix
-
-For each REQ-ID, determine status using all three sources:
-
-| VERIFICATION.md Status | SUMMARY Frontmatter | REQUIREMENTS.md | → Final Status |
-|------------------------|---------------------|-----------------|----------------|
-| passed                 | listed              | `[x]`           | **satisfied**  |
-| passed                 | listed              | `[ ]`           | **satisfied** (update checkbox) |
-| passed                 | missing             | any             | **partial** (verify manually) |
-| gaps_found             | any                 | any             | **unsatisfied** |
-| missing                | listed              | any             | **partial** (verification gap) |
-| missing                | missing             | any             | **unsatisfied** |
-
-### 5e. FAIL Gate and Orphan Detection
-
-**REQUIRED:** Any `unsatisfied` requirement MUST force `gaps_found` status on the milestone audit.
-
-**Orphan detection:** Requirements present in REQUIREMENTS.md traceability table but absent from ALL phase VERIFICATION.md files MUST be flagged as orphaned. Orphaned requirements are treated as `unsatisfied` — they were assigned but never verified by any phase.
-
-## 5.5. Nyquist Compliance Discovery
-
-Skip if `workflow.nyquist_validation` is explicitly `false` (absent = enabled).
-
-```bash
-NYQUIST_CONFIG=$(node ".agent/bin/mindforge-tools.cjs" config-get workflow.nyquist_validation --raw 2>/dev/null)
-```
-
-If `false`: skip entirely.
-
-For each phase directory, check `*-VALIDATION.md`. If exists, parse frontmatter (`nyquist_compliant`, `wave_0_complete`).
-
-Classify per phase:
-
-| Status | Condition |
-|--------|-----------|
-| COMPLIANT | `nyquist_compliant: true` and all tasks green |
-| PARTIAL | VALIDATION.md exists, `nyquist_compliant: false` or red/pending |
-| MISSING | No VALIDATION.md |
-
-Add to audit YAML: `nyquist: { compliant_phases, partial_phases, missing_phases, overall }`
-
-Discovery only — never auto-calls `/mindforge-validate-phase`.
-
-## 6. Aggregate into v{version}-MILESTONE-AUDIT.md
-
-Create `.planning/v{version}-v{version}-MILESTONE-AUDIT.md` with:
-
-```yaml
----
-milestone: {version}
-audited: {timestamp}
-status: passed | gaps_found | tech_debt
-scores:
-  requirements: N/M
-  phases: N/M
-  integration: N/M
-  flows: N/M
-gaps:  # Critical blockers
-  requirements:
-    - id: "{REQ-ID}"
-      status: "unsatisfied | partial | orphaned"
-      phase: "{assigned phase}"
-      claimed_by_plans: ["{plan files that reference this requirement}"]
-      completed_by_plans: ["{plan files whose SUMMARY marks it complete}"]
-      verification_status: "passed | gaps_found | missing | orphaned"
-      evidence: "{specific evidence or lack thereof}"
-  integration: [...]
-  flows: [...]
-tech_debt:  # Non-critical, deferred
-  - phase: 01-auth
-    items:
-      - "TODO: add rate limiting"
-      - "Warning: no password strength validation"
-  - phase: 03-dashboard
-    items:
-      - "Deferred: mobile responsive layout"
----
-```
-
-Plus full markdown report with tables for requirements, phases, integration, tech debt.
-
-**Status values:**
-- `passed` — all requirements met, no critical gaps, minimal tech debt
-- `gaps_found` — critical blockers exist
-- `tech_debt` — no blockers but accumulated deferred items need review
-
-## 7. Present Results
-
-Route by status (see `<offer_next>`).
-
-</process>
-
-<offer_next>
-Output this markdown directly (not as a code block). Route based on status:
-
----
-
-**If passed:**
-
-## ✓ Milestone {version} — Audit Passed
-
-**Score:** {N}/{M} requirements satisfied
-**Report:** .planning/v{version}-MILESTONE-AUDIT.md
-
-All requirements covered. Cross-phase integration verified. E2E flows complete.
-
-───────────────────────────────────────────────────────────────
-
-## ▶ Next Up
-
-**Complete milestone** — archive and tag
-
-/mindforge-complete-milestone {version}
-
-<sub>/clear first → fresh context window</sub>
-
-───────────────────────────────────────────────────────────────
-
----
-
-**If gaps_found:**
-
-## ⚠ Milestone {version} — Gaps Found
-
-**Score:** {N}/{M} requirements satisfied
-**Report:** .planning/v{version}-MILESTONE-AUDIT.md
-
-### Unsatisfied Requirements
-
-{For each unsatisfied requirement:}
-- **{REQ-ID}: {description}** (Phase {X})
-  - {reason}
-
-### Cross-Phase Issues
-
-{For each integration gap:}
-- **{from} → {to}:** {issue}
-
-### Broken Flows
-
-{For each flow gap:}
-- **{flow name}:** breaks at {step}
-
-### Nyquist Coverage
-
-| Phase | VALIDATION.md | Compliant | Action |
-|-------|---------------|-----------|--------|
-| {phase} | exists/missing | true/false/partial | `/mindforge-validate-phase {N}` |
-
-Phases needing validation: run `/mindforge-validate-phase {N}` for each flagged phase.
-
-───────────────────────────────────────────────────────────────
-
-## ▶ Next Up
-
-**Plan gap closure** — create phases to complete milestone
-
-/mindforge-plan-milestone-gaps
-
-<sub>/clear first → fresh context window</sub>
-
-───────────────────────────────────────────────────────────────
-
-**Also available:**
-- cat .planning/v{version}-MILESTONE-AUDIT.md — see full report
-- /mindforge-complete-milestone {version} — proceed anyway (accept tech debt)
-
-───────────────────────────────────────────────────────────────
-
----
-
-**If tech_debt (no blockers but accumulated debt):**
-
-## ⚡ Milestone {version} — Tech Debt Review
-
-**Score:** {N}/{M} requirements satisfied
-**Report:** .planning/v{version}-MILESTONE-AUDIT.md
-
-All requirements met. No critical blockers. Accumulated tech debt needs review.
-
-### Tech Debt by Phase
-
-{For each phase with debt:}
-**Phase {X}: {name}**
-- {item 1}
-- {item 2}
-
-### Total: {N} items across {M} phases
-
-───────────────────────────────────────────────────────────────
-
-## ▶ Options
-
-**A. Complete milestone** — accept debt, track in backlog
-
-/mindforge-complete-milestone {version}
-
-**B. Plan cleanup phase** — address debt before completing
-
-/mindforge-plan-milestone-gaps
-
-<sub>/clear first → fresh context window</sub>
-
-───────────────────────────────────────────────────────────────
-</offer_next>
-
-<success_criteria>
-- [ ] Milestone scope identified
-- [ ] All phase VERIFICATION.md files read
-- [ ] SUMMARY.md `requirements-completed` frontmatter extracted for each phase
-- [ ] REQUIREMENTS.md traceability table parsed for all milestone REQ-IDs
-- [ ] 3-source cross-reference completed (VERIFICATION + SUMMARY + traceability)
-- [ ] Orphaned requirements detected (in traceability but absent from all VERIFICATIONs)
-- [ ] Tech debt and deferred gaps aggregated
-- [ ] Integration checker spawned with milestone requirement IDs
-- [ ] v{version}-MILESTONE-AUDIT.md created with structured requirement gap objects
-- [ ] FAIL gate enforced — any unsatisfied requirement forces gaps_found status
-- [ ] Nyquist compliance scanned for all milestone phases (if enabled)
-- [ ] Missing VALIDATION.md phases flagged with validate-phase suggestion
-- [ ] Results presented with actionable next steps
-</success_criteria>

package/.agent/workflows/mindforge-audit-uat.md

@@ -1,109 +0,0 @@
-<purpose>
-Cross-phase audit of all UAT and verification files. Finds every outstanding item (pending, skipped, blocked, human_needed), optionally verifies against the codebase to detect stale docs, and produces a prioritized human test plan.
-</purpose>
-
-<process>
-
-<step name="initialize">
-Run the CLI audit:
-
-```bash
-AUDIT=$(node ".agent/bin/mindforge-tools.cjs" audit-uat --raw)
-```
-
-Parse JSON for `results` array and `summary` object.
-
-If `summary.total_items` is 0:
-```
-## All Clear
-
-No outstanding UAT or verification items found across all phases.
-All tests are passing, resolved, or diagnosed with fix plans.
-```
-Stop here.
-</step>
-
-<step name="categorize">
-Group items by what's actionable NOW vs. what needs prerequisites:
-
-**Testable Now** (no external dependencies):
-- `pending` — tests never run
-- `human_uat` — human verification items
-- `skipped_unresolved` — skipped without clear blocking reason
-
-**Needs Prerequisites:**
-- `server_blocked` — needs external server running
-- `device_needed` — needs physical device (not simulator)
-- `build_needed` — needs release/preview build
-- `third_party` — needs external service configuration
-
-For each item in "Testable Now", use Grep/Read to check if the underlying feature still exists in the codebase:
-- If the test references a component/function that no longer exists → mark as `stale`
-- If the test references code that has been significantly rewritten → mark as `needs_update`
-- Otherwise → mark as `active`
-</step>
-
-<step name="present">
-Present the audit report:
-
-```
-## UAT Audit Report
-
-**{total_items} outstanding items across {total_files} files in {phase_count} phases**
-
-### Testable Now ({count})
-
-| # | Phase | Test | Description | Status |
-|---|-------|------|-------------|--------|
-| 1 | {phase} | {test_name} | {expected} | {active/stale/needs_update} |
-...
-
-### Needs Prerequisites ({count})
-
-| # | Phase | Test | Blocked By | Description |
-|---|-------|------|------------|-------------|
-| 1 | {phase} | {test_name} | {category} | {expected} |
-...
-
-### Stale (can be closed) ({count})
-
-| # | Phase | Test | Why Stale |
-|---|-------|------|-----------|
-| 1 | {phase} | {test_name} | {reason} |
-...
-
----
-
-## Recommended Actions
-
-1. **Close stale items:** `/mindforge-verify-work {phase}` — mark stale tests as resolved
-2. **Run active tests:** Human UAT test plan below
-3. **When prerequisites met:** Retest blocked items with `/mindforge-verify-work {phase}`
-```
-</step>
-
-<step name="test_plan">
-Generate a human UAT test plan for "Testable Now" + "active" items only:
-
-Group by what can be tested together (same screen, same feature, same prerequisite):
-
-```
-## Human UAT Test Plan
-
-### Group 1: {category — e.g., "Billing Flow"}
-Prerequisites: {what needs to be running/configured}
-
-1. **{Test name}** (Phase {N})
-   - Navigate to: {where}
-   - Do: {action}
-   - Expected: {expected behavior}
-
-2. **{Test name}** (Phase {N})
-   ...
-
-### Group 2: {category}
-...
-```
-</step>
-
-</process>