Function handle_reactive_agent_names 

pub(super) async fn handle_reactive_agent_names(
    __arg0: State<AppState>,
) -> Json<Value>

Agent NAMES only, for LAN peers: not handle_reactive_agents, whose full AgentRegistration records (block_id, tab_id, registration_nonce, …) are routing details that stay behind full auth.

Reachable with the broadcast lan_key (lan_or_full_auth_middleware), so its output is public to anyone on the local network. Do not extend it without the owner’s decision. Each field so far had one:

• agents, enumerating names (2026-09-08): a lan_key holder could already confirm a specific name via /agentmux/reactive/agent?id=….
• agent_kinds ({name: "host" | "container"}, 2026-10-06, agentmux-mobile’s SPEC_FLEET_HOST_TAGS_AND_CLOUD_HOSTS_2026_10_06 §5.2, §11).
• agent_status ({name: {state, since_ms}}) and now_ms, decision D1 of 2026-10-07 (agentmux-mobile’s SPEC_AGENT_STATUS_AND_LIVE_PANE_FEED_2026_10_07 §3.4, §11), also on the fleet feed this route is the fallback for.
• agent_lines ({name: line}, 2026-10-13): content, each agent’s Swarm summary line (backend::agent_line); absent with swarm:sharesummaries off.

An agent with no kind, state or line is left out of that map.