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
Add Support for SEP-1036: URL Elicitation to Inspector #929
Scored 8/16 with the priority rubric added to AGENTS.md in #1891, as part of the backlog triage in #1872. Added to project board #28 with Status Incoming — meaning filed and scored but not yet approved for work. A maintainer decides whether it moves to Todo.
Axis
Score
Reasoning
Severity / impact
3/5
A spec capability the Inspector can't exercise. Nothing is broken; a thing servers may now do can't be tested here.
Urgency / staleness
4/5
Tied to a dated external dependency — the SEP, the spec PR, and the SDK change all land on their own schedule, and Inspector support wants to be ready alongside them.
Worth a second look. This issue already carries a p1-high label from an earlier, undocumented priority scheme, which disagrees with the Medium this rubric produces. Worth reconciling: either the old label should go, or severity here is being undercounted.
Scores are a starting point, not a verdict — the rubric is meant to be overruled when it's plainly wrong, provided the reason is written down.
Activity
[-]Add Support for SEP-1036: URL Elicitation[/-][+]Add Support for SEP-1036: URL Elicitation to Inspector[/+]He-Pin commentedon Jan 8, 2026
cliffhall commentedon Aug 1, 2026
Triage: Priority = Medium
Scored 8/16 with the priority rubric added to
AGENTS.mdin #1891, as part of the backlog triage in #1872. Added to project board #28 with Status Incoming — meaning filed and scored but not yet approved for work. A maintainer decides whether it moves to Todo.Related issues. One connected issue:
Scores are a starting point, not a verdict — the rubric is meant to be overruled when it's plainly wrong, provided the reason is written down.