W-F5: refresh safety — write-through vs rename-replace, concurrent-refresh race (gate, runs last) #1160

Open
opened 2026-08-11 22:01:32 +00:00 by shaggy · 0 comments
Collaborator

W-F5 — refresh safety (REV3 deferred rows 5–6): forced OAuth refresh write-through vs rename-replace; instrumented concurrent-refresh race. Highest risk — the one claim the prototype could never evidence. Runs LAST, as its own gate.

Priority raised 2026-08-11: P3's approved architecture (one persistent Pi RPC session per browser conversation) makes N sessions sharing one credentials file the steady state, so concurrent refresh moves from edge case to normal case. Branch feat/wf5-refresh-safety cut at base-pin time.

W-F5 — refresh safety (REV3 deferred rows 5–6): forced OAuth refresh write-through vs rename-replace; instrumented concurrent-refresh race. **Highest risk — the one claim the prototype could never evidence. Runs LAST, as its own gate.** Priority raised 2026-08-11: P3's approved architecture (one persistent Pi RPC session per browser conversation) makes N sessions sharing one credentials file the steady state, so concurrent refresh moves from edge case to normal case. Branch `feat/wf5-refresh-safety` cut at base-pin time.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: mosaicstack/stack#1160