kodelyth-ecc 2.19.0 → 2.20.0

package/.aider-ecc/commands/lessons.md

@@ -1,92 +0,0 @@
----
-description: Load, view, and save project lessons from tasks/lessons.md. Works on ALL platforms — Claude Code, Windsurf, Cursor, Codex, Antigravity, OpenCode.
----
-
-# /lessons — Project Self-Improvement
-
-Cross-platform command for the Compound Learning System. Works everywhere, with or without hooks.
-
-## Usage
-
-```
-/lessons              → load and show all lessons for this session
-/lessons save         → extract corrections from this session and write to tasks/lessons.md
-/lessons add "<rule>" → add a manual rule immediately
-/lessons clear        → show lessons and ask which to remove
-```
-
-## What This Command Does
-
-### `/lessons` (no args) — Load lessons
-
-1. Check if `tasks/lessons.md` exists in the project root
-2. Read all lesson rules (lines starting with `-`)
-3. Inject them as **PROJECT LESSONS — HARD RULES** for this session
-4. Print a summary of how many rules are active
-5. Apply them immediately — do not wait for another message
-
-If `tasks/lessons.md` does not exist yet, say:
-> "No lessons file found. Corrections you give me this session will build it. Run `/lessons save` at the end of the session to write them."
-
-### `/lessons save` — Capture session corrections
-
-Scan the current conversation for user corrections:
-- Phrases matching: "no don't", "use X instead", "stop doing Y", "wrong approach", "we always", "we never", "I told you", "that's not how we", "use X not Y"
-- Extract each as a plain-language rule
-- Show the extracted rules to the user before writing
-- Ask: "Write these N rules to tasks/lessons.md?"
-- On confirmation: create `tasks/` if needed, append rules with today's date
-
-### `/lessons add "<rule>"` — Add a manual rule
-
-Immediately append the rule to `tasks/lessons.md`:
-```
-## 2026-05-06
-- <rule>
-```
-Confirm: "Rule added. It will be active from the next session (or reload with /lessons)."
-
-### `/lessons clear` — Review and prune
-
-Show all current rules numbered. Ask: "Which numbers to remove? (e.g. 1,3,5 or 'all')"
-Remove selected lines and rewrite the file.
-
-## Format of tasks/lessons.md
-
-```markdown
-# Claude Lessons
-
-Project: **project-name**
-
-Auto-generated by Kodelyth ECC. Edit freely — add, remove, reword. These are YOUR rules.
-
----
-
-## 2026-05-06
-
-- use pnpm not npm
-- never add try/catch without logging the error first
-- we use Zod for validation, not Yup
-
-## 2026-05-10
-
-- component files go in src/components, not src/app
-- always use early returns, never deeply nested if blocks
-```
-
-## Platform Notes
-
-| Platform | Auto-load at start | Auto-capture at end | Manual via /lessons |
-|---|---|---|---|
-| Claude Code | Yes (SessionStart hook) | Yes (Stop hook) | Yes |
-| Windsurf | No | No | Yes — run `/lessons` at start of every session |
-| Cursor | No | No | Yes — run `/lessons` at start of every session |
-| Codex CLI | No | No | Yes — run `/lessons` at start of every session |
-| Antigravity | No | No | Yes — run `/lessons` at start of every session |
-| OpenCode | No | No | Yes — run `/lessons` at start of every session |
-
-**Tip for non-Claude-Code platforms:** Add `/lessons` as your first message in every session on this project. Takes 2 seconds and loads all your hard-earned rules instantly.
-
-## Arguments
-
-$ARGUMENTS

package/.aider-ecc/commands/loop-start.md

@@ -1,37 +0,0 @@
----
-description: Start an autonomous agent loop with quality gates and recovery controls
-argument-hint: "<task>"
----
-
-# Loop Start Command
-
-Start a managed autonomous loop pattern with safety defaults.
-
-## Usage
-
-`/loop-start [pattern] [--mode safe|fast]`
-
-- `pattern`: `sequential`, `continuous-pr`, `rfc-dag`, `infinite`
-- `--mode`:
-  - `safe` (default): strict quality gates and checkpoints
-  - `fast`: reduced gates for speed
-
-## Flow
-
-1. Confirm repository state and branch strategy.
-2. Select loop pattern and model tier strategy.
-3. Enable required hooks/profile for the chosen mode.
-4. Create loop plan and write runbook under `.claude/plans/`.
-5. Print commands to start and monitor the loop.
-
-## Required Safety Checks
-
-- Verify tests pass before first loop iteration.
-- Ensure `ECC_HOOK_PROFILE` is not disabled globally.
-- Ensure loop has explicit stop condition.
-
-## Arguments
-
-$ARGUMENTS:
-- `<pattern>` optional (`sequential|continuous-pr|rfc-dag|infinite`)
-- `--mode safe|fast` optional

package/.aider-ecc/commands/loop-status.md

@@ -1,28 +0,0 @@
----
-description: Show the status of running autonomous agent loops
----
-
-# Loop Status Command
-
-Inspect active loop state, progress, and failure signals.
-
-## Usage
-
-`/loop-status [--watch]`
-
-## What to Report
-
-- active loop pattern
-- current phase and last successful checkpoint
-- failing checks (if any)
-- estimated time/cost drift
-- recommended intervention (continue/pause/stop)
-
-## Watch Mode
-
-When `--watch` is present, refresh status periodically and surface state changes.
-
-## Arguments
-
-$ARGUMENTS:
-- `--watch` optional

package/.aider-ecc/commands/memory-evolve.md

@@ -1,71 +0,0 @@
----
-description: Phase 3.4 self-evolving memory. Convert reuse + routing-miss signals into PR-ready proposals (skill drafts + routing-rule additions). Never auto-applies.
----
-
-# /memory-evolve
-
-Run the self-evolving memory loop. Inspect what ECC has learned from your sessions, generate proposals, accept the ones you want as drafts, reject the rest. **Nothing is ever committed automatically** — accept writes a draft file you review.
-
-## Usage
-
-```
-/memory-evolve                    # default: stats + analyze + list
-/memory-evolve stats              # snapshot of recorded signals
-/memory-evolve analyze            # signals → proposals (idempotent)
-/memory-evolve list               # show all proposals
-/memory-evolve list --status pending
-/memory-evolve show <id>          # full proposed content + evidence
-/memory-evolve accept <id>        # write draft file to disk (NEVER commits)
-/memory-evolve reject <id> --note "covered by existing agent"
-```
-
-## Behavior
-
-1. **stats** prints the current signal snapshot:
-   - reuse: how many memories are tracked, total surfaces, top reused
-   - routing misses: how many substantive prompts had zero memory matches, top token clusters
-2. **analyze** applies thresholds and writes proposals to `~/.kodelythecc/evolve/proposals.jsonl`. Stable IDs — re-running does NOT duplicate.
-3. **list** filters by state. **show** prints the full draft markdown + evidence.
-4. **accept** writes the draft to its target path under `--root` (defaults to package root). Refuses to overwrite without `--overwrite`. Marks the proposal `accepted` with the absolute path.
-5. **reject** marks a proposal rejected with optional note.
-
-## Default thresholds
-
-| Signal | Default threshold | Override flag |
-|---|---|---|
-| Memory reuse count | 3 | `--reuse-min N` |
-| Distinct sessions per memory | 2 | `--reuse-min-sessions N` |
-| Routing-miss cluster total | 3 | `--miss-min N` |
-| Distinct prompts per cluster | 2 | `--miss-min-distinct N` |
-
-## Use cases
-
-- **Promote a recurring memory to a skill.** A memory that's been recalled 5 times across 4 sessions is probably ready to graduate.
-- **Find routing gaps.** Ten substantive prompts about "feature flags" that hit zero memories and (you suspect) no specialist agent → propose a routing entry.
-- **Audit what ECC has learned.** Before tagging a release, see what proposals are pending and decide which to accept.
-- **Reject noisy patterns.** Some clusters look real but cover ground that's already covered by an existing agent. Reject with a note for the audit trail.
-
-## Companion commands
-
-- **`/memory remember`** — manual memory capture. Without captured memories, evolve has nothing to learn from.
-- **`/skill-create`** — alternative path: create a skill from scratch instead of from an evolved memory.
-- **`/devil-mode`** — adversarial review of the accepted draft before commit.
-
-## Hard rules
-
-1. **NEVER commit accepted drafts automatically.** The CLI writes the file. The user reviews, edits, commits.
-2. **NEVER overwrite an existing file** without `--overwrite`. Even on accept.
-3. **Routing-addition diffs ship `TODO-agent`** intentionally so they cannot accidentally route real traffic.
-4. **All recording is fire-and-forget.** Hooks NEVER block on signal write failure.
-5. **Append-only proposal log.** State changes preserve the full audit trail.
-
-## Implementation
-
-Backed by:
-
-- `scripts/evolve/stats.js` — pure record/read of `~/.kodelythecc/evolve/{reuse.json, routing-misses.jsonl}`
-- `scripts/evolve/analyze.js` — pure functions: signals → proposals
-- `scripts/evolve/proposals.js` — append-only proposal log with state transitions
-- `hooks/memory/auto-recall.js` — fire-and-forget signal recording on every UserPromptSubmit
-
-CLI surface: `kodelyth-ecc evolve <stats|analyze|list|show|accept|reject>`. Skill: `self-evolving-memory`. Full reference: `docs/evolve.md`.

package/.aider-ecc/commands/memory.md

@@ -1,62 +0,0 @@
----
-description: Manage local Kodelyth Memory — recall, capture, review, and curate what your AI knows about you
----
-
-# /memory
-
-Local self-learning memory. Everything stays on this machine.
-
-## Subcommands
-
-### `/memory`
-Show storage stats and the 5 most recent memories for this project.
-
-### `/memory recall <query>`
-Search memory for `<query>` using BM25 keyword + tag retrieval. Surfaces the top 5 relevant matches.
-
-Example:
-```
-/memory recall stripe webhook signature
-```
-
-### `/memory remember "<title>"`
-Capture a new memory. The agent will:
-1. Ask for the approach (what worked) and any gotchas
-2. Auto-extract tags and language from the conversation
-3. Show you the proposed memory
-4. Store only after you confirm
-
-### `/memory review-pending`
-Show the queue of candidate memories extracted automatically by the Stop hook from your last session. Confirm each one to store, or skip.
-
-### `/memory forget <id>`
-Mark a memory deleted. It's a soft-delete (the row stays in the log marked `deleted: true`) so you can recover it by editing `~/.kodelythecc/memory/memories.jsonl`.
-
-### `/memory list`
-Show all stored memories — id, date, language, problem, tags.
-
-### `/memory rebuild`
-Rebuild the BM25 index from `memories.jsonl`. Run this if search results look stale or if you've manually edited the log.
-
-### `/memory inject [--query <text>]`
-Print the cache-friendly context block that the SessionStart hook would inject. Useful for debugging what your AI sees about you.
-
-## Implementation
-
-This command delegates to:
-```bash
-node ~/.claude/scripts/memory/cli.js <subcommand> [args]
-```
-
-Or invoke the agent directly:
-```
-use kodelyth-memory
-```
-
-## Storage location
-
-`~/.kodelythecc/memory/` (override with `KODELYTH_MEMORY_DIR` env var)
-
-- `memories.jsonl` — the source of truth
-- `index.json` — BM25 inverted index
-- `pending-review.jsonl` — Stop-hook candidates awaiting confirmation

package/.aider-ecc/commands/model-route.md

@@ -1,31 +0,0 @@
----
-description: Recommend the right model tier (trivial/standard/hard) for the current task
-argument-hint: "<task>"
----
-
-# Model Route Command
-
-Recommend the best model tier for the current task by complexity and budget.
-
-## Usage
-
-`/model-route [task-description] [--budget low|med|high]`
-
-## Routing Heuristic
-
-- `haiku`: deterministic, low-risk mechanical changes
-- `sonnet`: default for implementation and refactors
-- `opus`: architecture, deep review, ambiguous requirements
-
-## Required Output
-
-- recommended model
-- confidence level
-- why this model fits
-- fallback model if first attempt fails
-
-## Arguments
-
-$ARGUMENTS:
-- `[task-description]` optional free-text
-- `--budget low|med|high` optional

package/.aider-ecc/commands/multi-backend.md

@@ -1,163 +0,0 @@
----
-description: Fan out backend implementation across parallel specialist agents
-argument-hint: "<task>"
----
-
-# Backend - Backend-Focused Development
-
-Backend-focused workflow (Research → Ideation → Plan → Execute → Optimize → Review), Codex-led.
-
-## Usage
-
-```bash
-/backend <backend task description>
-```
-
-## Context
-
-- Backend task: $ARGUMENTS
-- Codex-led, Gemini for auxiliary reference
-- Applicable: API design, algorithm implementation, database optimization, business logic
-
-## Your Role
-
-You are the **Backend Orchestrator**, coordinating multi-model collaboration for server-side tasks (Research → Ideation → Plan → Execute → Optimize → Review).
-
-**Collaborative Models**:
-- **Codex** – Backend logic, algorithms (**Backend authority, trustworthy**)
-- **Gemini** – Frontend perspective (**Backend opinions for reference only**)
-- **Claude (self)** – Orchestration, planning, execution, delivery
-
----
-
-## Multi-Model Call Specification
-
-**Call Syntax**:
-
-```
-# New session call
-Bash({
-  command: "~/.claude/bin/codeagent-wrapper {{LITE_MODE_FLAG}}--backend codex - \"$PWD\" <<'EOF'
-ROLE_FILE: <role prompt path>
-<TASK>
-Requirement: <enhanced requirement (or $ARGUMENTS if not enhanced)>
-Context: <project context and analysis from previous phases>
-</TASK>
-OUTPUT: Expected output format
-EOF",
-  run_in_background: false,
-  timeout: 3600000,
-  description: "Brief description"
-})
-
-# Resume session call
-Bash({
-  command: "~/.claude/bin/codeagent-wrapper {{LITE_MODE_FLAG}}--backend codex resume <SESSION_ID> - \"$PWD\" <<'EOF'
-ROLE_FILE: <role prompt path>
-<TASK>
-Requirement: <enhanced requirement (or $ARGUMENTS if not enhanced)>
-Context: <project context and analysis from previous phases>
-</TASK>
-OUTPUT: Expected output format
-EOF",
-  run_in_background: false,
-  timeout: 3600000,
-  description: "Brief description"
-})
-```
-
-**Role Prompts**:
-
-| Phase | Codex |
-|-------|-------|
-| Analysis | `~/.claude/.ccg/prompts/codex/analyzer.md` |
-| Planning | `~/.claude/.ccg/prompts/codex/architect.md` |
-| Review | `~/.claude/.ccg/prompts/codex/reviewer.md` |
-
-**Session Reuse**: Each call returns `SESSION_ID: xxx`, use `resume xxx` for subsequent phases. Save `CODEX_SESSION` in Phase 2, use `resume` in Phases 3 and 5.
-
----
-
-## Communication Guidelines
-
-1. Start responses with mode label `[Mode: X]`, initial is `[Mode: Research]`
-2. Follow strict sequence: `Research → Ideation → Plan → Execute → Optimize → Review`
-3. Use `AskUserQuestion` tool for user interaction when needed (e.g., confirmation/selection/approval)
-
----
-
-## Core Workflow
-
-### Phase 0: Prompt Enhancement (Optional)
-
-`[Mode: Prepare]` - If ace-tool MCP available, call `mcp__ace-tool__enhance_prompt`, **replace original $ARGUMENTS with enhanced result for subsequent Codex calls**. If unavailable, use `$ARGUMENTS` as-is.
-
-### Phase 1: Research
-
-`[Mode: Research]` - Understand requirements and gather context
-
-1. **Code Retrieval** (if ace-tool MCP available): Call `mcp__ace-tool__search_context` to retrieve existing APIs, data models, service architecture. If unavailable, use built-in tools: `Glob` for file discovery, `Grep` for symbol/API search, `Read` for context gathering, `Task` (Explore agent) for deeper exploration.
-2. Requirement completeness score (0-10): >=7 continue, <7 stop and supplement
-
-### Phase 2: Ideation
-
-`[Mode: Ideation]` - Codex-led analysis
-
-**MUST call Codex** (follow call specification above):
-- ROLE_FILE: `~/.claude/.ccg/prompts/codex/analyzer.md`
-- Requirement: Enhanced requirement (or $ARGUMENTS if not enhanced)
-- Context: Project context from Phase 1
-- OUTPUT: Technical feasibility analysis, recommended solutions (at least 2), risk assessment
-
-**Save SESSION_ID** (`CODEX_SESSION`) for subsequent phase reuse.
-
-Output solutions (at least 2), wait for user selection.
-
-### Phase 3: Planning
-
-`[Mode: Plan]` - Codex-led planning
-
-**MUST call Codex** (use `resume <CODEX_SESSION>` to reuse session):
-- ROLE_FILE: `~/.claude/.ccg/prompts/codex/architect.md`
-- Requirement: User's selected solution
-- Context: Analysis results from Phase 2
-- OUTPUT: File structure, function/class design, dependency relationships
-
-Claude synthesizes plan, save to `.claude/plan/task-name.md` after user approval.
-
-### Phase 4: Implementation
-
-`[Mode: Execute]` - Code development
-
-- Strictly follow approved plan
-- Follow existing project code standards
-- Ensure error handling, security, performance optimization
-
-### Phase 5: Optimization
-
-`[Mode: Optimize]` - Codex-led review
-
-**MUST call Codex** (follow call specification above):
-- ROLE_FILE: `~/.claude/.ccg/prompts/codex/reviewer.md`
-- Requirement: Review the following backend code changes
-- Context: git diff or code content
-- OUTPUT: Security, performance, error handling, API compliance issues list
-
-Integrate review feedback, execute optimization after user confirmation.
-
-### Phase 6: Quality Review
-
-`[Mode: Review]` - Final evaluation
-
-- Check completion against plan
-- Run tests to verify functionality
-- Report issues and recommendations
-
----
-
-## Key Rules
-
-1. **Codex backend opinions are trustworthy**
-2. **Gemini backend opinions for reference only**
-3. External models have **zero filesystem write access**
-4. Claude handles all code writes and file operations