docs(roadmap): record export lifetime and retention qualifications
This commit is contained in:
@@ -1,6 +1,14 @@
|
||||
# Direct execution continuation
|
||||
|
||||
Current published A3 ref:214eb25fa557841d280b84b41e7f1e028511be7a; application source c6375876. Correspondence recovery, pasted-email recording and open surfaces are qualified within their recorded fixture scopes. Next: remaining Settings/import recovery and connected workflows. No immediate new owner decision is required for that independent work; protected gates remain pending.
|
||||
Current published A3 ref:50e16ff2e1ce29e5956e7609768730baf5c28cce; source2a02e102. Release branch:e1c8e84502e08144a32f496af8b03cb26f0ec815. Export/session and mocked retention failures qualified. Next: singular conversion copy, Rules density/recovery and remaining connected workflows. Existing protected gates unchanged.
|
||||
|
||||
## 11 November export lifetime and retention failure propagation
|
||||
|
||||
- A3 published/ref-readback50e16ff2e1ce29e5956e7609768730baf5c28cce; source2a02e102. Existing import session guard now also protects JSON/CSV export and local CSV conversion across unmount, changed context and invalidation, with current-language delayed feedback.35 cases/four suites, build/TypeScript and lint passed (14 new,21 existing).
|
||||
- Twelve actual UI configurations at390/768/1440 ×EN/NB ×light/dark passed36 native downloads,12 scans and two bounded SPA-unmount probes each. CSV BOM/CRLF/Unicode and JSON bytes matched fixtures; conversion retained Unicode. No API writes/unavailable reads/page exceptions.150 committed source/evidence/export bindings and36 raw/gzip receipts verified. Report A3 docs/ui-modernisation/JOB_EXPORT_LIFETIME.md. Native probes use250ms quiet windows; deterministic unit promises carry complementary lifetime evidence. No real private export or provider/session/security acceptance claimed.
|
||||
- Release published/ref-readbacke1c8e84502e08144a32f496af8b03cb26f0ec815, baseline3cca4418, on codex/release-rollback-health. Worker reproduced daily-prune/monthly-enumeration/sort/monthly-prune failures being masked under conditional Bash invocation. Explicit guards now stop upload/deploy continuation. Backup16/16, rollback6/6, syntax/diff passed; root reviewed exact diff, matched remote and verified three tested raw source identities/check receipts. Tests extract functions and mock pruning/upload; no real deletion, deploy or recovery. A failed real prune may already have removed eligible old files. Actual RR09/12/13 and release gates remain open. Release changes remain on their separate development branch.
|
||||
- New visible-text follow-up: conversion screenshot says one rows /1 rader. Fix singular count wording without changing conversion schema, then continue Rules density/recovery and other eligible IM10 workflows. Protected Phase10 D02/A3/homepage/provider/security/recovery/release gates unchanged.
|
||||
|
||||
|
||||
## 11 November correspondence visual checkpoint
|
||||
|
||||
|
||||
Reference in New Issue
Block a user