Guard Y249, Y338, Y339, and Y340 regressions - #121
Open
Parker-fi wants to merge 1 commit into
Open
Conversation
|
|
Parker-fi
force-pushed
the
case/y249-y338-y340
branch
from
August 26, 2026 10:36
cbe4e27 to
a720726
Compare
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.
Coverage
Every fixture and permission precondition is created by the runners before the checkpoints. Y249 is a narrow sentinel because its report has no confirmed fix commit.
Verification
pnpm checkpass.develop, including the browser subscription and all API checkpoints.12407c4092is present/regression;develop(0df82ae7ec) is absent/pass. The comparison has no missing results, harness errors, or gating regressions.