ledger: D/E-NEVER-PIN-BUMP — float-on-main ruling; non_exhaustive rejected#166
Merged
Conversation
non_exhaustive on Function/Model REJECTED by ruling; float-on-main loud-break + fix-forward is the designed drift protection. Meta-Lehre: audit nits are candidates, not decisions. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
|
You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard. |
Bugbot couldn't run - usage limit reachedBugbot is counted against Cursor usage for this user or team, and this run hit a usage or spend limit. A user or team admin can review and increase usage limits in the Cursor dashboard. (requestId: serverGenReqId_75f16e65-a16c-42c7-9aad-a5b4899906ce) |
…follow-up pointer - E-NEVER-PIN-BUMP now follows the ledger's entry contract: dated heading + separate mutable **Status:** line; RULING added to the header's status vocabulary in the same commit (first durable use). - D-NEVER-PIN-BUMP: 'rustdoc note landed in ruff (companion PR)' was premature — no such PR exists; softened to a named follow-up.
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
2 participants
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.
What
Ledger-only: calcifies the operator ruling "wir machen NIEMALS pin bump" (2026-07-06) as
D-NEVER-PIN-BUMP(DISCOVERY-MAP, appended) +E-NEVER-PIN-BUMP(EPIPHANIES, prepended, RULING [G]).Substance
branch = "main"; loud compile breaks + fuses + fix-forward are the designed drift protection (proved twice same-day: ruff fix(adr-025): correct the LOD depth formula — n = 16^r (4×4), not 4-ary #45guarded_writes→ OGAR fix(build): tolerate ruff #45 Function.guarded_writes #162 in minutes).#[non_exhaustive]onruff_spo_triplet::{Function, Model}(the fix(adr-025): correct the LOD depth formula — n = 16^r (4×4), not 4-ary #45 post-merge-audit nit) — it would erase the loud-break signal and permanently tax every construction site org-wide (non_exhaustive forbids struct literals even with..Default::default()outside the defining crate, including ruff's own frontends)...Default::default()(established in fix(build): tolerate ruff #45 Function.guarded_writes #162).No code changes. Append-only ledger discipline observed.
🤖 Generated with Claude Code
https://claude.ai/code/session_01Cg8DSUz1U4AvKqXiy9Xx2f