Repository navigation
docs: refresh the qualification report and the protocol-v3 statements - #187
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
1 participant
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.
Documentation-only refresh after the v2.5.0 publication qualification. No behavior, no AC.
docs/MULTIFORGE-QUALIFICATION.md— rewritten around the real state: delivery record (main8f319ad → 23b59e → 1d412fd → d7b2626 → 2674c43 → 52c05cc, releases v2.4.4 and v2.5.0 with their exact digests), platform matrix now GREEN on the release SHA itself (52 CI jobs on 2674c43, all three OSes), GitHub.com upgraded to qualified-live (full V3 chain + the four update flows), a new published-release update-flow table (2.4.3 fail-closed, bridge refusal, upgrade, apply, rollback, fresh-install smoke, verified bootstrap), and the limitations kept honest (v2.5.0 manifest attestation gap #185, PyPI pending external Trusted Publisher, Multi-Vault GUARDED, Self-Managed/GHES UNTESTED).Protocol statements corrected to the shipped reality (v3 is the current line; v2 is the bridge stop):
README.md/README.fr.md: the update-protocol paragraph.UPDATING.md: the release-assets step (v3 bundle + manifest,--protocol 2bridges) and the upgrade path paragraph.docs/DISTRIBUTION-LIFECYCLE.md: the consumed artifact (external manifest + anchor), the newer-protocol section (including the code a pre-bridge runtime actually prints, per the live E2E), and the versions table (release_v3.BUNDLE_PROTOCOL_VERSION= 3).SUPPORT.md: GitHub.com release source marked qualified live 2026-09-17.Purity (10 tests incl. FR/EN parity), conventions and the version invariants are green locally.