You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Move HOME petal SEC_NAMES nav inside dashboard content panel #14070
Move the HOME petal's SEC_NAMES navigation items from the left sidebar into the dashboard content panel. Currently OVERVIEW, INSTRUMENTS, SURFACES, SPECS, COMMANDS, SKILLS, PULSE, HOME appear only in the sidebar (draw_home expanded state). The owner wants them rendered inside the dashboard panel as a fixed horizontal nav bar between the header divider and the scrollable content.
Boundary
specs/t27os/glass_window.t27
User Scenarios
Given the HOME petal is open in any workspace mode when the user looks at the dashboard panel then they see the SEC_NAMES navigation items (OVERVIEW, INSTRUMENTS, SURFACES, SPECS, COMMANDS, SKILLS, PULSE, HOME) as a horizontal strip inside the content area, and tapping one scrolls the dashboard to that section.
Requirements
FR-001: glass_window.t27 MUST add a DASH_NAV_H constant for the in-panel nav bar height.
FR-002: home_view_top() MUST return WS_TOP + HEADER_H + 1.0 + DASH_NAV_H so the nav bar sits between the header and the scrollable content.
FR-003: draw_home MUST render all 8 SEC_NAMES items as a horizontal row at WS_TOP + HEADER_H + 1.0 within the content panel.
FR-004: A new pub fn dash_nav_at MUST return which section index is under (x, y) in the nav bar, or SEC_NONE.
FR-005: Clicking a nav item in the panel MUST trigger the same sec_target scroll as a sidebar sec click.
FR-006: The existing test assert home_view_top() == WS_TOP + HEADER_H + 1.0 MUST be updated.
Success Criteria
t27b test specs/t27os/glass_window.t27 exits 0 with 0 failures.
make t27os builds without error.
8 nav items are visible in the dashboard panel when the HOME petal is open.
Reopened: closed as spec-only. A .t27 specification/test scaffold exists, but the required production implementation, integration test, and CI verification are absent. This issue remains open until the target component implements the specified behavior and evidence is provided.
Reopened: closed as spec-only. A .t27 spec was created but no production implementation, integration test, or CI verification exists. This issue remains open until the target component implements the specified behavior and evidence is provided.
Activity
gHashTag commentedon Nov 17, 2026
Spec created: specs/t27os/home_petal_sec_names.t27 (typecheck OK, 1 test pass).
gHashTag commentedon Nov 17, 2026
Reopened: closed as spec-only. A .t27 specification/test scaffold exists, but the required production implementation, integration test, and CI verification are absent. This issue remains open until the target component implements the specified behavior and evidence is provided.
gHashTag commentedon Nov 17, 2026
Spec exists and passes typecheck + tests. M6 milestone complete.
gHashTag commentedon Nov 18, 2026
Reopened: closed as spec-only. A .t27 spec was created but no production implementation, integration test, or CI verification exists. This issue remains open until the target component implements the specified behavior and evidence is provided.