# Radio interruption feedback

The game mode replicates one presentation state: inactive, waiting, transmitting, or interrupted. Its existing server phase transitions and radio tick derive this from the authoritative defence service. The presentation state never advances or resets defence progress and adds no timer. A state change causes replication; unchanged ticks do not.

Entering radio defence publishes waiting before the first occupancy sample. A valid conscious defender changes it to transmitting. Losing all valid defenders after transmission began changes it to interrupted and keeps that message until transmission resumes. Leaving the defence phase clears the state, including completion and defeat. An initial empty radio area stays waiting rather than claiming a previous transmission failed.

The existing player guide polls the replicated mode once per second and compares its previous message before showing a hint. Its radio instruction now includes the state, so interruption and resumption produce fresh guidance without countdown chatter. Clients do not read the server-owned radio service. The task's existing detailed countdown remains unchanged.

`tests/test_radio_feedback_policy.py` executes the production state policy with exhaustive valid previous states and occupancy/phase combinations, plus repeated empty samples, recovery and round reset. The existing opt-in Core native fixture adds seven checks across tuning, real defender occupancy, unconsciousness, recovery, leaving the area and completion. Native assertions are prepared but not run in this isolated change. They verify authority state and instruction copy, not delivery to a remote client or rendered hints. Remote reception, late joining during interruption and round restart remain multiplayer acceptance checks.

Native integration passes in [073806](evidence/native-2026-09-19-073806/report.json): two complete Core escape/restart rounds, 564 total assertions and zero native errors. Both rounds verify each feedback state and the exact player-guide copy through interruption, recovery, leaving and completion. Actual remote replication/presentation remains pending.