chore(memory): R3 stopped-state audit and fix recorded (BDR-055, BLK-011)

This commit is contained in:
bchanot committed 2026-10-16 18:27:58 +02:00
1 parent 6371523f8c
commit 9464651140
8 files changed
+228

No files matched your search

+9
View File
@@ -436,3 +436,12 @@ Apply: any reader of user data (R3 SVG, R4 PDF reader, R5 pipeline) → refuse w
- vitest/React: effect with per-render deps (useT closure) + setState(new array) → infinite render loop (OOM); guard side-effectful restore per attempt with a ref.
- Visual parity: freeze happy-dom trees + Chromium screenshots BEFORE switch; same-build double capture gives the noise floor (30/30 identical); synthetic controls validate the comparator; baseline = `git archive develop` built in scratchpad (no worktree).
Apply: R4 PDF reader/writer (byte scanners, inflate), Step 13 uploads (reader in worker child), any parser fed untrusted input.
## LRN-057 | 2026-10-16 | Terminal-failure UX: bind data-safety promises to save status, census every retry surface
- Message promising data kept ("report kept in this tab") must read real persistence status (quota flag); else variant + core-free rescue (download of in-memory state).
- Capped recovery → enumerate EVERY failure surface (grep failure keys, retry handlers, full-page degraded states), not only those the patch touched; enforce with ESLint `no-restricted-syntax` on `t('<key>')` literals (dictionaries untouched, file-scoped exceptions; later block overrides earlier for same rule).
- Each "retry" label needs reachable path to the runtime's recovery; runtime-level restart on next call beats per-surface buttons.
- Rescue must exist in every non-ready state, not only terminal one: a restart loop offline never reaches "stopped".
- Status listeners from a state machine: notify via microtask, try/catch per listener, never inside load/recover try blocks; stable module-scope subscribe for useSyncExternalStore.
Apply: R4 PDF worker failure states, Step 8 avatar upload errors, any capped retry or offline mode.