Align the cap emulation on NextGraph's model, and confine it to a virtual user

Two batches, verified against nextgraph-rs throughout.

P1a — the capability surface. Reading was an ACL (Map<doc, Set<principal>>),
the exact inversion of key possession. It is now possession: `capFor(nuri)` is
the only question, there is no principal parameter anywhere, and nothing turns
a bare reference into a cap. Sharing is `shareCap(cap, toInbox)`, a Link
deposit; receiving needs no operation. `Nuri` and `ReadCap` are template
literal types, so passing a bare reference where a cap belongs is a compile
error, with runtime guards behind it for JavaScript callers.

The virtual user boundary. Every access function is now confined to the
connected user, through two rules on one criterion (possession), implemented in
two places so a lapse in either is caught by the other: authorization at the
passage points, and "do not even attempt" at the callers. The polyfill's own
machinery moved to physical.ts — unguarded, never exported — which replaced an
exemption list: the machinery no longer gets waved through the guard, it calls
something the guard never saw.

Removed, as emulating capabilities the target does not have:
- discovery.ts and its global index. There is no discovery in NextGraph; you
  follow links. It also pooled user data across wallets.
- the cross-account fan-out (listEntityDocs, resolveReadGraphs, allAccounts,
  loadShim), which was cross-user enumeration by construction.
- resolveInboxAnchor, a single inbox common to every user.

Caps are now stored where NextGraph stores them, and read back rather than
recomputed: AddRepo on the store's Store branch for documents a user creates,
AddLink on its User branch for caps received. Inboxes belong to someone — the
user's own, plus one per document — and connecting a user drains them all;
that is the library's job, not the app's.

Corrections worth recording: a ReadCap is `r:`, not `:k:` (reported by
NextGraph's developer, verified in BlockRef::readcap_nuri); received caps DO
have a register (AddLink), contrary to what this repo's notes claimed; and
"wallet" upstream means keyring — what owns three stores is a user, so the
vocabulary follows.

The cap value is the constant OK: the only question the emulation answers is
whether a cap is held. P1b replaces that one constant with a real key.

After this the shape is right and the isolation is still fake. Nothing here may
be described as anonymous or private.

packages/client/test/access-log.test.ts

@@ -28,6 +28,8 @@ import {
   resetConfig,
   setCurrentUser,
   getCurrentUser,
+  resetCaps,
+  connectedUser,
 } from "../src/polyfill";
 
 // ---------------------------------------------------------------------------
@@ -97,6 +99,17 @@ afterAll(() => {
 // Tests
 // ---------------------------------------------------------------------------
 
+// Two process-wide things bite this suite, which only wants to watch the log:
+//   - the cap registry: once ANY cap exists the reach guard applies to every reader;
+//   - connecting a user does WORK (restore + drain its inbox, see connect.ts), which
+//     both logs and files caps, asynchronously.
+// So: let any in-flight connection finish, THEN clear. Awaiting rather than hoping
+// is what makes this deterministic — `setCurrentUser` is fire-and-forget by design.
+beforeEach(async () => {
+  await connectedUser();
+  resetCaps();
+});
+
 describe("access-log: OFF by default", () => {
   beforeEach(() => {
     // Force the env var OFF for these tests, regardless of the shell environment.
@@ -147,8 +160,10 @@ describe("access-log: OFF by default", () => {
 });
 
 describe("access-log: ON via configure({ debugAccessLog: true })", () => {
-  beforeEach(() => {
+  beforeEach(async () => {
     setCurrentUser("alice");
+    await connectedUser(); // drain the connection work before counting log lines
+    resetCaps();
   });
 
   it("sparqlQuery emits a READ line with identity, nuri, label, and row-count", async () => {
@@ -262,9 +277,11 @@ describe("access-log: identity follows setCurrentUser", () => {
     } finally {
       restore();
     }
-    expect(lines.length).toBe(2);
-    expect(lines[0]).toMatch(/^\[first-user\]\[polyfill\] /); // identity-first, glued [polyfill] prefix
-    expect(lines[1]).toMatch(/^\[second-user\]\[polyfill\] /);
+    // Only this test's own lines: connecting a user legitimately logs its own reads.
+    const mine = lines.filter((l) => l.includes("step1") || l.includes("step2"));
+    expect(mine.length).toBe(2);
+    expect(mine[0]).toMatch(/^\[first-user\]\[polyfill\] /); // identity-first, glued [polyfill] prefix
+    expect(mine[1]).toMatch(/^\[second-user\]\[polyfill\] /);
   });
 
   it("prefix is (none) when no identity is set", async () => {