Handoff pack: correct routing rule (Slack cannot deliver to Astras)

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
ClaudeandClaude Opus 5.5 committed 2026-11-18 14:10:37 +00:00
1 parent 45afa47af5
commit 8def8e2b95
1 file changed
+3 -1
+3 -1
View File
@@ -30,7 +30,9 @@ For new sessions (NewMeltAstra, NewMeltAssist) and anyone resuming. Read in this
## 4. Routing lessons
- Native session IDs (Horsea host `remote-ssh-codex-managed:5bf202cd-...`): MeltAstra `01a1d30d-...`, MeltAssist `01a1e358-...`. TRON's native route failed twice ("Transport closed", "thread not found"); fallback = the shared Slack thread, which the Astras read. A delivery is not an acknowledgement.
- Native session IDs (Horsea host `remote-ssh-codex-managed:5bf202cd-...`): MeltAstra `01a1d30d-...`, MeltAssist `01a1e358-...`.
- **Slack cannot deliver to or wake an Astra session** (Yanqi, corrected 2026-11-18). Slack is only a public record and the channel to Claude. Tasks reach an Astra only via TRON's native send, and count as delivered only after the session's actual acknowledgement. If the native route fails ("Transport closed", "thread not found" happened twice), TRON reports it as a *blocker*; nobody treats a Slack post as a handoff. (On 2026-11-18 MeltAstra picked up Slack-posted work only because Yanqi woke that session directly; that is not a routing method.)
- A delivery is not an acknowledgement.
- Auto-approval can block GPU launches without verifiable user authorisation; supply the original user message or ask Yanqi one yes/no question; never route around it.
## 5. Current state (2026-11-18 evening)