Repository navigation
Install canonical routine eligibility producer - #44
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.
Install the missing routine eligibility producer using exactly five files from protected FS-GG/.github
416381bc4da37cb5089da08a45282e2222104c27. All payload bytes and modes match that immutable canonical source; the receiver protected base43a847a55e21ba75e3ee7b8310a16ade17789040contains none of these files, and the native producer workflow returned HTTP 404.Validation: copied canonical claim-generation fixtures passed all 59 controls; canonical offline delivery/security tests passed. Full receiver CI remains required. Root will evaluate this dedicated first installation through the canonical install route after exact-head CI passes. Ordinary routine eligibility remains unavailable for this bootstrap PR; native activation requires a subsequent genuine routine PR event.