🧹 Drift Cleanup — goal-convergence-emitter

First execution batch of the #2217 drift audit · CC-native-first in action

interactive playground · DELETE 1 / KEEP 3 · subtractive adoption

📊 What this PR removes

1
hook deleted
212→211
total hooks
100→99
async hooks
3
KEEP (justified)

🎯 The goal machinery — DELETE 1, KEEP the M140 trio

Click a row for the rationale. The point of the no-drift rule: it discriminates, it doesn't just delete.

FileHooks eventVerdict

🔻 Why the emitter is a Shadow

Before (drift)

CC writes goal-current.json
→ ork's emitter reads it
→ re-writes goal-history.jsonl (dup)
→ emits goal_converged → events.jsonl (no consumer)
→
After (native)

CC owns goal-current.json ✓
stop/goal-tracker already writes history ✓
budget ceilings stay in the M140 trio ✓
~one async hook lighter

✅ The KEEP is the interesting part

The M140 trio (prompt/goal-tracker + stop/goal-tracker + lifecycle/goal-budget-guard) stays — it enforces hard per-session turn/token ceilings (ORK_GOAL_MAX_TURNS_PER_SESSION=30, ORK_GOAL_MAX_TOKENS_PER_SESSION=250k) that native /goal has no equivalent for. Deleting it would lose a real safety guarantee. That distinction — DELETE the Shadow, KEEP the orthogonal — is exactly what shared/rules/cc-native-first.md codifies.

🗺️ Where this sits in the register

Drift register (5 surfaces, all audited in #2217): this PR is batch A. Remaining: notification THIN (→terminalSequence), session-registry THIN, and the version-matrix + version-check thread (tied to adopting CC 2.1.163 requiredMinimumVersion).

PR companion to #2217 · rule: shared/rules/cc-native-first.md (merged #2216)