Context
Operator gallery review for the Build Week submission (2026-07-21): two rendered defects on the Fleet surfaces, both V-B-A'd live. Round 2 of the film-floor arc (#15628's follow-up; same class as #15629's container-background findings).
Live latest-open sweep: checked latest 20 open issues at 2026-07-21T09:40Z; no equivalent.
The Problems (computed-style evidence)
- Detail header mismatched background —
.fm-detail-header computes rgb(14, 15, 13) (Neo stock container background) while the detail panel below is transparent: the "Agent detail" header strip reads as a differently-dark box. AgentDetail.scss sets no background on the header, so the framework default leaks through — the exact #15629 glitch class in a sibling component.
- Dock rail tabs loud + overflowing —
.neo-dashboard-dock-rail-tab buttons paint rgb(62, 99, 221) (the framework's primary button chrome; nothing in the agentos layer quiets them) and sit at left: 1589 with width 48 — 37px past the 1600px viewport edge: blue slivers with unreadable content at the layout's right edge.
The Fix
AgentDetail.scss: .fm-detail-header { background: transparent } (+ sweep .fm-detail-empty, .fm-detail-panes for the same leak).
- Agentos FM layer: quiet
.neo-dashboard-dock-rail-tab (transparent/dim token, NOT the framework file — src/dashboard/Container.scss must stay consumer-neutral).
- The rail overflow: measure the cockpit's width budget (nav + grid + detail + rail) against the host; fix the layout allocation if it's config-sized, or file the structural finding with evidence.
Acceptance Criteria
Out of Scope
- Framework-level rail-tab restyle (consumers beyond the FM own that decision).
Related
#15628 (film-floor round 1) · #15629 (merged, same glitch class) · FleetCockpitAutoHideRailNL (the rail's witness)
Origin Session ID: 86adbb95-6d48-4071-8d93-b2355d320a97
Retrieval Hint: detail header background transparent dock rail tab primary chrome viewport overflow film floor round 2
Context
Operator gallery review for the Build Week submission (2026-07-21): two rendered defects on the Fleet surfaces, both V-B-A'd live. Round 2 of the film-floor arc (#15628's follow-up; same class as #15629's container-background findings).
Live latest-open sweep: checked latest 20 open issues at 2026-07-21T09:40Z; no equivalent.
The Problems (computed-style evidence)
.fm-detail-headercomputesrgb(14, 15, 13)(Neo stock container background) while the detail panel below is transparent: the "Agent detail" header strip reads as a differently-dark box.AgentDetail.scsssets no background on the header, so the framework default leaks through — the exact #15629 glitch class in a sibling component..neo-dashboard-dock-rail-tabbuttons paintrgb(62, 99, 221)(the framework's primary button chrome; nothing in the agentos layer quiets them) and sit atleft: 1589with width 48 — 37px past the 1600px viewport edge: blue slivers with unreadable content at the layout's right edge.The Fix
AgentDetail.scss:.fm-detail-header { background: transparent }(+ sweep.fm-detail-empty,.fm-detail-panesfor the same leak)..neo-dashboard-dock-rail-tab(transparent/dim token, NOT the framework file —src/dashboard/Container.scssmust stay consumer-neutral).Acceptance Criteria
.fm-detail-header).Out of Scope
Related
#15628 (film-floor round 1) · #15629 (merged, same glitch class) · FleetCockpitAutoHideRailNL (the rail's witness)
Origin Session ID: 86adbb95-6d48-4071-8d93-b2355d320a97
Retrieval Hint:
detail header background transparent dock rail tab primary chrome viewport overflow film floor round 2