Repository navigation
Prepare explicit package-backed Verify provider loader - #462
Draft
EHotwagner wants to merge 5 commits into
Draft
EHotwagner wants to merge 5 commits into
EHotwagner wants to merge 5 commits into
Conversation
This branch has not been deployed
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.
Explicit Verify provider context now decodes the selected immutable schema-2 provenance and independently selected policy with the real SDD codecs, recomputes the complete Config request, and enters the existing non-passing planning path. Standalone provider mode returns input-unavailable until an admitted outer capture lifetime and teardown owner exists. This is a bounded source slice of #423; GOV-423-C2 remains open.
Validation: retained SDD harness run 38717696812, artifact 11964211226, qualifies exact Governance head bf2a368 with locked selected-package restore and the complete Verify suite in Debug and Release: 230 passed and 20 physical cases pending in each configuration. This does not replace the protected whole-solution matrix. Original failed run 38714014821 (fixture indentation; artifact upload failed) remains failed; its retained job log records the first cause. Successor focused run 38714953075 and the full Verify run preserve that history.
BLOCKED: normal Governance gate run 38827725522 confirms NU1101 for Commands absent and NU1102 for Artifacts 2.3.0 unavailable (nearest feed version 2.2.0). Deterministic build, both complete suite jobs, advisory API and committed-lock restore all stop at cold restore; compilation and their test stages were not reached. Required next boundary: normal org-feed availability/readback of Commands and Artifacts 2.3.0, followed by every required Governance gate context (the complete nine-check acceptance set). These exact selected candidate packages are not established publicly available. No merge, gate bypass, package publication or repack is admitted by this PR. The exact 12-package manifest is retained at SDD 1037e0b3c7762fba953157259dbd6da77f53b0f9, tests/fixtures/gov423-loader-package/expected-archives.json; qualified package run 38712477163/artifact 11960638495 SHA256 3f52c77d0d108aad940b594c2ed896eddd3f349d9ffff1cd683155f3c112c377 derives from original source c8aea9289a6cc410f076823bf1219a02314f00a7, run37951954780/artifact11626413573 SHA256 f814c81964b431baea787e30d0c510df93d3bf525a7e51f8de982c26c66e589e.
Outer capture lifetime/teardown, blocked-read/uncertain-close acceptance, real SDD→Verify→GateExecution/evidence acceptance, stronger profiles, C3/C4 and original custody holds remain open. Atlas governance/provider-loader-package-digest-boundary is included; governance/provider-capture-retention-boundary remains applicable. A prepared qualification update remains pending delivery so this draft preserves the qualified exact head.