@interop/was-react 0.5.0 → 0.6.0

package/README.md

@@ -379,38 +379,44 @@ The MUI entry supplies a router gate and status UI on top of this; see
 
 ## Login flow
 
-Login is driven by CHAPI Verifiable Presentation Requests (VPRs). The
-`useLogin().login()` action (backed by `loginWithWallet`) runs the flow, with a
-`phase` string surfaced for a progress line (`probing` to `storing-key` to
-`requesting-grants` to `verifying`):
+Login is a single CHAPI exchange -- App Connect. The `useLogin().login()` action
+(backed by `loginWithWallet`) runs the flow, with a `phase` string surfaced for
+a progress line (`connecting` to `verifying`):
 
 1. **CHAPI polyfill loads lazily.** The `credential-handler-polyfill` is loaded
    on demand the first time a wallet request is made, not at import time.
-2. **Probe (popup #1).** A VPR asking for DIDAuthentication plus the app's seed
-   credential is sent to the wallet. No credential returned means this is a
-   first run.
-3. **First run: mint and store the seed.** A fresh 32-byte master seed is
-   generated (`crypto.getRandomValues`), a seed credential is self-issued
-   (`issueSeedCredential`, using the configured `credentialType` and `vocabBase`
-   plus the app `origin` anti-phishing bind), and stored in the wallet via
-   `chapiStore`. The flow blocks until the wallet confirms the store -- a
-   dismissed store would silently break cross-device recovery.
-4. **Returning login: recover and verify.** When the probe returns the seed
-   credential, `parseSeedCredential` recovers the seed and cryptographically
-   verifies the credential carries the shared `AppKeyCredential` marker type and
-   is self-issued, origin-bound, and seed-to-DID bound.
-5. **Derive identity.** The stable `did:key` controller and its signer are
+2. **One popup.** A VPR carrying a `DIDAuthentication` query plus one
+   `AppConnectQuery` -- the app's display name, `credentialType`, and
+   `vocabBase`, a `capabilityQuery` entry per configured collection, and a
+   `urn:was:shared-collection` entry per shared collection -- is sent via
+   `navigator.credentials.get` (`buildAppConnectVpr`). A `null` response is a
+   user cancel (`LoginCancelledError`), not an error.
+3. **The wallet matches or mints.** On a first run the wallet generates the
+   32-byte seed itself, self-issues the origin-bound app-key credential, and
+   stores it in its own credential store under the same consent; on a returning
+   visit it matches the stored credential by the shared `AppKeyCredential`
+   marker type, the app's `credentialType`, the requesting origin, and the
+   seed-to-subject binding. The app never mints, and there is no second popup.
+4. **Verify the response.** `verifyLoginPresentation` checks the VP and embedded
+   proofs (purpose `authentication`, matching domain and challenge). A
+   presentation that verifies but carries no seed credential means the wallet
+   predates App Connect: the flow fails closed with `WalletUnsupportedError`
+   rather than degrading into a partial generic flow.
+5. **Recover the seed.** `parseSeedCredential` verifies the returned credential
+   carries the `AppKeyCredential` marker type and is self-issued, origin-bound,
+   and seed-to-DID bound, then recovers the seed.
+6. **Derive identity.** The stable `did:key` controller and its signer are
    derived deterministically from the seed via `CapabilityAgent.fromSeed`
    (`initAppSession` / `deriveIdentity`). The same seed yields the same identity
    on every device.
-6. **Request grants (popup #2).** `buildGrantsVpr` requests a per-collection
-   read/write zcap (plus a read-only space grant) for the controller DID. The
-   wallet provisions the collections and returns a signed presentation.
-7. **Verify the response.** `verifyLoginPresentation` checks the VP and embedded
-   proofs (purpose `authentication`, matching domain and challenge), and
-   `checkGrants` asserts every zcap is controlled by the app DID, shares one
-   space on a single WAS host, and is unexpired. The wallet decides where the
-   user's Space lives; the sync layer derives its target from the grants.
+7. **Check grants.** The delegated zcaps ride in the same presentation's
+   top-level `zcap` array. `checkGrants` asserts every zcap is controlled by the
+   app DID, shares one space on a single WAS host, covers each configured
+   collection's required actions, and is unexpired. A declined shared-collection
+   grant never fails the login. The wallet decides where the user's Space lives;
+   the sync layer derives its target from the grants. The wallet-provided
+   `appConnect: { firstRun }` member surfaces as the `{ firstRun }` the
+   `login()` promise resolves with.
 8. **Activate.** The session (seed, grants, earliest expiry) is persisted to
    IndexedDB, the encrypted local store is opened, the entity stores hydrate,
    and background WAS sync starts.

package/dist/identity/agents.d.ts

@@ -31,8 +31,8 @@
  *
  * Earlier versions used a second identity for app-provisioned collections: a
  * per-collection KAK, HKDF-derived from the master seed under the collection id
- * (`deriveCollectionKeys`, label `kak:v1:<collectionId>`). That derivation still
- * lives in `@interop/wallet-core/identity` but has no caller here. Unifying cost
+ * (`deriveCollectionKeys`, label `kak:v1:<collectionId>`). That derivation has
+ * been removed from `@interop/wallet-core/identity`. Unifying cost
  * the HKDF domain separation between collections -- the identity KAK now reads
  * every collection the app touches. In the multi-recipient model that key only
  * unwraps an epoch secret rather than being the content key, and the seed it was

package/dist/identity/agents.js

@@ -31,8 +31,8 @@
  *
  * Earlier versions used a second identity for app-provisioned collections: a
  * per-collection KAK, HKDF-derived from the master seed under the collection id
- * (`deriveCollectionKeys`, label `kak:v1:<collectionId>`). That derivation still
- * lives in `@interop/wallet-core/identity` but has no caller here. Unifying cost
+ * (`deriveCollectionKeys`, label `kak:v1:<collectionId>`). That derivation has
+ * been removed from `@interop/wallet-core/identity`. Unifying cost
  * the HKDF domain separation between collections -- the identity KAK now reads
  * every collection the app touches. In the multi-recipient model that key only
  * unwraps an epoch secret rather than being the content key, and the seed it was

package/dist/identity/documentLoader.d.ts.map

@@ -1 +1 @@
-{"version":3,"file":"documentLoader.d.ts","sourceRoot":"","sources":["../../src/identity/documentLoader.ts"],"names":[],"mappings":"AAYA;;GAEG;AACH,MAAM,MAAM,cAAc,GAAG,CAAC,GAAG,EAAE,MAAM,KAAK,OAAO,CAAC;IACpD,UAAU,EAAE,MAAM,GAAG,IAAI,CAAA;IACzB,QAAQ,EAAE,OAAO,CAAA;IACjB,WAAW,EAAE,MAAM,CAAA;CACpB,CAAC,CAAA;AAIF;;;;;GAKG;AACH,wBAAgB,oBAAoB,IAAI,cAAc,CAErD"}
+{"version":3,"file":"documentLoader.d.ts","sourceRoot":"","sources":["../../src/identity/documentLoader.ts"],"names":[],"mappings":"AAsBA;;GAEG;AACH,MAAM,MAAM,cAAc,GAAG,CAAC,GAAG,EAAE,MAAM,KAAK,OAAO,CAAC;IACpD,UAAU,EAAE,MAAM,GAAG,IAAI,CAAA;IACzB,QAAQ,EAAE,OAAO,CAAA;IACjB,WAAW,EAAE,MAAM,CAAA;CACpB,CAAC,CAAA;AAeF;;;;;GAKG;AACH,wBAAgB,oBAAoB,IAAI,cAAc,CAErD"}

package/dist/identity/documentLoader.js

@@ -3,13 +3,28 @@
  */
 /**
  * The app's one JSON-LD document loader: static security contexts plus did:key
- * / did:web resolution (`@interop/security-document-loader`). did:web DIDs on
- * loopback hosts (a local dev WAS server on `localhost` or `127.0.0.1`)
- * resolve over plain http; the resolver handles that natively, so no dev shim
- * is needed here.
+ * / did:web / did:webvh resolution. The resolver starts from
+ * `@interop/security-document-loader`'s default did:key + did:web driver set
+ * and adds the `@interop/did-method-webvh` driver, so a wallet may present its
+ * VP holder as a did:webvh (signed with a `<did:webvh>#<key>` verification
+ * method) and verification still resolves it. webvh resolution stays VERIFIED
+ * resolution: the driver's default history-log verifier (hash chain + entry
+ * proofs) is active, so a tampered `did.jsonl` fails closed. DIDs on loopback
+ * hosts (a local dev server) resolve over plain http; both the did:web
+ * resolver and the webvh driver's `did.jsonl` fetch handle that natively, so
+ * no dev shim is needed here.
  */
-import { securityLoader } from '@interop/security-document-loader';
-const baseLoader = securityLoader({ fetchRemoteContexts: true }).build();
+import { createDidWebvhDriver } from '@interop/did-method-webvh/driver';
+import { createDefaultDidResolver, securityLoader } from '@interop/security-document-loader';
+const didResolver = createDefaultDidResolver();
+// The webvh driver is resolution-only (`{ method, get, resolveDID }`) by
+// design; did-io's DidMethodDriver type also demands the key-generation
+// surface (generate, fromKeyPair, ...), which resolution never calls.
+didResolver.use(createDidWebvhDriver());
+const baseLoader = securityLoader({
+    fetchRemoteContexts: true,
+    didResolver
+}).build();
 /**
  * Builds the JSON-LD document loader handed to `@interop/vc` issuance and
  * verifier-core verification.

package/dist/identity/documentLoader.js.map

@@ -1 +1 @@
-{"version":3,"file":"documentLoader.js","sourceRoot":"","sources":["../../src/identity/documentLoader.ts"],"names":[],"mappings":"AAAA;;GAEG;AACH;;;;;;GAMG;AACH,OAAO,EAAE,cAAc,EAAE,MAAM,mCAAmC,CAAA;AAWlE,MAAM,UAAU,GAAG,cAAc,CAAC,EAAE,mBAAmB,EAAE,IAAI,EAAE,CAAC,CAAC,KAAK,EAAE,CAAA;AAExE;;;;;GAKG;AACH,MAAM,UAAU,oBAAoB;IAClC,OAAO,UAA4B,CAAA;AACrC,CAAC"}
+{"version":3,"file":"documentLoader.js","sourceRoot":"","sources":["../../src/identity/documentLoader.ts"],"names":[],"mappings":"AAAA;;GAEG;AACH;;;;;;;;;;;;GAYG;AACH,OAAO,EAAE,oBAAoB,EAAE,MAAM,kCAAkC,CAAA;AACvE,OAAO,EACL,wBAAwB,EACxB,cAAc,EACf,MAAM,mCAAmC,CAAA;AAW1C,MAAM,WAAW,GAAG,wBAAwB,EAAE,CAAA;AAC9C,yEAAyE;AACzE,wEAAwE;AACxE,sEAAsE;AACtE,WAAW,CAAC,GAAG,CACb,oBAAoB,EAAsD,CAC3E,CAAA;AAED,MAAM,UAAU,GAAG,cAAc,CAAC;IAChC,mBAAmB,EAAE,IAAI;IACzB,WAAW;CACZ,CAAC,CAAC,KAAK,EAAE,CAAA;AAEV;;;;;GAKG;AACH,MAAM,UAAU,oBAAoB;IAClC,OAAO,UAA4B,CAAA;AACrC,CAAC"}

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "@interop/was-react",
   "description": "React library for building 'Bring Your Own Everything' (BYOE) apps on Wallet Attached Storage: DID Auth login via CHAPI wallet, local-first encrypted storage, and background sync to a WAS server.",
-  "version": "0.5.0",
+  "version": "0.6.0",
   "type": "module",
   "scripts": {
     "build": "pnpm run clear && tsc",
@@ -47,13 +47,14 @@
   "sideEffects": false,
   "dependencies": {
     "@interop/data-integrity-core": "^8.4.0",
+    "@interop/did-method-webvh": "^5.0.0",
     "@interop/ed25519-signature": "^7.1.4",
     "@interop/ezcap": "^7.4.1",
-    "@interop/security-document-loader": "^9.4.4",
+    "@interop/security-document-loader": "^9.5.0",
     "@interop/vc": "^11.0.6",
     "@interop/verifier-core": "^3.5.0",
     "@interop/wallet-core": "^0.5.0",
-    "@interop/was-client": "^0.20.0",
+    "@interop/was-client": "^0.22.0",
     "@interop/webkms-client": "^14.7.1",
     "@interop/x25519-key-agreement-key": "^5.2.1",
     "@scure/base": "^2.2.0",