feat(console): fleet config panel — switch by identity, roster filtered to members (ADR Part A slice 2)

[brettchien]

Drafted by Orca (ecs-claude) — flagging authorship (shared GitHub identity).

Part A slice 2 of fleet-as-usage-grouping (#33), building on the backend from #34. Slice 1 taught oab-mcp's fleet_config to report each fleet's members; this wires the console so the config panel matches the new model.

What

• Switch by fleet identity, not cluster. A fleet is a usage-based group, so two fleets can share a cluster (orca + mira both on oab). Switching by cluster made them indistinguishable — the switch key moves from data-cluster → data-fleet (name). FleetConfigEntry gains members. selectFleet(name) derives the cluster it reads from and the members it filters by.
• Roster filtered to the fleet's members. New pure filterByMembers(deployments, members) keeps only deployments whose ECS service name (oab-{ns}-{name}) or short name is a member — mirroring studio-cp's resolve_service, which accepts both forms. Empty member list ⇒ whole cluster (legacy [[fleet]] semantics), roster unfiltered. null selection = default cluster, unfiltered.
• List by fleet. Each fleet button now shows its member services as chips (or whole cluster); the empty-config help points at the new [fleet.<name>] form.
• Fixtures model the canonical shape — orca + mira sharing cluster oab with distinct members — and the new [fleet.<name>] TOML the editor loads.

This realizes the ADR §4 consequence: "the config panel evolves: list fleets by name, roster filtered to a fleet's members, switch by fleet identity (not cluster)." The fleets.toml editor (slice C) carries over unchanged.

Verification

• npm run typecheck (tsc --noEmit) clean.
• npm run build (tsc + vite build) clean — this is what desktop.yml CI gates on for console/**.
• npm test (vitest) 31/31 (was 22; 9 new): member filtering — full-name, short-name, empty-list-is-whole-cluster, no-match, multi-match; switch-by-name with a shared cluster; member chip rendering; serviceName derivation.
• ⚠️ Console unit tests don't run in CI (ci.yml is Rust-only; desktop.yml runs build, not test) — so the vitest run above was done locally. build-test will still exercise the (unchanged) Rust backend.

Not in this slice

Reverse-MCP / Part B (ADR §3, §5 open questions) — next up per the plan (study → ADR → implement).

🤖 Generated with Claude Code