[Replay] Tracker: SDK replay correctness

[Chinmay-KB]

Goal

Track the independently closable work required to restore causal alignment between Flutter navigation, rendered frames, state signatures, target anchors, and interaction outcomes.

This is a coordination-only issue. Do not implement behavior here; implementation belongs in the linked issues.

Progress

Phase 1 — Reproduce and unblock scheduling

• [Replay] Add deterministic characterization tests for event/frame coherence #5
• [Replay] Remove transition waits from the serialized controller queue #6

Phase 2 — Establish coherent route/frame ownership

• [Replay] Replace the pending-route boolean with an awaitable route-capture barrier #7
• [Replay] Track frame provenance and prevent cross-route frame attribution #8
• [Replay] Make forced captures wait for a freshly painted Flutter frame #9

Phase 3 — Correct interaction outcomes and observability

• [Replay] Make tap settlement consume one coherent visual and semantic observation #10
• [Replay] Expose classified capture freshness and reuse diagnostics #11

Phase 4 — Prove the complete pipeline

• [Replay] Add integration coverage for navigation and interaction race matrix #12
• [Replay] Define SDK release and manual production replay acceptance gate #13

Dependency order

#5 characterization harness
 ├─> #6 non-blocking route scheduling
 │    ├─> #7 route-capture barrier
 │    │    ├─> #8 frame provenance
 │    │    └─> #10 coherent tap settlement
 │    └─> #9 fresh painted-frame capture
 ├─────────────────────────────┐
 #8 + #9 + #10 ───────────────> #11 diagnostics
 #5 through #11 ──────────────> #12 integration race matrix
 #12 + SDK/app release ───────> #13 manual production acceptance

Parallel work is allowed only where the linked issue’s prerequisites are already satisfied. Closing this tracker requires all child issues to be closed and the manual production acceptance gate in #13 to be explicitly approved.

Scope boundary

In scope:

• SDK capture scheduling and cancellation;
• route/frame/state provenance;
• tap and settle correlation;
• fresh paint capture behavior;
• privacy-safe degradation diagnostics;
• deterministic tests and production replay acceptance.

Out of scope:

• dashboard post-processing or heuristic repair;
• Context Graph semantic-binding generation;
• continuous/video capture;
• unrelated SDK cleanup.

Completion signal

The milestone is complete only when production sessions from the released SDK no longer show wrong-screen tap markers, destination actions with origin frames, early noVisibleChange followed by delayed navigation, unexplained same-frame visual changes, or unavailable referenced frames.

[Chinmay-KB]

Implementation stack #15-#24 has been merged into main. Child issues #5-#12 are closed. #13 remains open as the manual production replay acceptance gate, so this tracker should remain open until production sessions from the released SDK are sampled and accepted.