skill(slice-21 FR-1): mirror coordination-model summary into orchestrator role overlay (OPR.0.3.2.21.FR-1 commit 2)

Closes the optional rig-injected overlay scope from FR-1 IMPL-PRD
§29 + §66-68. The orchestrator agent.yaml at
packages/daemon/specs/agents/orchestration/orchestrator/agent.yaml
declares guidance/role.md as a startup file delivered via send_text
at boot — orchestrator agents receive this overlay AFTER the
openrig-user skill, so a short coordination-model summary here lands
the model most prominently for orchestrators specifically (who are
the seats most affected by the "agents don't default to the queue
system" dogfood finding behind this slice).

Edit (packages/daemon/specs/agents/orchestration/orchestrator/guidance/role.md):

The Communication section was the most concentrated gap: the prior
version named only rig send + rig capture + chatroom, with no
mention of rig queue or rig queue handoff. After this commit:

- The three coordination surfaces are summarized with the
  send / queue / queue-handoff usage model, each with a one-line
  use-case + an explicit pointer back to the full
  "Coordination primitives — when to use which" section in the
  openrig-user skill (so this overlay does not drift from the
  canonical surface — the skill remains authoritative).
- rig capture + chatroom + human-progress reporting stay in an
  "Other operator surfaces" sub-list so existing operator habits
  are not broken.
- A §1b reminder paragraph closes the section explicitly for
  orchestrators: a turn ends by passing the ball, never by going
  idle waiting on a confirmation the process does not include.
  Dispatch via rig queue create, stand by for the verdict back,
  do not phantom-gate the rig on imagined operator-input pauses.

No other sections of role.md changed (Startup checklist,
Responsibilities, Working rhythm, Principles all intact).

Acceptance: this is the commit-2 surface from FR-1 IMPL-PRD §93
estimate. The 1-2 sentence pointer mirror is sized to a short
summary block (3 bullets + reminder paragraph) so it lands inside
the role.md without bloating the orchestrator overlay.

Verification:
- Frontmatter: role.md has no frontmatter (operator guidance
  prose only); structure unchanged.
- Markdown structure: ## headers unchanged in count + placement;
  the new sub-content is plain bullets + paragraphs under the
  existing Communication ## header.
- No code change; no test surface affected; will run daemon test
  suite at full-tip review pre-velocity-qa.
- Body verification grep clean per banked discipline at commit
  time.

Branch: slice-21-fr-1-coordination-model-boot-instinct off LOCAL
main ea03680d. Chain: 43f2259f (FR-1 commit 1 primary skill) →
this commit. LOCAL only, NO push.

packages/daemon/specs/agents/orchestration/orchestrator/guidance/role.md

@@ -38,10 +38,34 @@ Then run:
 
 ## Communication
 
-- Send messages to agents via tmux or `rig send`
-- Read agent output via `rig capture`
-- Use the chatroom for broadcast announcements
-- Keep the human informed of progress at natural milestones
+You ship work through three coordination surfaces. See the
+"Coordination primitives — when to use which" section at the top of
+the `openrig-user` skill for full definitions, runnable examples,
+the §1b doctrine, and the anti-patterns list. Brief mental model:
+
+- `rig send <seat> "<text>"` — intra-pod nudges and quick context.
+  **NOT for durable work.** No queue record; the message lands and
+  is gone.
+- `rig queue create --source X --destination Y --tags ... --body ...`
+  — durable work item. Survives restarts. Tracked. Tag with
+  mission / slice / gate / checkpoint. Use this for any substantive
+  dispatch, verdict, or handoff.
+- `rig queue handoff <qitem-id> --destination <next> ...` — hot-potato
+  forward momentum. Chain-of-record preserved. **This is how a turn
+  ends — by passing the ball, never by going idle.**
+
+Other operator surfaces:
+
+- Read agent output via `rig capture`.
+- Use the chatroom for broadcast announcements where the
+  audience is the whole rig.
+- Keep the human informed of progress at natural milestones.
+
+§1b reminder for orchestrators: a turn ends by passing the ball,
+never by going idle holding the slice waiting on a confirmation
+the process does not include. If work is authorized, dispatch it
+via `rig queue create` and stand by for the verdict back; do not
+phantom-gate the rig on an imagined operator confirmation.
 
 ## Principles