feat(coding-agent): shared agent-status classifier, honest worker visibility, subagents bar rename

[snimu]

Part 1 of 3 for ENG-5794 (https://linear.app/primeintellect/issue/ENG-5794). Stack: this PR -> roster ledger (daemon-internal) -> subscription push + TUI consumption.

Summary

• add classifyAgentStatus, one pure status formula (running/idle/inactive) shared by every agent surface; the agents-view classifier (classifySessionRosterStatus) and the subagents-bar formula (countDirectSubagentStatuses) become thin adapters over it, so the two surfaces can no longer disagree on what a status means
• stop hiding sessions of non-ready workers: heavy RLM load flips a worker to recovering, which previously made the entire running family vanish from the agents view; the worker state now renders as the row's status label instead
• resident 0-message subagent sessions are live instead of draft-hidden: a spawned worker is visible from creation, before its first message lands (top-level drafts stay message-based; on-disk drafts of dead subagents are unaffected)
• rename the bar label agents -> subagents

Validation

• adversarial review enumerated the full old-vs-new input space for both adapters: zero status deltas; the in-process-residency nuance (activity implies a live session; in-process connections never stamp activeSessionId) verified against all snapshot builders
• new tests: classifier truth table, formula-equality property across both adapters, non-ready-worker visibility+label pin, resident 0-message subagent pin; mutants (classifier precedence inversion, queued-as-idle, restored hiding clause) each killed by a named test
• sandbox: scoped suites 108/108; blast radius (agents-view-mode, daemon-mode, daemon-list-format, interactive-mode-status, +2) 399 passed; root npm run check green

---

Note

Medium Risk
Changes agents-view visibility and lifecycle rules for subagents and non-ready workers; any code assuming those rows stay hidden will behave differently, though roster classification for existing inputs is intended to be unchanged.

Overview
Unifies running / idle / inactive behind a single classifyAgentStatus helper so the agents view and subagent summary bar use the same rules (including queued children counting as running before a session exists).

Agents view behavior changes: live sessions stay visible when the worker is starting, recovering, stopping, or failed (no longer filtered to workerState === "ready"); those rows show the worker state as the status label. Spawned subagents are live as soon as they are resident, even with zero messages—top-level empty sessions remain drafts.

The chat subagent summary bar label is renamed from agents to subagents, with border layout adjusted for the longer label.

^{Reviewed by Cursor Bugbot for commit ee28dc7. Bugbot is set up for automated code reviews on this repo. Configure here.}

Note

Add shared classifyAgentStatus classifier and show subagents from creation in agents view

• Introduces classifyAgentStatus in agent-roster.ts as the single status formula across daemon session lists and subagent summary lines, replacing bespoke per-field logic.
• Removes the workerState gate from shouldShowAgentsViewSession in agents-view-state.ts, so live sessions with non-ready worker states (starting, recovering, stopping, failed) are now visible instead of hidden; those states surface directly as the status label.
• Treats resident subagent sessions as live immediately upon creation in activeLifecycleForSession in daemon-session-list.ts, before any message is sent.
• Renames the summary bar label from 'agents' to 'subagents' in subagent-summary-line.ts and adjusts border width calculation accordingly.
• Behavioral Change: sessions previously hidden during worker startup/recovery are now visible with their raw worker state as the status label; subagent sessions appear as live from creation rather than draft.

^{Macroscope summarized ee28dc7.}

[cursor]

Cursor Bugbot has reviewed your changes and found 2 potential issues.

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.}

^{Reviewed by Cursor Bugbot for commit 8ecf7b0. Configure here.}