Repository navigation
Add verifiable local candidate regression workflow - #7
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
1 participant
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.
Maintainers can now supply a reviewed standalone Playwright candidate and two exact local Git worktrees, run the candidate unchanged, and independently recompute its pre-fix failure/post-fix pass evidence. The CLI verifies reset and native scalar assertions, binds sources/configuration/target fingerprints, retains partial observations on interruption, and treats infrastructure failures as inconclusive.
Also fixes Demo cancellation accepted during initialization without being applied, and documents ordinary-terminal Corepack startup plus complete target preparation. The experiment remains
SPIKE_CONDITIONAL; automatic generation and human effort savings are not claimed.Validation: 82/82 unit/process checks and 4/4 browser checks passed locally; the expanded real Git/Chromium integration also covers partial-attempt retention on cancellation, dirty targets, ordinary exceptions, browser closure and contradictory exports. Parent brand/workspace checks passed. A fresh Git export installed with ordinary-user pnpm 11.19.0 and passed the complete checks and 116-file package archive smoke. Independent code and documentation reviews found no remaining blocker. Both Node 22.23.2 and 24.20.0 jobs passed: https://github.com/AlbertXXuu/ReproLock/actions/runs/33902190829.
Real-case value validation is a separate experiment; merging this source does not grant product GO or change repository visibility.