CC 2.1.117 adoption + Milestone #117 Tier A

Plan vs. reality. Only 2 of 4 issues needed work — the other 2 were based on a misread of the matrix.

What shipped

IssuePlanned effortActual effortOutcome
#1441 CC 2.1.117 adoption60 min40 min14 matrix entries, MIN bump, doc table, mcpServers audit
#1440 CHANGELOG ghost5 min2 minGhost removed
#1444 hook backfill (4 events)90 min0 minInvalid premise — all 4 already registered
#1445 deprecated-ref sweep20 min0 minInvalid premise — no actual drift

2.1.117 matrix additions (14)

The 3 "already done" issues closed

#1444, #1449, #1453 were all filed based on the brainstorm's misread of cc-version-matrix.ts: having a matrix entry means the feature is TRACKED in compatibility, not that there's no hook. All 27 hook events actually have at least one registered handler.

Honest session note

Tier A was scoped at ~2-3 hours; real work took ~45 min because 2 of 4 issues evaporated on verification. This is exactly the kind of error the brainstorm should have caught by grep'ing hooks.json before filing. Lesson for /ork:brainstorm: verify claims against current code state, not against mental model.

Test plan

cd src/hooks && npx vitest run         7766/7766 pass
npm run build                          
npm run test:skills + test:agents      
./bin/validate-counts.sh               PASSED

Remaining in milestone #117

Tier B (#1446 MCP audit, #1447 Monitor wiring, #1448 OTEL analytics) + Tier C (#1450 PushNotification, #1451 release cadence, #1452 property-based testing) still open as originally scoped. Test-infra follow-ups #1436 and #1438 also still open.