Repository navigation
Conversation
#11347 landed the three bare-name import fixes, so the transition this row admitted is now PRESENT AT THE BASE and there is no delta left for it to admit. A consumed row refuses roster edits and landing (base equals head), so main's push fails namespace-wave-admission until it goes. This is the repayment half of the debt #11347's body declared, paid adjacent to the borrowing rather than deferred: the roster's resting state is empty, and it is a place rows pass through rather than live. Deletes the row and the doc paragraphs that described it -- a surviving doc block above an emptied array would assert a row that no longer exists. The general commentary on consumed rows and the #11182 relocation distinction is untouched. cargo check -p v1-compiler --lib: clean. cargo fmt --all --check: clean. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01D2AF1pri3WJkug5AtCYLGF
…ation set alone" Review 66052, correct and against me. I deleted the doc paragraphs describing my own row and left the neighbouring ones asserting a population the declaration no longer carries: ":1774" "What remains below is the #11182 relocation set alone" ":1803-1809" "these seven still admit a real delta and deleting them would refuse a live transition" Both are false against `&[]`. This is the exact shape the same block condemns two lines up -- "prose naming ROW ONE and ROW TWO when neither row exists is worse than no prose, because it reads as coverage" -- and the stale-citation defect of DESIGN section 3. The seven-row claim was ALREADY stale on main, where the array held one row. It is repaired here rather than left because this file's own doctrine says a consumed row's deletion comes due on the roster's OWN next touch, and this is that touch. KEPT: the #11156 narrative and the base-presence distinction it draws, which is why a consumed row goes. That reasoning is still true and still the point. cargo check -p v1-compiler --lib: clean. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01D2AF1pri3WJkug5AtCYLGF
|
Closing: stale auto-opened PR on It carries nothing main lacks and would be a large revert: the branch is 16 commits behind, and against current main it differs by 141 files / 12,242 deletions — including 237 lines this file has gained on main since #11356 landed. None of that is a change anyone authored here. The admission row it was written to delete is already gone: Deleting the branch so this does not re-open a third time. This is the second instance of the shape today (#11348 was the first) — a squash-merged branch re-proposed against a moved main looks exactly like a catastrophic revert, and it arrives wearing the original work's title. 🤖 Generated with Claude Code |
1 participant
Auto-opened by session-dashboard for session
sunny-carp-329.Pushing to
admission/retire-11193-anchor-rowadvances this PR.Worker attestation
Before flipping this PR to ready for review, confirm each item:
npm test,cargo test) and the result.Closes #Ndirective.Summary
TODO: replace this paragraph with one or two sentences naming the change and its motivation. Reviewers read this first.
Test plan