@voltro/plugin-auth 0.86.0 → 0.88.0

package/README.md

@@ -20,6 +20,21 @@ Installation, guides, the full API reference, and examples all live in the
 **[Voltro documentation](https://docs.voltro.dev/docs/intro/getting-started)** — the single source of truth. This README is
 deliberately short so there is nothing here to drift out of date.
 
+The opt-in `auth.guest` extension adds durable guest device credentials and
+registered sessions. Its current status is **built**; see [Guest
+identities](https://docs.voltro.dev/docs/authentication/guests) for the storage
+contract, trusted transaction-bound account upgrade and remaining validation
+limits.
+
+`@voltro/plugin-auth/guest` provides the same guest client and pure credential
+parser without React or server imports. Possession remains a server SQL check.
+
+`@voltro/plugin-auth/native` also exports `nativeGuestStore`: adapt a supplied
+durable native store and host-wide lock without a memory fallback. Create and
+Resume responses bind the guest subject to the device proof before exposing
+the session or persisting a new proof. Real OS-keystore verification remains
+separate from the port contract.
+
 ## Registered device sessions
 
 `rotateRegisteredSession` replaces a credential atomically and retains inactive
@@ -30,7 +45,75 @@ upgraded auth replicas. See the bilingual
 [session guide](https://docs.voltro.dev/docs/authentication/sessions) for authority
 checks, device families and revocation cache limits.
 
+`lockRegisteredSession(store, userId, sessionId)` reads an owned, unrotated
+credential under the device-family fence. Supply the store of an existing
+transaction, after the application's account/tenant fences, and keep that
+transaction through the protected write. The helper does not validate a signed
+token, expiry or application permissions. Root and presented-row locking reads
+also serve rotation, touch and family revocation; ordinary reads and zero cache
+TTL are not a substitute for native transaction semantics.
+
 ## License
 
 Proprietary. © 2026 Voltro UG. Your use is governed by the
 [Terms of Service](https://voltro.cloud/legal/terms). See the bundled `LICENSE`.
+
+
+### Complete device-family root discovery
+
+Account-wide DataStore registry revocation locks actual user-owned family roots
+in stable order before descendant rows. It never enumerates roots through an
+ordinary older snapshot or rediscoveries after the current-root query. Revoke-other-
+devices resolves its preserved lineage after acquiring the root roster, including
+an owned rotation alias; unknown/foreign keep IDs retain no unverified family.
+
+For an existing transaction, real owner/account fences must precede the registry's
+family fences. New-root issuance must change the same actual owner's persisted
+revision atomically with registration when an older repeatable-read snapshot is
+possible. PostgreSQL row locking alone does not refresh that snapshot. Applications
+owe whole-transaction retry/abort, not a cache workaround or fabricated owner.
+Cloud implements this with private users.sessionFamilyRevision and its existing
+account lifecycle fence. Other custom registries/issuers owe their equivalent
+native contract. Native dialect/rollback/concurrency/replica/restart proof remains
+required. Stop old issuers and apply declared schema before coordinated cutover.
+
+
+### Session reads require the owned canonical family root
+
+`findSession` and `listSessions` return only unrotated credentials whose canonical
+family root exists and has the same `userId`. A rotated root is still a valid
+anchor; its tenant and expiry do not replace those of the current credential.
+Missing, foreign or chained roots are refused without reconstructing any row.
+Custom `SessionStore` implementations must enforce this read contract too.
+Registry and Memory reads reject ambiguous duplicate IDs. PostgreSQL uses a
+single self-join on the actual sessions table for each lookup/enumeration.
+Memory insert/read results copy stored dates rather than exposing mutable
+references. These reads are point-in-time eligibility checks, not a replacement
+for locked current-session validation inside a protected write transaction.
+Positive revocation-cache entries still obey the configured TTL; choose the
+required revocation window explicitly.
+
+
+### Bind a revocation check to the signed user
+
+`makeSessionRevocationChecker(store, options).isLiveFor(sessionId, userId)`
+requires the verified signed user's ID. A live credential owned by another
+user is refused. The cached entry retains the actual row owner; checking a
+wrong user neither authorizes that user nor poisons the owner's verdict.
+`invalidate(sessionId)` clears that credential regardless of requested user.
+Positive freshness is capped by both TTL and observed row expiry.
+
+`SessionRevocationChecker` implementers must provide `isLiveFor`, `invalidate`
+and a finite nonnegative `ttlMs`. The ownerless `isLive` method is removed;
+unsupported objects fail construction rather than becoming cache options.
+Options accept only finite nonnegative `ttlMs`, nonnegative safe-integer
+`maxEntries` and a `now` clock function. Zero `maxEntries` disables caching.
+Normal HTTP auth, carried strategies and Cloud reauthorization/renewal pass
+the verified subject ID. Native root ownership, current account authorization
+and protected write fences remain separate requirements. Existing signed
+payloads and session schemas do not change. Run `voltro update` to receive the
+manual migration instructions for custom checker calls and implementations.
+
+With `requireSessionId: true`, a missing checker fails authentication even if
+the signed payload carries an ID. Wire a store, registry or conforming checker;
+the flag alone does not prove a persisted session.

package/THIRD-PARTY-NOTICES.md

@@ -1,15 +1,15 @@
 # Third-Party Notices — @voltro/plugin-auth
 
-This package uses the open-source software listed below. Each is the
+This package uses the third-party software listed below. Each is the
 property of its respective copyright holders and is used under the terms of
 its license. This file is provided for attribution; it grants no rights in
 @voltro/plugin-auth itself, which is proprietary (see LICENSE).
 
-Generated from the resolved runtime dependency closure (4 packages).
+Generated from the resolved runtime dependency closure (2 packages).
 
 ---
 
-## jose@6.2.12
+## jose@6.2.13
 
 License: MIT
 
@@ -37,214 +37,6 @@ OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
 SOFTWARE.
 ```
 
-## typeid-js@1.2.0
-
-License: Apache-2.0
-
-```
-Apache License
-                           Version 2.0, January 2004
-                        http://www.apache.org/licenses/
-
-   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
-
-   1. Definitions.
-
-      "License" shall mean the terms and conditions for use, reproduction,
-      and distribution as defined by Sections 1 through 9 of this document.
-
-      "Licensor" shall mean the copyright owner or entity authorized by
-      the copyright owner that is granting the License.
-
-      "Legal Entity" shall mean the union of the acting entity and all
-      other entities that control, are controlled by, or are under common
-      control with that entity. For the purposes of this definition,
-      "control" means (i) the power, direct or indirect, to cause the
-      direction or management of such entity, whether by contract or
-      otherwise, or (ii) ownership of fifty percent (50%) or more of the
-      outstanding shares, or (iii) beneficial ownership of such entity.
-
-      "You" (or "Your") shall mean an individual or Legal Entity
-      exercising permissions granted by this License.
-
-      "Source" form shall mean the preferred form for making modifications,
-      including but not limited to software source code, documentation
-      source, and configuration files.
-
-      "Object" form shall mean any form resulting from mechanical
-      transformation or translation of a Source form, including but
-      not limited to compiled object code, generated documentation,
-      and conversions to other media types.
-
-      "Work" shall mean the work of authorship, whether in Source or
-      Object form, made available under the License, as indicated by a
-      copyright notice that is included in or attached to the work
-      (an example is provided in the Appendix below).
-
-      "Derivative Works" shall mean any work, whether in Source or Object
-      form, that is based on (or derived from) the Work and for which the
-      editorial revisions, annotations, elaborations, or other modifications
-      represent, as a whole, an original work of authorship. For the purposes
-      of this License, Derivative Works shall not include works that remain
-      separable from, or merely link (or bind by name) to the interfaces of,
-      the Work and Derivative Works thereof.
-
-      "Contribution" shall mean any work of authorship, including
-      the original version of the Work and any modifications or additions
-      to that Work or Derivative Works thereof, that is intentionally
-      submitted to Licensor for inclusion in the Work by the copyright owner
-      or by an individual or Legal Entity authorized to submit on behalf of
-      the copyright owner. For the purposes of this definition, "submitted"
-      means any form of electronic, verbal, or written communication sent
-      to the Licensor or its representatives, including but not limited to
-      communication on electronic mailing lists, source code control systems,
-      and issue tracking systems that are managed by, or on behalf of, the
-      Licensor for the purpose of discussing and improving the Work, but
-      excluding communication that is conspicuously marked or otherwise
-      designated in writing by the copyright owner as "Not a Contribution."
-
-      "Contributor" shall mean Licensor and any individual or Legal Entity
-      on behalf of whom a Contribution has been received by Licensor and
-      subsequently incorporated within the Work.
-
-   2. Grant of Copyright License. Subject to the terms and conditions of
-      this License, each Contributor hereby grants to You a perpetual,
-      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
-      copyright license to reproduce, prepare Derivative Works of,
-      publicly display, publicly perform, sublicense, and distribute the
-      Work and such Derivative Works in Source or Object form.
-
-   3. Grant of Patent License. Subject to the terms and conditions of
-      this License, each Contributor hereby grants to You a perpetual,
-      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
-      (except as stated in this section) patent license to make, have made,
-      use, offer to sell, sell, import, and otherwise transfer the Work,
-      where such license applies only to those patent claims licensable
-      by such Contributor that are necessarily infringed by their
-      Contribution(s) alone or by combination of their Contribution(s)
-      with the Work to which such Contribution(s) was submitted. If You
-      institute patent litigation against any entity (including a
-      cross-claim or counterclaim in a lawsuit) alleging that the Work
-      or a Contribution incorporated within the Work constitutes direct
-      or contributory patent infringement, then any patent licenses
-      granted to You under this License for that Work shall terminate
-      as of the date such litigation is filed.
-
-   4. Redistribution. You may reproduce and distribute copies of the
-      Work or Derivative Works thereof in any medium, with or without
-      modifications, and in Source or Object form, provided that You
-      meet the following conditions:
-
-      (a) You must give any other recipients of the Work or
-          Derivative Works a copy of this License; and
-
-      (b) You must cause any modified files to carry prominent notices
-          stating that You changed the files; and
-
-      (c) You must retain, in the Source form of any Derivative Works
-          that You distribute, all copyright, patent, trademark, and
-          attribution notices from the Source form of the Work,
-          excluding those notices that do not pertain to any part of
-          the Derivative Works; and
-
-      (d) If the Work includes a "NOTICE" text file as part of its
-          distribution, then any Derivative Works that You distribute must
-          include a readable copy of the attribution notices contained
-          within such NOTICE file, excluding those notices that do not
-          pertain to any part of the Derivative Works, in at least one
-          of the following places: within a NOTICE text file distributed
-          as part of the Derivative Works; within the Source form or
-          documentation, if provided along with the Derivative Works; or,
-          within a display generated by the Derivative Works, if and
-          wherever such third-party notices normally appear. The contents
-          of the NOTICE file are for informational purposes only and
-          do not modify the License. You may add Your own attribution
-          notices within Derivative Works that You distribute, alongside
-          or as an addendum to the NOTICE text from the Work, provided
-          that such additional attribution notices cannot be construed
-          as modifying the License.
-
-      You may add Your own copyright statement to Your modifications and
-      may provide additional or different license terms and conditions
-      for use, reproduction, or distribution of Your modifications, or
-      for any such Derivative Works as a whole, provided Your use,
-      reproduction, and distribution of the Work otherwise complies with
-      the conditions stated in this License.
-
-   5. Submission of Contributions. Unless You explicitly state otherwise,
-      any Contribution intentionally submitted for inclusion in the Work
-      by You to the Licensor shall be under the terms and conditions of
-      this License, without any additional terms or conditions.
-      Notwithstanding the above, nothing herein shall supersede or modify
-      the terms of any separate license agreement you may have executed
-      with Licensor regarding such Contributions.
-
-   6. Trademarks. This License does not grant permission to use the trade
-      names, trademarks, service marks, or product names of the Licensor,
-      except as required for reasonable and customary use in describing the
-      origin of the Work and reproducing the content of the NOTICE file.
-
-   7. Disclaimer of Warranty. Unless required by applicable law or
-      agreed to in writing, Licensor provides the Work (and each
-      Contributor provides its Contributions) on an "AS IS" BASIS,
-      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
-      implied, including, without limitation, any warranties or conditions
-      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
-      PARTICULAR PURPOSE. You are solely responsible for determining the
-      appropriateness of using or redistributing the Work and assume any
-      risks associated with Your exercise of permissions under this License.
-
-   8. Limitation of Liability. In no event and under no legal theory,
-      whether in tort (including negligence), contract, or otherwise,
-      unless required by applicable law (such as deliberate and grossly
-      negligent acts) or agreed to in writing, shall any Contributor be
-      liable to You for damages, including any direct, indirect, special,
-      incidental, or consequential damages of any character arising as a
-      result of this License or out of the use or inability to use the
-      Work (including but not limited to damages for loss of goodwill,
-      work stoppage, computer failure or malfunction, or any and all
-      other commercial damages or losses), even if such Contributor
-      has been advised of the possibility of such damages.
-
-   9. Accepting Warranty or Additional Liability. While redistributing
-      the Work or Derivative Works thereof, You may choose to offer,
-      and charge a fee for, acceptance of support, warranty, indemnity,
-      or other liability obligations and/or rights consistent with this
-      License. However, in accepting such obligations, You may act only
-      on Your own behalf and on Your sole responsibility, not on behalf
-      of any other Contributor, and only if You agree to indemnify,
-      defend, and hold each Contributor harmless for any liability
-      incurred by, or claims asserted against, such Contributor by reason
-      of your accepting any such warranty or additional liability.
-
-   END OF TERMS AND CONDITIONS
-
-   APPENDIX: How to apply the Apache License to your work.
-
-      To apply the Apache License to your work, attach the following
-      boilerplate notice, with the fields enclosed by brackets "[]"
-      replaced with your own identifying information. (Don't include
-      the brackets!)  The text should be enclosed in the appropriate
-      comment syntax for the file format. We also recommend that a
-      file or class name and description of purpose be included on the
-      same "printed page" as the copyright notice for easier
-      identification within third-party archives.
-
-   Copyright [yyyy] [name of copyright owner]
-
-   Licensed under the Apache License, Version 2.0 (the "License");
-   you may not use this file except in compliance with the License.
-   You may obtain a copy of the License at
-
-       http://www.apache.org/licenses/LICENSE-2.0
-
-   Unless required by applicable law or agreed to in writing, software
-   distributed under the License is distributed on an "AS IS" BASIS,
-   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
-   See the License for the specific language governing permissions and
-   limitations under the License.
-```
-
 ## ulid@3.0.2
 
 License: MIT
@@ -273,19 +65,3 @@ OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
 SOFTWARE.
 ```
 
-## uuid@11.1.1
-
-License: MIT
-
-```
-The MIT License (MIT)
-
-Copyright (c) 2010-2020 Robert Kieffer and other contributors
-
-Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:
-
-The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.
-
-THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
-```
-

package/dist/admission.js

@@ -1,9 +1,8 @@
 import { Effect as e } from "effect";
-//#region src/admission.ts
+// src/admission.ts
 var t = (t, n, r = { store: void 0 }) => {
 	if (t === void 0) return e.succeed(null);
 	let i = t(n, r);
 	return e.isEffect(i) ? i : e.promise(() => i);
 };
-//#endregion
 export { t as decideAdmission };

package/dist/appUserStore.js

@@ -1,6 +1,6 @@
 import { memoryUserStore as e } from "./userStore.js";
 import { postgresUserStore as t } from "./postgresUserStore.js";
-//#region src/appUserStore.ts
+// src/appUserStore.ts
 var n = (n = {}) => ({ sql: r }) => r === void 0 ? e() : r.onDialectOrElse({
 	pg: () => t(r, n),
 	orElse: () => {
@@ -15,5 +15,4 @@ var n = (n = {}) => ({ sql: r }) => r === void 0 ? e() : r.onDialectOrElse({
 		return i.apply(r, [...t]);
 	};
 } });
-//#endregion
 export { n as appUserStore, r as deferredUserStore };

package/dist/authExtensions.js

@@ -0,0 +1,8 @@
+import { guestAuthPlugin as e } from "./guestPlugin.js";
+import { overlayAuthPlugin as t } from "./overlayPlugin.js";
+// src/authExtensions.ts
+var n = {
+	guest: e,
+	overlay: t
+};
+export { n as auth };

package/dist/csrf.js

@@ -1,5 +1,5 @@
 import { createHmac as e, randomBytes as t, timingSafeEqual as n } from "node:crypto";
-//#region src/csrf.ts
+// src/csrf.ts
 var r = "voltro:csrf", i = "x-csrf-token", a = (e) => e.toString("base64").replace(/\+/g, "-").replace(/\//g, "_").replace(/=+$/, ""), o = (e) => {
 	let t = e.replace(/-/g, "+").replace(/_/g, "/") + "=".repeat((4 - e.length % 4) % 4);
 	return Buffer.from(t, "base64");
@@ -18,5 +18,4 @@ var r = "voltro:csrf", i = "x-csrf-token", a = (e) => e.toString("base64").repla
 	let i = Buffer.from(e), a = Buffer.from(t);
 	return i.length !== a.length || !n(i, a) ? !1 : l(e, r);
 };
-//#endregion
 export { r as CSRF_COOKIE_NAME, i as CSRF_HEADER_NAME, l as isCsrfTokenWellFormed, c as issueCsrfToken, u as verifyCsrf };

package/dist/emailVerification.js

@@ -1,7 +1,7 @@
 import { newAuthId as e } from "./userStore.js";
 import { hashToken as t, mintToken as n } from "./tokens.js";
 import { Effect as r } from "effect";
-//#region src/emailVerification.ts
+// src/emailVerification.ts
 var i = 60, a = "email_not_verified", o = "emailVerified", s = (e) => e?.policy ?? "off", c = (e) => s(e) !== "off", l = (e, t) => {
 	if (e.emailVerifiedAt != null) return !0;
 	let n = t?.exemptAccountsCreatedBefore;
@@ -22,27 +22,29 @@ var i = 60, a = "email_not_verified", o = "emailVerified", s = (e) => e?.policy
 	body: JSON.stringify(t),
 	contentType: "application/json; charset=utf-8"
 }), p = (e, t, n) => `${e}${t}${t.includes("?") ? "&" : "?"}token=${encodeURIComponent(n)}`, m = (t, i, a) => r.gen(function* () {
-	let o = a.emailVerification, s = (a.now ?? Date.now)(), c = (o?.resendCooldownSeconds ?? 60) * 1e3;
-	if (c > 0) {
+	let o = t.email;
+	if (o === null) return !1;
+	let s = a.emailVerification, c = (a.now ?? Date.now)(), l = (s?.resendCooldownSeconds ?? 60) * 1e3;
+	if (l > 0) {
 		let e = yield* i.latestToken(t.id, "email-verify");
-		if (e && s - e.createdAt.getTime() < c) return !1;
+		if (e && c - e.createdAt.getTime() < l) return !1;
 	}
-	let l = n("email-verify", o?.ttlSeconds ?? 86400);
+	let u = n("email-verify", s?.ttlSeconds ?? 86400);
 	if (yield* i.insertToken({
 		id: e("tok"),
-		tokenHash: l.tokenHash,
+		tokenHash: u.tokenHash,
 		userId: t.id,
 		purpose: "email-verify",
-		expiresAt: l.expiresAt
+		expiresAt: u.expiresAt
 	}).pipe(r.ignore), !a.sendEmail) return !1;
-	let u = p(a.appBaseUrl ?? "", o?.callbackPath ?? "/auth/verify-email/callback", l.token);
+	let d = p(a.appBaseUrl ?? "", s?.callbackPath ?? "/auth/verify-email/callback", u.token);
 	return yield* r.tryPromise(() => a.sendEmail({
-		to: t.email,
+		to: o,
 		kind: "email-verify",
-		actionUrl: u,
+		actionUrl: d,
 		subject: "Confirm your email address",
-		text: `Confirm your email address: ${u}`,
-		html: `<p><a href="${u}">Confirm your email address</a> — this link expires in 24 hours.</p>`
+		text: `Confirm your email address: ${d}`,
+		html: `<p><a href="${d}">Confirm your email address</a> — this link expires in 24 hours.</p>`
 	})).pipe(r.ignore), !0;
 }), h = (e, t, n) => r.gen(function* () {
 	if (!e.email && !e.userId) return f(400, { error: "email or userId required" });
@@ -58,5 +60,4 @@ var i = 60, a = "email_not_verified", o = "emailVerified", s = (e) => e?.policy
 		verified: !0
 	})) : f(401, { error: "invalid or expired token" });
 });
-//#endregion
 export { a as EMAIL_NOT_VERIFIED_CODE, o as EMAIL_VERIFIED_METADATA_KEY, i as EMAIL_VERIFY_RESEND_COOLDOWN_S, c as emailVerificationActive, d as emailVerificationGuard, g as handleEmailVerifyConfirm, h as handleEmailVerifyRequest, u as isEmailVerified, m as sendEmailVerification, l as userEmailVerified };

package/dist/guest.d.ts

@@ -0,0 +1,99 @@
+import { SubjectIdentity } from '@voltro/protocol';
+
+/** Serializes operations in one client. A rejected existing credential never
+ * creates a replacement identity. Storage failures never enable memory fallback. */
+export declare const createGuestClient: (options: GuestClientOptions) => {
+    connect: () => Promise<GuestClientSession>;
+    /** Prepare without replacing the active proof, persist both proofs, then
+     * commit. A later connect recovers the same identity after a lost response. */
+    rotate: () => Promise<GuestClientSession>;
+    /** Revoke on the server first. Keep the durable proof on transport failure
+     * so the caller can retry; erase locally only after confirmed revocation. */
+    revoke: () => Promise<void>;
+    /** Turn this guest into an email/password account under the same subject ID
+     * (`authRoutesPlugin({ guestUpgrade })`). The device proof is erased only after the
+     * server confirmed the account; on any refusal or transport failure it stays. */
+    upgrade: (input: {
+        readonly email: string;
+        readonly password: string;
+    }) => Promise<{
+        readonly subject: unknown;
+    }>;
+    /** The registered account signed in on this device (cookie clients), or null. */
+    account: () => Promise<GuestClientAccount | null>;
+    /** The signed-in account if there is one, else this device's guest (resumed or created once).
+     * The usual entry for a game that offers accounts: a reload after `upgrade` or `signIn` stays the account. */
+    start: () => Promise<GuestClientPlayer>;
+    /** Sign in to an existing account with email and password (`authRoutesPlugin`), e.g. on a second
+     * device. This device's guest proof stays: after `signOut`, `start` resumes that guest. */
+    signIn: (input: {
+        readonly email: string;
+        readonly password: string;
+    }) => Promise<GuestClientAccount>;
+    /** End the account session on the server and clear its cookie. */
+    signOut: () => Promise<void>;
+};
+
+/** A registered account signed in on this device (by upgrade or sign-in), through the session cookie. */
+declare interface GuestClientAccount {
+    readonly subject: Extract<SubjectIdentity, {
+        readonly type: 'user';
+    }>;
+}
+
+export declare class GuestClientError extends Error {
+    readonly code: 'storage_unavailable' | 'credential_rejected' | 'upgrade_conflict' | 'account_signed_in' | 'transport_failed' | 'invalid_response';
+    readonly status?: number | undefined;
+    constructor(code: 'storage_unavailable' | 'credential_rejected' | 'upgrade_conflict' | 'account_signed_in' | 'transport_failed' | 'invalid_response', status?: number | undefined);
+}
+
+export declare interface GuestClientOptions {
+    readonly apiBaseUrl: string;
+    readonly storage: GuestCredentialStore;
+    readonly prefix?: string;
+    readonly fetch?: typeof globalThis.fetch;
+    /** Web clients include cookies and obtain a signed CSRF token for each post. */
+    readonly cookies?: boolean;
+    /** Prefix of the app's auth routes, for `upgrade`, `account`, `signIn` and `signOut` (default `/auth`). */
+    readonly accountPrefix?: string;
+}
+
+/** What `start` found: the signed-in account, else this device's guest. */
+declare type GuestClientPlayer = {
+    readonly kind: 'account';
+    readonly subject: GuestClientAccount['subject'];
+} | {
+    readonly kind: 'guest';
+    readonly subject: GuestClientSession['subject'];
+    readonly session: string;
+};
+
+export declare interface GuestClientSession {
+    readonly subject: Extract<SubjectIdentity, {
+        readonly type: 'user';
+    }> & {
+        readonly kind: 'guest';
+    };
+    readonly session: string;
+}
+
+/** Platform-backed durable secret storage. Native implementations use the
+ * operating system's secure store; writes resolve only after persistence. */
+export declare interface GuestCredentialStore {
+    /** Serialize the whole read/create/write operation across users of this
+     * namespace, including other browser tabs or native client instances. */
+    readonly exclusive: <A>(work: () => Promise<A>) => Promise<A>;
+    readonly read: () => Promise<string | null>;
+    /** Persist the opaque value, including an in-progress rotation journal. */
+    readonly write: (value: string) => Promise<void>;
+    readonly remove: () => Promise<void>;
+}
+
+/** Browser-safe shape only. Possession is verified against SQL on the server. */
+export declare const parseGuestCredential: (credential: string) => {
+    readonly guestId: string;
+    readonly deviceId: string;
+    readonly secret: string;
+} | null;
+
+export { }

package/dist/guest.js

@@ -0,0 +1,3 @@
+import { parseGuestCredential as e } from "./guestCredential.js";
+import { GuestClientError as t, createGuestClient as n } from "./guestClient.js";
+export { t as GuestClientError, n as createGuestClient, e as parseGuestCredential };