Feature: /ck:converge — autonomous make→check→make loop until APPROVE

Summary

Add a /ck:converge command (or --until-approved flag on /ck:make) that runs the full build-verify-fix cycle autonomously without requiring manual re-invocation between phases.

Current workflow (requires manual intervention)

/ck:make      # runs unattended ✓
              # ← must return to screen
/ck:check     # runs once, produces APPROVE/REVISE/REJECT
              # ← if REVISE, must manually trigger again
/ck:make      # re-runs unattended ✓
/ck:check     # second pass

The user must monitor for completion and re-trigger the cycle manually on REVISE verdicts.

Proposed: /ck:converge

/ck:converge --max-cycles 3

Internally runs:

1. /ck:make — autonomous build loop until CAVEKIT COMPLETE
2. /ck:check — gap analysis + peer review
3. If verdict == APPROVE → done, emit completion
4. If verdict == REVISE → go to step 1 (up to max-cycles)
5. If verdict == REJECT or max-cycles hit → stop, report

Why this matters

• Current cost: user must actively monitor a ~6h build session and re-trigger 2-3 times
• With /ck:converge: single invocation, fully unattended from sketch→approved

Alternative

Add --until-approved flag to existing /ck:make:

/ck:make --until-approved --max-cycles 3

This reuses the existing stop-hook loop infrastructure and just adds a post-COMPLETE check phase that re-activates the loop if verdict != APPROVE.

Related

• /ck:ship does sketch→map→make→check once but does not loop on REVISE
• Stop-hook already handles autonomous make loop; check phase is the missing piece