Add post-v1 shared-rule drift guard#3
Merged
Conversation
Owner
Author
|
Follow-up correction: the first shared-rule-drift workflow run failed at startup because the pinned actions/checkout SHA was accidentally truncated to 39 characters. Commit ea1c54c replaced it with the verified full-length actions/checkout v6.0.2 SHA. The rerun completed successfully: https://github.com/Shaelz/codebase-orient-skill/actions/runs/26362866265. No repository Actions/settings change was required. |
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.
Adds deterministic CI validation for the shared canonical/bootstrap rule blocks.
Adds explicit shared-rule markers and aligns the bootstrap embedded shared-rule snapshot to canonical wording. Future bootstrap-generated project-local skill content now receives synchronized shared-rule content; installer behavior is unchanged.
Freezes the former v1 release plan as
docs/releases/v1.0-validation-record.mdwhile leavingdocs/V1_RELEASE_PLAN.mdas a compatibility pointer.Validation performed:
This PR contains post-v1 maintenance hardening only. No merge is requested as part of this task.