Repository navigation
Use proportional CI and restrict automatic deployment to runtime changes - #232
Merged
Merged
Conversation
kinqsradio
changed the base branch from
chore/vertical-architecture-skills
to
main
October 24, 2026 06:07
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.
Known documentation, license and skill changes currently launch all five application CI jobs, and a green main CI can trigger automatic deployment when AUTO_DEPLOY is enabled. This change selects a conservative lightweight lane for those inputs, retains full checks for runtime/shared/unknown changes, and prevents a docs/skills-only success from automatically deploying.
The CI-only delta against #230 remains five files: the project scope map, eight consumer/preflight fixtures, CI and deployment workflows, and the owning development guide. Classification uses complete changed paths rather than line counts or labels. Selection and the final CI result run consistently; failed, cancelled, missing or unexpectedly skipped selected jobs fail the gate. CI/classifier changes and manual dispatch require the full lane.
Automatic deployment additionally requires a successful canonical-main push and a validated scope receipt bound to the exact repository, commit and event. PR artifacts cannot obtain deployment secrets. Server preflight rejects stale, dirty, diverged and foreign-branch states, then fast-forwards only to the selected revision with --no-pull. No reset, clean, production command or secret/settings change is included. Branch protection must require CI result when promoting the workflow; YAML does not configure that repository setting.
Dependency: public skills #8 → #9 → Orbyn #230 → this PR. The base remains company main because #230's branch is on the personal contribution fork; its prerequisite changes appear in the cumulative diff until #230 merges. The five-file overlay is reviewable at https://github.com/kinqsradio/Orbyn-contributions/compare/chore/upstream-maintenance...chore/scoped-ci. After #230 merges, reconcile this branch with its actual merged main revision before evaluating the final diff.
Current head 4f910ba merges #230 head 5ae4d36 without rewriting history. Both consumer PRs contain the same audited 55 skills, 220 managed files and 61 unchanged evaluation definitions, pinned to the actual released public main commit 78761582248b810d97ae19627bff69014cddc6bd. Public PRs #8 and #9 are merged in order and their final main CI is green.
Validation: all eight disposable CI/server-preflight fixtures pass on the current head; exact pin, source/host assets and diff checks pass. The public candidate passes 82 helper tests and hosted Python 3.11/3.13 checks. Hosted CI for this consumer head is pending and must be assessed separately. An earlier full hosted run passed at a446098, but it is not a current-head receipt. Real hosted docs-only skipping and production SSH/deployment are not claimed as tested. No application source, REA engine/adapters/pins, models, private configuration or local output was changed. The human explicitly authorized #8 → #9 → actual merged public pin → #230 → #232. This PR will merge after #230 and current-head checks pass. Product #231 and REA changes remain outside this delivery scope.