docs: record table-fidelity feature batch as code-complete

- DECISIONS.md: new "Table-fidelity features" section + deferred items
  (smart-tracker rejected, highlight/phantom coupling deferred,
  abandoned-game localStorage cleanup deferred).
- CLAUDE.md: current state, test count 78->87, key files, known gaps.
- spec: record that the driver unit test covers the bot-suppression
  path in place of the considered-and-dropped ai-game-casual integration
  test (resolves a spec/implementation drift the final review flagged).

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

docs/superpowers/specs/2026-05-18-table-fidelity-features-design.md

@@ -156,8 +156,12 @@ core) are untouched.
 - Unit (`driver`): after a decision cycle that incurs ≥1 retry, only the final
   move's announcement(s) remain in `game.announcements`; intermediate
   rejections are absent.
-- Integration (`ai-game-casual`): the human side receives the bot's final move
-  announcement and no retry-rejection announcements.
+- The `driver` unit test is the chosen coverage for the bot-suppression path:
+  it drives the real `BotDriver` → `handleCommit` → `announceWith` pipeline, so
+  it verifies suppression at the commit-path level. A separate `ai-game-casual`
+  WebSocket integration test was considered and dropped — it would only
+  additionally exercise the trivial `broadcastSinceLast` pass-through filter,
+  for materially more harness complexity.
 
 ---