npm - mindforge-cc - Versions diffs - 8.2.0 → 10.0.0 - Mend

mindforge-cc 8.2.0 → 10.0.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.

Files changed (1667) hide show

package/docs/Templates/Execution/STATE.md DELETED Viewed

@@ -1,176 +0,0 @@
-# State Template
-Template for `.planning/STATE.md` — the project's living memory.
----
-## File Template
-```markdown
-# Project State
-## Project Reference
-See: .planning/PROJECT.md (updated [date])
-**Core value:** [One-liner from PROJECT.md Core Value section]
-**Current focus:** [Current phase name]
-## Current Position
-Phase: [X] of [Y] ([Phase name])
-Plan: [A] of [B] in current phase
-Status: [Ready to plan / Planning / Ready to execute / In progress / Phase complete]
-Last activity: [YYYY-MM-DD] — [What happened]
-Progress: [░░░░░░░░░░] 0%
-## Performance Metrics
-**Velocity:**
-- Total plans completed: [N]
-- Average duration: [X] min
-- Total execution time: [X.X] hours
-**By Phase:**
-| Phase | Plans | Total | Avg/Plan |
-|-------|-------|-------|----------|
-| - | - | - | - |
-**Recent Trend:**
-- Last 5 plans: [durations]
-- Trend: [Improving / Stable / Degrading]
-*Updated after each plan completion*
-## Accumulated Context
-### Decisions
-Decisions are logged in PROJECT.md Key Decisions table.
-Recent decisions affecting current work:
-- [Phase X]: [Decision summary]
-- [Phase Y]: [Decision summary]
-### Pending Todos
-[From .planning/todos/pending/ — ideas captured during sessions]
-None yet.
-### Blockers/Concerns
-[Issues that affect future work]
-None yet.
-## Session Continuity
-Last session: [YYYY-MM-DD HH:MM]
-Stopped at: [Description of last completed action]
-Resume file: [Path to .continue-here*.md if exists, otherwise "None"]
-```
-<purpose>
-STATE.md is the project's short-term memory spanning all phases and sessions.
-**Problem it solves:** Information is captured in summaries, issues, and decisions but not systematically consumed. Sessions start without context.
-**Solution:** A single, small file that's:
-- Read first in every workflow
-- Updated after every significant action
-- Contains digest of accumulated context
-- Enables instant session restoration
-</purpose>
-<lifecycle>
-**Creation:** After ROADMAP.md is created (during init)
-- Reference PROJECT.md (read it for current context)
-- Initialize empty accumulated context sections
-- Set position to "Phase 1 ready to plan"
-**Reading:** First step of every workflow
-- progress: Present status to user
-- plan: Inform planning decisions
-- execute: Know current position
-- transition: Know what's complete
-**Writing:** After every significant action
-- execute: After SUMMARY.md created
-  - Update position (phase, plan, status)
-  - Note new decisions (detail in PROJECT.md)
-  - Add blockers/concerns
-- transition: After phase marked complete
-  - Update progress bar
-  - Clear resolved blockers
-  - Refresh Project Reference date
-</lifecycle>
-<sections>
-### Project Reference
-Points to PROJECT.md for full context. Includes:
-- Core value (the ONE thing that matters)
-- Current focus (which phase)
-- Last update date (triggers re-read if stale)
-the agent reads PROJECT.md directly for requirements, constraints, and decisions.
-### Current Position
-Where we are right now:
-- Phase X of Y — which phase
-- Plan A of B — which plan within phase
-- Status — current state
-- Last activity — what happened most recently
-- Progress bar — visual indicator of overall completion
-Progress calculation: (completed plans) / (total plans across all phases) × 100%
-### Performance Metrics
-Track velocity to understand execution patterns:
-- Total plans completed
-- Average duration per plan
-- Per-phase breakdown
-- Recent trend (improving/stable/degrading)
-Updated after each plan completion.
-### Accumulated Context
-**Decisions:** Reference to PROJECT.md Key Decisions table, plus recent decisions summary for quick access. Full decision log lives in PROJECT.md.
-**Pending Todos:** Ideas captured via /mindforge-add-todo
-- Count of pending todos
-- Reference to .planning/todos/pending/
-- Brief list if few, count if many (e.g., "5 pending todos — see /mindforge-check-todos")
-**Blockers/Concerns:** From "Next Phase Readiness" sections
-- Issues that affect future work
-- Prefix with originating phase
-- Cleared when addressed
-### Session Continuity
-Enables instant resumption:
-- When was last session
-- What was last completed
-- Is there a .continue-here file to resume from
-</sections>
-<size_constraint>
-Keep STATE.md under 100 lines.
-It's a DIGEST, not an archive. If accumulated context grows too large:
-- Keep only 3-5 recent decisions in summary (full log in PROJECT.md)
-- Keep only active blockers, remove resolved ones
-The goal is "read once, know where we are" — if it's too long, that fails.
-</size_constraint>

package/docs/Templates/Execution/SUMMARY-COMPLEX.md DELETED Viewed

@@ -1,59 +0,0 @@
----
-phase: XX-name
-plan: YY
-subsystem: [primary category]
-tags: [searchable tech]
-requires:
-  - phase: [prior phase]
-    provides: [what that phase built]
-provides:
-  - [bullet list of what was built/delivered]
-affects: [list of phase names or keywords]
-tech-stack:
-  added: [libraries/tools]
-  patterns: [architectural/code patterns]
-key-files:
-  created: [important files created]
-  modified: [important files modified]
-key-decisions:
-  - "Decision 1"
-patterns-established:
-  - "Pattern 1: description"
-duration: Xmin
-completed: YYYY-MM-DD
----
-# Phase [X]: [Name] Summary (Complex)
-**[Substantive one-liner describing outcome]**
-## Performance
-- **Duration:** [time]
-- **Tasks:** [count completed]
-- **Files modified:** [count]
-## Accomplishments
-- [Key outcome 1]
-- [Key outcome 2]
-## Task Commits
-1. **Task 1: [task name]** - `hash`
-2. **Task 2: [task name]** - `hash`
-3. **Task 3: [task name]** - `hash`
-## Files Created/Modified
-- `path/to/file.ts` - What it does
-- `path/to/another.ts` - What it does
-## Decisions Made
-[Key decisions with brief rationale]
-## Deviations from Plan (Auto-fixed)
-[Detailed auto-fix records per MindForge deviation rules]
-## Issues Encountered
-[Problems during planned work and resolutions]
-## Next Phase Readiness
-[What's ready for next phase]
-[Blockers or concerns]

package/docs/Templates/Execution/SUMMARY-MINIMAL.md DELETED Viewed

@@ -1,41 +0,0 @@
----
-phase: XX-name
-plan: YY
-subsystem: [primary category]
-tags: [searchable tech]
-provides:
-  - [bullet list of what was built/delivered]
-affects: [list of phase names or keywords]
-tech-stack:
-  added: [libraries/tools]
-  patterns: [architectural/code patterns]
-key-files:
-  created: [important files created]
-  modified: [important files modified]
-key-decisions: []
-duration: Xmin
-completed: YYYY-MM-DD
----
-# Phase [X]: [Name] Summary (Minimal)
-**[Substantive one-liner describing outcome]**
-## Performance
-- **Duration:** [time]
-- **Tasks:** [count]
-- **Files modified:** [count]
-## Accomplishments
-- [Most important outcome]
-- [Second key accomplishment]
-## Task Commits
-1. **Task 1: [task name]** - `hash`
-2. **Task 2: [task name]** - `hash`
-## Files Created/Modified
-- `path/to/file.ts` - What it does
-## Next Phase Readiness
-[Ready for next phase]

package/docs/Templates/Execution/SUMMARY-STANDARD.md DELETED Viewed

@@ -1,48 +0,0 @@
----
-phase: XX-name
-plan: YY
-subsystem: [primary category]
-tags: [searchable tech]
-provides:
-  - [bullet list of what was built/delivered]
-affects: [list of phase names or keywords]
-tech-stack:
-  added: [libraries/tools]
-  patterns: [architectural/code patterns]
-key-files:
-  created: [important files created]
-  modified: [important files modified]
-key-decisions:
-  - "Decision 1"
-duration: Xmin
-completed: YYYY-MM-DD
----
-# Phase [X]: [Name] Summary
-**[Substantive one-liner describing outcome]**
-## Performance
-- **Duration:** [time]
-- **Tasks:** [count completed]
-- **Files modified:** [count]
-## Accomplishments
-- [Key outcome 1]
-- [Key outcome 2]
-## Task Commits
-1. **Task 1: [task name]** - `hash`
-2. **Task 2: [task name]** - `hash`
-3. **Task 3: [task name]** - `hash`
-## Files Created/Modified
-- `path/to/file.ts` - What it does
-- `path/to/another.ts` - What it does
-## Decisions & Deviations
-[Key decisions or "None - followed plan as specified"]
-[Minor deviations if any, or "None"]
-## Next Phase Readiness
-[What's ready for next phase]

package/docs/Templates/Execution/SUMMARY.md DELETED Viewed

@@ -1,248 +0,0 @@
-# Summary Template
-Template for `.planning/phases/XX-name/{phase}-{plan}-SUMMARY.md` - phase completion documentation.
----
-## File Template
-```markdown
----
-phase: XX-name
-plan: YY
-subsystem: [primary category: auth, payments, ui, api, database, infra, testing, etc.]
-tags: [searchable tech: jwt, stripe, react, postgres, prisma]
-# Dependency graph
-requires:
-  - phase: [prior phase this depends on]
-    provides: [what that phase built that this uses]
-provides:
-  - [bullet list of what this phase built/delivered]
-affects: [list of phase names or keywords that will need this context]
-# Tech tracking
-tech-stack:
-  added: [libraries/tools added in this phase]
-  patterns: [architectural/code patterns established]
-key-files:
-  created: [important files created]
-  modified: [important files modified]
-key-decisions:
-  - "Decision 1"
-  - "Decision 2"
-patterns-established:
-  - "Pattern 1: description"
-  - "Pattern 2: description"
-requirements-completed: []  # REQUIRED — Copy ALL requirement IDs from this plan's `requirements` frontmatter field.
-# Metrics
-duration: Xmin
-completed: YYYY-MM-DD
----
-# Phase [X]: [Name] Summary
-**[Substantive one-liner describing outcome - NOT "phase complete" or "implementation finished"]**
-## Performance
-- **Duration:** [time] (e.g., 23 min, 1h 15m)
-- **Started:** [ISO timestamp]
-- **Completed:** [ISO timestamp]
-- **Tasks:** [count completed]
-- **Files modified:** [count]
-## Accomplishments
-- [Most important outcome]
-- [Second key accomplishment]
-- [Third if applicable]
-## Task Commits
-Each task was committed atomically:
-1. **Task 1: [task name]** - `abc123f` (feat/fix/test/refactor)
-2. **Task 2: [task name]** - `def456g` (feat/fix/test/refactor)
-3. **Task 3: [task name]** - `hij789k` (feat/fix/test/refactor)
-**Plan metadata:** `lmn012o` (docs: complete plan)
-_Note: TDD tasks may have multiple commits (test → feat → refactor)_
-## Files Created/Modified
-- `path/to/file.ts` - What it does
-- `path/to/another.ts` - What it does
-## Decisions Made
-[Key decisions with brief rationale, or "None - followed plan as specified"]
-## Deviations from Plan
-[If no deviations: "None - plan executed exactly as written"]
-[If deviations occurred:]
-### Auto-fixed Issues
-**1. [Rule X - Category] Brief description**
-- **Found during:** Task [N] ([task name])
-- **Issue:** [What was wrong]
-- **Fix:** [What was done]
-- **Files modified:** [file paths]
-- **Verification:** [How it was verified]
-- **Committed in:** [hash] (part of task commit)
-[... repeat for each auto-fix ...]
----
-**Total deviations:** [N] auto-fixed ([breakdown by rule])
-**Impact on plan:** [Brief assessment - e.g., "All auto-fixes necessary for correctness/security. No scope creep."]
-## Issues Encountered
-[Problems and how they were resolved, or "None"]
-[Note: "Deviations from Plan" documents unplanned work that was handled automatically via deviation rules. "Issues Encountered" documents problems during planned work that required problem-solving.]
-## User Setup Required
-[If USER-SETUP.md was generated:]
-**External services require manual configuration.** See [{phase}-USER-SETUP.md](./{phase}-USER-SETUP.md) for:
-- Environment variables to add
-- Dashboard configuration steps
-- Verification commands
-[If no USER-SETUP.md:]
-None - no external service configuration required.
-## Next Phase Readiness
-[What's ready for next phase]
-[Any blockers or concerns]
----
-*Phase: XX-name*
-*Completed: [date]*
-```
-<frontmatter_guidance>
-**Purpose:** Enable automatic context assembly via dependency graph. Frontmatter makes summary metadata machine-readable so plan-phase can scan all summaries quickly and select relevant ones based on dependencies.
-**Fast scanning:** Frontmatter is first ~25 lines, cheap to scan across all summaries without reading full content.
-**Dependency graph:** `requires`/`provides`/`affects` create explicit links between phases, enabling transitive closure for context selection.
-**Subsystem:** Primary categorization (auth, payments, ui, api, database, infra, testing) for detecting related phases.
-**Tags:** Searchable technical keywords (libraries, frameworks, tools) for tech stack awareness.
-**Key-files:** Important files for @context references in PLAN.md.
-**Patterns:** Established conventions future phases should maintain.
-**Population:** Frontmatter is populated during summary creation in execute-plan.md. See `<step name="create_summary">` for field-by-field guidance.
-</frontmatter_guidance>
-<one_liner_rules>
-The one-liner MUST be substantive:
-**Good:**
-- "JWT auth with refresh rotation using jose library"
-- "Prisma schema with User, Session, and Product models"
-- "Dashboard with real-time metrics via Server-Sent Events"
-**Bad:**
-- "Phase complete"
-- "Authentication implemented"
-- "Foundation finished"
-- "All tasks done"
-The one-liner should tell someone what actually shipped.
-</one_liner_rules>
-<example>
-```markdown
-# Phase 1: Foundation Summary
-**JWT auth with refresh rotation using jose library, Prisma User model, and protected API middleware**
-## Performance
-- **Duration:** 28 min
-- **Started:** 2025-01-15T14:22:10Z
-- **Completed:** 2025-01-15T14:50:33Z
-- **Tasks:** 5
-- **Files modified:** 8
-## Accomplishments
-- User model with email/password auth
-- Login/logout endpoints with httpOnly JWT cookies
-- Protected route middleware checking token validity
-- Refresh token rotation on each request
-## Files Created/Modified
-- `prisma/schema.prisma` - User and Session models
-- `src/app/api/auth/login/route.ts` - Login endpoint
-- `src/app/api/auth/logout/route.ts` - Logout endpoint
-- `src/middleware.ts` - Protected route checks
-- `src/lib/auth.ts` - JWT helpers using jose
-## Decisions Made
-- Used jose instead of jsonwebtoken (ESM-native, Edge-compatible)
-- 15-min access tokens with 7-day refresh tokens
-- Storing refresh tokens in database for revocation capability
-## Deviations from Plan
-### Auto-fixed Issues
-**1. [Rule 2 - Missing Critical] Added password hashing with bcrypt**
-- **Found during:** Task 2 (Login endpoint implementation)
-- **Issue:** Plan didn't specify password hashing - storing plaintext would be critical security flaw
-- **Fix:** Added bcrypt hashing on registration, comparison on login with salt rounds 10
-- **Files modified:** src/app/api/auth/login/route.ts, src/lib/auth.ts
-- **Verification:** Password hash test passes, plaintext never stored
-- **Committed in:** abc123f (Task 2 commit)
-**2. [Rule 3 - Blocking] Installed missing jose dependency**
-- **Found during:** Task 4 (JWT token generation)
-- **Issue:** jose package not in package.json, import failing
-- **Fix:** Ran `npm install jose`
-- **Files modified:** package.json, package-lock.json
-- **Verification:** Import succeeds, build passes
-- **Committed in:** def456g (Task 4 commit)
----
-**Total deviations:** 2 auto-fixed (1 missing critical, 1 blocking)
-**Impact on plan:** Both auto-fixes essential for security and functionality. No scope creep.
-## Issues Encountered
-- jsonwebtoken CommonJS import failed in Edge runtime - switched to jose (planned library change, worked as expected)
-## Next Phase Readiness
-- Auth foundation complete, ready for feature development
-- User registration endpoint needed before public launch
----
-*Phase: 01-foundation*
-*Completed: 2025-01-15*
-```
-</example>
-<guidelines>
-**Frontmatter:** MANDATORY - complete all fields. Enables automatic context assembly for future planning.
-**One-liner:** Must be substantive. "JWT auth with refresh rotation using jose library" not "Authentication implemented".
-**Decisions section:**
-- Key decisions made during execution with rationale
-- Extracted to STATE.md accumulated context
-- Use "None - followed plan as specified" if no deviations
-**After creation:** STATE.md updated with position, decisions, issues.
-</guidelines>

package/docs/Templates/Profile/DEV-PREFERENCES.md DELETED Viewed

@@ -1,21 +0,0 @@
----
-description: Load developer preferences into this session
----
-# Developer Preferences
-> Generated by MindForge on {{generated_at}} from {{data_source}}.
-> Run `/mindforge-profile-user --refresh` to regenerate.
-## Behavioral Directives
-Follow these directives when working with this developer. Higher confidence
-directives should be applied directly. Lower confidence directives should be
-tried with hedging ("Based on your profile, I'll try X -- let me know if
-that's off").
-{{behavioral_directives}}
-## Stack Preferences
-{{stack_preferences}}