Sylvain Duchesne
4382d04391
Avant : `ensureRepoOpen` résolvait son attente sur le 1er push d'abonnement (= TabInfo, ~1-3ms) — donc AVANT la vraie barrière de sync. Correct par chance sur ce broker (State suit TabInfo d'~1ms), faux si State tarde. Maintenant : - `subscribe.ts` : `docChangeType(resp)` extrait le variant (`State`/`Patch`/ `TabInfo`/…) sans cast `any` ; `subscribeDoc`/`subscribeDocs` le passent en 2e arg NON-cassant (les appelants 0-arg — discovery, inbox — inchangés). - `ensureRepoOpen` n'agit que sur `type === "State"` → attend la vraie barrière. - État de sync par-doc explicite : `getSyncState(nuri): "syncing"|"synced"| "timed-out"|"unknown"`. Le fallback 8s marque `timed-out`, JAMAIS `synced` — les deux ne sont plus confondus (base du futur signal app + du « trop long = signal »). - Fake ng (sans doc_subscribe) : résolution immédiate préservée (bun test intact). gate : tsc propre ; bun test 117 ; test:e2e 39 passed (CONTRAT 3 vert, events=["TabInfo","State"] ; reconnexion cold-read 176ms/10.8s — l'attente du 1er State se déclenche vite, pas de gonflement par timeout). Pas de régression app (le rouge du test reconnexion est pré-existant et broker-lenteur, vérifié sur lib vierge). Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
@ng-eventually/client
Two entry points — the data-plane is SDK-identical, the polyfill bootstrap is separate:
| Import | Surface |
|---|---|
@ng-eventually/client |
The same signature as the SDK — ng, useShape, inbox (+ types). A drop-in for @ng-org/web / @ng-org/orm; as NextGraph matures it resolves to the real SDK (build alias removed) with no code change. |
@ng-eventually/client/polyfill |
The only non-SDK surface — configure, setCurrentUser, and capability helpers (getCaps, grantRead, canRead/canWrite). It falls away as NextGraph matures. |
// bootstrap (the only non-SDK call) — inject the real SDK
import { configure } from "@ng-eventually/client/polyfill";
configure({ ng: realNg, useShape: realUseShape, sharedWallet, currentUser });
// from here on, a pure SDK surface:
import { ng, useShape, inbox } from "@ng-eventually/client";
await ng.doc_create(/* … */);
const set = useShape(MyShape, scope); // filtered to what the identity may read
await inbox.post(targetInbox, ref); // deposit (anticipated SDK API)
What the polyfill adds on top of the real SDK (each emulated for now, native as NextGraph matures):
- Shared-wallet identity (one wallet for everyone; the current identity id is relayed to the SDK).
- Capability enforcement — a read filter + write guard over emulated grants attached to documents; the app declares a document's read policy and issues directed read grants.
- Anticipated methods (inbox
post, capability ops) with their future-SDK shapes, emulated for now.
Generic: no application domain. The consumer application injects its shapes and performs the acts of granting access. The relationship concept ("who is connected to whom") is the consumer application's own — the client exposes only directed per-document read grants.