test(cv): qualify preview exit across the autosave boundary

2026-10-10 22:06:18 +02:00
parent b5bda1caa5
commit 5d9997f601
2 changed files with 21 additions and 8 deletions
@@ -1,5 +1,11 @@
 # P5-15-01 intermittent observations

+## P5-15-03 temporal qualification successor
+
+The pending-draft preview-exit regression used real time, while the actual editor schedules autosave after 800 ms. A slow assertion can legitimately observe Saved instead of Unsaved. The test now controls that editing-session clock, retains the original pending value/focus/Unsaved/no-write assertions, then crosses the existing debounce boundary and verifies the exact retained headline, expected revision 4, successful Saved state and unchanged editor value. The affected CV/Analytics suites pass 46/46; test count is unchanged. No CV save implementation, timeout or success assertion was weakened.
+
+This establishes the temporal contract and removes the test's dependency on machine speed. It does not reconstruct the historical failing run's missing timing trace: IF-CV-UNSAVED-01 remains OPEN as an incident observation, with this bounded test qualification recorded separately. Preserve a future failing save/version trace if it recurs.
+
 ## IF-CV-UNSAVED-01 — Preview exit “Unsaved” assertion

 **OPEN; cause not established; no CV repair.** PRES-C06/C10/E08. R-01's first complete frontend rerun passed463/failed1 of464. The case `[P5-11 PRES-C06 C10 E08] returning from preview focuses the existing editor without changing the pending draft` failed its `getByText('Unsaved')` assertion in `cv-builder-deep-link.test.tsx` (recorded line751).