feat(web): make the conductor and its workers legible in the session list

[saucam]

First slice of P5.1 (conductor-frontends-design.md §12).

Why

The conductor has been drivable since P3 — codeoid attach conductor works — but in the web UI it renders as an ordinary row called "conductor", and its dispatch workers appear as unrelated top-level sessions named worker-scout-c0234348. Nothing on screen says the fleet is a fleet.

What

Workers group under the conductor. They carry no parent pointer — the conductor→worker link lives in the dispatch queue, not on SessionInfo — but the daemon enforces one conductor per tenant, so it's an unambiguous parent.

This reuses the existing collaboration grouping rather than adding a second mechanism, keeping groupFleet's three properties: pure and testable without a reactive root; uniform shape so the renderer never branches on "is this a fleet"; and orphans promoted, not dropped — a worker whose conductor isn't in the list still renders at top level rather than vanishing.

isConductor is kept separate from isFleet rather than folded into one "has children" flag, because the two group kinds differ in what their children are: a collaboration's role-children are long-lived sessions you drive; dispatch workers are disposable and die with their task.

Two badges. cond marks the conductor in the product accent rather than a semantic colour — the status vocabulary (§6) owns warn/danger/success, and "this row is the conductor" is an identity, not a state, so a conductor in trouble must still read as error from its StatusDot. ship/scout marks a worker's contract, scout quiet and ship warn-coloured for the same reason WriteBadge flags a writing role.

Worker shape is parsed from the name (worker-<shape>-<task>) because SessionInfo carries no shape field — the ship/scout contract lives on the dispatch task, which the session list doesn't join against. Guarded on role === "worker" so a user-named session starting with worker- is never mislabelled; only the daemon sets that role.

Two smaller judgment calls:

• Workers sort oldest-first with a name tiebreak, not createdAt alone — several can spawn in the same millisecond, and a list that reorders while you read it is worse than one that looks stale.
• Filtering matches role and shape, so scout or conductor finds these rows.

Verification

• 22 fleet unit tests (7 new), 35 across both lib suites
• tsc -b, eslint, and the production vite build all clean
• Name parsing checked against real daemon output — worker-scout-c0234348 with role: "worker", observed driving an actual dispatch

⚠️ Pre-existing gap this surfaced

No component test in web/ can run locally. The jsdom environment is broken: html-encoding-sniffer requires @exodus/bytes as CJS, but it resolves ESM-only —

Error: require() of ES Module .../@exodus/bytes/encoding-lite.js
from .../html-encoding-sniffer/lib/html-encoding-sniffer.js not supported.

That silently excludes 6 test files, including SessionListPane.test.tsx — which is exactly the file that would cover the badge rendering here. npm run test still reports green ("12 passed") with the failure demoted to an unhandled error, so it's easy to miss.

jsdom was also simply not installed despite being in package.json; installing it moved the failure from "package missing" to the ESM/CJS conflict above. bun.lock and package.json are untouched by this PR.

The badge rendering is therefore covered only by typecheck and build. Worth its own fix before P5.2 adds real components.

Next

P5.2 — the docked conductor surface: CenterPane branches on role === "conductor" with the state-grouped fleet rail, backed by a new state/fleet.ts over the fleet.subscribe contract (verified working end-to-end in #319's testing).

🤖 Generated with Claude Code

[highflame-oracle]

🔮 Oracle Review

🎯 Start Here

web/src/components/SessionListPane.tsx (~20 min) — Security changes in SessionListPane.tsx

---

📋 PR Summary

What this PR does: Implements visual grouping and differentiation for conductors and their dispatch workers in the web session list UI, allowing workers to appear as children under their conductor row with role-specific badges.

Key changes:

• Workers now group under conductor rows using existing collaboration grouping logic
• Added 'cond' badge for conductors and 'ship'/'scout' badges for workers based on parsed session names
• Implemented stable sorting (oldest-first with name tiebreak) and role-based filtering

Areas affected: SessionListPane.tsx (UI rendering and badges), fleet.ts (grouping and sorting logic), Session filtering behavior

Testing notes: 22 fleet unit tests (7 new), typecheck and build verified; component tests blocked by pre-existing jsdom/ESM compatibility issue unrelated to this PR

---

🔍 Code Review

This is a well-architected feature that thoughtfully reuses existing patterns rather than introducing parallel mechanisms. The implementation demonstrates strong attention to edge cases with proper orphan handling, stable sorting to prevent UI jitter, and appropriate role-based guards against spoofing.

What's good:

• ✨ Reuses existing groupFleet mechanism instead of adding a second grouping path, maintaining architectural simplicity
• ✨ Orphan promotion ensures workers render at top level if their conductor is missing, rather than vanishing
• ✨ Role-guards prevent user-named sessions starting with 'worker-' from being mislabeled as workers

Review Stats:

---

Generated by Oracle - Highflame's AI Code Reviewer