[codex] Raise coverage threshold with focused tests#42
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.
Summary
LibrusSession, auth photo CLI paths, render edge cases, and release-notes parsingWhy
Branch coverage was still below the documented target even though the existing suite passed locally. This change closes the known weak branches and makes the coverage gate enforceable in CI.
Validation
npm testnpm run test:coveragenpm run lintnpx prettier --check test/cli-supporting.test.ts test/librus-session.test.ts test/release-notes.test.ts test/render.test.ts vitest.config.tsNotes
npm run format:checkstill reports the unrelated untracked.tasks/README.md, which is intentionally excluded from this PR.