fix(ci): qualify first release hardening#91
Draft
f0rr0 wants to merge 1 commit into
Draft
Conversation
f0rr0
force-pushed
the
f0rr0/release-hardening-qualification
branch
22 times, most recently
from
July 19, 2026 03:21
c68154b to
a9e9e43
Compare
Bind Windows consumers to verified tool envelopes and make mobile receipt gates fail closed.
f0rr0
force-pushed
the
f0rr0/release-hardening-qualification
branch
from
July 19, 2026 05:15
a9e9e43 to
7bb6680
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.
Purpose
Qualification-only transport for the first-release hardening tree. Do not merge this PR.
This branch exists only so GitHub can exercise the complete release matrix against one immutable candidate. No history repair or publication is authorized by this PR.
Exact Q15 candidate
03c0520c5aca5172d0f28b26cc6beff9f03cc1cb09bb4386242c27251e5b8da11df0d4e4803a3018main:06816d377f96ab8e53d3c6ec8732577cc4386f2evalid, signersid_26@outlook.comFailure-class closure
oliphaunt.dllas their backend provider. Every normal and delay-loadedpostgres.exeimport is rejected. PL/pgSQL must importoliphaunt.dllas the positive provider canary; demand-linked modules may omit an unused provider import, with that classification recorded in the v2 artifact evidence.liboliphaunt.xcframework, never nested slice frameworks.Q14 proved every independent producer except the Windows extension artifact row. That row built all 38 selected DLLs and then exposed an over-strict audit:
earthdistance.dlllegitimately has no backend-provider import because it resolves no backend symbols. Q15 corrects the invariant without weakening thepostgres.exerejection.Local proof for this exact tree
postgres.exeregressions.earthdistance.dllalone was provider-import-free; Q15 uses the scalable linker-semantic rule and PL/pgSQL canary rather than a module allowlist.The protected-main repair and all publication actions remain separate, explicitly approved operations after this exact SHA reaches
Qualified.