Write & POST June 9 standup to Slack (12:30-13:30 UTC window) — queue-for-N+2 substrate fix from 2026-06-08 cron

Post the June 9 standup to Carson Slack DM (target D0B0980TR88) in the 12:30-13:30 UTC window. This is the queue-for-N+2 fix: queued by the 2026-06-08 04:10 UTC cron alongside the June 8 standup, so a single missed cron cannot again take out a day. Body will be dynamically composed at lease time based on live state at 12:25 UTC (do NOT use a pre-staged memory file; compose fresh after the final refresh). Mandatory step (0): eval "$(~/bin/gh-fleet-token.sh)" as an isolated standalone-line shell statement, then verify ${#GH_TOKEN}==40 on the next line. Mandatory final-refresh step: live gh pr view on all owned PRs (#11428/#11429/#11440/#11517/#11569/#11695/#11789 + agent-infra #319 + older 8); read last 25 Carson DMs; read resource-ask thread for any replies (if the June 8 standup posted the escalation default and Carson replied any direction, that reply is the headline). Send-side timing/status guard: do NOT post before 2026-06-09T12:30:00Z. Post-push duplicate-suppression gate: read last 25 Carson DMs to confirm no duplicate same-topic ping. Atomic completion: PATCH this task to completed with metadata.slack_ts, memory_file (write memory/standups/2026-06-09.md at lease time), delivered_at immediately after Slack delivery. If Carson replied to the resource-ask escalation default in the meantime, the standup body must reflect the decision and acknowledge it explicitly (no acting-as-if it didn't happen).