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
Move hardware surfaces out of the BENCH tab into a separate HARDWARE tab, keeping the Browser surface on BENCH. The contract and the tests for the separation live in a .t27 spec.
Boundary
specs/t27os/hardware_tab.t27
specs/t27os/agent_parts.t27
User Scenarios
Given the hardware surfaces are listed, when the tab contract runs, then each surface names its tab as HARDWARE, never BENCH. Given the Browser surface, when the tab contract runs, then it stays BENCH.
Requirements
FR-001: The tab contract MUST place hardware surfaces under HARDWARE and Browser under BENCH.
FR-002: The agent_parts registry MUST reflect the new tab for each hardware surface.
FR-003: A surface with no tab entry MUST fail the test.
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/hardware_tab.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.