Repository navigation
Delete the six consumed gunbc#11306 admission rows - #11316
Merged
Merged
Conversation
Contributor
Author
|
The floor red here is expected and must not be "fixed" — fixing it would mean restoring the six rows this PR exists to delete. Measurement is clean: Once #11306 lands, base and head both carry the relocation, the deltas stop being producible, and this diff collapses to the row deletion alone — at which point the rows would report stale and refuse every unrelated PR, which is the trigger this PR discharges. So the sequencing is load-bearing, not a preference: #11306 first, then this. It stays a draft until then. — sent from vivid-stag-90 |
gunbai-bot Bot
pushed a commit
that referenced
this pull request
Sep 14, 2026
The const's prose about what remains used to rot beside the array. Empty-is-not-permissive and the #11306/#11316 inheritance live on gunbc.namespace.transition_admission; this cut still inherits six files or zero, never a pre-migration onto an unlanded PR. Co-authored-by: Cursor <cursoragent@cursor.com>
1 of 2 tasks
gunbai-bot Bot
pushed a commit
that referenced
this pull request
Sep 14, 2026
#11356 landed and retired the gunbc#11193 anchor admission row — the row this branch had already retired when the wall charged it to this touch. The identical deletions reconcile exactly as the standing ruling predicts: the row is gone from both sides and this branch's own six remain. Both sides also independently removed the stale #11182 prose, which is the fourth time that paragraph has been repaired today by two different lanes reaching the same conclusion from the same rule. One sentence of main's is kept rather than dropped with its body: main's revision says empty is the roster's resting state, which is true in general and false in the instant after this merge, since six rows are present. It is folded in as a sentence that stays true either way — the six are consumed by their own merge and #11316 is already authored to delete them, so a populated roster is a transition and never a steady state. Verified by identity: six rows, RepositoryVisibility 1, PublicRepository 2, PrivateRepository 3; no #11193 row and no #11182 prose survives. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01MSpQ3EJ1Nn8V16yEDqbG4F
briansrls
pushed a commit
that referenced
this pull request
Sep 14, 2026
…11345) * Cut the namespace transition-admission roster to directory membership. Delete the hand-Rust const so permission is one .dag file per relocation; appends and consumed deletions no longer collide on a shared array. Co-authored-by: Cursor <cursoragent@cursor.com> * Type expected_candidates as DeclarationRef, not a string list. The wall still joins declaring-module identity; the authored row now names those identities with the same declaration-reference type as enclosing. Co-authored-by: Cursor <cursoragent@cursor.com> * Supersede the const-ness-as-safety claim in the roster carrier. Permission stays authored and reviewable; the vehicle is directory membership, not a const. Missing directory is the empty roster and admits fewer rows, never more. Co-authored-by: Cursor <cursoragent@cursor.com> * Home the empty-roster standing record on the membership module. The const's prose about what remains used to rot beside the array. Empty-is-not-permissive and the #11306/#11316 inheritance live on gunbc.namespace.transition_admission; this cut still inherits six files or zero, never a pre-migration onto an unlanded PR. Co-authored-by: Cursor <cursoragent@cursor.com> * Drop the leftover const census and refuse a phantom candidate leaf. The #11182 permission paragraph had attached to WaveAdmissionPopulation after the const died. Candidate DeclarationRef.decl_name must equal Binding.spelling. Co-authored-by: Cursor <cursoragent@cursor.com> * Enumerate the directory-row parse helpers on the seed census. The bijection sentence on that row was false after the const was replaced; name the helpers the loader actually added. Co-authored-by: Cursor <cursoragent@cursor.com> * Do not re-home the consumed gunbc#11193 admission as a directory row. Co-authored-by: Cursor <cursoragent@cursor.com> #11356 owns that deletion (also carried on #11214). Copying it onto the new carrier would duplicate their receipt and keep a consumed row on a roster touch. * Own the used_row fixture strings; Binding is no longer &'static. Co-authored-by: Cursor <cursoragent@cursor.com> #11250's merge-queue tests used const-roster literals; the directory cut stores owned String. * Stop claiming the admission roster is a .rs file. Row files are .dag and in sweep; roster_touched still reads the unfiltered diff because prefix match is not in_sweep_scope. Co-authored-by: Cursor <cursoragent@cursor.com> --------- Co-authored-by: Brian Searls <briansearls1@gmail.com> Co-authored-by: Cursor <cursoragent@cursor.com>
Their DISSOLVE-ON fired: #11306 merged as 9f5e498, so the repository- visibility relocation is present at the base of every pull_request build, the six TargetChanged deltas are no longer producible, and the rows report CONSUMED — refusing every unrelated PR until they go. Their paragraph goes with them rather than being left describing rows that no longer exist. REBUILT FROM MAIN RATHER THAN MERGED FORWARD. This branch was authored before #11306 landed and had drifted 114 commits behind; merging main into it conflicted on the branch's own stale copies of that PR's files, and its diff against main had become a 715-file, 81k-line revert. A draft in that state is dangerous rather than merely stale, so the branch is reset to main and carries exactly one change: the roster returns to empty, which is its resting state. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
gunbai-bot
Bot
force-pushed
the
session/vivid-stag-90-consumed-rows
branch
from
September 15, 2026 17:12
26b51a4 to
7b22434
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Deletes the six
repository visibility unifies onto its resource module (gunbc#11306)rows fromNAMESPACE_TRANSITION_ADMISSIONS, and the paragraph that stood above them.Their trigger has fired. #11306 merged as
9f5e4988c59, so the repository-visibility relocation is present at the base of everypull_requestbuild, the sixTargetChangeddeltas are no longer producible, and the rows report CONSUMED — at which point they refuse every unrelated PR until they go. They are currently the only rows in the roster, so this returns it to empty, which is its resting state.Rebuilt from
mainrather than merged forward. This branch was authored before #11306 landed, as the consumed-ledger rule requires, and had since drifted 114 commits behind. Mergingmaininto it conflicted on the branch's own stale copies of #11306's files, and its diff againstmainhad become a 715-file, 81k-line revert — a draft in that state is dangerous rather than merely stale, because anything that landed it would undo four days of unrelated work. The branch is therefore reset tomainand carries exactly one change. Its diff is now one file,-88/+1.Why this existed as a draft first.
gunbc.v1_maintenance_standingadmits aNAMESPACE_TRANSITION_ADMISSIONSrow as a consumed ledger entry rather thanMaintenanceRefusal::NewEscapeHatchOrAdmissionRowon the condition that its deletion follow-up is authored before the carrying PR is enqueued and then lands. This PR is that condition, discharged.cargo fmt --all --checkandcargo check -p v1-compilerpass.🤖 Generated with Claude Code