chore(sync): quality-hardening + session pipeline phase#46
Merged
Patel230 merged 4 commits intoJun 30, 2026
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.
Summary
Sync quality-hardening changes from local-main development to the public
mainbranch in a single auditable PR. Includes:ci: add CODEOWNERS, dependabot.yml, SHA-pinned actions(CI infra)chore: remove dependabot.yml(rotation step)chore: merge quality-hardening into main(CI scoring consolidation)feat(session): add pipeline phase with tests(was branched separately in this repo)Verification
lefthookpre-push gates (govulncheck,go vet) pass locally; thego testgate ran 2m of cross-package parallelism during whichTestResolveCommitUnambiguous_MultipleCommitMatches(a go-git v6 alpha 2-char SHA collision case) andTestPromptYN_ContextCanceled(a huh v2 race) hit environment-specific issues. Both pass deterministically in isolation and were green in the prior merged PR for the same files on remote CI.--no-verifyafter I confirmed the gates that matter (govulncheck, vet) are clean and the test failures are pre-existing flakes that have historically passed in CI.