Keep replaced tab navigation owners from overwriting newer state

This commit is contained in:
2026-11-08 01:09:19 +00:00
parent a352593aed
commit 1ed58126da
3 changed files with 104 additions and 2 deletions
+14
View File
@@ -37,3 +37,17 @@ and scroll offsets are not serialized by this store. Their existing mounted
state remains intact within a session. Settings inner-topic persistence is a
separate companion change. Manager-owned integrated browser capture/build and
publication are still required; this lane did not deploy or restart anything.
## Replacement-owner write ordering
A disposed owner skips writes that have not started, including operations queued
behind another storage owner. Already-started operations share a small per-key
read/write order with replacement owners; replacement reads wait for an old
in-flight write before merging and saving newer navigation. Idle operation keys
are removed, and a failure never poisons later operations.
18 focused tab/controller/full-app navigation cases passed after this follow-up
(`/tmp/memwatch/out.hBbm4Y`), including a blocked old write plus a queued old write,
disposal, replacement navigation and delayed release. The newer state wins for
both an in-memory store and distinct SharedPreferences store instances sharing
a logical key. Two independent ordering-helper tests passed (`out.FffOAC`).