fix(evidence): retain portable truthful action rows - #10
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
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.
Stack and scope
REC-F08 only. Base branch is recovery/rec-f05 (PR #7), not main: this reuses its verified SQLite constructor-failure cleanup rather than duplicating that fix. Original selected origin/main baseline: d150b78. Merge ordering remains an external decision; orchestrator will not merge.
Authorized fixture copies
The user explicitly authorized exact copies of the two captures required by existing World tests. Originals remain untouched. No assertions were weakened or new skips added.
Windows/Linux CI installs Tesseract for these offline image replays. One unrelated pre-existing private-capture skip remains: test_retained_native_close_roi_matches_independent_button_measurement.
Verification (Python 3.12, offline)
No BlueStacks/ADB/native/device operation or live acceptance occurred. These are offline recovery changes, not route readiness or permission to retry.