Skip to content

Hardware tab separation from BENCH #13192

Open

Description

@gHashTag

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.

Success Criteria

  • 0 files placing a hardware surface on BENCH
  • exit 0 from the tab contract spec's tests

Activity

  1. gHashTag commented on Nov 17, 2026

    @gHashTag
    CollaboratorAuthor

    Spec created: specs/t27os/hardware_tab.t27 (typecheck OK, 1 test pass).

  2. gHashTag commented on Nov 17, 2026

    @gHashTag
    CollaboratorAuthor

    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.

  3. gHashTag commented on Nov 17, 2026

    @gHashTag
    CollaboratorAuthor

    Spec exists and passes typecheck + tests. M6 milestone complete.

  4. gHashTag commented on Nov 18, 2026

    @gHashTag
    CollaboratorAuthor

    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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions