DEDICATED_WORKER mode + persistent OPFS storage, for stories/tests that need identity/spaces to
survive a page reload. A bare createOpfsWorker (HOST mode) spins up one independent OPFS
worker per browser tab with no cross-tab coordination — since OPFS access handles are exclusive
per file across the whole origin, a second tab locks out (see the failure-mode comment on
OpfsWorker.run in @dxos/sql-sqlite). This preset elects a single leader via navigator.locks
(through a coordinator SharedWorker) so follower tabs proxy through the leader instead.
Additional config deep-merged UNDER the persistent/DEDICATED_WORKER settings (which
always win on conflicting keys) — e.g. a caller-supplied runtime.services block.
DEDICATED_WORKER mode + persistent OPFS storage, for stories/tests that need identity/spaces to survive a page reload. A bare
createOpfsWorker(HOST mode) spins up one independent OPFS worker per browser tab with no cross-tab coordination — since OPFS access handles are exclusive per file across the whole origin, a second tab locks out (see the failure-mode comment onOpfsWorker.runin@dxos/sql-sqlite). This preset elects a single leader vianavigator.locks(through a coordinatorSharedWorker) so follower tabs proxy through the leader instead.