Repository navigation
ci: tier browser coverage for development and release checks - #8
Merged
Merged
Conversation
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
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.
Change
Development PRs run twelve critical real-engine browser scenarios, adding all visual comparisons for code or unknown path changes. Documentation-only PRs retain critical workflows without screenshots. Release-targeted PRs, release/main/hotfix pushes, weekly schedules and manual dispatch retain the complete suite. Remove the duplicate develop merge-push run while preserving the required
checksjob.Keep all test assertions and visual baselines. Document coverage selection and deferred scenarios; retain critical failure artifacts separately from the visual run.
Evidence
npm run check: passed, including 118 Vitest and 10 Node checks.git diff --check: passed.Compatibility
No application, saved-format, dependency, engine-pin or baseline changes. Browser workers remain serial. Extended browser coverage is deferred from development PRs to full runs, with all visual comparisons still required for code changes.