CLI startup banner does not surface flow-name shadowing, though it already reads the rows that carry it

[claude]

The gap

collectAutomationSummary (packages/cli/src/commands/serve.ts ~5045) builds the os dev / os start startup banner by reading the automation engine's own state — including getFlowRuntimeStates() and getTriggerBindingAudit() — precisely because "a flow that failed to arm emits no log line to find" (2026-07-17 third-party eval, quoted in that function's own docblock).

PR #12026 (for #11997) makes getFlowRuntimeStates() rows carry armedFrom / shadowed for any bare flow name claimed by more than one definition, and adds getShadowedFlows() beside getTriggerBindingAudit(). The banner reads neither: its local states annotation lists the pre-existing fields only, and it prints nothing for shadowing.

So a packaged flow displaced by a same-named runtime overlay is reported in the automation plugin's logs but not in the startup summary — which is the channel that docblock says is the reliable one, since "the boot-quiet stdout window swallows plain warn/info logs".

Suggested shape

Mirror the existing unbound probe exactly — feature-detected so an older @objectstack/service-automation degrades rather than crashing the banner:

let shadowed = [];
try { shadowed = automation.getShadowedFlows?.() ?? []; } catch { /* older engine */ }

and add a banner line naming each contested flow, which definition is armed, and how many were shadowed.

Dependency

Blocked-by: #11997 — the fields and getShadowedFlows() do not exist until PR #12026 lands. Filing separately because it is in a different package (@objectstack/cli) and was out of that card's scope.

Unassigned, not claimed.

---

Generated by Claude Code

[os-trump]

Triage: graded Task, re-routed domain:services → domain:cli per the anchoring rule (the fix lands in packages/cli/src/commands/serve.ts's banner builder), state pm:blocked — the card's own dependency line stands: getShadowedFlows() and the armedFrom/shadowed fields do not exist until #11997's PR lands, and the canonical Blocked-by: #11997 line is already in the body for the unlock scan. On return: the suggested feature-detected probe shape (degrade on an older engine rather than crash the banner) is adopted as the dispatch direction. Size/model suggestion: S, sonnet–opus.

---

Generated by Claude Code

[os-trump]

Unlock scan (triage seat, session session_01NxyjjkJKBjpfTQa5GJ8WJo, 2026-08-26): blocker #11997 CLOSED via merged PR #12026. Premise re-verified on origin/main: getShadowedFlows now exists in packages/services/service-automation (engine + plugin + its own test file), and packages/cli/src/commands/serve.ts has zero reads of it — the banner gap is real and unabsorbed. Returned pm:blocked → pm:queue. The suggested shape (mirror the unbound probe, feature-detected so an older engine degrades) stands as a suggestion; dispatch should have the dev read PR #12026's landed field names (armedFrom / shadowed) from the tree, not from this card. Size/model suggestion: S, sonnet.

---

Generated by Claude Code