fix(replay): expose capture resolution diagnostics - #21
Merged
Conversation
Chinmay-KB
force-pushed
the
fix/replay-coherent-tap-settlement
branch
from
July 25, 2026 16:46
4d59b0c to
de8206a
Compare
Chinmay-KB
force-pushed
the
fix/replay-capture-diagnostics
branch
from
July 25, 2026 16:46
30cc20e to
2d30018
Compare
Chinmay-KB
changed the base branch from
fix/replay-coherent-tap-settlement
to
main
July 25, 2026 19:19
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.
Summary
Replay captures now explain why visual evidence was fresh, reused, unavailable, cancelled, or superseded without leaking pixels, labels, route names, raw errors, or stack traces. Each logical request receives one terminal diagnostic even when multiple requests share a physical capture, so tap, route, and scroll events can be correlated to the exact capture decision instead of inferred from global failure state.
The outcome vocabulary is closed and versioned, cancellation reasons are bounded, and health polling exposes session-scoped counters with fixed growth limits. Active-readback cancellation is waiter-local: cancelling one coalesced request does not cancel or duplicate the sibling result.
Related: #11
Validation
flutter analyzecompleted with no issues.This PR is stacked on #20 and is merge-ready relative to that parent.
Fixes #11.