This is the question dorothy asked goulard before HALT. Until it's answered, no work order can begin.
theMesh2 is the operator-facing widget over localMesh. Either:
localMesh.py to serve a new /mesh HTML widget endpoint, ship the radix UI as a view on the existing service. Low risk, one repo.theMesh2/ widget (Qt or browser) that consumes localMesh APIs. Cleaner separation, two artifacts.Qt frameless on untitledSDK (matches pinger / ecoute2 / pocketViewer)? Browser page on neonForge ?p=themesh (cookie theme, mobile-friendly)? Both?
Maps to existing /resume and /kill. Straight wire, or richer semantics — halt messaging only, halt agents only, halt all?
From: defaults to operator? Or to a selected agent persona? Recipient autocompletes from registry?
3×3 grid of status cards, one per localMesh service. Card: name, kind, uptime, status dot. Polls /status every 5s.
Vertical list from /registry/online. Row: agent name, agentId, last-seen, ACTIVE / IDLE / OFFLINE state badge.
Form: from / to (autocomplete) / message body / send. POSTs to /message. Shows rate-limit (5/60s) status.
Tail of recent mesh messages.
Full registry dump with last-seen, agentId, sigil, callSign per agent.
Two big buttons. GO = /resume, HALT = /kill. Confirmation modal on HALT.
Radix Tabs primitive (per radix-vault) — services / agents / messages / registry.