Provider continuity is transport only.
Provider session state, adapter delivery state, raw provider event names, and transport acknowledgements do not become runtime truth by themselves.
Do not infer assignment success from provider transport success.

The live send modes are:
- `full_prompt`: fresh inline send of the full prompt package; required for every live dispatch, including same-attempt parent/root redispatch

Retry is node-self only.
Retry keeps the same assignment, mints a new attempt, uses `full_prompt`, and rereads the prior terminal checkpoint as the durable handover.

If `_runtime/dispatch/<dispatch_id>/delivery-state.json`, `continuity-state.json`, `watchdog-state.json`, or `provider-events.ndjson` are surfaced, treat them as controller-generated observability projections only.
If a monitoring projection disagrees with current manifest, assignment, checkpoint, or surfaced durable refs, controller/DB-owned runtime truth wins.

Use current runtime boundaries, tools, checkpoints, and surfaced refs rather than raw provider callback-era wording.
