dispatch-messagelisted

Compose, sanitize, and emit a VantagePeers `send_message` call in the **v2 telegraphic grid** — a fixed-field structure with NO free narrative slot. **Canonical source**: VantageRegistry (`get_skill_content name=dispatch-message`). Local `.claude/skills/dispatch-message/SKILL.md` MUST be a byte-exact mirror of VR canonical. Fetch from VR; do not edit locally. PRINCIPLE — outbound messages cross multiple enforcement hooks, and orchestrators reflexively add relative-time prose (elapsed-since asides, upcoming-deferral phrasings) that carries no information and trips `block-time-estimates` / `enforce-ship-24-7`. v1 sanitized that prose reactively. **v2 removes the slot it lives in.** If the structure has no place for a narrative aside, there is no temptation to write one. Format imposed upstream eliminates the cause; it does not merely reject the symptom downstream. ## THE GRID (v2 — mandatory shape) Every outbound message is exactly these fields, in this order: ``` [TAG] <task-ref> evidence: <raw shell command -> output, multi-line ok; or "n/a"> finding: <one concise observable fact> action: <imperative verb + object — 1 line max> next: <the next step already dispatched, OR "standby"> Orchestrator: <Name> — <Team> | <YYYY-MM-DD> ``` - **No `context:` / `background:` / `summary:` / `rappel:` / `recap:` field exists.** There is nowhere to put chronological prose. This is the point. - `evidence:`, `finding:`, `action:`, `next:` are the ONLY body fields. Use `n/a`