@soleri/forge 5.13.1 → 5.14.1

package/dist/lib.d.ts

@@ -12,3 +12,4 @@ export type { AgentConfig, AgentConfigInput, SetupTarget, ScaffoldResult, Scaffo
 export { AgentConfigSchema, SETUP_TARGETS } from './types.js';
 export { generateExtensionsIndex, generateExampleOp } from './templates/extensions.js';
 export { generateClaudeMdTemplate } from './templates/claude-md-template.js';
+export { getEngineRulesContent, getEngineMarker } from './templates/shared-rules.js';

package/dist/lib.js

@@ -11,4 +11,5 @@ export { patchIndexTs, patchClaudeMdContent } from './patching.js';
 export { AgentConfigSchema, SETUP_TARGETS } from './types.js';
 export { generateExtensionsIndex, generateExampleOp } from './templates/extensions.js';
 export { generateClaudeMdTemplate } from './templates/claude-md-template.js';
+export { getEngineRulesContent, getEngineMarker } from './templates/shared-rules.js';
 //# sourceMappingURL=lib.js.map

package/dist/lib.js.map

@@ -1 +1 @@
-{"version":3,"file":"lib.js","sourceRoot":"","sources":["../src/lib.ts"],"names":[],"mappings":"AAAA;;;;;GAKG;AACH,OAAO,EAAE,QAAQ,EAAE,eAAe,EAAE,UAAU,EAAE,MAAM,iBAAiB,CAAC;AACxE,OAAO,EAAE,gBAAgB,EAAE,6BAA6B,EAAE,MAAM,0BAA0B,CAAC;AAC3F,OAAO,EAAE,SAAS,EAAE,MAAM,qBAAqB,CAAC;AAChD,OAAO,EAAE,YAAY,EAAE,oBAAoB,EAAE,MAAM,eAAe,CAAC;AAWnE,OAAO,EAAE,iBAAiB,EAAE,aAAa,EAAE,MAAM,YAAY,CAAC;AAC9D,OAAO,EAAE,uBAAuB,EAAE,iBAAiB,EAAE,MAAM,2BAA2B,CAAC;AACvF,OAAO,EAAE,wBAAwB,EAAE,MAAM,mCAAmC,CAAC"}
+{"version":3,"file":"lib.js","sourceRoot":"","sources":["../src/lib.ts"],"names":[],"mappings":"AAAA;;;;;GAKG;AACH,OAAO,EAAE,QAAQ,EAAE,eAAe,EAAE,UAAU,EAAE,MAAM,iBAAiB,CAAC;AACxE,OAAO,EAAE,gBAAgB,EAAE,6BAA6B,EAAE,MAAM,0BAA0B,CAAC;AAC3F,OAAO,EAAE,SAAS,EAAE,MAAM,qBAAqB,CAAC;AAChD,OAAO,EAAE,YAAY,EAAE,oBAAoB,EAAE,MAAM,eAAe,CAAC;AAWnE,OAAO,EAAE,iBAAiB,EAAE,aAAa,EAAE,MAAM,YAAY,CAAC;AAC9D,OAAO,EAAE,uBAAuB,EAAE,iBAAiB,EAAE,MAAM,2BAA2B,CAAC;AACvF,OAAO,EAAE,wBAAwB,EAAE,MAAM,mCAAmC,CAAC;AAC7E,OAAO,EAAE,qBAAqB,EAAE,eAAe,EAAE,MAAM,6BAA6B,CAAC"}

package/dist/skills/brain-debrief.md

@@ -16,33 +16,43 @@ When the user wants to understand what patterns have proven valuable, what anti-
 ### "What have I learned?" (General debrief)
 
 1. Get the big picture:
+
    ```
    YOUR_AGENT_core op:brain_stats
    ```
+
    Total sessions, patterns captured, quality scores, coverage gaps.
 
 2. Get patterns ranked by proven strength:
+
    ```
    YOUR_AGENT_core op:brain_strengths
    ```
+
    Focus on strength >= 70 and successRate >= 0.7.
 
 3. Check memory landscape:
+
    ```
    YOUR_AGENT_core op:memory_topics
    ```
+
    Shows how knowledge clusters by topic.
 
 4. Check for stale knowledge:
+
    ```
    YOUR_AGENT_core op:vault_age_report
    ```
+
    Find entries that haven't been updated recently — candidates for review.
 
 5. Run a curator health audit:
+
    ```
    YOUR_AGENT_core op:curator_health_audit
    ```
+
    Vault quality score, tag normalization status, duplicate density.
 
 6. Present: top 5 strongest patterns, top 3 recurring anti-patterns, stale entries needing refresh, and coverage gaps.
@@ -50,22 +60,26 @@ When the user wants to understand what patterns have proven valuable, what anti-
 ### "What's working across projects?" (Cross-project intelligence)
 
 1. Get patterns promoted to the global pool:
+
    ```
    YOUR_AGENT_core op:brain_global_patterns
    ```
 
 2. Get recommendations based on project similarity:
+
    ```
    YOUR_AGENT_core op:brain_recommend
      params: { projectName: "<current project>" }
    ```
 
 3. Check linked projects:
+
    ```
    YOUR_AGENT_core op:project_linked_projects
    ```
 
 4. Search across all projects for relevant patterns:
+
    ```
    YOUR_AGENT_core op:memory_cross_project_search
      params: { query: "<topic>", crossProject: true }
@@ -76,28 +90,33 @@ When the user wants to understand what patterns have proven valuable, what anti-
 ### "Am I getting smarter?" (Learning velocity)
 
 1. Recent stats:
+
    ```
    YOUR_AGENT_core op:brain_stats
      params: { since: "<7 days ago>" }
    ```
 
 2. Longer period for comparison:
+
    ```
    YOUR_AGENT_core op:brain_stats
      params: { since: "<30 days ago>" }
    ```
 
 3. Memory stats:
+
    ```
    YOUR_AGENT_core op:memory_stats
    ```
 
 4. Vault analytics:
+
    ```
    YOUR_AGENT_core op:admin_vault_analytics
    ```
 
 5. Search insights — what queries are people running, what's missing:
+
    ```
    YOUR_AGENT_core op:admin_search_insights
    ```
@@ -107,17 +126,21 @@ When the user wants to understand what patterns have proven valuable, what anti-
 ### "Build fresh intelligence" (Rebuild)
 
 1. Run the full pipeline:
+
    ```
    YOUR_AGENT_core op:brain_build_intelligence
    ```
+
    Compute strengths, update global registry, refresh project profiles.
 
 2. Consolidate vault (curator cleanup):
+
    ```
    YOUR_AGENT_core op:curator_consolidate
    ```
 
 3. Show updated metrics:
+
    ```
    YOUR_AGENT_core op:brain_stats
    ```
@@ -127,21 +150,25 @@ When the user wants to understand what patterns have proven valuable, what anti-
 ### "Export what I know" (Portability)
 
 Export brain intelligence:
+
 ```
 YOUR_AGENT_core op:brain_export
 ```
 
 Export memory:
+
 ```
 YOUR_AGENT_core op:memory_export
 ```
 
 Export vault as backup:
+
 ```
 YOUR_AGENT_core op:vault_backup
 ```
 
 These can be imported into another vault:
+
 ```
 YOUR_AGENT_core op:brain_import
 YOUR_AGENT_core op:memory_import
@@ -151,6 +178,7 @@ YOUR_AGENT_core op:vault_import
 ## Presenting Intelligence
 
 Format as a report:
+
 - **Strengths**: Top patterns with strength scores and domains
 - **Risks**: Recurring anti-patterns that keep appearing
 - **Gaps**: Domains with low coverage or stale knowledge
@@ -165,22 +193,22 @@ Debrief is complete when the user's specific question has been answered with dat
 
 ## Agent Tools Reference
 
-| Op | When to Use |
-|----|-------------|
-| `brain_stats` | Aggregate metrics — sessions, patterns, quality |
-| `brain_strengths` | Patterns ranked by proven strength |
-| `brain_global_patterns` | Cross-project promoted patterns |
-| `brain_recommend` | Project-similarity recommendations |
-| `brain_build_intelligence` | Rebuild full intelligence pipeline |
-| `brain_export` / `brain_import` | Portable intelligence transfer |
-| `memory_topics` | Knowledge clusters by topic |
-| `memory_stats` | Memory statistics |
-| `memory_export` / `memory_import` | Memory portability |
-| `memory_cross_project_search` | Search across linked projects |
-| `vault_age_report` | Find stale entries needing refresh |
-| `vault_backup` / `vault_import` | Vault backup and restore |
-| `curator_health_audit` | Vault quality score and status |
-| `curator_consolidate` | Full vault cleanup pipeline |
-| `admin_vault_analytics` | Overall knowledge quality metrics |
-| `admin_search_insights` | Search miss analysis — what's not found |
-| `project_linked_projects` | See connected projects |
+| Op                                | When to Use                                     |
+| --------------------------------- | ----------------------------------------------- |
+| `brain_stats`                     | Aggregate metrics — sessions, patterns, quality |
+| `brain_strengths`                 | Patterns ranked by proven strength              |
+| `brain_global_patterns`           | Cross-project promoted patterns                 |
+| `brain_recommend`                 | Project-similarity recommendations              |
+| `brain_build_intelligence`        | Rebuild full intelligence pipeline              |
+| `brain_export` / `brain_import`   | Portable intelligence transfer                  |
+| `memory_topics`                   | Knowledge clusters by topic                     |
+| `memory_stats`                    | Memory statistics                               |
+| `memory_export` / `memory_import` | Memory portability                              |
+| `memory_cross_project_search`     | Search across linked projects                   |
+| `vault_age_report`                | Find stale entries needing refresh              |
+| `vault_backup` / `vault_import`   | Vault backup and restore                        |
+| `curator_health_audit`            | Vault quality score and status                  |
+| `curator_consolidate`             | Full vault cleanup pipeline                     |
+| `admin_vault_analytics`           | Overall knowledge quality metrics               |
+| `admin_search_insights`           | Search miss analysis — what's not found         |
+| `project_linked_projects`         | See connected projects                          |

package/dist/skills/brainstorming.md

@@ -1,6 +1,6 @@
 ---
 name: brainstorming
-description: "You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation."
+description: 'You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.'
 ---
 
 <!-- Adapted from superpowers (MIT License) -->
@@ -52,12 +52,14 @@ This returns the intent type (BUILD, FIX, VALIDATE, DESIGN, IMPROVE, DELIVER) an
 **BEFORE asking any questions or exploring code**, search for existing knowledge. Follow this order:
 
 ### Vault First
+
 ```
 YOUR_AGENT_core op:search_intelligent
   params: { query: "<the feature or idea the user described>" }
 ```
 
 Look for:
+
 - **Previous designs** — was this discussed or attempted before?
 - **Architectural decisions** — are there constraints from past decisions?
 - **Patterns** — established approaches in this codebase
@@ -84,18 +86,22 @@ YOUR_AGENT_core op:memory_cross_project_search
 ```
 
 ### Web Search Second
+
 If the vault doesn't have prior art, search the web for:
+
 - **Existing libraries/tools** that solve this problem (don't build what exists)
 - **Reference implementations** in similar projects
 - **Best practices** and established patterns for this type of feature
 - **Known pitfalls** that others have documented
 
 ### Present Findings
+
 Present vault + web findings to the user: "Before we design this, here's what I found..." This informs the design conversation and prevents reinventing solutions.
 
 ## The Process
 
 **Understanding the idea:**
+
 - Check out the current project state first (files, docs, recent commits)
 - Ask questions one at a time to refine the idea
 - Prefer multiple choice questions when possible, but open-ended is fine too
@@ -103,6 +109,7 @@ Present vault + web findings to the user: "Before we design this, here's what I
 - Focus on understanding: purpose, constraints, success criteria
 
 **Exploring approaches:**
+
 - Propose 2-3 different approaches with trade-offs
 - Present options conversationally with your recommendation and reasoning
 - Lead with your recommended option and explain why
@@ -110,6 +117,7 @@ Present vault + web findings to the user: "Before we design this, here's what I
 - **Reference web findings** — if an existing library solves this, recommend it over custom code
 
 **Presenting the design:**
+
 - Once you understand what you're building, present the design
 - Scale each section to its complexity
 - Ask after each section whether it looks right so far
@@ -133,10 +141,12 @@ YOUR_AGENT_core op:capture_knowledge
 This ensures future brainstorming sessions can reference what was decided and why.
 
 **Documentation:**
+
 - Write the validated design to `docs/plans/YYYY-MM-DD-<topic>-design.md`
 - Commit the design document to git
 
 **Implementation:**
+
 - Invoke the writing-plans skill to create a detailed implementation plan
 - Do NOT invoke any other skill. writing-plans is the next step.
 
@@ -160,11 +170,11 @@ This ensures future brainstorming sessions can reference what was decided and wh
 
 ## Agent Tools Reference
 
-| Op | When to Use |
-|----|-------------|
-| `route_intent` | Classify the type of work (BUILD, FIX, etc.) |
-| `search_intelligent` | Search vault for prior art |
-| `vault_tags` / `vault_domains` | Browse knowledge landscape |
-| `brain_strengths` | Check proven patterns |
-| `memory_cross_project_search` | Check if other projects solved this |
-| `capture_knowledge` | Persist design decision to vault |
+| Op                             | When to Use                                  |
+| ------------------------------ | -------------------------------------------- |
+| `route_intent`                 | Classify the type of work (BUILD, FIX, etc.) |
+| `search_intelligent`           | Search vault for prior art                   |
+| `vault_tags` / `vault_domains` | Browse knowledge landscape                   |
+| `brain_strengths`              | Check proven patterns                        |
+| `memory_cross_project_search`  | Check if other projects solved this          |
+| `capture_knowledge`            | Persist design decision to vault             |

package/dist/skills/code-patrol.md

@@ -75,13 +75,13 @@ YOUR_AGENT_core op:brain_strengths
 
 With vault patterns loaded, review the code checking for:
 
-| Check | Source | Severity |
-|-------|--------|----------|
-| Violates a critical rule | `search (severity: critical)` | Must fix |
-| Matches a known anti-pattern | `search (type: anti-pattern)` | Must fix |
-| Doesn't follow a proven pattern | `brain_strengths` | Should fix |
-| Breaks project conventions | `project_list_rules` | Should fix |
-| Misses an opportunity to use a pattern | `search_intelligent` | Could improve |
+| Check                                  | Source                        | Severity      |
+| -------------------------------------- | ----------------------------- | ------------- |
+| Violates a critical rule               | `search (severity: critical)` | Must fix      |
+| Matches a known anti-pattern           | `search (type: anti-pattern)` | Must fix      |
+| Doesn't follow a proven pattern        | `brain_strengths`             | Should fix    |
+| Breaks project conventions             | `project_list_rules`          | Should fix    |
+| Misses an opportunity to use a pattern | `search_intelligent`          | Could improve |
 
 ### Step 4: Present the Review
 
@@ -146,6 +146,7 @@ YOUR_AGENT_core op:search_intelligent
 ```
 
 Check system health:
+
 ```
 YOUR_AGENT_core op:admin_health
 ```
@@ -153,6 +154,7 @@ YOUR_AGENT_core op:admin_health
 ## The Magic
 
 This feels like magic because:
+
 1. It's not ESLint — it catches things like "we decided not to use inheritance here" or "this API pattern caused production issues last month"
 2. The rules come from YOUR team's experience, not a generic config file
 3. It gets smarter over time — every captured pattern becomes a new check
@@ -162,15 +164,15 @@ A linter checks syntax. Code patrol checks wisdom.
 
 ## Agent Tools Reference
 
-| Op | When to Use |
-|----|-------------|
-| `route_intent` | Classify the code's domain |
-| `vault_domains` | See which domains are relevant |
-| `search_intelligent` | Find relevant patterns for this code |
-| `search` | Find anti-patterns and critical rules |
-| `project_list_rules` | Project-specific conventions |
-| `get_behavior_rules` | Behavioral rules |
-| `brain_strengths` | Proven patterns to check against |
-| `capture_quick` | Capture new patterns discovered during review |
-| `capture_knowledge` | Capture new conventions |
-| `admin_health` | Post-review health check |
+| Op                   | When to Use                                   |
+| -------------------- | --------------------------------------------- |
+| `route_intent`       | Classify the code's domain                    |
+| `vault_domains`      | See which domains are relevant                |
+| `search_intelligent` | Find relevant patterns for this code          |
+| `search`             | Find anti-patterns and critical rules         |
+| `project_list_rules` | Project-specific conventions                  |
+| `get_behavior_rules` | Behavioral rules                              |
+| `brain_strengths`    | Proven patterns to check against              |
+| `capture_quick`      | Capture new patterns discovered during review |
+| `capture_knowledge`  | Capture new conventions                       |
+| `admin_health`       | Post-review health check                      |

package/dist/skills/context-resume.md

@@ -34,6 +34,7 @@ YOUR_AGENT_core op:plan_list_tasks
 ```
 
 Present:
+
 - Plan objective and current status
 - Which tasks are completed, in progress, or pending
 - What's next to do
@@ -66,6 +67,7 @@ YOUR_AGENT_core op:loop_is_active
 ```
 
 If active:
+
 ```
 YOUR_AGENT_core op:loop_status
 ```
@@ -119,6 +121,7 @@ Format as a concise standup:
 ## The Magic
 
 This feels like magic because the user just says "catch me up" and the agent:
+
 1. Knows what plans are active and where they stand
 2. Remembers what happened last session (even across context compactions)
 3. Shows what knowledge was recently captured
@@ -129,15 +132,15 @@ No other tool does this — the agent has genuine persistent memory.
 
 ## Agent Tools Reference
 
-| Op | When to Use |
-|----|-------------|
-| `plan_stats` | Find active plans |
-| `get_plan` | Load plan details |
+| Op                | When to Use                 |
+| ----------------- | --------------------------- |
+| `plan_stats`      | Find active plans           |
+| `get_plan`        | Load plan details           |
 | `plan_list_tasks` | See task status within plan |
-| `memory_search` | Find session summaries |
-| `memory_list` | Browse recent memories |
-| `vault_recent` | Recently captured knowledge |
-| `loop_is_active` | Check for in-flight loops |
-| `loop_status` | Get loop details |
-| `brain_strengths` | Relevant proven patterns |
-| `admin_health` | System health check |
+| `memory_search`   | Find session summaries      |
+| `memory_list`     | Browse recent memories      |
+| `vault_recent`    | Recently captured knowledge |
+| `loop_is_active`  | Check for in-flight loops   |
+| `loop_status`     | Get loop details            |
+| `brain_strengths` | Relevant proven patterns    |
+| `admin_health`    | System health check         |

package/dist/skills/executing-plans.md

@@ -41,6 +41,7 @@ YOUR_AGENT_core op:plan_stats
 If no tracked plan exists, read the plan file from `docs/plans/`.
 
 Review critically — identify any questions or concerns about the plan.
+
 - If concerns: Raise them with your human partner before starting
 - If no concerns: Create TodoWrite and proceed
 
@@ -56,9 +57,11 @@ YOUR_AGENT_core op:loop_start
 The loop tracks iterations and validates progress automatically.
 
 ### Step 3: Execute Batch
+
 **Default: First 3 tasks**
 
 For each task:
+
 1. Mark as in_progress:
    ```
    YOUR_AGENT_core op:update_task
@@ -79,7 +82,9 @@ YOUR_AGENT_core op:loop_iterate
 ```
 
 ### Step 4: Report
+
 When batch complete:
+
 - Show what was implemented
 - Show verification output
 - Check loop status:
@@ -89,7 +94,9 @@ When batch complete:
 - Say: "Ready for feedback."
 
 ### Step 5: Continue
+
 Based on feedback:
+
 - Apply changes if needed
 - Execute next batch
 - Repeat until complete
@@ -101,11 +108,13 @@ After all tasks complete and verified:
 1. Run final verification (use verification-before-completion skill)
 
 2. Complete the validation loop:
+
    ```
    YOUR_AGENT_core op:loop_complete
    ```
 
 3. Reconcile plan — compare what was planned vs what actually happened:
+
    ```
    YOUR_AGENT_core op:plan_reconcile
      params: {
@@ -116,12 +125,14 @@ After all tasks complete and verified:
    ```
 
 4. Complete plan lifecycle — extract knowledge and archive:
+
    ```
    YOUR_AGENT_core op:plan_complete_lifecycle
      params: { planId: "<id>" }
    ```
 
 5. Archive the plan for historical reference:
+
    ```
    YOUR_AGENT_core op:plan_archive
      params: { planId: "<id>" }
@@ -150,6 +161,7 @@ Don't wait until the end — capture insights as they happen.
 ## When to Stop and Ask for Help
 
 **STOP executing immediately when:**
+
 - Hit a blocker mid-batch (missing dependency, test fails, instruction unclear)
 - Plan has critical gaps preventing starting
 - You don't understand an instruction
@@ -160,12 +172,14 @@ Don't wait until the end — capture insights as they happen.
 ## When to Revisit Earlier Steps
 
 **Return to Review (Step 1) when:**
+
 - Partner updates the plan based on your feedback
 - Fundamental approach needs rethinking
 
 **Don't force through blockers** - stop and ask.
 
 ## Remember
+
 - Review plan critically first
 - Follow plan steps exactly
 - Don't skip verifications
@@ -177,25 +191,26 @@ Don't wait until the end — capture insights as they happen.
 
 ## Agent Tools Reference
 
-| Op | When to Use |
-|----|-------------|
-| `get_plan` | Load tracked plan |
-| `plan_list_tasks` | List all tasks in the plan |
-| `plan_stats` | Plan overview and metrics |
-| `update_task` | Mark tasks in_progress / completed |
-| `loop_start` | Begin validation loop for iterative execution |
-| `loop_iterate` | Track each iteration |
-| `loop_status` | Check loop progress |
-| `loop_complete` | Finish validation loop |
-| `plan_reconcile` | Compare planned vs actual (post-execution) |
-| `plan_complete_lifecycle` | Extract knowledge from execution |
-| `plan_archive` | Archive plan for history |
-| `session_capture` | Save session context |
-| `capture_quick` | Capture mid-execution learnings |
+| Op                        | When to Use                                   |
+| ------------------------- | --------------------------------------------- |
+| `get_plan`                | Load tracked plan                             |
+| `plan_list_tasks`         | List all tasks in the plan                    |
+| `plan_stats`              | Plan overview and metrics                     |
+| `update_task`             | Mark tasks in_progress / completed            |
+| `loop_start`              | Begin validation loop for iterative execution |
+| `loop_iterate`            | Track each iteration                          |
+| `loop_status`             | Check loop progress                           |
+| `loop_complete`           | Finish validation loop                        |
+| `plan_reconcile`          | Compare planned vs actual (post-execution)    |
+| `plan_complete_lifecycle` | Extract knowledge from execution              |
+| `plan_archive`            | Archive plan for history                      |
+| `session_capture`         | Save session context                          |
+| `capture_quick`           | Capture mid-execution learnings               |
 
 ## Integration
 
 **Required workflow skills:**
+
 - writing-plans — Creates the plan this skill executes
 - verification-before-completion — Verify work before claiming completion
 - test-driven-development — Follow TDD for each implementation step

package/dist/skills/fix-and-learn.md

@@ -66,6 +66,7 @@ If vault returns a match with high confidence — **use it**. Don't re-investiga
 ### Step 3: Search the Web
 
 If the vault has no answer, search for existing solutions before investigating from scratch:
+
 - Known issues in the library/framework
 - Stack Overflow answers for the exact error
 - GitHub issues on relevant repos
@@ -85,6 +86,7 @@ YOUR_AGENT_core op:loop_start
 ### Step 5: Diagnose and Fix
 
 Only if Steps 2-3 didn't produce a solution, apply the systematic debugging approach (use systematic-debugging skill):
+
 1. Reproduce the issue
 2. Isolate the root cause
 3. **Plan the fix before writing code** — even a one-line mental plan
@@ -123,6 +125,7 @@ YOUR_AGENT_core op:capture_knowledge
 ```
 
 For quick captures:
+
 ```
 YOUR_AGENT_core op:capture_quick
   params: { title: "<bug>", description: "<root cause and fix>" }
@@ -148,17 +151,17 @@ Fix is complete when: the bug is resolved, tests pass (Step 6), and the root cau
 
 ## Agent Tools Reference
 
-| Op | When to Use |
-|----|-------------|
-| `route_intent` | Classify as FIX intent |
-| `search_intelligent` | Check vault for known bugs |
-| `memory_search` | Search across session memories |
-| `memory_topics` | See if bugs cluster in an area |
-| `memory_stats` | Understand debugging landscape |
-| `loop_start` | Begin iterative fix cycle |
-| `loop_iterate` | Track each fix attempt |
-| `loop_complete` | Finish fix cycle |
-| `capture_knowledge` | Full anti-pattern capture |
-| `capture_quick` | Fast capture |
-| `curator_detect_duplicates` | Prevent redundant entries |
-| `admin_health` | Verify system health |
+| Op                          | When to Use                    |
+| --------------------------- | ------------------------------ |
+| `route_intent`              | Classify as FIX intent         |
+| `search_intelligent`        | Check vault for known bugs     |
+| `memory_search`             | Search across session memories |
+| `memory_topics`             | See if bugs cluster in an area |
+| `memory_stats`              | Understand debugging landscape |
+| `loop_start`                | Begin iterative fix cycle      |
+| `loop_iterate`              | Track each fix attempt         |
+| `loop_complete`             | Finish fix cycle               |
+| `capture_knowledge`         | Full anti-pattern capture      |
+| `capture_quick`             | Fast capture                   |
+| `curator_detect_duplicates` | Prevent redundant entries      |
+| `admin_health`              | Verify system health           |