docs: verify v4.7.5 implementation, fix stale restoreFromSession docstring (v4.7.6) Verification pass over the v4.7.5 background-sync work (save 2ce3e994721e): - vault_locked confirmed in WARNINGS not FAILURES (sync-outcome.ts) - lock() confirmed to no longer clear the MV3 session key; clearSessionKey now only runs on restore-failure hygiene paths - restoreFromSession() confirmed to derive rootKey unconditionally in real mode (no recovery-field gate) - Gates re-run clean: tsc RC=0, full vitest 3679 passed / 40 todo / 0 fail, focused suites 61/61, npm run build RC=0 (chrome+firefox+mobile) One defect found and fixed: restoreFromSession docstring still claimed the session key is 'cleared on lock' — stale after v4.7.5 and a maintenance hazard (invites a future change that re-breaks background sync). Corrected to state the key deliberately survives lock(). Comment-only change; bumped patch for version-tracking discipline. Also commits the v4.7.5 session continuity block that was pending since the last save.

dev · 3 weeks ago · 2026-08-01 · 5.7 MB

$ koh steal kepr.uk/peach-browser@ec56ceb632a1
·
← 2ce3e994721e f17d073716b4 →
⇓ download .face