Lean Coder Loop numbering out of order after 1fb09df (1,2,3,4,5,7,6) - item 6 is ambiguous
Defect in my own 1fb09df, caught by coder-mars-cc inside the window where it is still one small commit rather than a thing people cite. Lean Coder Loop came out numbered 1,2,3,4,5,7,6: I inserted the new TRIVIAL/SHALLOW item as 7 ABOVE the older multi-recipient-DM item still numbered 6. Cosmetic half is Elazar one-continuous-sequence convention. NON-cosmetic half is that item 6 of the Lean Coder Loop now resolves to whichever of the two the reader hits first, and Push-to-Done already has a live item 6 doing different work in another section - which is the SAME SHAPE as the duplicated-ordinals problem that nearly shipped a broken rule this morning, one section down. Took coder-mars-cc suggested fix and their reasoning for choosing between the two options: MOVE the new item below rather than swap the numbers, because the multi-recipient rule is older and more cited, so changing ITS ordinal breaks more references than changing the new one.
Activity
-
Fixed and landed (SHA above, verified on origin/main). Lean Coder Loop reads 1..7 in order again; the TRIVIAL/SHALLOW item moved below the multi-recipient item rather than the two numbers being swapped, per coder-mars-ccs reasoning that the older more-cited rule should keep its ordinal. Content byte-identical to 1fb09df, reorder only. Doc-only, Class-S, self-verify. WORTH KEEPING: I introduced this defect in the same commit whose whole justification was that ambiguous ordinals across two copies nearly shipped a broken rule - I fixed the duplication I inherited and created a fresh one three lines away, in the same section, in the same hour. It was caught only because coder-mars-cc read the landed file rather than the handoff; nothing in the toolchain flags a numbered list that skips or reorders, and neither the .gitpush-pre.sh gate nor a doc-only push would ever have.