ctx-cc 3.3.2 → 3.3.3

package/agents/ctx-designer.md

@@ -623,6 +623,45 @@ If ALL criteria pass:
 }
 ```
 
+## Delivery Guarantee Loop
+
+```
+┌─────────────────────────────────────────┐
+│    DESIGN DELIVERY GUARANTEE LOOP       │
+├─────────────────────────────────────────┤
+│                                         │
+│  verify design → ALL PASS?              │
+│     │                                   │
+│     ├─ YES → COMPLETE (100% working)    │
+│     │                                   │
+│     └─ NO → debug/fix → verify again    │
+│              ↑                     │    │
+│              └─────────────────────┘    │
+│                                         │
+│  Loop continues until:                  │
+│  1. ALL checks pass, OR                 │
+│  2. Max attempts (10) → escalate        │
+│                                         │
+│  NEVER mark complete with failures      │
+│                                         │
+└─────────────────────────────────────────┘
+```
+
+**Design work is ONLY marked complete when:**
+- ✓ All approval gates passed (mood board, direction, prototype)
+- ✓ Three-level check passes (exists, substantive, wired)
+- ✓ Visual verification matches prototype
+- ✓ WCAG 2.2 AA compliance verified
+- ✓ Browser renders correctly (all breakpoints)
+- ✓ No console errors
+- ✓ All acceptance criteria satisfied
+
+**If ANY fails:**
+- Set status = "debugging"
+- Spawn ctx-debugger for technical issues
+- Return to designer for visual/a11y issues
+- Loop until 100% verified
+
 </verification>
 
 <output>

package/agents/ctx-executor.md

@@ -312,11 +312,40 @@ After each task:
 - Set status = "debugging"
 - Capture error details
 - Hand off to ctx-debugger
+- **Loop until fixed** (debug → fix → verify → repeat)
 
 ### If All Tasks Complete
 - Set status = "verifying"
 - Hand off to ctx-verifier
 
+## 8. Delivery Guarantee
+
+```
+┌─────────────────────────────────────────┐
+│       EXECUTOR DELIVERY GUARANTEE       │
+├─────────────────────────────────────────┤
+│                                         │
+│  execute task → quick verify            │
+│     │                                   │
+│     ├─ PASS → commit → next task        │
+│     │                                   │
+│     └─ FAIL → debug → fix → verify      │
+│              ↑                     │    │
+│              └─────────────────────┘    │
+│                                         │
+│  NEVER commit failing code              │
+│  NEVER skip to next task on failure     │
+│  ALWAYS loop until 100% working         │
+│                                         │
+└─────────────────────────────────────────┘
+```
+
+**Task is ONLY committed when:**
+- ✓ Build passes
+- ✓ Tests pass
+- ✓ Lint passes
+- ✓ No blocking anti-patterns
+
 </process>
 
 <commit_message_examples>

package/agents/ctx-planner.md

@@ -148,6 +148,15 @@ Write `.ctx/phases/{story_id}/PLAN.md`:
 - Run tests
 - Browser verify each criterion
 
+## Delivery Guarantee
+Every task loops until verified:
+```
+execute → verify → PASS? → commit
+              ↓ NO
+          debug → fix → verify again
+```
+NEVER mark done until ALL criteria pass.
+
 ## Notes
 {Key insights from research}
 ```

package/agents/ctx-verifier.md

@@ -399,9 +399,42 @@ Based on results:
 - Update PRD progress
 
 **If FAIL:**
-- Create fix tasks mapped to failing criteria
-- Set status = "debugging" or "executing"
-- Keep current story
+- Analyze failure type:
+  - **Build/Test/Runtime error** → Set status = "debugging"
+  - **Missing feature** → Set status = "executing" with fix tasks
+- Record `debug_issue` with error details
+- **DO NOT mark as complete until 100% pass**
+
+## 11. Delivery Guarantee Loop
+
+```
+┌─────────────────────────────────────────┐
+│         DELIVERY GUARANTEE LOOP         │
+├─────────────────────────────────────────┤
+│                                         │
+│  verify → ALL CRITERIA PASS?            │
+│     │                                   │
+│     ├─ YES → COMPLETE (100% working)    │
+│     │                                   │
+│     └─ NO → debug/fix → verify again    │
+│              ↑                     │    │
+│              └─────────────────────┘    │
+│                                         │
+│  Loop continues until:                  │
+│  1. ALL criteria pass, OR               │
+│  2. Max debug attempts (10) → escalate  │
+│                                         │
+│  NEVER mark complete with failures      │
+│                                         │
+└─────────────────────────────────────────┘
+```
+
+**Key principle:** Work is ONLY marked complete when:
+- ✓ ALL acceptance criteria pass
+- ✓ Three-level check passes (exists, substantive, wired)
+- ✓ No blocking anti-patterns
+- ✓ Browser verification passes (if UI)
+- ✓ Build + Tests + Lint all green
 
 </process>
 

package/commands/ctx.md

@@ -88,8 +88,12 @@ Route to: **Three-Level Verification**
    - Level 2: Substantive (real code, not stub?)
    - Level 3: Wired (imported and used?)
 3. Scan for anti-patterns (TODO, empty catch, placeholders)
-4. If all pass: complete phase, update STATE.md
-5. If fails: create fix tasks, set status = "executing"
+4. Browser verification (if UI)
+5. **DELIVERY GUARANTEE:**
+   - If ALL pass: complete phase → COMPLETE
+   - If ANY fail: set status = "debugging" → fix → verify again
+   - Loop until 100% working or max attempts
+   - NEVER mark complete with failures
 
 ### If status = "paused"
 Route to: **Resume**
@@ -149,9 +153,14 @@ executing → debugging (if verification fails)
 executing → verifying (if all tasks done)
 debugging → executing (if fix works)
 debugging → ESCALATE (if max attempts fail)
-verifying → executing (if anti-patterns found)
-verifying → COMPLETE (if all passes)
+verifying → debugging (if any check fails)    ← LOOP BACK
+verifying → COMPLETE (if ALL pass 100%)       ← ONLY EXIT
 paused → (previous state)
+
+DELIVERY GUARANTEE LOOP:
+  verifying ←→ debugging ←→ executing
+       ↓
+  COMPLETE (only when 100% verified)
 ```
 </state_transitions>
 

package/commands/verify.md

@@ -121,8 +121,11 @@ Based on results:
   - Set status to "initializing" for next story
   - Update current story reference
 - **FAIL**:
-  - Create fix tasks
-  - Set status = "debugging" or "executing"
+  - Analyze failure type:
+    - **Build/Test/Runtime error** → Set status = "debugging" (spawn ctx-debugger)
+    - **Missing feature/incomplete** → Create fix tasks, set status = "executing"
+  - Record `debug_issue` in STATE.md with error details
+  - Debug mode will loop until fixed (max 10 attempts)
 </workflow>
 
 <output_format>

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "ctx-cc",
-  "version": "3.3.2",
+  "version": "3.3.3",
   "description": "CTX 3.3 (Continuous Task eXecution) - AI that learns your preferences. Learning system, predictive planning, self-healing deployments (Sentry/LogRocket), voice control for hands-free development.",
   "keywords": [
     "claude",