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
List enforcement-placing skills and give each one route to the ladder - part 1 of 2 #16028
Part 1 of 2 of #15729, split at intake (owner Q93). The done-when below is copied from #15729 as written.
Done when
AC12 (list and ladder half): every existing skill that recommends, places or builds enforcement or an instruction is on the recorded list with its route: a synced ladder copy plus a Selection rules row, or a call to /corrections:codify.
Every skill routed to a synced copy is named in the ladder's Selection rules table, and the shared-copy sync check passes.
The pull request body names this repository's dogfooding step.
AC7: nothing is cut here, so no control result is owed.
AC10: no new enforcement-placing skill is added here.
Size: Medium
Complexity: Medium
Uncertainty: Knowable
Flags: none
Blocked by: none
Understood: this is part 1 of 2 of #15729, split at intake. It asks that every existing skill that recommends, places or builds enforcement is listed with one route to the enforcement ladder. The route is either a synced ladder copy plus a Selection rules row, or a call to /corrections:codify. The shared-copy sync check must pass, and the pull request body must name the dogfooding step. Nothing is cut and no new skill is added here.
Nothing is missing that blocks triage. The work is to read the skills and settle the list first. Part 2 is #15729's other half, filed as #16029. This is not a duplicate. I found no merged pull request that already does it.
Not admitted to the issue lane yet: blocker #15708 is not closed by a listed human or a merge; blocker #15706 is not closed by a listed human or a merge; blocker #15711 is not closed by a listed human or a merge.
Activity
github-actions commentedon Nov 13, 2026
Size: Medium
Complexity: Medium
Uncertainty: Knowable
Flags: none
Blocked by: none
Understood: this is part 1 of 2 of #15729, split at intake. It asks that every existing skill that recommends, places or builds enforcement is listed with one route to the enforcement ladder. The route is either a synced ladder copy plus a Selection rules row, or a call to
/corrections:codify. The shared-copy sync check must pass, and the pull request body must name the dogfooding step. Nothing is cut and no new skill is added here.Nothing is missing that blocks triage. The work is to read the skills and settle the list first. Part 2 is #15729's other half, filed as #16029. This is not a duplicate. I found no merged pull request that already does it.
Automated triage. A maintainer reviews it.
melodic-automation-lanes commentedon Nov 13, 2026
Not admitted to the issue lane yet: blocker #15708 is not closed by a listed human or a merge; blocker #15706 is not closed by a listed human or a merge; blocker #15711 is not closed by a listed human or a merge.
melodic-automation-lanes commentedon Nov 16, 2026
{"v":1,"actor_id":337595936,"title_sha256":"e31d77e07c171879e6f69d6139845e1f4b359ead0e1ffea34b7c64666f81dca0","body_sha256":"690c4332818864b9a12ba37cc9a6c9b75253cfd538ee18f68fd3dd9e8b3902aa"}
github-actions commentedon Nov 16, 2026