@namch/agent-assistant 1.0.2 → 1.0.3

package/commands/code/hard.md

@@ -213,6 +213,65 @@ One phase at a time, each phase independent: Phase 1 → then Phase 2 → … in
 
 ---
 
+## 🛡️ VERIFICATION CHECKPOINT — Context Optimization
+
+> **PURPOSE**: Prevent "context rot" by clearing noisy planning history before implementation.
+> 
+> Long-running planning sessions fill context with noise that degrades code generation quality.
+> This checkpoint acts as a "firewall" between Planning and Implementation phases.
+
+### ⚡ OPTIONS (Present to User)
+
+```markdown
+## 🛡️ Context Optimization Checkpoint
+
+**Planning Complete** — Plan file created at: `./reports/plans/PLAN-{task}.md`
+
+**Choose how to proceed with implementation:**
+
+| Option | Action | Description |
+|--------|--------|-------------|
+| **1. 🚀 Clear context & Auto-Implement** | `RECOMMENDED` | Fresh start: Reload Plan file, ignore chat history, begin implementation immediately |
+| **2. ⏸️ Clear context & Manual** | `SAFE` | Clear context, reload Plan, pause for your command before coding |
+| **3. ⚠️ Continue (No Clear)** | `RISKY` | Proceed with full history attached (may cause hallucination) |
+
+⏳ Awaiting selection...
+```
+
+### 🔄 EXECUTION BEHAVIOR
+
+```yaml
+option_1_clear_auto_implement:
+  behavior: "RECOMMENDED - Simulate fresh start"
+  steps:
+    1. ACKNOWLEDGE: "🚀 Executing Clear context & Auto-Implement..."
+    2. CONTEXT_DIRECTIVE: |
+       ⛔ IGNORE all previous chat messages and reasoning chains.
+       ✅ RELOAD: `./reports/plans/PLAN-{task}.md` as SOLE SOURCE OF TRUTH.
+       ✅ PROCEED: Begin Phase 4 (Implementation) immediately.
+    3. LOAD: Read Plan file completely
+    4. EXECUTE: Start Implementation phase with fresh context mindset
+
+option_2_clear_manual:
+  behavior: "Clear and wait for explicit command"
+  steps:
+    1. ACKNOWLEDGE: "⏸️ Context cleared. Plan reloaded."
+    2. CONTEXT_DIRECTIVE: |
+       ⛔ IGNORE all previous chat messages and reasoning chains.
+       ✅ RELOAD: `./reports/plans/PLAN-{task}.md` as SOLE SOURCE OF TRUTH.
+    3. OUTPUT: "Ready for implementation. Type `/continue` or give specific instructions."
+    4. WAIT: For user command before proceeding
+
+option_3_continue_no_clear:
+  behavior: "Proceed with caution - context rot risk"
+  steps:
+    1. WARN: "⚠️ Continuing with full history. Higher hallucination risk."
+    2. PROCEED: Continue to Phase 4 with existing context
+    3. MONITOR: Watch for signs of context confusion
+```
+
+---
+
 ## 🎭 Phase 4: IMPLEMENTATION
 
 | Attribute | Value                               |

package/commands/code.md

@@ -16,9 +16,10 @@ execution-mode: router
 ## 🛑 PRE-FLIGHT (DO FIRST — BLOCKS EXECUTION)
 
 **LOAD now** (in order; path `./rules/` or `~/.{TOOL}/skills/agent-assistant/rules/`):
-1. ORCHESTRATION-LAWS.md  
-2. ADAPTIVE-EXECUTION.md  
-3. EXECUTION-PROTOCOL.md  
+
+1. ORCHESTRATION-LAWS.md
+2. ADAPTIVE-EXECUTION.md
+3. EXECUTION-PROTOCOL.md
 
 **⛔ Do not run any workflow phase until all are loaded.** Follow **all** rules in those files. Then run this file's ROUTING LOGIC, LOAD the chosen variant workflow, and execute it.
 
@@ -33,6 +34,9 @@ IF task is simple (clear requirements, single file):
 IF task is complex (multi-file, research needed):
   → Route to /code:hard
 
+IF task is complex AND context optimization is critical:
+  → Route to /code:focus
+
 IF unsure:
   → Default to /code:fast (escalate if needed)
 ```
@@ -41,10 +45,11 @@ IF unsure:
 
 ## AVAILABLE ROUTES
 
-| Route        | When to Use                              |
-| ------------ | ---------------------------------------- |
-| `/code:fast` | Quick implementation, clear requirements |
-| `/code:hard` | Complex features, multi-file changes     |
+| Route         | When to Use                                             |
+| ------------- | ------------------------------------------------------- |
+| `/code:fast`  | Quick implementation, clear requirements                |
+| `/code:hard`  | Complex features, multi-file changes                    |
+| `/code:focus` | Complex features with **enforced context optimization** |
 
 ---
 
@@ -59,6 +64,7 @@ IF unsure:
 
 1. ⚡ **Fast** → `/code:fast` — Quick implementation
 2. ⚡⚡⚡ **Hard** → `/code:hard` — Full development cycle
+3. 🎯 **Focus** → `/code:focus` — Full cycle with **automatic context clearing** (prevents hallucination)
 
 ⏳ Awaiting selection...
 ```

package/commands/cook/focus.md

@@ -0,0 +1,262 @@
+---
+description: 🔒 Focused Feature — Complete development with enforced context optimization
+version: "1.0"
+category: engineering
+execution-mode: execute
+---
+
+# /cook:focus — Focus Feature Development
+
+> **MISSION**: Full feature development with **enforced context optimization**.
+>
+> This variant automatically clears context before implementation—no user prompt required.
+> Use when you want guaranteed clean implementation without context rot risk.
+
+<feature>$ARGUMENTS</feature>
+
+---
+
+## 🛑 PRE-FLIGHT (DO FIRST — BLOCKS PHASE 1)
+
+**LOAD now** (in order; path `./rules/` or `~/.{TOOL}/skills/agent-assistant/rules/`):
+
+1. ORCHESTRATION-LAWS.md
+2. ADAPTIVE-EXECUTION.md
+3. EXECUTION-PROTOCOL.md
+
+**⛔ Do not run Phase 1 until all are loaded.** Follow **all** rules in those files; they override any conflicting instructions in this file.
+
+---
+
+## 🔀 TIERED EXECUTION
+
+> Reference: `{RULES_PATH}/ADAPTIVE-EXECUTION.md`
+
+| Tier       | When                          | Action                       |
+| ---------- | ----------------------------- | ---------------------------- |
+| **TIER 1** | runSubagent/Agent Tool EXISTS | Invoke sub-agent (MANDATORY) |
+| **TIER 2** | Tool MISSING or SYSTEM error  | EMBODY agent file (FALLBACK) |
+
+**❌ Anti-Lazy**: Never use TIER 2 when TIER 1 tool available.
+
+---
+
+## 📁 DELIVERABLE FILES
+
+| Agent        | Output                                          |
+| ------------ | ----------------------------------------------- |
+| brainstormer | `./reports/brainstorms/BRAINSTORM-{feature}.md` |
+| researcher   | `./reports/researchers/RESEARCH-{feature}.md`   |
+| scouter      | `./reports/scouts/SCOUT-{feature}.md`           |
+| designer     | `./reports/designs/DESIGN-{feature}.md`         |
+| planner      | `./reports/plans/PLAN-{feature}.md`             |
+
+All files in `./reports/` → English only.
+
+---
+
+## 🔗 PHASE DEPENDENCIES
+
+| Phase              | Requires               | Blocking    |
+| ------------------ | ---------------------- | ----------- |
+| P1: Brainstorm     | User request           | No          |
+| P2: Research       | User request           | No          |
+| P3: Scout          | User request           | No          |
+| P3.5: DB Design    | Data requirements      | Conditional |
+| P4: Design         | Scout findings         | Conditional |
+| P5: Planning       | RESEARCH + SCOUT files | **YES**     |
+| P5.5: Context Gate | **PLAN file**          | **AUTO**    |
+| P6: Implementation | **PLAN file**          | **YES**     |
+| P7: Testing        | PLAN + Code            | **YES**     |
+| P8: Review         | PLAN + Code + Tests    | **YES**     |
+
+**⛔ Blocking**: If input missing → STOP → Create it first → Resume
+
+---
+
+## ⛔ INCREMENTAL EXECUTION (MANDATORY)
+
+One phase at a time, each phase independent: Phase 1 → then Phase 2 → … in one reply. No batching (load only what each phase needs). **Within each phase:** when doing a part, output it in format so user sees what's happening (announce before doing). Format: rules/EXECUTION-PROTOCOL.md § Phase output structure.
+
+---
+
+## 🎭 Phase 1: REQUIREMENTS CLARIFICATION
+
+| Agent | `brainstormer`                                                       |
+| ----- | -------------------------------------------------------------------- |
+| Goal  | Full requirements discovery                                          |
+| Exit  | Requirements clear, constraints identified, success criteria defined |
+
+---
+
+## 🎭 Phase 2: RESEARCH
+
+| Agent | `researcher`                                                               |
+| ----- | -------------------------------------------------------------------------- |
+| Goal  | Research best practices and patterns                                       |
+| Exit  | Patterns researched, best practices identified, recommendations documented |
+
+---
+
+## 🎭 Phase 3: CODEBASE ANALYSIS
+
+| Agent | `scouter`                                                               |
+| ----- | ----------------------------------------------------------------------- |
+| Goal  | Map architecture and integration points                                 |
+| Exit  | Architecture understood, integration points mapped, patterns documented |
+
+---
+
+## 🎭 Phase 3.5: DATABASE DESIGN (IF DATA CHANGES)
+
+| Agent   | `database-architect`                                        |
+| ------- | ----------------------------------------------------------- |
+| Trigger | Feature involves database changes/migrations                |
+| Goal    | Schema design and data modeling                             |
+| Exit    | Schema designed, migrations planned, query patterns defined |
+
+---
+
+## 🎭 Phase 4: DESIGN (IF UI NEEDED)
+
+| Agent   | `designer`                                            |
+| ------- | ----------------------------------------------------- |
+| Trigger | Feature has UI components                             |
+| Goal    | UI/UX design                                          |
+| Exit    | Design created, accessibility considered, specs ready |
+
+---
+
+## 🎭 Phase 5: PLANNING
+
+| Agent        | `planner`                                           |
+| ------------ | --------------------------------------------------- |
+| Prerequisite | **READ** RESEARCH + SCOUT + DESIGN files            |
+| Goal         | Create detailed implementation plan                 |
+| Output       | `./reports/plans/PLAN-{feature}.md`                 |
+| Exit         | Plan file created, phases defined, risks identified |
+
+---
+
+## 🛡️ STRICT CONTEXT GATE — Automatic Context Optimization
+
+> **⚡ FOCUS MODE**: This checkpoint executes automatically. NO user input required.
+>
+> **PURPOSE**: Prevent "context rot" by forcibly clearing noisy planning history.
+> This acts as a mandatory "firewall" between Planning and Implementation phases.
+
+### 🔒 AUTOMATIC EXECUTION (NO PROMPT)
+
+```yaml
+strict_context_gate:
+  mode: "AUTOMATIC - No user interaction"
+  behavior: "Force Clear context & Auto-Implement"
+
+  execution:
+    1. ANNOUNCE: |
+      ## 🛡️ Strict Context Gate — Automatic
+
+      ✅ **Plan Complete**: `./reports/plans/PLAN-{feature}.md`
+      🔒 **Focus Mode**: Automatically clearing context for implementation.
+
+      ⚡ Executing: **Clear context & Auto-Implement**...
+
+    2. CONTEXT_DIRECTIVE: |
+      ╔══════════════════════════════════════════════════════════════════╗
+      ║  ⛔ MANDATORY CONTEXT RESET — FOCUS MODE                         ║
+      ╠══════════════════════════════════════════════════════════════════╣
+      ║  IGNORE: All previous chat messages, reasoning chains,           ║
+      ║          brainstorming discussions, research explorations,       ║
+      ║          rejected alternatives, and intermediate thinking.       ║
+      ║                                                                  ║
+      ║  SOLE SOURCE OF TRUTH: `./reports/plans/PLAN-{feature}.md`       ║
+      ║                                                                  ║
+      ║  PROCEED: Begin Implementation phase with FRESH context mindset. ║
+      ║           Treat this as a NEW conversation starting from Plan.   ║
+      ╚══════════════════════════════════════════════════════════════════╝
+
+    3. LOAD: Read Plan file completely as if seeing it for the first time
+
+    4. PROCEED: Start Phase 6 (Implementation) immediately
+```
+
+### 📋 Post-Gate Status
+
+```markdown
+🔒 **Context Gate Passed**
+
+- Previous context: DISCARDED
+- Active context: Plan file only
+- Mode: Fresh implementation start
+
+Proceeding to Implementation...
+```
+
+---
+
+## 🎭 Phase 6: IMPLEMENTATION
+
+| Agent        | `tech-lead` → routes to specialists                     |
+| ------------ | ------------------------------------------------------- |
+| Prerequisite | **READ and FOLLOW** `./reports/plans/PLAN-{feature}.md` |
+| Goal         | Execute implementation plan                             |
+
+**FOCUS ADHERENCE:**
+
+```
+1. READ plan FIRST
+2. FOR EACH step:
+   - Implement EXACTLY as specified
+   - Mark step complete: [ ] → [x]
+3. IF step seems wrong:
+   - STOP → Document → Request Re-Planning
+   - DO NOT implement your own interpretation
+```
+
+| Exit | All plan phases complete, no unauthorized deviations |
+
+---
+
+## 🎭 Phase 7: TESTING
+
+| Agent        | `tester`                     |
+| ------------ | ---------------------------- |
+| Prerequisite | **READ** PLAN + Code changes |
+| Goal         | Comprehensive testing        |
+
+**PLAN CHECKPOINT VERIFICATION:**
+
+```
+FOR EACH checkpoint in PLAN:
+  - Write test that verifies criteria
+  - Document: "Checkpoint X → Test Y"
+```
+
+| Exit | All tests pass, each plan checkpoint has test |
+
+---
+
+## 🎭 Phase 8: REVIEW
+
+| Agent        | `reviewer`                       |
+| ------------ | -------------------------------- |
+| Prerequisite | **READ** PLAN + Code + Tests     |
+| Goal         | Quality review + Plan compliance |
+
+**REVIEW CHECKLIST:**
+
+- Does code implement plan specification?
+- Any unauthorized deviations?
+- All plan phases reflected in code?
+
+| Exit | Code matches plan intent, standards met, approved |
+
+---
+
+## COMPLETION
+
+Present feature report with:
+
+1. ✅ **Done** — Feature complete (Focus Mode)
+2. 🚀 **Deploy** → `/deploy:preview`
+3. 📝 **Docs** → `/docs:core`

package/commands/cook/hard.md

@@ -134,6 +134,65 @@ One phase at a time, each phase independent: Phase 1 → then Phase 2 → … in
 
 ---
 
+## 🛡️ VERIFICATION CHECKPOINT — Context Optimization
+
+> **PURPOSE**: Prevent "context rot" by clearing noisy planning history before implementation.
+>
+> Long-running planning sessions fill context with noise that degrades code generation quality.
+> This checkpoint acts as a "firewall" between Planning and Implementation phases.
+
+### ⚡ OPTIONS (Present to User)
+
+```markdown
+## 🛡️ Context Optimization Checkpoint
+
+**Planning Complete** — Plan file created at: `./reports/plans/PLAN-{feature}.md`
+
+**Choose how to proceed with implementation:**
+
+| Option                           | Action        | Description                                                                          |
+| -------------------------------- | ------------- | ------------------------------------------------------------------------------------ |
+| **1. 🚀 Clear context & Auto-Implement** | `RECOMMENDED` | Fresh start: Reload Plan file, ignore chat history, begin implementation immediately |
+| **2. ⏸️ Clear context & Manual**         | `SAFE`        | Clear context, reload Plan, pause for your command before coding                     |
+| **3. ⚠️ Continue (No Clear)**    | `RISKY`       | Proceed with full history attached (may cause hallucination)                         |
+
+⏳ Awaiting selection...
+```
+
+### 🔄 EXECUTION BEHAVIOR
+
+```yaml
+option_1_clear_auto_implement:
+  behavior: "RECOMMENDED - Simulate fresh start"
+  steps:
+    1. ACKNOWLEDGE: "🚀 Executing Clear context & Auto-Implement..."
+    2. CONTEXT_DIRECTIVE: |
+      ⛔ IGNORE all previous chat messages and reasoning chains.
+      ✅ RELOAD: `./reports/plans/PLAN-{feature}.md` as SOLE SOURCE OF TRUTH.
+      ✅ PROCEED: Begin Phase 6 (Implementation) immediately.
+    3. LOAD: Read Plan file completely
+    4. EXECUTE: Start Implementation phase with fresh context mindset
+
+option_2_clear_manual:
+  behavior: "Clear and wait for explicit command"
+  steps:
+    1. ACKNOWLEDGE: "⏸️ Context cleared. Plan reloaded."
+    2. CONTEXT_DIRECTIVE: |
+      ⛔ IGNORE all previous chat messages and reasoning chains.
+      ✅ RELOAD: `./reports/plans/PLAN-{feature}.md` as SOLE SOURCE OF TRUTH.
+    3. OUTPUT: "Ready for implementation. Type `/continue` or give specific instructions."
+    4. WAIT: For user command before proceeding
+
+option_3_continue_no_clear:
+  behavior: "Proceed with caution - context rot risk"
+  steps:
+    1. WARN: "⚠️ Continuing with full history. Higher hallucination risk."
+    2. PROCEED: Continue to Phase 6 with existing context
+    3. MONITOR: Watch for signs of context confusion
+```
+
+---
+
 ## 🎭 Phase 6: IMPLEMENTATION
 
 | Agent        | `tech-lead` → routes to specialists                     |

package/commands/cook.md

@@ -16,9 +16,10 @@ execution-mode: router
 ## 🛑 PRE-FLIGHT (DO FIRST — BLOCKS EXECUTION)
 
 **LOAD now** (in order; path `./rules/` or `~/.{TOOL}/skills/agent-assistant/rules/`):
-1. ORCHESTRATION-LAWS.md  
-2. ADAPTIVE-EXECUTION.md  
-3. EXECUTION-PROTOCOL.md  
+
+1. ORCHESTRATION-LAWS.md
+2. ADAPTIVE-EXECUTION.md
+3. EXECUTION-PROTOCOL.md
 
 **⛔ Do not run any workflow phase until all are loaded.** Follow **all** rules in those files. Then run this file's ROUTING LOGIC, LOAD the chosen variant workflow, and execute it.
 
@@ -33,6 +34,9 @@ IF feature is simple (clear spec, low complexity):
 IF feature is complex (multi-component, research needed):
   → Route to /cook:hard
 
+IF feature is complex AND context optimization is critical:
+  → Route to /cook:focus
+
 IF unsure:
   → Default to /cook:fast
 ```
@@ -41,10 +45,11 @@ IF unsure:
 
 ## AVAILABLE ROUTES
 
-| Route        | When to Use                          |
-| ------------ | ------------------------------------ |
-| `/cook:fast` | Quick features, clear specifications |
-| `/cook:hard` | Complex features, full workflow      |
+| Route         | When to Use                                             |
+| ------------- | ------------------------------------------------------- |
+| `/cook:fast`  | Quick features, clear specifications                    |
+| `/cook:hard`  | Complex features, full workflow                         |
+| `/cook:focus` | Complex features with **enforced context optimization** |
 
 ---
 
@@ -59,6 +64,7 @@ IF unsure:
 
 1. ⚡ **Fast** → `/cook:fast` — Quick implementation
 2. ⚡⚡⚡ **Hard** → `/cook:hard` — Full feature development
+3. 🎯 **Focus** → `/cook:focus` — Full development with **automatic context clearing** (prevents hallucination)
 
 ⏳ Awaiting selection...
 ```

package/commands/debug/focus.md

@@ -0,0 +1,155 @@
+---
+description: 🔒 Focused Debug — Deep investigation with enforced context optimization
+version: "1.0"
+category: debugging
+execution-mode: execute
+---
+
+# /debug:focus — Focus Deep Investigation
+
+> **MISSION**: Thorough investigation with **enforced context optimization**.
+>
+> This variant automatically clears context before fix handoff—no user prompt required.
+> Use when you want guaranteed clean fix handoff without hypothesis drift.
+
+<issue>$ARGUMENTS</issue>
+
+---
+
+## 🛑 PRE-FLIGHT (DO FIRST — BLOCKS PHASE 1)
+
+**LOAD now** (in order; path `./rules/` or `~/.{TOOL}/skills/agent-assistant/rules/`):
+
+1. ORCHESTRATION-LAWS.md
+2. ADAPTIVE-EXECUTION.md
+3. EXECUTION-PROTOCOL.md
+
+**⛔ Do not run Phase 1 until all are loaded.** Follow **all** rules in those files; they override any conflicting instructions in this file.
+
+---
+
+## 🔀 TIERED EXECUTION
+
+| Tier       | When               | Action                       |
+| ---------- | ------------------ | ---------------------------- |
+| **TIER 1** | runSubagent EXISTS | Invoke sub-agent (MANDATORY) |
+| **TIER 2** | Tool MISSING       | EMBODY agent file (FALLBACK) |
+
+---
+
+## 📁 DELIVERABLE FILES
+
+| Agent    | Output                              |
+| -------- | ----------------------------------- |
+| debugger | `./reports/debugs/DEBUG-{issue}.md` |
+
+All files in `./reports/` → English only.
+
+---
+
+## ⛔ INCREMENTAL EXECUTION (MANDATORY)
+
+One phase at a time, each phase independent: Phase 1 → then Phase 2 → … in one reply. No batching (load only what each phase needs). **Within each phase:** when doing a part, output it in format so user sees what's happening (announce before doing).
+
+---
+
+## 🎭 Phase 1: INFORMATION GATHERING
+
+| Agent | `scouter`                                 |
+| ----- | ----------------------------------------- |
+| Goal  | Gather context and reproduction steps     |
+| Exit  | Context gathered, reproduction documented |
+
+---
+
+## 🎭 Phase 2: HYPOTHESIS FORMATION
+
+| Agent | `debugger`                          |
+| ----- | ----------------------------------- |
+| Goal  | Form and rank hypotheses            |
+| Exit  | Hypotheses documented with evidence |
+
+---
+
+## 🎭 Phase 3: ROOT CAUSE ANALYSIS
+
+| Agent  | `debugger`                                      |
+| ------ | ----------------------------------------------- |
+| Goal   | Deep investigation                              |
+| Output | `./reports/debugs/DEBUG-{issue}.md`             |
+| Exit   | Root cause identified, failure chain documented |
+
+---
+
+## 🎭 Phase 4: SOLUTION DESIGN
+
+| Agent | `planner`                               |
+| ----- | --------------------------------------- |
+| Goal  | Design fix strategy                     |
+| Exit  | Fix approach defined with rollback plan |
+
+---
+
+## 🛡️ STRICT CONTEXT GATE — Automatic Context Optimization
+
+> **⚡ FOCUS MODE**: This checkpoint executes automatically. NO user input required.
+>
+> **PURPOSE**: Prevent "context rot" by forcibly clearing noisy debugging history.
+> This acts as a mandatory "firewall" before handoff to fix workflows.
+
+### 🔒 AUTOMATIC EXECUTION (NO PROMPT)
+
+```yaml
+strict_context_gate:
+  mode: "AUTOMATIC - No user interaction"
+  behavior: "Force Clear context & Fix"
+
+  execution:
+    1. ANNOUNCE: |
+      ## 🛡️ Strict Context Gate — Automatic
+
+      ✅ **Debug Complete**: Root cause identified, fix strategy designed.
+      🔒 **Focus Mode**: Automatically clearing context for fix handoff.
+
+      ⚡ Executing: **Clear context & Fix**...
+
+    2. CONTEXT_DIRECTIVE: |
+      ╔══════════════════════════════════════════════════════════════════╗
+      ║  ⛔ MANDATORY CONTEXT RESET — FOCUS MODE                        ║
+      ╠══════════════════════════════════════════════════════════════════╣
+      ║  IGNORE: All debugging hypotheses, failed investigation paths,  ║
+      ║          rejected theories, and intermediate reasoning.         ║
+      ║                                                                  ║
+      ║  SOLE SOURCE OF TRUTH: Root cause + Fix strategy.               ║
+      ║                                                                  ║
+      ║  HANDOFF: Ready for `/fix:focus` implementation.               ║
+      ║           Fix should treat root cause as fresh context.         ║
+      ╚══════════════════════════════════════════════════════════════════╝
+
+    3. OUTPUT: Root cause + Fix strategy summary
+
+    4. PROCEED: To COMPLETION
+```
+
+### 📋 Post-Gate Status
+
+```markdown
+🔒 **Context Gate Passed**
+
+- Previous context: DISCARDED
+- Active context: Root cause + Fix strategy only
+- Mode: Clean handoff ready
+
+Ready for fix implementation...
+```
+
+---
+
+## COMPLETION
+
+Present findings with:
+
+1. ✅ **Root Cause** — Identified (Focus Mode)
+2. 🔒 **Context Optimized** — Ready for focus fix
+3. 🔧 **Fix** → `/fix:focus`
+4. 📝 **Document** → `/docs:core`