Problem
docs/commands.md was not updated for the actionability gate shipped in 3.1.0 (#316): the /idd-list section (~L117-134) does not mention the gate or the Parked / Needs diagnosis groups, the /idd-implement section does not say a parked or blocked issue now aborts before any branch or comment is created, and the Complexity table (~L252) still has only the three "verdict → next step" rows with no row for a non-routable value. User-facing docs and behaviour have diverged.
Source
Expected
docs/commands.md describes, in one paragraph per consumer, what the gate withholds, what the operator sees (reason + surfaced raw value), and the human remedies (apply/remove parking-lot, clear ### Blocking via idd-update, run /idd-diagnose). The Complexity table gains a "non-routable" row pointing at the reference.
Acceptance criteria
Complexity
Simple — documentation only.
Problem
docs/commands.mdwas not updated for the actionability gate shipped in 3.1.0 (#316): the/idd-listsection (~L117-134) does not mention the gate or the Parked / Needs diagnosis groups, the/idd-implementsection does not say a parked or blocked issue now aborts before any branch or comment is created, and the Complexity table (~L252) still has only the three "verdict → next step" rows with no row for a non-routable value. User-facing docs and behaviour have diverged.Source
plugins/issue-driven-dev/references/actionability-gate.md.Expected
docs/commands.mddescribes, in one paragraph per consumer, what the gate withholds, what the operator sees (reason + surfaced raw value), and the human remedies (apply/removeparking-lot, clear### Blockingvia idd-update, run/idd-diagnose). The Complexity table gains a "non-routable" row pointing at the reference.Acceptance criteria
/idd-list,/idd-implement,/idd-plan,/idd-allsections mention the gatedocs/commands.mdComplexity
Simple — documentation only.