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
idd-list: #84's blocked-label and wait-class signals lost their extraction step after the three-signal gate (Blocked-group claim without an operative rule) #337
Before PR #318, idd-list Step 3.7 fed three signals into the Blocked (waiting on external) group: a non-empty ### Blocking section, a blocked label, and a wait-class Suggested-next (cluster UNKNOWN wait / waiting for a collaborator reply). Round 2 rewired Step 3.7 around the shared three-signal gate and kept a sentence saying the blocked label and wait-class signals "only affect Blocked-group placement, not the gate" — but the entry's group is now produced solely by idd_actionability_group, and no step computes those two signals any more.
Effect: an issue carrying a blocked label with an empty ### Blocking section landed in the Blocked group on main and lands in Actionable now after #318, with a lifecycle command attached. This repo has no blocked label today (so nothing changes here), but the plugin ships to repos that use that convention, and the wait-class heuristic is label-independent.
Either restore an operative instruction in Step 3.7 — when GROUP=actionable, a blocked label or a wait-class Suggested-next still moves the entry to the Blocked group with the label name / wait pattern as blocked_reason — and define what the Blocked row prints when $BLOCK_LINE is empty; or delete the two claims and record honestly that #84's two secondary signals were retired in 3.1.0.
Acceptance criteria
Step 3.7 and Step 5 of idd-list/SKILL.md agree on what feeds the Blocked group
A test pins whichever choice is made (label-only issue → Blocked, or claim removed)
CHANGELOG entry
Complexity
Simple — single skill file plus one test assertion; the decision is binary and the #84 contract is already written.
Activity
feat: actionability gate round 3 — per-bullet Blocking reader, undiag…