mindforge-cc 8.2.0 → 10.0.0

package/.mindforge/intelligence/skill-gap-analyser.md

@@ -1,40 +0,0 @@
-# MindForge Intelligence — Skill Gap Analyser
-
-## Purpose
-Identify required/recommended skills for a phase, compare with installed
-skills, and report gaps before planning.
-
-## Run points
-1. `/mindforge:plan-phase` start
-2. `/mindforge:discuss-phase`
-3. `/mindforge:health`
-
-## Analysis flow
-1. Extract work signals from roadmap/context/requirements/architecture.
-2. Map work categories to required/recommended skills.
-3. Validate skills in manifest + filesystem + status.
-4. Report missing/deprecated required skills and mitigation options.
-
-## Category -> skill mapping
-- UI/UX -> accessibility (required), performance (recommended)
-- Database changes -> database-patterns (required), data-privacy (if PII)
-- API endpoints -> api-design (required), security-review (if auth)
-- Auth/payments/PII -> security-review (required), data-privacy (required for PII)
-- Performance work -> performance (required)
-- New feature -> testing-standards (required), documentation (recommended)
-
-## Gap definition
-A required skill is a gap if:
-- not present in MANIFEST
-- manifest path missing
-- marked deprecated with no replacement
-
-## Output
-Produce `Skill Gap Analysis` section with:
-- required skills table
-- recommended skills table
-- explicit gap count and options
-
-## Health mode
-In `/mindforge:health`, include org-level recommendation list using recent
-phase patterns and missing capability frequencies.

package/.mindforge/intelligence/smart-compaction.md

@@ -1,71 +0,0 @@
-# MindForge Intelligence — Smart Context Compaction
-
-## Purpose
-Replace truncation with structured extraction so future sessions preserve reasoning,
-constraints, and in-progress state.
-
-## Triggering and level selection
-Day 2 threshold (`70%`) remains valid and now invokes Day 5 Level 1.
-Level selection uses both context usage and session depth.
-
-- Light session (`<5` tasks): use Level 1 even when context is high.
-- Moderate session (`5-10` tasks): use Level 2 at `80%+`.
-- Deep session (`10+` tasks): use Level 2 at `75%+`.
-- Level 3 at `90%+` or urgent near-limit state.
-
-## Levels
-### Level 1 — Lightweight
-Quick checkpoint: update `STATE.md` and `HANDOFF.json` with next task.
-
-### Level 2 — Structured extraction
-Capture:
-- decisions made
-- discoveries
-- implicit knowledge
-- quality signals
-- precise in-progress state
-
-### Level 3 — Emergency extraction
-Capture minimum viable continuation context before hard limit.
-
-## Level 2 extraction protocol
-### Block A — Decisions made
-For each decision: what, why, alternatives ruled out, impact area, ADR need.
-
-### Block B — Discoveries
-For each finding: fact, location, significance, assumption impact.
-
-### Block C — Current task state
-Record plan id, completed steps, remaining steps, current file, and inconsistency state.
-
-### Block D — Implicit knowledge
-Capture quirks, environment facts, and workarounds.
-
-A knowledge item qualifies as a **quirk** if either:
-1. It contradicts documentation or expected tool behavior.
-2. A new agent reading only plans/personas would not infer it.
-
-### Block E — Quality signals
-Capture failed assumptions, friction patterns, quality gate root causes, and next-plan suggestions.
-
-## Level 2 HANDOFF schema additions
-- `decisions_made[]`
-- `discoveries[]`
-- `implicit_knowledge[]`
-- `quality_signals[]`
-- `in_progress.current_state`
-
-## Session restart protocol
-When loading Level 2 handoff:
-1. Print compact summary counts.
-2. Preload `implicit_knowledge` before plan execution.
-3. If `in_progress.current_state` is inconsistent, block execution and ask to resolve first.
-4. If user asks to inspect first, print first 50 lines of the inconsistent file inline.
-
-## Compaction quality metric
-Write one entry to `.mindforge/metrics/compaction-quality.jsonl`:
-- `decisions_captured`
-- `discoveries_captured`
-- `implicit_knowledge_items`
-- `quality_signals_captured`
-- `next_session_continuation_success` (auto-inferred from next session, nullable initially)

package/.mindforge/memory/MEMORY-SCHEMA.md

@@ -1,155 +0,0 @@
-# MindForge v2 — Knowledge Graph Schema
-
-## Overview
-
-The MindForge knowledge graph is built from five JSONL files — all append-only,
-all at `.mindforge/memory/`. Every entry has a consistent base schema plus
-type-specific fields.
-
-## Base schema (all entry types)
-
-```json
-{
-  "id":               "kb-uuid-v4",
-  "timestamp":        "ISO-8601",
-  "type":             "architectural_decision|code_pattern|bug_pattern|team_preference|domain_knowledge",
-  "topic":            "Short title (≤ 80 chars)",
-  "content":          "Full knowledge content (no limit)",
-  "source":           "Where this was captured: 'Phase 3 retro', 'Debug session 2026-01', 'Manual entry'",
-  "project":          "project-name from PROJECT.md",
-  "confidence":       0.0,
-  "tags":             ["tag1", "tag2"],
-  "linked_adrs":      ["ADR-007"],
-  "times_referenced": 0,
-  "last_referenced":  null,
-  "deprecated":       false,
-  "deprecated_by":    null
-}
-```
-
-## Type-specific schemas
-
-### `architectural_decision`
-
-Extended fields:
-
-```json
-{
-  "decision":     "Use argon2id for password hashing",
-  "rationale":    "bcrypt is showing its age; argon2id is the modern standard",
-  "alternatives": ["bcrypt", "scrypt", "pbkdf2"],
-  "phase_number": 3,
-  "adr_reference": "ADR-007"
-}
-```
-
-Capture trigger: Phase completion (ADR files extracted), `/mindforge:discuss-phase`
-
-### `code_pattern`
-
-Extended fields:
-
-```json
-{
-  "pattern_type": "good|anti-pattern",
-  "language":     "typescript",
-  "example_good": "// Code showing the correct pattern",
-  "example_bad":  "// Code showing the incorrect pattern (for anti-patterns)",
-  "applies_to":   ["auth", "database", "api"]
-}
-```
-
-Capture trigger: Smart compaction Block D, debug session root cause
-
-### `bug_pattern`
-
-Extended fields:
-
-```json
-{
-  "bug_category":   "auth|database|api|ui|performance|security",
-  "symptom":        "Login works in tests but fails in production with cookie errors",
-  "root_cause":     "httpOnly cookies require HTTPS; dev server was HTTP",
-  "fix":            "Enable HTTPS in dev or use secure: false in development only",
-  "prevention":     "Always configure cookie settings per-environment",
-  "severity_when_missed": "HIGH",
-  "recurrence_count": 1
-}
-```
-
-Capture trigger: Debug session completion, security findings, retrospective "what went wrong"
-
-### `team_preference`
-
-Extended fields:
-
-```json
-{
-  "preference_type": "style|tool|process|convention|architecture",
-  "applies_when":    "When implementing auth",
-  "preference":      "Always use argon2id, never bcrypt. See ADR-007.",
-  "strength":        "strong|moderate|weak",
-  "override_allowed": true
-}
-```
-
-Capture trigger: Retrospective "what should we keep doing", steering instructions,
-MINDFORGE.md changes from retrospective
-
-### `domain_knowledge`
-
-Extended fields:
-
-```json
-{
-  "domain":     "JWT security",
-  "tech_stack": ["node.js", "typescript"],
-  "knowledge":  "JWT access tokens should be short-lived (15 min). Refresh tokens in httpOnly cookies, not localStorage. Never decode JWT without verifying signature.",
-  "source_url": "https://auth0.com/docs/secure/tokens/json-web-tokens",
-  "verified_at": "2026-01-15"
-}
-```
-
-Capture trigger: Research engine output, `/mindforge:remember --add`
-
-## Confidence scoring
-
-Confidence (0.0–1.0) represents how strongly this knowledge should be applied:
-
-| Confidence | Meaning | How set |
-| :--- | :--- | :--- |
-| 0.9–1.0 | Strong team decision — always apply | Manual entry, strong steering, ADR |
-| 0.7–0.9 | Clear pattern — apply unless there's a reason not to | Retrospective, debug session |
-| 0.5–0.7 | Observed pattern — consider but verify | Smart compaction Block D |
-| 0.3–0.5 | Weak signal — informational only | Single observation |
-| < 0.3 | Hypothesis — don't apply proactively | Auto-captured, unverified |
-
-## Confidence reinforcement
-
-Each time an entry is referenced (retrieved and the advice was followed):
-
-```bash
-confidence = min(1.0, confidence + 0.05)
-times_referenced += 1
-```
-
-Each time an entry is contradicted (a different decision was made):
-
-```bash
-confidence = max(0.0, confidence - 0.10)
-```
-
-## Deprecation
-
-When a knowledge entry becomes outdated (e.g., team switches from argon2id to Passkeys):
-
-```json
-{
-  "deprecated": true,
-  "deprecated_by": "kb-uuid-of-newer-entry",
-  "deprecated_reason": "Superseded by WebAuthn/Passkeys approach (ADR-031)"
-}
-```
-
-Deprecated entries are never deleted — they are excluded from active retrieval
-but available for historical queries.

package/.mindforge/memory/engine/capture-protocol.md

@@ -1,36 +0,0 @@
-# MindForge v2 — Knowledge Capture Protocol
-
-## Purpose
-
-The Capture Engine automatically extracts valuable engineering knowledge from session artifacts to ensure that project-specific wisdom is preserved beyond a single handoff.
-
-## Capture Triggers
-
-MindForge monitors the following lifecycle events for knowledge extraction:
-
-1. **Phase Completion**: Extracting architectural decisions from `PROJECT.md` and phase retrospectives.
-2. **Hardened Debugging**: Capturing "root cause -> fix" patterns from completed debug reports.
-3. **Manual Command**: Using `/mindforge:remember --add` to explicitly record team preferences or domain knowledge.
-4. **ADR Generation**: Parsing newly created Architecture Decision Records.
-
-## Extraction Logic
-
-The extraction process (via `knowledge-capture.js`) involves:
-
-- **Structural Parsing**: Identifying standardized headings (e.g., "Decision", "Root Cause", "Pattern").
-- **Deduplication**: Checking for existing entries with similar content to prevent knowledge bloat.
-- **Initial Confidence**: Assigning a default confidence score (usually 0.5) to newly captured entries.
-- **Auto-Tagging**: Inferring tags based on the file path and content context (e.g., `#nodejs`, `#security`).
-
-## Inhibitors (What NOT to capture)
-
-To prevent the knowledge base from becoming "noisy", the system ignores:
-
-- Transient session state (e.g., local file counts).
-- Intermediate debugging steps that didn't lead to a fix.
-- Content marked with `#no-capture` or inside blocks labeled "Confidential".
-
-## Retention Policy
-
-- **Append-only**: Entries are never physically deleted.
-- **Deprecation**: Outdated entries are marked as `deprecated: true` and replaced by newer entries with the same `source_id`.

package/.mindforge/memory/engine/global-sync-spec.md

@@ -1,42 +0,0 @@
-# MindForge v2 — Global Knowledge Sync Specification
-
-## Purpose
-
-Allow knowledge to flow between projects via a machine-level global store.
-Team members can promote project-specific insights to their global knowledge base,
-which loads into every future project's session start.
-
-## Storage locations
-
-- **Project-local:** `.mindforge/memory/knowledge-base.jsonl` (per repo)
-- **Global (machine):** `~/.mindforge/global-knowledge-base.jsonl` (per developer)
-
-## Sync rules
-
-- Promotion is MANUAL — nothing is auto-promoted to global. Use `/mindforge:remember --promote [ID]`.
-- Loading is AUTOMATIC — global entries load at every session start if relevant.
-- Project entries take precedence over global entries (same ID = local wins).
-- Global entries receive a metadata flag `global: true` but are ranked alongside project entries based on relevance.
-
-## What should be promoted to global
-
-Good candidates for global promotion:
-
-- Language-agnostic security practices ("always validate input before database queries")
-- Technology-specific best practices learned through experience ("argon2id over bcrypt")
-- Universal debugging patterns ("check the timezone mismatch before blaming async code")
-- Cross-project architectural preferences ("Repository pattern over active record")
-
-## Global entry metadata
-
-When promoted to global, entries gain:
-
-```json
-{
-  "global": true,
-  "promoted_at": "ISO-8601",
-  "promoted_from_project": "saas-app",
-  "promoted_by": "git-config-user-email",
-  "global_applicability": "all|typescript|nodejs|react|[specific]"
-}
-```

package/.mindforge/memory/engine/retrieval-spec.md

@@ -1,44 +0,0 @@
-# MindForge v2 — Knowledge Retrieval Specification
-
-## Purpose
-
-The Retrieval Engine is responsible for identifying and loading the most relevant pieces of long-term memory into the current session context to improve agent performance and consistency.
-
-## Components
-
-- **Indexer (`knowledge-indexer.js`)**: Handles the scoring and ranking of knowledge entries.
-- **Session Loader (`session-memory-loader.js`)**: Orchestrates the loading of relevant memories at the start of a session.
-
-## Scoring Logic (TF-IDF + Heuristics)
-
-Relevance is calculated using a multi-factor scoring model:
-
-1. **Text Search (TF-IDF)**:
-    - Tokenizes the query and knowledge text.
-    - Calculates Term Frequency (TF) and Inverse Document Frequency (IDF).
-    - Entries must have a positive TF-IDF score to be considered relevant if keywords are present.
-
-2. **Confidence & Recency**:
-    - **Confidence Score**: Boosts entries with higher confidence levels (reinforced over time).
-    - **Recency Decay**: Prefer more recent knowledge entries, especially for bug patterns.
-
-3. **Tag Overlap**:
-    - Queries can include required tags (e.g., `#typescript`).
-    - Entries with matching tags receive a significant boost.
-
-4. **Inhibitors**:
-    - Deprecated entries are never retrieved.
-    - Low-confidence "noise" entries are filtered out.
-
-## Context Injection
-
-During session start, the loader:
-1. Performs a broad search based on the current project's primary technology stack and recent activities.
-2. Selects the top `N` (default 5-10) most relevant entries.
-3. Injects them into the agent's secondary context (e.g., as a dedicated "Memory context" block).
-
-## SDK Interface
-
-```typescript
-const relevantKnowledge = await memory.query("query string", ["#tag1"], 5);
-```

package/.mindforge/memory/knowledge-base.jsonl

@@ -1,15 +0,0 @@
-{"id":"34a7925f-7361-4836-91eb-916495033861","timestamp":"2026-03-22T17:25:37.659Z","type":"team_preference","topic":"Use Tailwind","content":"Always use Tailwind for CSS.","source":"manual","project":"[Project Name]","confidence":0.9,"tags":["ui","css"],"linked_adrs":[],"times_referenced":0,"last_referenced":null,"deprecated":false,"deprecated_by":null}
-{"id":"34a7925f-7361-4836-91eb-916495033861","timestamp":"2026-03-22T17:25:37.659Z","type":"team_preference","topic":"Use Tailwind","content":"Always use Tailwind for CSS.","source":"manual","project":"[Project Name]","confidence":0.9500000000000001,"tags":["ui","css"],"linked_adrs":[],"times_referenced":1,"last_referenced":"2026-03-22T17:25:37.665Z","deprecated":false,"deprecated_by":null}
-{"id":"34a7925f-7361-4836-91eb-916495033861","timestamp":"2026-03-22T17:25:37.659Z","type":"team_preference","topic":"Use Tailwind","content":"Always use Tailwind for CSS.","source":"manual","project":"[Project Name]","confidence":0.9500000000000001,"tags":["ui","css"],"linked_adrs":[],"times_referenced":1,"last_referenced":"2026-03-22T17:25:37.665Z","deprecated":true,"deprecated_by":null,"deprecated_reason":"Switching to Vanilla CSS","deprecated_at":"2026-03-22T17:25:37.666Z"}
-{"id":"a2d4b3a6-fdaa-4c9a-b654-286d9ea133e2","timestamp":"2026-03-22T17:25:37.670Z","type":"domain_knowledge","topic":"Auth with JWT","content":"Secure JWT with httpOnly cookies.","source":"manual","project":"[Project Name]","confidence":0.8,"tags":["auth"],"linked_adrs":[],"times_referenced":0,"last_referenced":null,"deprecated":false,"deprecated_by":null}
-{"id":"6c1f0f31-3903-4b95-bae8-5473ffbec9eb","timestamp":"2026-03-22T17:25:37.671Z","type":"domain_knowledge","topic":"Database SQL","content":"Use indexed columns for fast queries.","source":"manual","project":"[Project Name]","confidence":0.7,"tags":["db"],"linked_adrs":[],"times_referenced":0,"last_referenced":null,"deprecated":false,"deprecated_by":null}
-{"id":"a9878977-cb7c-4dcf-8161-760ffd5e7de9","timestamp":"2026-03-22T17:25:37.673Z","type":"code_pattern","topic":"React Memo","content":"Use React.memo to prevent re-renders.","source":"manual","project":"[Project Name]","confidence":0.6,"tags":["ui"],"linked_adrs":[],"times_referenced":0,"last_referenced":null,"deprecated":false,"deprecated_by":null}
-{"id":"739dcb0a-9c4b-40d2-846b-535b7e4cb274","timestamp":"2026-03-22T17:25:51.782Z","type":"team_preference","topic":"Use Tailwind","content":"Always use Tailwind for CSS.","source":"manual","project":"[Project Name]","confidence":0.9,"tags":["ui","css"],"linked_adrs":[],"times_referenced":0,"last_referenced":null,"deprecated":false,"deprecated_by":null}
-{"id":"739dcb0a-9c4b-40d2-846b-535b7e4cb274","timestamp":"2026-03-22T17:25:51.782Z","type":"team_preference","topic":"Use Tailwind","content":"Always use Tailwind for CSS.","source":"manual","project":"[Project Name]","confidence":0.9500000000000001,"tags":["ui","css"],"linked_adrs":[],"times_referenced":1,"last_referenced":"2026-03-25T17:42:57.286Z","deprecated":false,"deprecated_by":null}
-{"id":"a9878977-cb7c-4dcf-8161-760ffd5e7de9","timestamp":"2026-03-22T17:25:37.673Z","type":"code_pattern","topic":"React Memo","content":"Use React.memo to prevent re-renders.","source":"manual","project":"[Project Name]","confidence":0.65,"tags":["ui"],"linked_adrs":[],"times_referenced":1,"last_referenced":"2026-03-25T17:42:57.297Z","deprecated":false,"deprecated_by":null}
-{"id":"a2d4b3a6-fdaa-4c9a-b654-286d9ea133e2","timestamp":"2026-03-22T17:25:37.670Z","type":"domain_knowledge","topic":"Auth with JWT","content":"Secure JWT with httpOnly cookies.","source":"manual","project":"[Project Name]","confidence":0.8500000000000001,"tags":["auth"],"linked_adrs":[],"times_referenced":1,"last_referenced":"2026-03-25T17:42:57.298Z","deprecated":false,"deprecated_by":null}
-{"id":"6c1f0f31-3903-4b95-bae8-5473ffbec9eb","timestamp":"2026-03-22T17:25:37.671Z","type":"domain_knowledge","topic":"Database SQL","content":"Use indexed columns for fast queries.","source":"manual","project":"[Project Name]","confidence":0.75,"tags":["db"],"linked_adrs":[],"times_referenced":1,"last_referenced":"2026-03-25T17:42:57.299Z","deprecated":false,"deprecated_by":null}
-{"id":"f3df4851-b705-429d-a3b1-2c90eac2d73c","timestamp":"2026-04-08T19:47:41.444Z","type":"pillar_health","topic":"Phase 99 Architectural Health","content":"RSA Alignment: 0.785\nIDC Upgrades: 1","source":"PillarHealth Analysis (Phase 99)","project":"[Project Name]","confidence":1,"tags":[],"linked_adrs":[],"times_referenced":0,"last_referenced":null,"deprecated":false,"deprecated_by":null,"rsa_avg":0.785,"idc_avg":1}
-{"id":"a24f9667-b90a-49fe-90cd-9fe545ce98fb","timestamp":"2026-04-08T19:47:41.446Z","type":"stability_pattern","topic":"REQ-02 Alignment Recovery","content":"Synthesized refocus instruction: STAY ON TRACK WITH AUTH","source":"SCS Synthesis (Phase 99)","project":"[Project Name]","confidence":0.72,"tags":[],"linked_adrs":[],"times_referenced":0,"last_referenced":null,"deprecated":false,"deprecated_by":null,"req_id":"REQ-02","efficacy_score":0.72}
-{"id":"f3df4851-b705-429d-a3b1-2c90eac2d73c","timestamp":"2026-04-08T19:47:41.444Z","type":"pillar_health","topic":"Phase 99 Architectural Health","content":"RSA Alignment: 0.785\nIDC Upgrades: 1","source":"PillarHealth Analysis (Phase 99)","project":"[Project Name]","confidence":1,"tags":[],"linked_adrs":[],"times_referenced":1,"last_referenced":"2026-04-08T19:48:13.482Z","deprecated":false,"deprecated_by":null,"rsa_avg":0.785,"idc_avg":1}
-{"id":"a24f9667-b90a-49fe-90cd-9fe545ce98fb","timestamp":"2026-04-08T19:47:41.446Z","type":"stability_pattern","topic":"REQ-02 Alignment Recovery","content":"Synthesized refocus instruction: STAY ON TRACK WITH AUTH","source":"SCS Synthesis (Phase 99)","project":"[Project Name]","confidence":0.77,"tags":[],"linked_adrs":[],"times_referenced":1,"last_referenced":"2026-04-08T19:48:13.484Z","deprecated":false,"deprecated_by":null,"req_id":"REQ-02","efficacy_score":0.72}

package/.mindforge/memory/pattern-library.jsonl

@@ -1 +0,0 @@
-{"id":"LOCAL-SAFE-001","tags":["performance"],"description":"Standard optimization"}

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

@@ -1,6 +0,0 @@
-{
-  "pattern-library.jsonl": {
-    "lastSync": "2026-04-11T15:30:35.299Z",
-    "localCount": 1
-  }
-}

package/.mindforge/memory/team-preferences.jsonl

@@ -1,5 +0,0 @@
-{"id":"34a7925f-7361-4836-91eb-916495033861","timestamp":"2026-03-22T17:25:37.659Z","type":"team_preference","topic":"Use Tailwind","content":"Always use Tailwind for CSS.","source":"manual","project":"[Project Name]","confidence":0.9,"tags":["ui","css"],"linked_adrs":[],"times_referenced":0,"last_referenced":null,"deprecated":false,"deprecated_by":null}
-{"id":"34a7925f-7361-4836-91eb-916495033861","timestamp":"2026-03-22T17:25:37.659Z","type":"team_preference","topic":"Use Tailwind","content":"Always use Tailwind for CSS.","source":"manual","project":"[Project Name]","confidence":0.9500000000000001,"tags":["ui","css"],"linked_adrs":[],"times_referenced":1,"last_referenced":"2026-03-22T17:25:37.665Z","deprecated":false,"deprecated_by":null}
-{"id":"34a7925f-7361-4836-91eb-916495033861","timestamp":"2026-03-22T17:25:37.659Z","type":"team_preference","topic":"Use Tailwind","content":"Always use Tailwind for CSS.","source":"manual","project":"[Project Name]","confidence":0.9500000000000001,"tags":["ui","css"],"linked_adrs":[],"times_referenced":1,"last_referenced":"2026-03-22T17:25:37.665Z","deprecated":true,"deprecated_by":null,"deprecated_reason":"Switching to Vanilla CSS","deprecated_at":"2026-03-22T17:25:37.666Z"}
-{"id":"739dcb0a-9c4b-40d2-846b-535b7e4cb274","timestamp":"2026-03-22T17:25:51.782Z","type":"team_preference","topic":"Use Tailwind","content":"Always use Tailwind for CSS.","source":"manual","project":"[Project Name]","confidence":0.9,"tags":["ui","css"],"linked_adrs":[],"times_referenced":0,"last_referenced":null,"deprecated":false,"deprecated_by":null}
-{"id":"739dcb0a-9c4b-40d2-846b-535b7e4cb274","timestamp":"2026-03-22T17:25:51.782Z","type":"team_preference","topic":"Use Tailwind","content":"Always use Tailwind for CSS.","source":"manual","project":"[Project Name]","confidence":0.9500000000000001,"tags":["ui","css"],"linked_adrs":[],"times_referenced":1,"last_referenced":"2026-03-25T17:42:57.286Z","deprecated":false,"deprecated_by":null}

package/.mindforge/metrics/METRICS-SCHEMA.md

@@ -1,42 +0,0 @@
-# MindForge Metrics — Schema Reference
-
-## Files
-- `session-quality.jsonl`
-- `phase-metrics.jsonl`
-- `skill-usage.jsonl`
-- `compaction-quality.jsonl`
-
-All files are append-only JSONL.
-
-## session-quality.jsonl fields
-- session_id, date, phase, developer_id
-- tasks_attempted, tasks_completed, tasks_failed
-- verify_pass_rate, quality_gates_failed
-- security_findings, context_compactions
-- skills_loaded_count, antipatterns_detected
-- session_quality_score, session_quality_score_raw
-
-Score formula:
-- base 100
-- minus task/gate/security/antipattern penalties
-- bonus for zero gate failures and zero security findings
-- keep both raw and clamped (`0-100`) score for trend analysis
-
-## phase-metrics.jsonl fields
-- phase lifecycle and delivery coverage
-- difficulty score
-- security and UAT outcomes
-- phase_quality_score
-
-## skill-usage.jsonl fields
-- date, phase, plan
-- skill_name, skill_version
-- trigger_type (`text_match|file_path_match|file_name_match`)
-- trigger_keyword
-- task_outcome, verify_passed_first_try
-
-## compaction-quality.jsonl fields
-- date, compaction_level, context_pct_at_compaction
-- decisions_captured, discoveries_captured
-- implicit_knowledge_items, quality_signals_captured
-- next_session_continuation_success (auto-inferred where possible)

package/.mindforge/metrics/quality-tracker.md

@@ -1,32 +0,0 @@
-# MindForge Metrics — Quality Tracker
-
-## Trend windows
-- short: last 5 sessions
-- medium: last 20 sessions
-- long: all sessions
-
-## Key targets
-- Verify pass rate > 85% (warning < 75%)
-- Task failure rate < 10% (warning > 20%)
-- Compactions < 1 per 8 tasks (warning > 2 per session)
-
-## Early warnings
-- quality score drop >= 10 points over 3 sessions
-- any CRITICAL security finding after clean streak
-- compaction overhead > 2/session
-- stale skills not triggered in 10 sessions
-
-## Quality metrics -> agent behaviour adjustment
-Automatic adjustments at session start:
-
-- If verify pass rate < 75% over last 3 sessions:
-  tighten verify-step determinism checks before execution.
-- If last-session task failure rate > 20%:
-  halve estimated scope and suggest splitting.
-- If compaction frequency > 2/session:
-  proactively summarize every 4 tasks.
-- If security findings trend worsens over 3 phases:
-  force-load `security-review` for all tasks in current phase.
-
-Always report adjustment to user:
-`Quality signal detected: [signal]. Adjusting behaviour: [adjustment].`

package/.mindforge/mirrors/mirror-sre-776a1cf9/.agent/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)