Repository navigation
chore: enforce governed development quality - #152
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.
Intent
Make
nestjs-yalcexplicitly Git-tracked and AI-managed, and establish a rigorous, independently reviewed delivery standard before the pending audit-retention change is delivered.Risk and compatibility
No runtime or public API behavior changes. This updates repository governance, contributor instructions, the PR template, and the Syncwheel control manifest. The already-merged
release-root-versionstack is removed from the active manifest; its remote branch is intentionally retained for the later approved cleanup manifest.Validation evidence
JEST_WORKERS=50% npm run ci:checkspassed on commit1ff84c6e3c40105ffe6ab76044af61a3e31e71d1Commands and results:
Independent review
A Luna xhigh reviewer is assessing the current head against the new rubric. Any blocking finding will be fixed on this same branch before merge.
Post-merge enforcement
After this bootstrap PR merges,
devbranch protection will require all eight existing CI jobs, one independent approval made after the latest push, resolved review conversations, and the same rules for administrators.