feat(user-interface): apply team routing in /user-interface:design #7041

Activity

1. github-actions

   added

   needs-triageNot yet classified. Floor until a type and one priority tier are set.Not yet classified. Floor until a type and one priority tier are set.

   on Oct 11, 2026
2. kyle-sexton

   added a commit that references this issue on Oct 11, 2026

   fix(user-interface): confine browserslist reads and check team routin…

   ...

   f6a5a3e
3. github-actions commented on Oct 11, 2026

   

   github-actionsBot

   on Oct 11, 2026 – with GitHub Actions

   Contributor

   More actions

   Thanks for the report. Automated triage handed this issue to a maintainer.

   _{Automated triage. A maintainer reviews it.}
4. github-actions

   added

   needs-humanHuman-in-the-loop required; autonomous sessions must not resolve items carrying this.Human-in-the-loop required; autonomous sessions must not resolve items carrying this.

   on Oct 11, 2026
5. kyle-sexton

   removed

   needs-triageNot yet classified. Floor until a type and one priority tier are set.Not yet classified. Floor until a type and one priority tier are set.

   on Oct 12, 2026
6. kyle-sexton

   added the

   Feature

   issue type on Oct 12, 2026
7. kyle-sexton commented on Oct 13, 2026

   

   kyle-sexton

   on Oct 13, 2026

   MemberAuthor

   More actions

   Decision recorded. The owner approved applying independently verified recommendations on 2026-10-12.

   • Admit feat(user-interface): apply team routing in /user-interface:design #7041 to an agent lane as C3 scoped (clear needs-human, add agent-ready)? → Yes, admit as C3
     Basis: plugins/user-interface/scripts/detect.mjs:249-308 (validated-only); feat(user-interface): apply team routing in /user-interface:design #7041 'Done when'

   #7039 validates the team routing key but nothing applies it, so a team deny has no effect. Done-when criteria and the convention's Team layer rules are stated; nothing on main applies it yet.

   Verified by an independent fresh-context check (confirmed, risk low): origin/main plugins/user-interface/scripts/detect.mjs:249-310 (checkRouting validates, teamOnly routing); origin/main plugins/user-interface/skills/design/SKILL.md: no --config read; origin/main docs/conventions/routing-as-data/README.md:104 'Team layer', :153 adopters row 'validated, but /user-interface:design does not apply it yet'; plugins/user-interface/tests/detect.test.mjs exists; git grep for user-interface detect/routing consumers outside the plugin: docs only (assumption true); gh pr list search 7041: #7039, #7060 merged, nothing applies routing

   Admission to an agent lane stays with the work-class rules and owner ratification.
8. kyle-sexton commented on Oct 13, 2026

   

   kyle-sexton

   on Oct 13, 2026

   MemberAuthor

   More actions

   Owner batch-ratified this admission in an attended session on 2026-10-12: work-class: scoped. Rule: class C1-C3, no trust surface, the independent check confirmed the recorded decision, and no owner step remains.
9. kyle-sexton

   added

   work-class: scopedA briefed fix or small feature; blast radius bounded by the brief, tests exist.A briefed fix or small feature; blast radius bounded by the brief, tests exist.

   agent-readyFully specified and briefed; eligible for autonomous pickup from the frontier.Fully specified and briefed; eligible for autonomous pickup from the frontier.

   priority: mediumReal value, no hard deadline; normal backlog flow.Real value, no hard deadline; normal backlog flow.

   and removed

   needs-humanHuman-in-the-loop required; autonomous sessions must not resolve items carrying this.Human-in-the-loop required; autonomous sessions must not resolve items carrying this.

   agent-readyFully specified and briefed; eligible for autonomous pickup from the frontier.Fully specified and briefed; eligible for autonomous pickup from the frontier.

   on Oct 13, 2026
10. kyle-sexton commented on Oct 18, 2026

    

    kyle-sexton

    on Oct 18, 2026

    MemberAuthor

    More actions

    Agent Brief

    Type: Feature
    Summary: Apply the user-interface team layer's routing key in /user-interface:design.

    Current behavior:
    The user-interface team layer's routing key (rows, disable, deny) is validated by the detect script's config check and shown by setup check, but the detect script computes installed routes from the bundled routing rows only, and the design skill never reads the resolved config. A team routing.deny: [figma] has no effect.

    Desired behavior:
    The resolved routes follow the routing-as-data convention's Team layer: a team row overrides the bundled row with the same concern and id key by key, a new team row adds a route, disable and deny are unions, a route skipped by deny names the team file as its source, and a missing or malformed team file degrades to the bundled routes with a disclosure. The design skill reads the resolved config and names the team file when deny skips a route.

    Key interfaces:

    • The detect script's resolved routes output: includes team routing.
    • The design skill's route source: the resolved config.

    Acceptance criteria:

    • Detect tests cover a team override row, a team-added row, disable, deny with the team file named as source, and a malformed team file that degrades to bundled routes with a disclosure.
    • scripts/run-test-file.sh passes on the detect test file.
    • The design skill reads the resolved config and names the team file when deny skips a route.
    • The validated-only notes in the user-interface README and the routing-as-data adopters row are gone.
    • CI's skill-quality passes on the PR (a PR check; this run does not run it).
    • scripts/check-changelog-fragments.sh passes.

    Out of scope:

    • The repo-wide config shape (feat(conventions): one setup lifecycle for where plugins store team conventions and settings #6594).
    • The bundled routing rows themselves.

    ---

    This was generated by AI during backlog shaping. Held, not admitted: this brief is drafted and checked, but the issue lane would stop on it today. It is admitted, by adding agent-ready, once the lane can run the skill-quality check scripts (Automation Lanes' PR #7912). Held under the owner's 2026-10-18 lane-narrowing course correction.
11. kyle-sexton

    added

    needs-humanHuman-in-the-loop required; autonomous sessions must not resolve items carrying this.Human-in-the-loop required; autonomous sessions must not resolve items carrying this.

    agent-readyFully specified and briefed; eligible for autonomous pickup from the frontier.Fully specified and briefed; eligible for autonomous pickup from the frontier.

    and removed

    needs-humanHuman-in-the-loop required; autonomous sessions must not resolve items carrying this.Human-in-the-loop required; autonomous sessions must not resolve items carrying this.

    on Oct 18, 2026
12. kyle-sexton

    closed this as completedin #8074on Oct 20, 2026