Take a paired ruling after each restructure of a chunk ruled worse

AGENTS.md

@@ -58,7 +58,7 @@ In `docs/decisions.md`:
 - Plan items rank by `rank_todo.py`'s goal weights, code health first
 - Posts announcing a release wait for its publish, and their drafts wait for the finished release
 - A chunk ruled worse merges where a plan item of its release already restores that code's reading, and that item takes the ruling's places
-- A chunk ruled worse that restructures the places takes a second paired ruling against the same base, and merges where it is not worse
+- A chunk ruled worse that restructures the places takes a paired ruling after each restructure, against the same base, and merges once one is not worse
 - No schema validation
 - The gate runs on Deno and Bun
 - The gate installs the tarball

docs/decisions.md

@@ -707,14 +707,16 @@ unmeasured, and past a pass's round cap it goes unreviewed. Where an item of the
 reworks that code again, restructuring it inside the chunk does the work twice. Before the chunk
 merges, that item's detail names every place the ruling voted worse.
 
-## A chunk ruled worse that restructures the places takes a second paired ruling against the same base, and merges where it is not worse
+## A chunk ruled worse that restructures the places takes a paired ruling after each restructure, against the same base, and merges once one is not worse
 
-2026-10-31, the maintainer, on PR #112: its ruling voted Locality worse, no plan item of its release
-reworked that code, and a restructure after the ruling addressed most of its places. Serves code
-health. Valid while the comprehension check runs once per chunk.
+2026-10-31, widened to each restructure 2026-11-03, the maintainer, on PR #112: its ruling voted
+Locality worse, no plan item of its release reworked that code, and a restructure after the ruling
+addressed most of its places. Serves code health. Valid while the comprehension check runs once per
+chunk.
 
-The second ruling reads the restructured head against the first ruling's base, with the same seats,
-and both rulings stay in the history. A restructure past a pass's round cap still goes unreviewed,
+Each later ruling reads the restructured head against the first ruling's base, with the same seats,
+and every ruling stays in the history. Each restructure runs one rung higher; past the top rung,
+the maintainer decides. A restructure past a pass's round cap still goes unreviewed,
 so the PR summary names it.
 
 ## No schema validation