mindforge-cc 11.3.0 → 11.4.0

package/docs/Templates/System/CONTEXT.md

@@ -0,0 +1,352 @@
+# Phase Context Template
+
+Template for `.planning/phases/XX-name/{phase_num}-CONTEXT.md` - captures implementation decisions for a phase.
+
+**Purpose:** Document decisions that downstream agents need. Researcher uses this to know WHAT to investigate. Planner uses this to know WHAT choices are locked vs flexible.
+
+**Key principle:** Categories are NOT predefined. They emerge from what was actually discussed for THIS phase. A CLI phase has CLI-relevant sections, a UI phase has UI-relevant sections.
+
+**Downstream consumers:**
+- `mindforge-phase-researcher` — Reads decisions to focus research (e.g., "card layout" → research card component patterns)
+- `mindforge-planner` — Reads decisions to create specific tasks (e.g., "infinite scroll" → task includes virtualization)
+
+---
+
+## File Template
+
+```markdown
+# Phase [X]: [Name] - Context
+
+**Gathered:** [date]
+**Status:** Ready for planning
+
+<domain>
+## Phase Boundary
+
+[Clear statement of what this phase delivers — the scope anchor. This comes from ROADMAP.md and is fixed. Discussion clarifies implementation within this boundary.]
+
+</domain>
+
+<decisions>
+## Implementation Decisions
+
+### [Area 1 that was discussed]
+- **D-01:** [Specific decision made]
+- **D-02:** [Another decision if applicable]
+
+### [Area 2 that was discussed]
+- **D-03:** [Specific decision made]
+
+### [Area 3 that was discussed]
+- **D-04:** [Specific decision made]
+
+### the agent's Discretion
+[Areas where user explicitly said "you decide" — the agent has flexibility here during planning/implementation]
+
+</decisions>
+
+<specifics>
+## Specific Ideas
+
+[Any particular references, examples, or "I want it like X" moments from discussion. Product references, specific behaviors, interaction patterns.]
+
+[If none: "No specific requirements — open to standard approaches"]
+
+</specifics>
+
+<canonical_refs>
+## Canonical References
+
+**Downstream agents MUST read these before planning or implementing.**
+
+[List every spec, ADR, feature doc, or design doc that defines requirements or constraints for this phase. Use full relative paths so agents can read them directly. Group by topic area when the phase has multiple concerns.]
+
+### [Topic area 1]
+- `path/to/spec-or-adr.md` — [What this doc decides/defines that's relevant]
+- `path/to/doc.md` §N — [Specific section and what it covers]
+
+### [Topic area 2]
+- `path/to/feature-doc.md` — [What capability this defines]
+
+[If the project has no external specs: "No external specs — requirements are fully captured in decisions above"]
+
+</canonical_refs>
+
+<code_context>
+## Existing Code Insights
+
+### Reusable Assets
+- [Component/hook/utility]: [How it could be used in this phase]
+
+### Established Patterns
+- [Pattern]: [How it constrains/enables this phase]
+
+### Integration Points
+- [Where new code connects to existing system]
+
+</code_context>
+
+<deferred>
+## Deferred Ideas
+
+[Ideas that came up during discussion but belong in other phases. Captured here so they're not lost, but explicitly out of scope for this phase.]
+
+[If none: "None — discussion stayed within phase scope"]
+
+</deferred>
+
+---
+
+*Phase: XX-name*
+*Context gathered: [date]*
+```
+
+<good_examples>
+
+**Example 1: Visual feature (Post Feed)**
+
+```markdown
+# Phase 3: Post Feed - Context
+
+**Gathered:** 2025-01-20
+**Status:** Ready for planning
+
+<domain>
+## Phase Boundary
+
+Display posts from followed users in a scrollable feed. Users can view posts and see engagement counts. Creating posts and interactions are separate phases.
+
+</domain>
+
+<decisions>
+## Implementation Decisions
+
+### Layout style
+- Card-based layout, not timeline or list
+- Each card shows: author avatar, name, timestamp, full post content, reaction counts
+- Cards have subtle shadows, rounded corners — modern feel
+
+### Loading behavior
+- Infinite scroll, not pagination
+- Pull-to-refresh on mobile
+- New posts indicator at top ("3 new posts") rather than auto-inserting
+
+### Empty state
+- Friendly illustration + "Follow people to see posts here"
+- Suggest 3-5 accounts to follow based on interests
+
+### the agent's Discretion
+- Loading skeleton design
+- Exact spacing and typography
+- Error state handling
+
+</decisions>
+
+<canonical_refs>
+## Canonical References
+
+### Feed display
+- `docs/features/social-feed.md` — Feed requirements, post card fields, engagement display rules
+- `docs/decisions/adr-012-infinite-scroll.md` — Scroll strategy decision, virtualization requirements
+
+### Empty states
+- `docs/design/empty-states.md` — Empty state patterns, illustration guidelines
+
+</canonical_refs>
+
+<specifics>
+## Specific Ideas
+
+- "I like how Twitter shows the new posts indicator without disrupting your scroll position"
+- Cards should feel like Linear's issue cards — clean, not cluttered
+
+</specifics>
+
+<deferred>
+## Deferred Ideas
+
+- Commenting on posts — Phase 5
+- Bookmarking posts — add to backlog
+
+</deferred>
+
+---
+
+*Phase: 03-post-feed*
+*Context gathered: 2025-01-20*
+```
+
+**Example 2: CLI tool (Database backup)**
+
+```markdown
+# Phase 2: Backup Command - Context
+
+**Gathered:** 2025-01-20
+**Status:** Ready for planning
+
+<domain>
+## Phase Boundary
+
+CLI command to backup database to local file or S3. Supports full and incremental backups. Restore command is a separate phase.
+
+</domain>
+
+<decisions>
+## Implementation Decisions
+
+### Output format
+- JSON for programmatic use, table format for humans
+- Default to table, --json flag for JSON
+- Verbose mode (-v) shows progress, silent by default
+
+### Flag design
+- Short flags for common options: -o (output), -v (verbose), -f (force)
+- Long flags for clarity: --incremental, --compress, --encrypt
+- Required: database connection string (positional or --db)
+
+### Error recovery
+- Retry 3 times on network failure, then fail with clear message
+- --no-retry flag to fail fast
+- Partial backups are deleted on failure (no corrupt files)
+
+### the agent's Discretion
+- Exact progress bar implementation
+- Compression algorithm choice
+- Temp file handling
+
+</decisions>
+
+<canonical_refs>
+## Canonical References
+
+### Backup CLI
+- `docs/features/backup-restore.md` — Backup requirements, supported backends, encryption spec
+- `docs/decisions/adr-007-cli-conventions.md` — Flag naming, exit codes, output format standards
+
+</canonical_refs>
+
+<specifics>
+## Specific Ideas
+
+- "I want it to feel like pg_dump — familiar to database people"
+- Should work in CI pipelines (exit codes, no interactive prompts)
+
+</specifics>
+
+<deferred>
+## Deferred Ideas
+
+- Scheduled backups — separate phase
+- Backup rotation/retention — add to backlog
+
+</deferred>
+
+---
+
+*Phase: 02-backup-command*
+*Context gathered: 2025-01-20*
+```
+
+**Example 3: Organization task (Photo library)**
+
+```markdown
+# Phase 1: Photo Organization - Context
+
+**Gathered:** 2025-01-20
+**Status:** Ready for planning
+
+<domain>
+## Phase Boundary
+
+Organize existing photo library into structured folders. Handle duplicates and apply consistent naming. Tagging and search are separate phases.
+
+</domain>
+
+<decisions>
+## Implementation Decisions
+
+### Grouping criteria
+- Primary grouping by year, then by month
+- Events detected by time clustering (photos within 2 hours = same event)
+- Event folders named by date + location if available
+
+### Duplicate handling
+- Keep highest resolution version
+- Move duplicates to _duplicates folder (don't delete)
+- Log all duplicate decisions for review
+
+### Naming convention
+- Format: YYYY-MM-DD_HH-MM-SS_originalname.ext
+- Preserve original filename as suffix for searchability
+- Handle name collisions with incrementing suffix
+
+### the agent's Discretion
+- Exact clustering algorithm
+- How to handle photos with no EXIF data
+- Folder emoji usage
+
+</decisions>
+
+<canonical_refs>
+## Canonical References
+
+### Organization rules
+- `docs/features/photo-organization.md` — Grouping rules, duplicate policy, naming spec
+- `docs/decisions/adr-003-exif-handling.md` — EXIF extraction strategy, fallback for missing metadata
+
+</canonical_refs>
+
+<specifics>
+## Specific Ideas
+
+- "I want to be able to find photos by roughly when they were taken"
+- Don't delete anything — worst case, move to a review folder
+
+</specifics>
+
+<deferred>
+## Deferred Ideas
+
+- Face detection grouping — future phase
+- Cloud sync — out of scope for now
+
+</deferred>
+
+---
+
+*Phase: 01-photo-organization*
+*Context gathered: 2025-01-20*
+```
+
+</good_examples>
+
+<guidelines>
+**This template captures DECISIONS for downstream agents.**
+
+The output should answer: "What does the researcher need to investigate? What choices are locked for the planner?"
+
+**Good content (concrete decisions):**
+- "Card-based layout, not timeline"
+- "Retry 3 times on network failure, then fail"
+- "Group by year, then by month"
+- "JSON for programmatic use, table for humans"
+
+**Bad content (too vague):**
+- "Should feel modern and clean"
+- "Good user experience"
+- "Fast and responsive"
+- "Easy to use"
+
+**After creation:**
+- File lives in phase directory: `.planning/phases/XX-name/{phase_num}-CONTEXT.md`
+- `mindforge-phase-researcher` uses decisions to focus investigation AND reads canonical_refs to know WHAT docs to study
+- `mindforge-planner` uses decisions + research to create executable tasks AND reads canonical_refs to verify alignment
+- Downstream agents should NOT need to ask the user again about captured decisions
+
+**CRITICAL — Canonical references:**
+- The `<canonical_refs>` section is MANDATORY. Every CONTEXT.md must have one.
+- If your project has external specs, ADRs, or design docs, list them with full relative paths grouped by topic
+- If ROADMAP.md lists `Canonical refs:` per phase, extract and expand those
+- Inline mentions like "see ADR-019" scattered in decisions are useless to downstream agents — they need full paths and section references in a dedicated section they can find
+- If no external specs exist, say so explicitly — don't silently omit the section
+</guidelines>

package/docs/getting-started.md

@@ -1,4 +1,4 @@
-# MindForge — Getting Started (v11.0.0)
+# MindForge — Getting Started (v11.3.1)
 
 This guide gets you from zero to a working MindForge project in under five minutes.
 

package/docs/troubleshooting.md

@@ -1,4 +1,4 @@
-# MindForge Troubleshooting (v10.0.1)
+# MindForge Troubleshooting (v11.3.1)
 
 This page lists common issues and fast fixes. If you get stuck, start with
 `/mindforge:health`.

package/docs/user-guide.md

@@ -1,4 +1,4 @@
-# MindForge User Guide (v11.0.0)
+# MindForge User Guide (v11.3.1)
 
 This guide gets you from install to productive, with the minimum needed to run MindForge in a real project.
 

package/examples/starter-project/.planning/ARCHITECTURE.md

@@ -0,0 +1,23 @@
+# Architecture
+
+## Overview
+[One paragraph: what the system is and the single most important design decision.]
+
+## Components
+
+| Component | Responsibility | Notes |
+|-----------|----------------|-------|
+| [Name] | [What it owns] | [Key constraint] |
+
+## Data Flow
+[Describe how a request/event moves through the system, e.g. `client -> API -> service -> store`.]
+
+## Key Decisions
+
+### [ADR-01]: [Decision title]
+**Context**: [Why a decision was needed]
+**Decision**: [What was chosen]
+**Consequences**: [Trade-offs accepted]
+
+## Constraints
+- [Technical or business constraint that shapes the design]

package/examples/starter-project/.planning/RELEASE-CHECKLIST.md

@@ -0,0 +1,22 @@
+# Release Checklist
+
+Gate before any release ships. Every box must be checked.
+
+## Quality
+- [ ] All tests pass (`npm test`)
+- [ ] Build succeeds
+- [ ] No known Medium+ security findings
+- [ ] Coverage meets the project threshold
+
+## Versioning
+- [ ] Version bumped in all source-of-truth files
+- [ ] CHANGELOG updated with this release's entry
+- [ ] Git tag created and matches package version
+
+## Verification
+- [ ] Installed artifact verified end-to-end (not just source)
+- [ ] Release notes reviewed
+- [ ] Rollback plan documented
+
+## Sign-off
+- [ ] Owner approved

package/examples/starter-project/.planning/REQUIREMENTS.md

@@ -0,0 +1,31 @@
+# Requirements
+
+**Defined:** [date]
+**Core Value:** [from PROJECT.md]
+
+## v1 Requirements
+
+Each requirement is checkable and maps to a roadmap phase.
+
+### [Category]
+
+- [ ] **[CAT]-01**: [User-centric, testable, atomic requirement]
+- [ ] **[CAT]-02**: [User-centric, testable, atomic requirement]
+
+## v2 Requirements
+
+Acknowledged but deferred — not in the current roadmap.
+
+- **[CAT]-01**: [Requirement description]
+
+## Out of Scope
+
+| Feature | Reason |
+|---------|--------|
+| [Feature] | [Why excluded] |
+
+## Traceability
+
+| Requirement | Phase | Status |
+|-------------|-------|--------|
+| [CAT]-01 | Phase 1 | Pending |

package/examples/starter-project/.planning/ROADMAP.md

@@ -0,0 +1,28 @@
+# Roadmap
+
+## Overview
+[One paragraph describing the journey from first commit to v1.]
+
+## Phases
+
+- [ ] **Phase 1: [Name]** - [One-line description]
+- [ ] **Phase 2: [Name]** - [One-line description]
+- [ ] **Phase 3: [Name]** - [One-line description]
+
+## Phase Details
+
+### Phase 1: [Name]
+**Goal**: [What this phase delivers]
+**Depends on**: Nothing (first phase)
+**Success Criteria** (what must be TRUE):
+  1. [Observable behavior from the user's perspective]
+  2. [Observable behavior from the user's perspective]
+
+Plans:
+- [ ] 01-01: [Brief description of first plan]
+
+## Progress
+
+| Phase | Plans Complete | Status | Completed |
+|-------|----------------|--------|-----------|
+| 1. [Name] | 0/1 | Not started | - |

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "mindforge-cc",
-  "version": "11.3.0",
+  "version": "11.4.0",
   "description": "MindForge \u2014 Sovereign Agentic Intelligence Framework. Sovereign Stability: Production-Hardened Agentic Intelligence (v11)",
   "bin": {
     "mindforge-cc": "bin/install.js",
@@ -9,21 +9,40 @@
   "files": [
     ".agent/CLAUDE.md",
     ".agent/hooks/",
+    ".agent/mindforge/",
+    ".agent/forge/",
+    ".agent/skills/",
+    ".claude/CLAUDE.md",
+    ".claude/commands/",
     ".mindforge/MINDFORGE-SCHEMA.json",
     ".mindforge/MINDFORGE-V2-SCHEMA.json",
     ".mindforge/config.json",
+    ".mindforge/imported-agents.jsonl",
+    ".mindforge/engine/",
     ".mindforge/personas/",
     ".mindforge/skills/",
-    ".mindforge/engine/",
+    ".mindforge/governance/",
+    ".mindforge/integrations/",
+    ".mindforge/intelligence/",
+    ".mindforge/memory/",
+    "!.mindforge/memory/pattern-library.jsonl",
+    ".mindforge/metrics/",
+    "!.mindforge/metrics/token-usage.jsonl",
+    ".mindforge/models/",
+    ".mindforge/org/",
+    ".mindforge/plugins/",
+    ".mindforge/team/",
+    ".mindforge/docs/",
     "bin/",
     "subagents/",
-    ".mindforge/imported-agents.jsonl",
     "docs/getting-started.md",
     "docs/user-guide.md",
     "docs/sdk-reference.md",
     "docs/commands-reference.md",
     "docs/troubleshooting.md",
     "docs/faq.md",
+    "docs/References/",
+    "docs/Templates/",
     "examples/",
     "CHANGELOG.md",
     "LICENSE",

package/subagents/categories/01-core-development/.claude-plugin/plugin.json

@@ -4,12 +4,12 @@
   "description": "Essential development subagents for everyday coding tasks - backend, frontend, fullstack, mobile, and API design",
   "author": {
     "name": "MindForge Team",
-    "url": "https://github.com/sairam0424"
+    "email": "uggesairam0000@gmail.com"
   },
   "repository": "https://github.com/sairam0424/MindForge",
   "license": "MIT",
   "agents": [
-    "./api-designer.md",
+    "./api-designer-cc.md",
     "./backend-developer.md",
     "./design-bridge.md",
     "./electron-pro.md",

package/subagents/categories/01-core-development/api-designer-cc.md

@@ -1,5 +1,5 @@
 ---
-name: api-designer-cc
+name: "api-designer-cc"
 description: "Use this agent when designing new APIs, creating API specifications, or refactoring existing API architecture for scalability and developer experience. Invoke when you need REST/GraphQL endpoint design, OpenAPI documentation, authentication patterns, or API versioning strategies."
 tools: Read, Write, Edit, Bash, Glob, Grep
 model: sonnet

package/subagents/categories/01-core-development/backend-developer.md

@@ -1,5 +1,5 @@
 ---
-name: backend-developer
+name: "backend-developer"
 description: "Use this agent when building server-side APIs, microservices, and backend systems that require robust architecture, scalability planning, and production-ready implementation."
 tools: Read, Write, Edit, Bash, Glob, Grep
 model: sonnet

package/subagents/categories/01-core-development/design-bridge.md

@@ -1,5 +1,5 @@
 ---
-name: design-bridge
+name: "design-bridge"
 description: "Use this agent when you need to translate a DESIGN.md from the <DESIGN_MD_SOURCE> repository into polished Claude Code instructions for building user interfaces that faithfully match the chosen brand. Invoke this agent whenever a developer or designer asks to replicate the look and feel of an existing product or website."
 tools: Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch
 model: opus

package/subagents/categories/01-core-development/electron-pro.md

@@ -1,5 +1,5 @@
 ---
-name: electron-pro
+name: "electron-pro"
 description: "Use this agent when building Electron desktop applications that require native OS integration, cross-platform distribution, security hardening, and performance optimization. Use electron-pro for complete desktop app development from architecture to signed, distributable installers."
 tools: Read, Write, Edit, Bash, Glob, Grep
 model: sonnet

package/subagents/categories/01-core-development/frontend-developer.md

@@ -1,5 +1,5 @@
 ---
-name: frontend-developer
+name: "frontend-developer"
 description: "Use when building complete frontend applications across React, Vue, and Angular frameworks requiring multi-framework expertise and full-stack integration."
 tools: Read, Write, Edit, Bash, Glob, Grep
 model: sonnet

package/subagents/categories/01-core-development/fullstack-developer.md

@@ -1,5 +1,5 @@
 ---
-name: fullstack-developer
+name: "fullstack-developer"
 description: "Use this agent when you need to build complete features spanning database, API, and frontend layers together as a cohesive unit."
 tools: Read, Write, Edit, Bash, Glob, Grep
 model: sonnet

package/subagents/categories/01-core-development/graphql-architect.md

@@ -1,5 +1,5 @@
 ---
-name: graphql-architect
+name: "graphql-architect"
 description: "Use this agent when designing or evolving GraphQL schemas across microservices, implementing federation architectures, or optimizing query performance in distributed graphs."
 tools: Read, Write, Edit, Bash, Glob, Grep
 model: opus

package/subagents/categories/01-core-development/microservices-architect.md

@@ -1,5 +1,5 @@
 ---
-name: microservices-architect
+name: "microservices-architect"
 description: "Use when designing distributed system architecture, decomposing monolithic applications into independent microservices, or establishing communication patterns between services at scale."
 tools: Read, Write, Edit, Bash, Glob, Grep
 model: opus

package/subagents/categories/01-core-development/mobile-developer.md

@@ -1,5 +1,5 @@
 ---
-name: mobile-developer
+name: "mobile-developer"
 description: "Use this agent when building cross-platform mobile applications requiring native performance optimization, platform-specific features, and offline-first architecture. Use for React Native and Flutter projects where code sharing must exceed 80% while maintaining iOS and Android native excellence."
 tools: Read, Write, Edit, Bash, Glob, Grep
 model: sonnet

package/subagents/categories/01-core-development/ui-designer.md

@@ -1,5 +1,5 @@
 ---
-name: ui-designer
+name: "ui-designer"
 description: "Use this agent when designing visual interfaces, creating design systems, building component libraries, or refining user-facing aesthetics requiring expert visual design, interaction patterns, and accessibility considerations."
 tools: Read, Write, Edit, Bash, Glob, Grep
 model: sonnet

package/subagents/categories/01-core-development/websocket-engineer.md

@@ -1,5 +1,5 @@
 ---
-name: websocket-engineer
+name: "websocket-engineer"
 description: "Use this agent when implementing real-time bidirectional communication features using WebSockets, Socket.IO, or similar technologies at scale."
 tools: Read, Write, Edit, Bash, Glob, Grep
 model: sonnet

package/subagents/categories/02-language-specialists/.claude-plugin/plugin.json

@@ -4,7 +4,7 @@
   "description": "Language-specific expert agents with deep framework knowledge - Python, TypeScript, Go, Rust, Java, and more",
   "author": {
     "name": "MindForge Team",
-    "url": "https://github.com/sairam0424"
+    "email": "uggesairam0000@gmail.com"
   },
   "repository": "https://github.com/sairam0424/MindForge",
   "license": "MIT",
@@ -31,7 +31,7 @@
     "./powershell-7-expert.md",
     "./python-pro.md",
     "./rails-expert.md",
-    "./react-specialist.md",
+    "./react-specialist-cc.md",
     "./rust-engineer.md",
     "./spring-boot-engineer.md",
     "./sql-pro.md",

package/subagents/categories/02-language-specialists/angular-architect.md

@@ -1,5 +1,5 @@
 ---
-name: angular-architect
+name: "angular-architect"
 description: "Use when architecting enterprise Angular 15+ applications with complex state management, optimizing RxJS patterns, designing micro-frontend systems, or solving performance and scalability challenges in large codebases."
 tools: Read, Write, Edit, Bash, Glob, Grep
 model: sonnet

package/subagents/categories/02-language-specialists/cpp-pro.md

@@ -1,5 +1,5 @@
 ---
-name: cpp-pro
+name: "cpp-pro"
 description: "Use this agent when building high-performance C++ systems requiring modern C++20/23 features, template metaprogramming, or zero-overhead abstractions for systems programming, embedded systems, or performance-critical applications."
 tools: Read, Write, Edit, Bash, Glob, Grep
 model: sonnet