storeRegistry: route ng through @ng-eventually/client (post-merge integration)

Post-merge audit of main's shared-wallet shim: storeRegistry.ts was the only
runtime path still importing `ng` from @ng-org/web directly, bypassing the lib.
Route it through @ng-eventually/client (the ng proxy forwards doc_create /
sparql_update / sparql_query). Now the only @ng-org runtime imports in the app
are the single injection point (ngSession) + documented exceptions (auth-setup,
mock harness) + generated ORM type-only bindings — the decision_2026-06-17
invariant holds again.

Still in-app, to move into the lib later: storeRegistry, AccountContext, the
isolation filter (distinct from the lib's ReadCap filter).

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

src/shared/utils/storeRegistry.ts

@@ -25,7 +25,7 @@
  * against the verified SDK surface but must be validated against a live broker.
  */
 
-import { ng } from '@ng-org/web';
+import { ng } from '@ng-eventually/client';
 import { sessionPromise } from './ngSession';
 import { normalizeUsername } from '../context/AccountContext';