Skip to content

[spec] automation/app-tabs.t27 -- map every app tab to the TRI CLAW /mcp tools that serve it #10532

Closed as not planned

Description

@gHashTag

Goal

Write specs/automation/app-tabs.t27: every tab of the app mapped to the tools that serve it at TRI CLAW's one /mcp, each link labelled EXACT or SUGGESTED, the gaps (routes with no tool) and the unmapped HUD views listed.

Why this matters

Owner, 2026-10-18: join every tab into the one TRI CLAW MCP. The spec says which tools each tab reads and where a tab still reads a route no tool serves.

Source of truth

specs/automation/app-tabs.t27; the service it maps onto is specs/t27mcp/service.t27 (see #10484).

Deliverable

PR #10491 (spec + seal).

Done when

Spec parses, its tests pass, seal saved; required checks green.

How to verify

./target/release/t27c test-report specs/automation/app-tabs.t27

Risks

None beyond the spec itself; the change is one spec and its seal.

Links (issue, PR, ADR)

PR #10491; service spec PR #10484.

User Scenarios

  • Given the TRI CLAW MCP service spec exists at specs/t27mcp/service.t27, when the app-tabs.t27 spec is written, then every app tab is mapped to the tools serving it at /mcp with links labelled EXACT or SUGGESTED.
  • Given the app-tabs.t27 spec is complete, when the compiler runs its test report, then gaps (routes with no tool) and unmapped HUD views are explicitly listed in the spec output.

Requirements

  • FR-001: The spec specs/automation/app-tabs.t27 MUST enumerate every application tab and associate each with the TRI CLAW /mcp tools that serve it.
  • FR-002: Each tab-to-tool link MUST be labelled EXACT or SUGGESTED.
  • FR-003: The spec MUST list all gaps where a tab reads a route that no tool serves.
  • FR-004: The spec MUST list all unmapped HUD views.
  • FR-005: The spec MUST parse and pass its tests via t27c test-report.
  • FR-006: A seal file MUST be saved for the spec as part of the deliverable.

Success Criteria

  • ./target/release/t27c test-report specs/automation/app-tabs.t27 exits with exit 0
  • The spec file specs/automation/app-tabs.t27 exists and contains mappings for all app tabs
  • The seal for specs/automation/app-tabs.t27 is present in .trinity/seals/
  • Required CI checks pass (green)

Boundary

  • specs/automation/app-tabs.t27
  • specs/t27mcp/service.t27
  • .trinity/seals/Tools.json

Activity

  1. added a commit that references this issue on Oct 18, 2026
    28a7cff
  2. added
    shape-refusedClosed by the issue-shape gate (specs/policy/issue_shape.t27); a passing edit reopens it
    on Oct 18, 2026
  3. github-actions commented on Oct 18, 2026

    @github-actions
    Contributor

    Closed by the issue-shape gate (specs/policy/issue_shape.t27, #7498): an issue must have the template's sections. Edit the body; an edit that passes reopens it.

    • missing: ## Boundary -- list every file this task may touch, one per line (- specs/x.t27); without it the Queen reserves nothing and no bee can take the issue
    • missing: ## User Scenarios -- at least one Given/When/Then scenario
    • missing: ## Requirements -- numbered obligations, FR-001: ... MUST ...
    • missing: ## Success Criteria -- an outcome a machine can settle: a number with a unit, a backticked file, exit 0, or a backticked command
  4. added a commit that references this issue on Oct 18, 2026
    3934062
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

    phi-loopPHI LOOP development cyclequeen-shapedshape-refusedClosed by the issue-shape gate (specs/policy/issue_shape.t27); a passing edit reopens itspec-task

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions