crank

Malicious tool definition detected

Merge and cleanup ```bash git merge --no-ff "swarm/${epic_id}" -m "chore: merge swarm/${epic_id}" git worktree remove "/tmp/swarm-${epic_id}" git branch -d "swarm/${epic_id}" ``` ## CC Estimation Heuristic Each extract-method refactoring saves approximately 3-5 CC points. For CC 30+, plan 6-10 extractions to reach CC <15.

Malicious tool definition detected

Generate tests following the project's existing test patterns.

Malicious tool definition detected

## Final Batched Validation When all issues complete, check whether a full /vibe is needed: ```bash # Check wave checkpoint verdicts — skip final vibe if ALL waves passed clean ALL_PASS=true for checkpoint in .agents/crank/wave-*-checkpoint.json; do verdict=$(jq -r '.acceptance_verdict // "UNKNOWN"' "$checkpoint" 2>/dev/null) if [[ "$verdict" != "PASS" ]]; then ALL_PASS=false break fi done ``` **If ALL waves passed acceptance check with PASS verdict (no WARNs, no retries):** Skip the final /vibe

Tool passed security scan

Malicious tool definition detected

Mail human (--human, not mayor/ since we ARE mayor) gt mail send --human -s "BLOCKER: <issue> - <failure-type>" -m "See issue for details" # 4.

Malicious tool definition detected

Tool passed security scan

Malicious tool definition detected

| ```bash # Record verdict in epic notes bd update <epic-id> --append-notes "CRANK_ACCEPT: wave=$wave verdict=<PASS|WARN|FAIL> at $(date -Iseconds)" ```

Malicious tool definition detected

Malicious tool definition detected

- Keep state in files/issue trackers, not long conversational memory. - Prefer deterministic checks over subjective completion.

Tool passed security scan

Tool passed security scan

Tool passed security scan