Repository navigation
ci: install canonical routine eligibility producer - #460
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.
Install the first routine-eligibility producer using the closed five-file installation predicate in work-roadmap and tools/routine-delivery.py. All five added files preserve their Git blob identities and modes from protected FS-GG/.github commit
3d9bf3280de22d8d391edcf71dcfdedbf56325cd. Governance main currently has none of these files and no native routine producer. PR459 remains independent and unchanged.Preflight: static byte/mode equality, exact five additions, disjoint PR459 paths, and diff whitespace checks. Existing routine-eligibility and claim-generation fixtures exercise exact-head refusal, base-loaded execution, and protected-operation refusal. A custom pipeline model is deferred for this literal canonical copy; required hosted checks and exact-head coordination-coherence qualification remain mandatory.
Installation delivers source with activation pending. Subsequent genuine routine PR observation is still required. The parent integrator owns final installation inspection/apply and merge; no publication is requested.