/status reports only 2 of its 5 sections: the health facts and the Router are in different processes #1011

Closed
opened 2026-10-27 13:38:40 +00:00 by sam · 0 comments
Owner

Found by ultrareview on PR #892.

newStatusHealth wires five sources, but three can never render:

  • containers reads b.containerPool and lastPoll reads b.d, both populated only in archied's boot.
  • channels is hardcoded nil (the Messaging Service owns the channels now; see 8cda.6.8).

The only production 'router.Health =' is gateway_runtime.go:70 in setupGatewayChat, which runs solely in the archie-gateway process. RunGateway never calls setupContainers and never builds a daemon.Daemon, so in the process that serves every /status the container pool and poll loop do not exist. Only Broker (taskActionsConn) and Chat model actually render.

The daemon also builds b.statusHealth (setupChatRuntime runs in both processes) with real container and poll sources that nothing ever serves, because the daemon has no Router. channelHealth() is likewise now referenced only by tests.

wp9s's own commit message accepted this as a standalone-Gateway limitation ('aggregating across processes would need a new daemon RPC and is deliberately not built'). The Messaging Service extraction made it universal: before it, the daemon built its own Telegram router where those sources were live, so Telegram /status showed all five.

Fixed already in the follow-up: the command description no longer claims workers and channels. Still open: either build the cross-process health contract so the Gateway can report daemon-owned facts, or ratify the two-section /status and delete the unreachable sources plus channelHealth. docs/prds/status-health-surface.md's table still describes the five-section version.

Related: 8cda.6.8 (channel lifecycle publishing), and the shared lastPollAt bead.

Close reason

Landed (Option B, the PRD-settled shape): the dead pool/poll producers deleted. The Gateway renders the two sections it can serve, which docs/prds/status-health-surface.md:106-117 ratifies as per-process.


Imported from beads archie-core-1xfd · GitHub #905 · type bug · priority P1 · created 2026-09-19 · closed 2026-09-21

Found by ultrareview on PR #892. newStatusHealth wires five sources, but three can never render: - containers reads b.containerPool and lastPoll reads b.d, both populated only in archied's boot. - channels is hardcoded nil (the Messaging Service owns the channels now; see 8cda.6.8). The only production 'router.Health =' is gateway_runtime.go:70 in setupGatewayChat, which runs solely in the archie-gateway process. RunGateway never calls setupContainers and never builds a daemon.Daemon, so in the process that serves every /status the container pool and poll loop do not exist. Only Broker (taskActionsConn) and Chat model actually render. The daemon also builds b.statusHealth (setupChatRuntime runs in both processes) with real container and poll sources that nothing ever serves, because the daemon has no Router. channelHealth() is likewise now referenced only by tests. wp9s's own commit message accepted this as a *standalone-Gateway* limitation ('aggregating across processes would need a new daemon RPC and is deliberately not built'). The Messaging Service extraction made it universal: before it, the daemon built its own Telegram router where those sources were live, so Telegram /status showed all five. Fixed already in the follow-up: the command description no longer claims workers and channels. Still open: either build the cross-process health contract so the Gateway can report daemon-owned facts, or ratify the two-section /status and delete the unreachable sources plus channelHealth. docs/prds/status-health-surface.md's table still describes the five-section version. Related: 8cda.6.8 (channel lifecycle publishing), and the shared lastPollAt bead. ### Close reason Landed (Option B, the PRD-settled shape): the dead pool/poll producers deleted. The Gateway renders the two sections it can serve, which docs/prds/status-health-surface.md:106-117 ratifies as per-process. --- _Imported from beads `archie-core-1xfd` · GitHub #905 · type bug · priority P1 · created 2026-09-19 · closed 2026-09-21_
sam added the highbug labels 2026-10-27 13:38:40 +00:00
sam self-assigned this 2026-10-27 13:38:40 +00:00
sam closed this issue 2026-10-27 13:38:40 +00:00
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: sam/archie#1011