user-interface: offer to install and onboard a better design tool #6449

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 5, 2026
2. github-actions commented on Oct 5, 2026

   

   github-actionsBot

   on Oct 5, 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.}
3. 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 5, 2026
4. 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
5. kyle-sexton

   added the

   Feature

   issue type on Oct 12, 2026
6. 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.

   • Where do the install command and sign-in step live? → the row's existing pointer (vendor setup page)
     Basis: .claude/rules/skill-bodies-state-current-rules.md (point at live upstream source); plugins/user-interface/reference/routing.json note ('every other row does [carry a pointer]')
   • Does the offer cover paid rows? → only when no free row covers the concern
     Basis: plugins/user-interface/skills/design/SKILL.md 'Combine routes and settle conflicts' (cited in issue); judgment
   • How does a row move from deferred to confirmed? → after a recorded end-to-end onboarding test, with as_of updated
     Basis: plugins/user-interface/reference/routing.json (status, as_of fields); issue acceptance; judgment

   Wants /user-interface:design to offer installing a higher-ranked uninstalled route, with sign-in, only on the user's yes, and to onboard one account-bound route end to end. The account-bound rows in routing.json are all deferred, while the acceptance limits the offer to non-deferred rows, so nothing is offerable until one row is onboarded and confirmed.

   Verification notes:

   • Minor: not every account-bound row is deferred. The built-in Artifact tool row (account login) is confirmed, but it is not installable, so the record's point holds for installable rows.
   • Q2 already matches main: design/SKILL.md:68 says a paid row is suggested only when no free row covers the concern.

   Verified by an independent fresh-context check (confirmed, risk low): gh issue view 6449 (open, no owner decision); origin/main plugins/user-interface/reference/routing.json: version 2; every installable account-bound row (figma, subframe, supernova, stitch, magic, pencil, paper, brilliant, etc.) status deferred, with pointer and as_of 2026-10-04; origin/main design/SKILL.md:62-68 (installed, not deferred, paid only when no free row); docs/conventions/routing-as-data/README.md:61-62: version changes only when the row contract changes - assumption true; a new command field would be a contract change, which supports Q1

   Admission to an agent lane stays with the work-class rules and owner ratification.