docs: surgically prune plan-blocks references to fix remaining doc drift

src/capabilities/slack.md

@@ -55,7 +55,7 @@ Whenever a reply will take more than ~2 seconds — i.e. *any* reply that involv
 
 **`respond()` auto-clears the status.** Sam SETS status mid-session; `respond()` CLEARS it on exit. Sam never needs to remember to clear status before the final reply — the runtime does that. This closed a recurring slip class (operator reading the final reply while the status indicator still said "drafting the PR"). See the 2026-05-13 journal entries for the original failure mode.
 
-This is unconditional. Sam doesn't decide whether the work "warrants" a status — if there's a tool call, there's a status. (The skill `src/skills/slack-dynamic-messaging/skill.md` covers the other live-UX features — streaming, plan blocks, feedback buttons — which remain judgment calls.)
+This is unconditional. Sam doesn't decide whether the work "warrants" a status — if there's a tool call, there's a status. (The skill `src/skills/slack-dynamic-messaging/skill.md` covers the other live-UX features — streaming, rotating loading messages, feedback buttons — which remain judgment calls.)
 
 ## Cancel — `:no_entry:` reaction
 

src/skills/slack-dynamic-messaging/skill.md

@@ -1,6 +1,6 @@
 ---
 name: slack-dynamic-messaging
-description: Governs the formatting, section labeling, and live-UX feature decisions (streaming, status, plan blocks, feedback buttons, source citations) for any multi-line or PR-summarizing Slack reply.
+description: Governs the formatting, section labeling, and live-UX feature decisions (streaming, status, rotating loading messages, feedback buttons, source citations) for any multi-line or PR-summarizing Slack reply.
 when_to_use: Before drafting any Slack reply that summarizes a PR/issue, cites sources, has multiple steps, is longer than ~10 lines, or will take more than ~2 seconds to process.
 ---