Release pass 0.11.0: what an operator now schedules, and the roadmap reconciled - #37
Merged
Merged
Conversation
…the build Exit criteria against what actually ran, not against what the line promised: five released wheels rather than fixtures, the released 0.10.0 from PyPI rather than a store this build wrote and called 0.10.0's, and two prunes racing under the multi-process standard against a real Postgres server. Three sentences are reconciled rather than quietly edited. The anchor does not detect an append, and the bullet said "erased or appended" until today. Coverage does not come from events, because `ACTION_PROPOSED` carries an `action_hash` and nothing that maps it back to a name. And `CONTROL-MAPPING.md` is still not written, which the v0.11 line cited in the present tense. Readiness re-measured, and the version moves to 0.11.0. Signed-off-by: arpan <contact@arpanghoshal.com>
…nscripts `operations.mdx` is the page this milestone most changes and said nothing about either new command. Anchoring and pruning are the two things v0.11 gives an operator to run, and both are runs **their** scheduler makes: nothing sweeps, nothing reaps, and no hold expires, which is the same rule about a timer that `SPEC-v0.9.md` §4 applied to a budget hold. The interval is the claim. An anchor freezes a prefix, so the window you are exposed to is `(last anchored seq, current head]`, and that number is what to quote rather than any sentence about tamper-evidence. Three pages quoted a verify transcript headed `ctrlrun 0.10.0`. The guard that runs verify and compares caught all three. `ROADMAP.md` gains the line about retention shipping twice: the review the build order required for the prune found seven defects, and the merge did not wait for it. `SPEC-v0.11.md` §13.4 has all seven. Readiness re-measured at 6,221 against a checkout carrying the extras CI installs, and `CLAIMS.md` needed no repointing. Signed-off-by: arpan <contact@arpanghoshal.com>
|
Important Review skippedAuto reviews are disabled on base/target branches other than the default branch. Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Advanced Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
This was referenced Sep 14, 2026
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.
Pairs with ctrlrun#206, and stacks on #36.
operations.mdxis the page this milestone most changes and said nothing about either new command. Anchoring and pruning are the two things v0.11 gives an operator to run, and both are runs their scheduler makes. The "there is nothing to run" bullet now says which two commands write, and that no hold expires, which isSPEC-v0.9.md§4's rule about a timer applied unchanged.The interval is the claim. An anchor freezes a prefix, so the window you are exposed to is
(last anchored seq, current head], and that number is what to quote rather than any sentence about tamper-evidence.Three pages quoted a verify transcript headed
ctrlrun 0.10.0. The guard that actually runs verify and compares caught all three.ROADMAP.mdmarks v0.11 shipped, with exit criteria stated as what ran rather than what the line promised, and a "Reconciled against what shipped" block for the four sentences that did not survive the build: the anchor detects truncation and not append; coverage comes from receipts and not events, becauseACTION_PROPOSEDcarries anaction_hashand nothing that maps it back;CONTROL-MAPPING.mdis still not written; and retention shipped twice, because the review the build order made required for the prune found seven defects and the merge did not wait for it.test_release_documents.pyre-pins the README paragraph the kernel rewrapped. Only one of its four lines carries a word the T180 scan looks for, and the allow-list carries only that one, because an entry matching nothing is how a softened allow-list gets caught.Every generator run against the release branch:
CLAIMS.mdneeded no repointing:scripts/repoint-claims.pyre-pointed 0, unresolved 0.git statusin the kernel tree afterwards is clean apart from the commit this pairs with.Do not merge before #36. The tag is the maintainer's.
🤖 Generated with Claude Code