cndgrr 919135db12 the two flags mean one thing by unblocked, and a key set is a set ... B1: deliverable_keys answered a multiset, so a `+` title whose segments normalize to one key made collision_flags find the issue adjacent to itself and chain it to its own number — the comment asked an issue to declare `Blocked by` itself, and two such carriers corrupted the chain between them. The keys are deduped where the set property belongs. B2: window_in_scope excluded only blocked/epic/post-merge, admitting `needs-triage` and label-less issues, so the sweep could add `needs-triage` to an issue and then tell it about a mint-time membership call in the same pass. Both flags now call one unblocked_claimable predicate — #293 D2 corrected gives one gloss on `unblocked` and D3b says D3 uses it. The window log line says "unblocked", not "ready": D3b corrected exactly that wording, and the flag fires on `claimed` too.		2026-08-04 18:54:52 +00:00
..
action.yml	fix: enforce triage author only on issue arrival	2026-07-23 10:31:15 +00:00
issueflow-reconcile.sh	the two flags mean one thing by unblocked, and a key set is a set	2026-08-04 18:54:52 +00:00