The portal fetched display.status once and then only listened for lease events, so a start via the
CLI, a gateway auto-start, or a crash stayed invisible until remount (jeremiah-k #23). The serve-side
watcher now also stats env + launcher.pid per served home and broadcasts a full display.status
snapshot when either moves; the portal applies it through the same connection-qualified predicate.
Live: start/stop from a separate process reached the socket in 0.12 s / 0.36 s.
bc36ddb5f9