[MOB-01] Align mobile attention with optional relay delivery #15

ID: MOB-01 (F-006). Priority: P1. Blocked by: #6. Backlog: #1.

Scope and reuse

Reuse adopted upstream mobile awareness, APNs/FCM, widgets/Live Activities and
scoped deep links. Align a native foreground actionable list and direct refresh
with the environment-owned current attention projection. Add only the compact
relay mapping needed for optional background delivery.

Acceptance criteria

• Foreground mobile works through direct environment connections without relay.
  Request actions use existing environment-scoped commands.
• A notification/deep link retains environment/thread identity and refreshes
  direct state before offering an action. Already-resolved or unavailable
  targets display their real state, not a stale approval prompt.
• Relay hints never resolve attention or overwrite newer authoritative direct
  state. Adopt compatible upstream categories instead of a parallel taxonomy.
• Device registration, opt-out and delivery errors follow upstream policy.
  Foreground/background transitions do not duplicate one event's notifications.
• Default external payloads contain opaque identifiers and category/revision
  information, not prompts, paths, raw errors or tool output. Sensitive labels
  are not required to deliver a useful generic notification.
• APNs/FCM or relay failure affects only background delivery; it cannot break
  direct operation. Custom-signed/self-hosted push setup is a separate rollout
  decision, not a hidden prerequisite.
• Cover direct-only, relay-enabled, stale notification, revoked link, offline
  destination, two environments sharing local thread IDs and delivery opt-out
  on iOS/Android. Integrated device use requires permission.

Coverage and non-goals

All provider-derived canonical attention and existing supported connection
modes. Web/desktop state remains unchanged; local OS delivery belongs to ATT-06.
No mandatory coordinator, new push service, global acknowledgement or server
host notification.