Repository navigation
Finalize RMQ v1.0.0-rc.1 - #5
Merged
Merged
Conversation
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.
Prepare RMQ
1.0.0-rc.1for release with checked client examples, clearer theorem/model guides, canonical rank/select proof reuse, and reproducible source packaging. The Mathlib-free Lean 4.22 footprint, half-open leftmost RMQ semantics, public theorem contracts, and distinctions between formal costs and native behavior are preserved.The release tooling now checks package metadata and checkout byte identities, strengthens current-claim and evidence controls, and retains the source/receipt relationships behind qualification. The fresh Astra audit's P2-01 finding is repaired: a negative scanner case must finish normally with exit 1 and the intended diagnostic; a timeout cannot earn a pass. The tag workflow supplies full history and an external log to the existing checks and marks new RC tags as prereleases.
Validation:
docs/internal/audit_reports/; scope and remaining publication gates are indocs/internal/v1/V1_POST_BLIND_DISPOSITION.md.02cb4e40b4bbd7e07f8b7bb4ad878dcb401c52f8, including cachedlake build, strict claim/design checks, hygiene, paper checks and the full topology regression. All 33 commits passed individual design checks.143fa1e5on both Windows shells (unchanged production inputs transfer to the final source): all 134 policy and 21 context cases have exact expected normal exits, with no timeout or overflow and completed cleanup. Final focused controls passed on pwsh, Windows PowerShell 5.1 and POSIX.Historical failures remain explicit. The older Linux aggregate remains failed; its passing components, separately repaired checks and exact-input transfers are documented, rather than relabeled as a successful final aggregate. Hosted
Lean gateandReproduce artifactmust pass before protected merge. This PR does not promote the RC to stable or authorize retargeting an existing tag.The replacement source archive independently matches all 5,090 tracked Git files, modes and hashes. Its Git-free unpacked smoke passed with the explicitly recorded reused cache; source hashes remained unchanged afterward.
CI follow-up at
697e3f0a91e4aa63d177fead41e50388cd0c02d9: the Windows PR job exposed a fixture that switchedcore.autocrlfwithout materializing the new checkout. The packager correctly rejected its dirty metadata. The test now checks out the fixture after each setting change, invalidates cached stat matches, and asserts clean status before preserving the same archive/blob/mode checks. The production packager and every Lean source are unchanged. The failed hosted run is retained.The focused repair passes all 11 packaging tests under both inherited line-ending settings on Windows and POSIX, checkout-byte controls, cached build, strict claim and per-commit design checks, topology baseline and hygiene. Earlier full regressions retain their recorded commits; they are not presented as new runs. Newly authenticated source/evidence archives and a separate versioned delivery receipt identify the repaired head. Hosted checks must succeed for this updated candidate before merge.