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
{{ message }}
Repository navigation
user-interface: onboard one account-bound design route end to end and run the offer evals #8987
#6449 builds the offer logic in /user-interface:design and writes its eval cases. Every installable account-bound row in plugins/user-interface/reference/routing.json is deferred, so nothing is offerable until one row is onboarded with a real sign-in. Onboarding needs a person's account, and running the evals is a paid run.
At least one account-bound route is onboarded end to end and marked confirmed.
Onboard one account-bound route end to end with a sign-in, flip it to confirmed with as_of updated, and run the three evals (offer, decline, accept; paid).
The decision settles the open questions. #6449, the blocker, is closed. The work is to onboard the figma@claude-plugins-official route with a host sign-in. The next steps are to flip its three routing.json rows to confirmed with a new as_of, and to post the offer, decline and accept eval results. Those steps need a person's sign-in and a paid run, so they run attended on a host. No charge is added. If the route needs a paid seat, stop and raise it as a cost question.
Released for re-triage under the owner's 2026-10-24 rule: an issue stops for a person only for an intent or vision question, a security call, a host or attended run, or spend outside prepaid credit. The hold label came off and intake triage runs again now; it re-applies a hold, with a numbered question, when one of those applies.
To hold this issue again, add needs-human (or status: needs-decision) and say why in a comment.
Hold restored: the 2026-10-25 release took needs-human off, but this issue does need a person under the owner's stop rule. Reason (attended): "Onboarding needs a person's account, and running the evals is a paid run"; onboard one route "with a sign-in"
Released for re-triage under the owner's standing direction (2026-10-27): a person is involved only for "1. A change to the original intent or vision. 2. A finding during implementation ... that changes the intent, vision or primary design. 3. A real HIGH/CRITICAL security or cost risk", where cost is anything that can bill (Azure, GitHub larger runners or private-repo Actions, paid storage, plan or seat changes) and model usage under the subscriptions or API credits is not cost. None applies here. The hold label came off and intake triage runs again; an open blocked-by edge, if any, makes admission wait for that blocker.
To hold this issue again, add needs-human (or status: needs-decision) and name which of the three applies.
Refinement. A read-only run explored this repository, searched its issues and pull requests, and read the allowed docs to draft what follows. On an issue a listed human filed, it counts as the issue's spec once posted, while unedited; it is still model text, so check it.
Intended outcome: After #6449 lands the offer logic, one account-bound row in plugins/user-interface/reference/routing.json is onboarded with a real sign-in, set to confirmed with as_of updated, and the offer, decline and accept evals are run.
Dependencies
#6449: builds the offer logic and eval cases this issue exercises; still open
Which single account-bound row should be onboarded, and whose account is used for the sign-in?
RECOMMENDED: figma@claude-plugins-official (account login, deferred, listed under three concerns) Basis: plugins/user-interface/reference/routing.json:12
Is a person's sign-in and a paid eval run in scope for an unattended lane? The body has no task list, so admission cannot split those items off.
RECOMMENDED: No: rewrite the body as a task list with the sign-in, the row flip and the eval run as separate done-when items, so a person does the sign-in and eval run. Basis: judgment
Should this wait for #6667, which also confirms deferred rows, so the two do not edit the same row?
RECOMMENDED: Yes: settle the overlap first, or state that this issue owns only the one chosen row. Basis: 6667
Sources read
/home/runner/work/_temp/refine-data/context.json: issue 8987 has no task list, is blocked by #6449, and needs a sign-in plus a paid eval run
plugins/user-interface/reference/routing.json:12: figma@claude-plugins-official is account login, status deferred, as_of 2026-10-04
To answer, post a comment that starts with this line:
**Decision recorded.** <answer>
Automated refinement by the lanes App. Answer with a comment whose first line is **Decision recorded.**.
Re-triage. Not an owner stop. The eval run spends model credit, which the owner's rule does not count as cost, and the sign-in is an attended host step, not an intent, design or security decision. The issue waits on #6449, which is still open and already linked as its blocker.
The refinement's open questions, settled from the repository:
Which row: figma@claude-plugins-official. It is the highest-ranked installable account-bound row, account: login, status: deferred, and it appears under three concerns (plugins/user-interface/reference/routing.json:12, :30, :42). The Artifact row is already confirmed but is a built-in tool, not an installable route.
Who signs in: the host run on the owner's machine, with an account the operator already uses. It uses Figma's remote MCP server, which Figma lists as available on the free Starter plan (https://help.figma.com/hc/en-us/articles/32132100833559-Guide-to-the-Figma-MCP-server; the desktop server needs a paid Dev or Full seat). No seat or plan is bought. The host runner records which account type was used and never stores a credential. host-run is added so the issue lane does not pick this up.
figma@claude-plugins-official is installed and signed in on a host through the remote MCP server on a free plan, with no seat or plan purchase (if the route turns out to need a paid seat, stop and bring that to the owner as a cost question), and /user-interface:design offers it for a typography-color, design-systems or design-tool-handoff request.
Its three rows in plugins/user-interface/reference/routing.json read status: confirmed, with as_of set to the run date.
figma@claude-plugins-official is installed and signed in on a host through the remote MCP server on a free plan, with no seat or plan purchase (if the route turns out to need a paid seat, stop and bring that to the owner as a cost question), and /user-interface:design offers it for a typography-color, design-systems or design-tool-handoff request.
Its three rows in plugins/user-interface/reference/routing.json read status: confirmed, with as_of set to the run date.
Route: every criterion needs a person's sign-in or a live eval run. The issue carries attended, which admission refuses (.github/actions/resolve-config/admission-rules.json:9), so the issue lane does not pick it up.
Activity
github-actions commentedon Oct 22, 2026
Proposed work class: work-class: scoped
Basis: automated intake triage; the lanes App applied this class.
Size: Small
Complexity: Low
Uncertainty: Knowable
Flags: none
Blocked by: none
#8987 (comment)
The decision settles the open questions. #6449, the blocker, is closed. The work is to onboard the
figma@claude-plugins-officialroute with a host sign-in. The next steps are to flip its threerouting.jsonrows toconfirmedwith a newas_of, and to post the offer, decline and accept eval results. Those steps need a person's sign-in and a paid run, so they run attended on a host. No charge is added. If the route needs a paid seat, stop and raise it as a cost question.Automated triage, applied by the lanes App.
kyle-sexton commentedon Oct 25, 2026
Released for re-triage under the owner's 2026-10-24 rule: an issue stops for a person only for an intent or vision question, a security call, a host or attended run, or spend outside prepaid credit. The hold label came off and intake triage runs again now; it re-applies a hold, with a numbered question, when one of those applies.
To hold this issue again, add
needs-human(orstatus: needs-decision) and say why in a comment.kyle-sexton commentedon Oct 25, 2026
Hold restored: the 2026-10-25 release took
needs-humanoff, but this issue does need a person under the owner's stop rule. Reason (attended): "Onboarding needs a person's account, and running the evals is a paid run"; onboard one route "with a sign-in"kyle-sexton commentedon Oct 27, 2026
Released for re-triage under the owner's standing direction (2026-10-27): a person is involved only for "1. A change to the original intent or vision. 2. A finding during implementation ... that changes the intent, vision or primary design. 3. A real HIGH/CRITICAL security or cost risk", where cost is anything that can bill (Azure, GitHub larger runners or private-repo Actions, paid storage, plan or seat changes) and model usage under the subscriptions or API credits is not cost. None applies here. The hold label came off and intake triage runs again; an open blocked-by edge, if any, makes admission wait for that blocker.
To hold this issue again, add
needs-human(orstatus: needs-decision) and name which of the three applies.3 remaining items
melodic-automation-lanes commentedon Oct 27, 2026
Refinement. A read-only run explored this repository, searched its issues and pull requests, and read the allowed docs to draft what follows. On an issue a listed human filed, it counts as the issue's spec once posted, while unedited; it is still model text, so check it.
Intended outcome: After #6449 lands the offer logic, one account-bound row in plugins/user-interface/reference/routing.json is onboarded with a real sign-in, set to confirmed with as_of updated, and the offer, decline and accept evals are run.
Dependencies
Related work
Open questions
RECOMMENDED: figma@claude-plugins-official (account login, deferred, listed under three concerns) Basis: plugins/user-interface/reference/routing.json:12
RECOMMENDED: No: rewrite the body as a task list with the sign-in, the row flip and the eval run as separate done-when items, so a person does the sign-in and eval run. Basis: judgment
RECOMMENDED: Yes: settle the overlap first, or state that this issue owns only the one chosen row. Basis: 6667
Sources read
To answer, post a comment that starts with this line:
Automated refinement by the lanes App. Answer with a comment whose first line is
**Decision recorded.**.kyle-sexton commentedon Oct 28, 2026
Re-triage. Not an owner stop. The eval run spends model credit, which the owner's rule does not count as cost, and the sign-in is an attended host step, not an intent, design or security decision. The issue waits on #6449, which is still open and already linked as its blocker.
The refinement's open questions, settled from the repository:
figma@claude-plugins-official. It is the highest-ranked installable account-bound row,account: login,status: deferred, and it appears under three concerns (plugins/user-interface/reference/routing.json:12,:30,:42). TheArtifactrow is alreadyconfirmedbut is a built-in tool, not an installable route.host-runis added so the issue lane does not pick this up.Acceptance criteria (run once #6449 is closed):
figma@claude-plugins-officialis installed and signed in on a host through the remote MCP server on a free plan, with no seat or plan purchase (if the route turns out to need a paid seat, stop and bring that to the owner as a cost question), and/user-interface:designoffers it for a typography-color, design-systems or design-tool-handoff request.plugins/user-interface/reference/routing.jsonreadstatus: confirmed, withas_ofset to the run date.kyle-sexton commentedon Nov 1, 2026
Decision recorded.
The blocker #6449 closed as completed on 2026-10-29, so the 2026-10-28 criteria can run now, on an attended host run.
Issue Triage session decision on evidence, read at origin/main
75087c11f4.Blocker: the body's
Blocked by: #6449; user-interface: offer to install and onboard a better design tool #6449 closed as completed 2026-10-29T14:03:49Z.The 2026-10-28 re-triage settled the 2026-10-27 refinement questions: the row is
figma@claude-plugins-official(plugins/user-interface/reference/routing.json:12,:30,:42, each stillstatus: deferred,as_of: 2026-10-04), the sign-in is on a host, and user-experience: install-test and confirm the unconfirmed and deferred route rows #6667 is closed (completed 2026-10-28). Its criteria stand unchanged:figma@claude-plugins-officialis installed and signed in on a host through the remote MCP server on a free plan, with no seat or plan purchase (if the route turns out to need a paid seat, stop and bring that to the owner as a cost question), and/user-interface:designoffers it for a typography-color, design-systems or design-tool-handoff request.Its three rows in
plugins/user-interface/reference/routing.jsonreadstatus: confirmed, withas_ofset to the run date.The offer, decline and accept evals from user-interface: offer to install and onboard a better design tool #6449 run on the subscription login, and each result is posted here.
Route: every criterion needs a person's sign-in or a live eval run. The issue carries
attended, which admission refuses (.github/actions/resolve-config/admission-rules.json:9), so the issue lane does not pick it up.github-actions commentedon Nov 1, 2026
The triage sweep dispatched intake triage for this issue (attempt 1 of 2).