feat!: useShapeQuery prend le Scope du SDK, et un store se nomme par sa reference

packages/polyfill/README.md

@@ -1,7 +1,7 @@
 # @ng-eventually/polyfill
 
 One entry point. Most of what it publishes has the same signature as the future SDK —
-`ng`, `useShape`, `watchShape`, `docs`, `inbox`, `storeRegistry`, `readUnion` (+ types) —
+`ng`, `useShape`, `useShapeQuery`, `docs`, `inbox`, `storeRegistry`, `readUnion` (+ types) —
 and is 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.
 
@@ -34,9 +34,14 @@ import {
 
 configure({ ng: realNg, useShape: realUseShape, getSession, sharedWallet });
 await ensureIdentity();              // who I am (returned), connection work awaited
-const doc = await storeRegistry.createEntityDoc("protected");
+// A store is named by its reference — `doc_create` takes one, and the session is where
+// upstream gets it. Omit it and the document goes to the private store, as upstream does.
+const doc = await storeRegistry.createEntityDoc(await storeRegistry.protectedStore());
 await docs.sparqlUpdate(sid, `INSERT DATA { … }`, doc);
-const subjects = await readUnion(await storeRegistry.listMyEntityDocs("protected"));
+// Reading is by SHAPE, over the SDK's own scope. `did:ng:i` is the whole local dataset;
+// naming documents in `graphs` reads exactly those. There is no "list my documents" call
+// and no way to scope a read by store — neither exists upstream.
+const query = useShapeQuery(NoteShape, { graphs: "did:ng:i" });
 ```
 
 ## Principle — the polyfill compensates, it never extends