test: reconnexion « relit ses propres données » — VERT, retrait de @wip (bug résolu)

Le bug de reconnexion (page fraîche même identité relit vide) est RÉSOLU côté lib
(résolution de compte déterministe + dé-dup des ensureAccount concurrents). Le
scénario passe 2/2 sur broker réel → retrait de @wip (redevient @data bloquant),
en-tête corrigé. `storeRegistry.ts` : config `provisionRetry` (retry anti-fork).

Non-régression vérifiée : isolation + inscription verts.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

src/shared/utils/storeRegistry.ts

@@ -53,6 +53,13 @@ configureStoreRegistry({
   },
   // The app maps its username handle to the identity id the lib keys on.
   normalizeId: normalizeUsername,
+  // Anti-fork bounded retry (real broker): on a fresh page over the persistent
+  // wallet (reconnection under the SAME identity) the shim may not be synced when
+  // the first read fires → 0 rows. Without this, the registry would provision a
+  // NEW account (a fork), so the fresh page reads its own data as empty. The
+  // bounded backoff waits the sync-lag window out before concluding "genuinely
+  // new". Bounded (never an open-ended broker poll).
+  provisionRetry: { attempts: 8, baseMs: 150, maxStepMs: 2000 },
 });
 
 // --- Re-export the lib's account record + registry surface (unchanged API) ---