WIP: Recover presence leases after Redis state loss #47

Draft
KofTwentyTwo wants to merge 6 commits from feature/presence-recovery-1300 into feature/collab
pull from: feature/presence-recovery-1300
6 Commits
Author SHA1 Message Date
james.maesandCodex 776ebe3fcb test(collaboration): verify packaged presence recovery
Co-Authored-By: Codex (GPT-6) <noreply@openai.com>
2026-10-29 09:56:37 -05:00
james.maesandGPT-6 7d987eca2a test: cover shared readiness and partial presence loss
Co-Authored-By: GPT-6 (Codex) <noreply@openai.com>
2026-10-26 07:37:47 -05:00
james.maesandGPT-6 0062644530 test: verify controlled presence restore across JVMs
Co-Authored-By: GPT-6 (Codex) <noreply@openai.com>
2026-10-26 07:31:33 -05:00
james.maesandGPT-6 4b0d6a32d6 perf: avoid repeated table scans during presence recovery
Clean the table when its recovery generation is created, retaining lazy cleanup for record rooms. Add guard-loss regression and diagnostic measurements at 1,000 and 10,000 leases; expose browser profiles and await dashboard redirect before navigation.

Co-Authored-By: GPT-6 (Codex) <noreply@openai.com>
2026-10-26 07:10:54 -05:00
james.maesandGPT-6 1c195d689e test: verify browser presence recovery across JVMs
Exercise unavailable rendering and automatic lease rejoin through actual Chromium and two backend processes after disposable Redis loss. Retain traces and screenshots; frontend serving remains fixture-only and opt-in.

Co-Authored-By: GPT-6 (Codex) <noreply@openai.com>
2026-10-26 06:50:30 -05:00
james.maesandGPT-6 ef2c0c11a0 feat: detect lost Redis presence authority and rejoin
Report unavailable presence during recovery, invalidate stale leases, and isolate controlled restores by host generation. Add store, HTTP and independent-JVM recovery acceptance. Browser, maintenance enforcement and performance qualification remain open in QQQ #1300.

Co-Authored-By: GPT-6 (Codex) <noreply@openai.com>
2026-10-26 06:42:52 -05:00