CC 2.1.140–2.1.148 Adoption — Doc Bundle Playground

Branch: docs/cc-adoption-bundle-2.1.140-148 · Targets: v8.1.0+ doc currency · Conflict surface: zero (doc-only)

What this PR changes

Edit 1 — brainstorm L398: terminalSequence alternative

BEFORE > Push notifications (CC 2.1.110+): For long brainstorm sessions, use PushNotification to alert when synthesis is complete (requires Remote Control with "Push when Claude decides").
AFTER > Push notifications (CC 2.1.110+): ...same as before... > > Lighter alternative (CC 2.1.141+): Hooks can emit desktop notifications, window titles, and bells natively via the terminalSequence field in hook JSON output — no Remote Control required, no Anthropic round-trip. See #1847 for the migration of ork's existing notification hooks.

Edit 2 — brainstorm L419: /goal compatibility floor

BEFORE Set a completion condition with /goal (CC 2.1.139+) and this skill will keep working across turns until the condition is met.
AFTER Set a completion condition with /goal (CC 2.1.139+, 2.1.143+ recommended for this skill) and this skill will keep working across turns until the condition is met. > Why 2.1.143+: Pre-2.1.143 /goal evaluator could fire while background shells or delegated subagents were still running — racing the parallel agents this skill spawns in Phase 2. Fixed in CC 2.1.143.

Why this bundle

OrchestKit's CC floor is >= 2.1.139 but several brainstorm-relevant fixes shipped in 2.1.141 and 2.1.143. Without these notes, callers running the floor minimum would hit silent races (e.g., /goal firing during parallel brainstorm). Doc-only PR, no code paths change, no manifest churn.

The memory updates capture lessons from this multi-session investigation: the /loop dedup is now upstream-codified, and the GH secondary-rate-limit lesson was discovered the hard way during the parallel agent sweep (Track A).

Filed alongside cross-link comments on #1830, #1897, #1862, #1874 and new tracking issues #1923–#1925 + Track A's 19-issue CC adoption sweep across milestones #142–#152.