wire-mesh-core 1.53.0 → 1.55.0

package/dist/domain/mesh-session.d.cts

@@ -1,7 +1,7 @@
-import { D as DeviceId, E as DataRequestFrame, N as Frame, Q as PeerAdvert, T as DataHaveFrame, U as ManageError, V as ManageCommand, W as ManageOk, _t as RevocationEntry, f as CapabilityScope, ot as ProtocolVersion, p as CapabilityToken, w as DataEntriesFrame } from "../protocol-CNFRVx9w.cjs";
-import { t as IdentityPort } from "../identity-CUkDHCRK.cjs";
+import { D as DeviceId, E as DataRequestFrame, N as Frame, T as DataHaveFrame, U as ManageError, V as ManageCommand, W as ManageOk, bt as RevocationEntry, et as PeerAdvert, f as CapabilityScope, lt as ProtocolVersion, p as CapabilityToken, w as DataEntriesFrame } from "../protocol-PhUVprXA.cjs";
+import { t as IdentityPort } from "../identity-CmD4l_Mp.cjs";
 import { t as Clock } from "../clock-DiSx-WKM.cjs";
-import { r as Transport, t as Connection } from "../transport-De0zHlaA.cjs";
+import { r as Transport, t as Connection } from "../transport-CbXX1Xd-.cjs";
 //#region src/domain/mesh-session.d.ts
 /** How long to wait for the node's handshake before calling it unanswered. A relay-only node never sends one; that is a state to display, not an error. */
 export declare const HANDSHAKE_TIMEOUT_MS = 3000;
@@ -79,6 +79,8 @@ export interface MeshSession {
   readonly revocationAnnouncements: AsyncIterable<RevocationEntry>;
   connect: (address: string, localDomains: readonly string[]) => Promise<void>;
   sendPing: () => Promise<void>;
+  /** Sends a ping-frame and resolves with the round-trip time in milliseconds once the correlated pong-frame arrives -- FIFO-paired against this call's own ping, since ping-frame carries no correlation id of its own (spec/transport.cddl): the Nth call's own promise resolves against the Nth pong received after it, never matched by any other means. Rejects if the connection closes, or (when timeoutMs is given) if no pong arrives within timeoutMs, rather than resolving a sentinel value the way sendManageRequest's own timeout does -- there is no natural "no answer" value for a bare millisecond count to double as. Unlike sendPing (fire-and-forget, answered by nothing on an ordinary peer connection), this is answered only by a peer that replies to ping with pong -- today, relay-hub's own frame handling (wire-mesh#181) -- so calling this against a connection to a plain peer that never sends pong hangs until timeoutMs (if given) or forever. Exists to isolate the sender-to-hub leg of a relayed path.trace round trip: time this over the same connection a relayed manage-request travelled, then subtract it from path.trace's own end-to-end RTT to recover the hub-to-target leg. */
+  sendPingMeasureRtt: (timeoutMs?: number) => Promise<number>;
   /** Attaches this token to every `manage-request` sent from now on. */
   setToken: (token: CapabilityToken) => void;
   /** Announces one or more already-minted revocation-entries to the peer. Sent directly over the connection, never relay-wrapped -- revocation-announce is a gossiped broadcast, not a request addressed to a specific peer, so it has no targetDevice/token parameters the way sendManageRequest does. */
@@ -93,7 +95,9 @@ export interface MeshSession {
 }
 export declare function createMeshSession(transport: Readonly<Transport>, identity: Readonly<IdentityPort>, clock?: Readonly<Clock>, reconnect?: ReconnectPolicy | null,
 /** This node's own directly-reachable "host:port" candidates (wire-mesh#38), advertised in this session's self-advert so other peers can attempt a direct connection instead of always falling back to a relay. Omit (or pass none) for a caller with nothing to offer, e.g. a browser client. */
-addresses?: readonly string[]): MeshSession;
+addresses?: readonly string[],
+/** Fired for every peer-advert entry as it's applied to the directory, regardless of source -- the hook a gossip-expansion consumer (wire-mesh#187, gossip-expansion.ts's own createGossipExpansion) uses to observe newly-gossiped peers without becoming a second, competing consumer of this session's own single-reader events stream (each emitted SessionEvent wakes at most one waiter, so a second for-await loop over events would silently steal events from whichever consumer already reads it). Omit for a caller with no use for it, exactly today's behaviour. */
+onPeerAdvert?: (advert: PeerAdvert) => void): MeshSession;
 /** A MeshSession built over a connection that already exists (a Transport's own listen() handed it to onConnection), extended with the one thing a dial-side session can't offer: the device-id of the specific peer at the other end. Unlike createMeshSession, which may end up talking to a relay gossiping about many devices at once, an accepted connection is the agent-comms case -- exactly two peers, directly connected -- so "the peer" is well-defined here in a way it structurally isn't for the dial side. */
 export interface AcceptedMeshSession extends MeshSession {
   /** Resolves with the device-id carried by the first peer-advert this connection's remote sends -- the same self-advertisement mechanism createMeshSession's own directory already relies on for every peer, just narrowed to "the one peer this specific connection is with" rather than accumulated into a directory of possibly many. There is no transport-level authentication behind this yet (see wire-mesh#45's own createTlsTransport item): it is only as trustworthy as the remote's own gossip, exactly the same trust level the dial-side directory already has for every entry in it. */
@@ -109,6 +113,8 @@ export interface AcceptedMeshSessionOptions {
   onFrame?: (connection: Readonly<Connection>, frame: Frame) => void | Promise<void>;
   /** Fired once this session's own connection.receive() stream ends -- the counterpart a RelayHub's own forgetConnection needs, since its registry is keyed by this exact Connection and must be cleaned up when it specifically ends. */
   onSessionEnd?: (connection: Readonly<Connection>) => void;
+  /** Fired for every peer-advert entry as it's applied to the directory, regardless of source -- alongside (never instead of) this session's own internal peerDeviceId resolution, which uses this identical hook internally and keeps working unchanged. See createMeshSession's own onPeerAdvert doc comment for why this exists: a gossip-expansion consumer (wire-mesh#187) needs to observe every advert without becoming a second, competing consumer of this session's own single-reader events stream. */
+  onPeerAdvert?: (advert: PeerAdvert) => void;
 }
 /** Wires an already-accepted Connection up as a full MeshSession, mirroring exactly what createMeshSession's own dial path does once a connection exists (send handshake, send self-advert, negotiate, consume frames) -- the wire-mesh#45 prerequisite agent-comms needs, since its peers both listen and dial rather than only ever dialing the way web-console's own console UI does. Reconnect does not apply here: if this connection drops, only the remote redialing and being accepted again produces a new connection, and therefore a new session -- there is nothing on this side to retry. */
 export declare function acceptMeshSession(connection: Readonly<Connection>, identity: Readonly<IdentityPort>, localDomains: readonly string[], options?: Readonly<AcceptedMeshSessionOptions>): Promise<AcceptedMeshSession>;

package/dist/domain/mesh-session.d.mts

@@ -1,7 +1,7 @@
-import { D as DeviceId, E as DataRequestFrame, N as Frame, Q as PeerAdvert, T as DataHaveFrame, U as ManageError, V as ManageCommand, W as ManageOk, _t as RevocationEntry, f as CapabilityScope, ot as ProtocolVersion, p as CapabilityToken, w as DataEntriesFrame } from "../protocol-CNFRVx9w.mjs";
-import { t as IdentityPort } from "../identity-9TmmK7vP.mjs";
+import { D as DeviceId, E as DataRequestFrame, N as Frame, T as DataHaveFrame, U as ManageError, V as ManageCommand, W as ManageOk, bt as RevocationEntry, et as PeerAdvert, f as CapabilityScope, lt as ProtocolVersion, p as CapabilityToken, w as DataEntriesFrame } from "../protocol-PhUVprXA.mjs";
+import { t as IdentityPort } from "../identity-BXrJ6_YM.mjs";
 import { t as Clock } from "../clock-DiSx-WKM.mjs";
-import { r as Transport, t as Connection } from "../transport-C7KVkhgb.mjs";
+import { r as Transport, t as Connection } from "../transport-DG9ouGe-.mjs";
 //#region src/domain/mesh-session.d.ts
 /** How long to wait for the node's handshake before calling it unanswered. A relay-only node never sends one; that is a state to display, not an error. */
 export declare const HANDSHAKE_TIMEOUT_MS = 3000;
@@ -79,6 +79,8 @@ export interface MeshSession {
   readonly revocationAnnouncements: AsyncIterable<RevocationEntry>;
   connect: (address: string, localDomains: readonly string[]) => Promise<void>;
   sendPing: () => Promise<void>;
+  /** Sends a ping-frame and resolves with the round-trip time in milliseconds once the correlated pong-frame arrives -- FIFO-paired against this call's own ping, since ping-frame carries no correlation id of its own (spec/transport.cddl): the Nth call's own promise resolves against the Nth pong received after it, never matched by any other means. Rejects if the connection closes, or (when timeoutMs is given) if no pong arrives within timeoutMs, rather than resolving a sentinel value the way sendManageRequest's own timeout does -- there is no natural "no answer" value for a bare millisecond count to double as. Unlike sendPing (fire-and-forget, answered by nothing on an ordinary peer connection), this is answered only by a peer that replies to ping with pong -- today, relay-hub's own frame handling (wire-mesh#181) -- so calling this against a connection to a plain peer that never sends pong hangs until timeoutMs (if given) or forever. Exists to isolate the sender-to-hub leg of a relayed path.trace round trip: time this over the same connection a relayed manage-request travelled, then subtract it from path.trace's own end-to-end RTT to recover the hub-to-target leg. */
+  sendPingMeasureRtt: (timeoutMs?: number) => Promise<number>;
   /** Attaches this token to every `manage-request` sent from now on. */
   setToken: (token: CapabilityToken) => void;
   /** Announces one or more already-minted revocation-entries to the peer. Sent directly over the connection, never relay-wrapped -- revocation-announce is a gossiped broadcast, not a request addressed to a specific peer, so it has no targetDevice/token parameters the way sendManageRequest does. */
@@ -93,7 +95,9 @@ export interface MeshSession {
 }
 export declare function createMeshSession(transport: Readonly<Transport>, identity: Readonly<IdentityPort>, clock?: Readonly<Clock>, reconnect?: ReconnectPolicy | null,
 /** This node's own directly-reachable "host:port" candidates (wire-mesh#38), advertised in this session's self-advert so other peers can attempt a direct connection instead of always falling back to a relay. Omit (or pass none) for a caller with nothing to offer, e.g. a browser client. */
-addresses?: readonly string[]): MeshSession;
+addresses?: readonly string[],
+/** Fired for every peer-advert entry as it's applied to the directory, regardless of source -- the hook a gossip-expansion consumer (wire-mesh#187, gossip-expansion.ts's own createGossipExpansion) uses to observe newly-gossiped peers without becoming a second, competing consumer of this session's own single-reader events stream (each emitted SessionEvent wakes at most one waiter, so a second for-await loop over events would silently steal events from whichever consumer already reads it). Omit for a caller with no use for it, exactly today's behaviour. */
+onPeerAdvert?: (advert: PeerAdvert) => void): MeshSession;
 /** A MeshSession built over a connection that already exists (a Transport's own listen() handed it to onConnection), extended with the one thing a dial-side session can't offer: the device-id of the specific peer at the other end. Unlike createMeshSession, which may end up talking to a relay gossiping about many devices at once, an accepted connection is the agent-comms case -- exactly two peers, directly connected -- so "the peer" is well-defined here in a way it structurally isn't for the dial side. */
 export interface AcceptedMeshSession extends MeshSession {
   /** Resolves with the device-id carried by the first peer-advert this connection's remote sends -- the same self-advertisement mechanism createMeshSession's own directory already relies on for every peer, just narrowed to "the one peer this specific connection is with" rather than accumulated into a directory of possibly many. There is no transport-level authentication behind this yet (see wire-mesh#45's own createTlsTransport item): it is only as trustworthy as the remote's own gossip, exactly the same trust level the dial-side directory already has for every entry in it. */
@@ -109,6 +113,8 @@ export interface AcceptedMeshSessionOptions {
   onFrame?: (connection: Readonly<Connection>, frame: Frame) => void | Promise<void>;
   /** Fired once this session's own connection.receive() stream ends -- the counterpart a RelayHub's own forgetConnection needs, since its registry is keyed by this exact Connection and must be cleaned up when it specifically ends. */
   onSessionEnd?: (connection: Readonly<Connection>) => void;
+  /** Fired for every peer-advert entry as it's applied to the directory, regardless of source -- alongside (never instead of) this session's own internal peerDeviceId resolution, which uses this identical hook internally and keeps working unchanged. See createMeshSession's own onPeerAdvert doc comment for why this exists: a gossip-expansion consumer (wire-mesh#187) needs to observe every advert without becoming a second, competing consumer of this session's own single-reader events stream. */
+  onPeerAdvert?: (advert: PeerAdvert) => void;
 }
 /** Wires an already-accepted Connection up as a full MeshSession, mirroring exactly what createMeshSession's own dial path does once a connection exists (send handshake, send self-advert, negotiate, consume frames) -- the wire-mesh#45 prerequisite agent-comms needs, since its peers both listen and dial rather than only ever dialing the way web-console's own console UI does. Reconnect does not apply here: if this connection drops, only the remote redialing and being accepted again produces a new connection, and therefore a new session -- there is nothing on this side to retry. */
 export declare function acceptMeshSession(connection: Readonly<Connection>, identity: Readonly<IdentityPort>, localDomains: readonly string[], options?: Readonly<AcceptedMeshSessionOptions>): Promise<AcceptedMeshSession>;

package/dist/domain/mesh-session.mjs

@@ -12,8 +12,43 @@ function createRelayPairings() {
 	};
 }
 //#endregion
-//#region src/domain/mesh-session.ts
-const MS_PER_SECOND = 1e3;
+//#region src/domain/ping-round-trips.ts
+function createPingRoundTrips() {
+	const pending = [];
+	function cancel(sentAt) {
+		const index = pending.findIndex((entry) => entry.sentAt === sentAt);
+		if (index === -1) return false;
+		pending.splice(index, 1);
+		return true;
+	}
+	return {
+		resolveOldest(nowMs) {
+			const entry = pending.shift();
+			if (entry !== void 0) entry.resolve(nowMs - entry.sentAt);
+		},
+		rejectAll(reason) {
+			for (const entry of pending.splice(0)) entry.reject(new Error(reason));
+		},
+		async sendAndAwait(sentAt, sendPing, timeoutMs) {
+			const rtt = new Promise((resolve, reject) => {
+				pending.push({
+					sentAt,
+					resolve,
+					reject
+				});
+			});
+			await sendPing();
+			if (timeoutMs === void 0) return rtt;
+			return Promise.race([rtt, new Promise((_resolve, reject) => {
+				setTimeout(() => {
+					if (cancel(sentAt)) reject(/* @__PURE__ */ new Error("timed out waiting for pong"));
+				}, timeoutMs);
+			})]);
+		}
+	};
+}
+//#endregion
+//#region src/domain/gossip-extensions.ts
 /** peer-advert's own three typed fields -- reserved so a `sendGossipUpdate` caller can never override the session's own device-id, address list, or freshness timestamp by supplying an extension of the same name. */
 const RESERVED_PEER_ADVERT_KEYS = /* @__PURE__ */ new Set([
 	"device",
@@ -29,6 +64,9 @@ function validateGossipExtensions(extensions) {
 		if (!GOSSIP_EXTENSION_KEY_PATTERN.test(key)) throw new Error(`sendGossipUpdate extension key "${key}" must be domain-qualified as "<domain>/<field>" (e.g. "presence/status")`);
 	}
 }
+//#endregion
+//#region src/domain/mesh-session.ts
+const MS_PER_SECOND = 1e3;
 /** How long to wait for the node's handshake before calling it unanswered. A relay-only node never sends one; that is a state to display, not an error. */
 const HANDSHAKE_TIMEOUT_MS = 3e3;
 function localHandshake(domains) {
@@ -61,6 +99,7 @@ function createSessionCore(identity, clock, reconnect, dial, onPeerAdvert, addre
 	const incomingBacklog = [];
 	const revocationWaiters = [];
 	const revocationBacklog = [];
+	const pingRoundTrips = createPingRoundTrips();
 	function snapshot() {
 		return {
 			state,
@@ -100,6 +139,11 @@ function createSessionCore(identity, clock, reconnect, dial, onPeerAdvert, addre
 			...token !== null ? { token } : {}
 		};
 	}
+	/** The "not connected" guard every send* method on the public session needs, deduplicated into one place rather than repeated inline at each call site: throws unless there is a live connection AND the session's own state machine agrees it is "connected" (transmit's own connection===null check alone doesn't cover the latter). Returns the connection itself, narrowed non-null, for a caller that needs to send directly on it (sendPing/sendPingMeasureRtt); a caller that only needs the throwing side effect (sendManageRequest and friends, which go through transmit instead) calls this and discards the result. */
+	function requireConnectedLink() {
+		if (connection === null || state.status !== "connected") throw new Error("not connected");
+		return connection;
+	}
 	/** Sends a frame, wrapping it as relay-data first when viaRelay is set -- the single choke point every outbound manage-request/manage-response passes through, so a consumer of sendManageRequest/respond never needs its own relay-wrapping logic. When relaying, toDevice is stamped onto the outer relay-data-frame's own `to-device` field so the hub addresses it to the correct pairing directly (wire-mesh#30) rather than falling back to whichever pairing it last saw -- the one case this is omitted is a response to a request that itself arrived with no from-device to echo back, which is left to that same hub fallback exactly as an unaddressed relay-data always has been. */
 	async function transmit(frame, viaRelay, toDevice) {
 		if (connection === null) throw new Error("not connected");
@@ -177,6 +221,7 @@ function createSessionCore(identity, clock, reconnect, dial, onPeerAdvert, addre
 		else if (frame.type === "relay-inbound") relayPairings.add(frame["source-device"]);
 		else if (frame.type === "manage-response") applyManageResponse(frame);
 		else if (frame.type === "manage-request") applyManageRequest(frame);
+		else if (frame.type === "pong") pingRoundTrips.resolveOldest(clock.now());
 		else if (frame.type === "revocation-announce") for (const entry of frame.entries) emitRevocationEntry(entry);
 	}
 	/** Establishes a relay-connect pairing to targetDevice if this session isn't already paired with it -- a no-op when it already is, whether that pairing was established by this session's own prior relay-connect (initiator role) or learned from an incoming relay-inbound (target role, replying back to whoever dialed it). Pairing with a new target never tears down an existing pairing with a different one: this connection can hold several simultaneously (wire-mesh#30's own multiplexed adjacency map), so a later request back to an already-paired target must not re-send relay-connect for it. relay-connect has no ack frame: the initiator proceeds to relay-data right after sending it. */
@@ -219,6 +264,7 @@ function createSessionCore(identity, clock, reconnect, dial, onPeerAdvert, addre
 	function handleDisconnect(reason, address, localDomains) {
 		if (feedCancelled) return;
 		rejectPendingManageRequests("disconnected before a response arrived");
+		pingRoundTrips.rejectAll("disconnected before a pong arrived");
 		if (reconnect !== null && attempt < reconnect.maxAttempts) {
 			attempt += 1;
 			const currentAttempt = attempt;
@@ -377,20 +423,32 @@ function createSessionCore(identity, clock, reconnect, dial, onPeerAdvert, addre
 				await doConnect(address, localDomains);
 			},
 			async sendPing() {
-				if (connection === null || state.status !== "connected") throw new Error("not connected");
+				const link = requireConnectedLink();
 				const ping = { type: "ping" };
 				frameLog.push({
 					direction: "sent",
 					frame: ping
 				});
-				await connection.send(ping);
+				await link.send(ping);
 				emit();
 			},
+			async sendPingMeasureRtt(timeoutMs) {
+				const link = requireConnectedLink();
+				return pingRoundTrips.sendAndAwait(clock.now(), async () => {
+					const ping = { type: "ping" };
+					frameLog.push({
+						direction: "sent",
+						frame: ping
+					});
+					await link.send(ping);
+					emit();
+				}, timeoutMs);
+			},
 			setToken(token) {
 				currentToken = token;
 			},
 			async sendManageRequest(command, scope, targetDevice, token, timeoutMs) {
-				if (connection === null || state.status !== "connected") throw new Error("not connected");
+				requireConnectedLink();
 				if (targetDevice !== void 0) await ensureRelayPairing(targetDevice);
 				const frame = buildManageRequest(command, scope, token);
 				const requestId = frame["request-id"];
@@ -417,7 +475,7 @@ function createSessionCore(identity, clock, reconnect, dial, onPeerAdvert, addre
 				})]);
 			},
 			async sendRevocationAnnounce(entries) {
-				if (connection === null || state.status !== "connected") throw new Error("not connected");
+				requireConnectedLink();
 				const frame = {
 					type: "revocation-announce",
 					entries: [...entries]
@@ -430,7 +488,7 @@ function createSessionCore(identity, clock, reconnect, dial, onPeerAdvert, addre
 				emit();
 			},
 			async sendGossipUpdate(extensions) {
-				if (connection === null || state.status !== "connected") throw new Error("not connected");
+				requireConnectedLink();
 				const frame = buildSelfAdvert(extensions);
 				frameLog.push({
 					direction: "sent",
@@ -440,7 +498,7 @@ function createSessionCore(identity, clock, reconnect, dial, onPeerAdvert, addre
 				emit();
 			},
 			async sendDataFrame(frame) {
-				if (connection === null || state.status !== "connected") throw new Error("not connected");
+				requireConnectedLink();
 				frameLog.push({
 					direction: "sent",
 					frame
@@ -459,6 +517,7 @@ function createSessionCore(identity, clock, reconnect, dial, onPeerAdvert, addre
 					reconnectTimer = null;
 				}
 				rejectPendingManageRequests("connection closed before a response arrived");
+				pingRoundTrips.rejectAll("connection closed before a pong arrived");
 				if (connection !== null) await connection.close();
 				if (state.status === "connected" || state.status === "connecting" || state.status === "reconnecting") state = {
 					status: "closed",
@@ -470,8 +529,8 @@ function createSessionCore(identity, clock, reconnect, dial, onPeerAdvert, addre
 		}
 	};
 }
-function createMeshSession(transport, identity, clock = { now: () => Date.now() }, reconnect = null, addresses = []) {
-	const { session } = createSessionCore(identity, clock, reconnect, async (address) => transport.connect(address), void 0, addresses);
+function createMeshSession(transport, identity, clock = { now: () => Date.now() }, reconnect = null, addresses = [], onPeerAdvert) {
+	const { session } = createSessionCore(identity, clock, reconnect, async (address) => transport.connect(address), onPeerAdvert, addresses);
 	return session;
 }
 /** Wires an already-accepted Connection up as a full MeshSession, mirroring exactly what createMeshSession's own dial path does once a connection exists (send handshake, send self-advert, negotiate, consume frames) -- the wire-mesh#45 prerequisite agent-comms needs, since its peers both listen and dial rather than only ever dialing the way web-console's own console UI does. Reconnect does not apply here: if this connection drops, only the remote redialing and being accepted again produces a new connection, and therefore a new session -- there is nothing on this side to retry. */
@@ -483,9 +542,11 @@ async function acceptMeshSession(connection, identity, localDomains, options = {
 	});
 	let peerDeviceIdResolved = false;
 	const { session, wireUpConnection } = createSessionCore(identity, clock, null, null, (advert) => {
-		if (peerDeviceIdResolved) return;
-		peerDeviceIdResolved = true;
-		resolvePeerDeviceId?.(advert.device);
+		if (!peerDeviceIdResolved) {
+			peerDeviceIdResolved = true;
+			resolvePeerDeviceId?.(advert.device);
+		}
+		options.onPeerAdvert?.(advert);
 	}, options.addresses, options.onFrame, options.onSessionEnd);
 	await wireUpConnection(connection, options.label ?? "accepted", localDomains);
 	return {

package/dist/domain/notice-board.d.cts

@@ -1,8 +1,8 @@
-import { D as DeviceId, Et as RoomNoticeClaims, T as DataHaveFrame, Tt as RoomNotice, p as CapabilityToken } from "../protocol-CNFRVx9w.cjs";
+import { D as DeviceId, Ot as RoomNotice, T as DataHaveFrame, kt as RoomNoticeClaims, p as CapabilityToken } from "../protocol-PhUVprXA.cjs";
 import { KeyValueStorage } from "../ports/storage.cjs";
-import { t as IdentityPort } from "../identity-CUkDHCRK.cjs";
+import { t as IdentityPort } from "../identity-CmD4l_Mp.cjs";
 import { t as Clock } from "../clock-DiSx-WKM.cjs";
-import { a as RevocationCheck } from "../tokens-Cl8sQo7o.cjs";
+import { a as RevocationCheck } from "../tokens-DIPzZ9JJ.cjs";
 import { RoomNoticeVerdictReason } from "./room.cjs";
 //#region src/domain/notice-board.d.ts
 /**

package/dist/domain/notice-board.d.mts

@@ -1,8 +1,8 @@
-import { D as DeviceId, Et as RoomNoticeClaims, T as DataHaveFrame, Tt as RoomNotice, p as CapabilityToken } from "../protocol-CNFRVx9w.mjs";
+import { D as DeviceId, Ot as RoomNotice, T as DataHaveFrame, kt as RoomNoticeClaims, p as CapabilityToken } from "../protocol-PhUVprXA.mjs";
 import { KeyValueStorage } from "../ports/storage.mjs";
-import { t as IdentityPort } from "../identity-9TmmK7vP.mjs";
+import { t as IdentityPort } from "../identity-BXrJ6_YM.mjs";
 import { t as Clock } from "../clock-DiSx-WKM.mjs";
-import { a as RevocationCheck } from "../tokens-CVyPoJ6l.mjs";
+import { a as RevocationCheck } from "../tokens-BVrgBeqF.mjs";
 import { RoomNoticeVerdictReason } from "./room.mjs";
 //#region src/domain/notice-board.d.ts
 /**

package/dist/domain/relay-hub.cjs

@@ -95,6 +95,12 @@ function createRelayHub() {
 			});
 			return;
 		}
+		if (frame.type === "ping") {
+			try {
+				await connection.send({ type: "pong" });
+			} catch {}
+			return;
+		}
 	}
 	return {
 		async handleConnection(connection) {

package/dist/domain/relay-hub.d.cts

@@ -1,8 +1,8 @@
-import { N as Frame } from "../protocol-CNFRVx9w.cjs";
-import { t as Connection } from "../transport-De0zHlaA.cjs";
+import { N as Frame } from "../protocol-PhUVprXA.cjs";
+import { t as Connection } from "../transport-CbXX1Xd-.cjs";
 //#region src/domain/relay-hub.d.ts
 export interface RelayHub {
-  /** Drives one accepted connection until it closes: registers gossip-advertised devices, re-broadcasts each gossip frame to every other connected client and replies to the gossiping connection with a catch-up frame of every other already-known device, answers relay-connect by pairing and notifying the target, and forwards relay-data within established pairings. Resolves when the connection's frame stream ends. Internally just registerConnection followed by a loop of onFrame calls and a final onDisconnect -- kept as its own method since a dedicated hub deployment (wire-mesh-node/cloudflare-hub) has nothing else driving the connection and wants the whole lifecycle in one call. */
+  /** Drives one accepted connection until it closes: registers gossip-advertised devices, re-broadcasts each gossip frame to every other connected client and replies to the gossiping connection with a catch-up frame of every other already-known device, answers relay-connect by pairing and notifying the target, forwards relay-data within established pairings, and replies to a bare ping with a bare pong (wire-mesh#181) so a client can time its own sender-to-hub leg independent of anything being relayed. Resolves when the connection's frame stream ends. Internally just registerConnection followed by a loop of onFrame calls and a final onDisconnect -- kept as its own method since a dedicated hub deployment (wire-mesh-node/cloudflare-hub) has nothing else driving the connection and wants the whole lifecycle in one call. */
   handleConnection: (connection: Readonly<Connection>) => Promise<void>;
   /** Registers a connection with this hub without taking over its own frame-consumption loop (wire-mesh#102) -- the entry point an "ordinary opted-in node relays for peers it's already talking to" uses, alongside onFrame/onDisconnect below, to let a MeshSession's own single connection.receive() loop drive this hub rather than running a second, competing one. Must be called once, before the first onFrame call for this connection, so gossip fan-out (which forwards to every OTHER registered connection) already sees it. */
   registerConnection: (connection: Readonly<Connection>) => void;

package/dist/domain/relay-hub.d.mts

@@ -1,8 +1,8 @@
-import { N as Frame } from "../protocol-CNFRVx9w.mjs";
-import { t as Connection } from "../transport-C7KVkhgb.mjs";
+import { N as Frame } from "../protocol-PhUVprXA.mjs";
+import { t as Connection } from "../transport-DG9ouGe-.mjs";
 //#region src/domain/relay-hub.d.ts
 export interface RelayHub {
-  /** Drives one accepted connection until it closes: registers gossip-advertised devices, re-broadcasts each gossip frame to every other connected client and replies to the gossiping connection with a catch-up frame of every other already-known device, answers relay-connect by pairing and notifying the target, and forwards relay-data within established pairings. Resolves when the connection's frame stream ends. Internally just registerConnection followed by a loop of onFrame calls and a final onDisconnect -- kept as its own method since a dedicated hub deployment (wire-mesh-node/cloudflare-hub) has nothing else driving the connection and wants the whole lifecycle in one call. */
+  /** Drives one accepted connection until it closes: registers gossip-advertised devices, re-broadcasts each gossip frame to every other connected client and replies to the gossiping connection with a catch-up frame of every other already-known device, answers relay-connect by pairing and notifying the target, forwards relay-data within established pairings, and replies to a bare ping with a bare pong (wire-mesh#181) so a client can time its own sender-to-hub leg independent of anything being relayed. Resolves when the connection's frame stream ends. Internally just registerConnection followed by a loop of onFrame calls and a final onDisconnect -- kept as its own method since a dedicated hub deployment (wire-mesh-node/cloudflare-hub) has nothing else driving the connection and wants the whole lifecycle in one call. */
   handleConnection: (connection: Readonly<Connection>) => Promise<void>;
   /** Registers a connection with this hub without taking over its own frame-consumption loop (wire-mesh#102) -- the entry point an "ordinary opted-in node relays for peers it's already talking to" uses, alongside onFrame/onDisconnect below, to let a MeshSession's own single connection.receive() loop drive this hub rather than running a second, competing one. Must be called once, before the first onFrame call for this connection, so gossip fan-out (which forwards to every OTHER registered connection) already sees it. */
   registerConnection: (connection: Readonly<Connection>) => void;

package/dist/domain/relay-hub.mjs

@@ -94,6 +94,12 @@ function createRelayHub() {
 			});
 			return;
 		}
+		if (frame.type === "ping") {
+			try {
+				await connection.send({ type: "pong" });
+			} catch {}
+			return;
+		}
 	}
 	return {
 		async handleConnection(connection) {

package/dist/domain/relay-use-gate.d.cts

@@ -1,5 +1,5 @@
-import { N as Frame } from "../protocol-CNFRVx9w.cjs";
-import { t as Connection } from "../transport-De0zHlaA.cjs";
+import { N as Frame } from "../protocol-PhUVprXA.cjs";
+import { t as Connection } from "../transport-CbXX1Xd-.cjs";
 //#region src/domain/relay-use-gate.d.ts
 export interface RelayUseAuthorizationTracker {
   /** True once authorize() has been called for this exact connection and revoke() has not been called since. */

package/dist/domain/relay-use-gate.d.mts

@@ -1,5 +1,5 @@
-import { N as Frame } from "../protocol-CNFRVx9w.mjs";
-import { t as Connection } from "../transport-C7KVkhgb.mjs";
+import { N as Frame } from "../protocol-PhUVprXA.mjs";
+import { t as Connection } from "../transport-DG9ouGe-.mjs";
 //#region src/domain/relay-use-gate.d.ts
 export interface RelayUseAuthorizationTracker {
   /** True once authorize() has been called for this exact connection and revoke() has not been called since. */

package/dist/domain/revocation-view.d.cts

@@ -1,5 +1,5 @@
-import { _t as RevocationEntry } from "../protocol-CNFRVx9w.cjs";
-import { a as RevocationCheck, d as VerifyRevocationEntryOptions, o as RevocationEntryVerdict } from "../tokens-Cl8sQo7o.cjs";
+import { bt as RevocationEntry } from "../protocol-PhUVprXA.cjs";
+import { a as RevocationCheck, d as VerifyRevocationEntryOptions, o as RevocationEntryVerdict } from "../tokens-DIPzZ9JJ.cjs";
 //#region src/domain/revocation-view.d.ts
 /**
  * An in-memory RevocationCheck fed by ingested revocation-announce frames. Keyed by token-id alone, per management.cddl's contract: a token-id can legitimately carry multiple recorded entries from different issuers (the token's own issuer, and/or any number of parties holding a delegated manage:revoke authorization over it) -- entriesFor returns every one of them unfiltered, since checking which actually apply (issuer-match, or a verified authorization) is verifyTokenChain's own obligation, not this store's.

package/dist/domain/revocation-view.d.mts

@@ -1,5 +1,5 @@
-import { _t as RevocationEntry } from "../protocol-CNFRVx9w.mjs";
-import { a as RevocationCheck, d as VerifyRevocationEntryOptions, o as RevocationEntryVerdict } from "../tokens-CVyPoJ6l.mjs";
+import { bt as RevocationEntry } from "../protocol-PhUVprXA.mjs";
+import { a as RevocationCheck, d as VerifyRevocationEntryOptions, o as RevocationEntryVerdict } from "../tokens-BVrgBeqF.mjs";
 //#region src/domain/revocation-view.d.ts
 /**
  * An in-memory RevocationCheck fed by ingested revocation-announce frames. Keyed by token-id alone, per management.cddl's contract: a token-id can legitimately carry multiple recorded entries from different issuers (the token's own issuer, and/or any number of parties holding a delegated manage:revoke authorization over it) -- entriesFor returns every one of them unfiltered, since checking which actually apply (issuer-match, or a verified authorization) is verifyTokenChain's own obligation, not this store's.

package/dist/domain/room-rekey.d.cts

@@ -1,8 +1,8 @@
-import { D as DeviceId, V as ManageCommand, p as CapabilityToken } from "../protocol-CNFRVx9w.cjs";
-import { t as IdentityPort } from "../identity-CUkDHCRK.cjs";
+import { D as DeviceId, V as ManageCommand, p as CapabilityToken } from "../protocol-PhUVprXA.cjs";
+import { t as IdentityPort } from "../identity-CmD4l_Mp.cjs";
 import { t as Clock } from "../clock-DiSx-WKM.cjs";
 import { IncomingManageRequest, ManageOutcome, MeshSession } from "./mesh-session.cjs";
-import { a as RevocationCheck } from "../tokens-Cl8sQo7o.cjs";
+import { a as RevocationCheck } from "../tokens-DIPzZ9JJ.cjs";
 //#region src/domain/room-rekey.d.ts
 /**
  * Builds a room.rekey command per room.cddl. The outer verb is room:member, the same "one resource, several inner verbs" pattern room.send/room.leave/room.members already establish -- not a new capability of its own.

package/dist/domain/room-rekey.d.mts

@@ -1,8 +1,8 @@
-import { D as DeviceId, V as ManageCommand, p as CapabilityToken } from "../protocol-CNFRVx9w.mjs";
-import { t as IdentityPort } from "../identity-9TmmK7vP.mjs";
+import { D as DeviceId, V as ManageCommand, p as CapabilityToken } from "../protocol-PhUVprXA.mjs";
+import { t as IdentityPort } from "../identity-BXrJ6_YM.mjs";
 import { t as Clock } from "../clock-DiSx-WKM.mjs";
 import { IncomingManageRequest, ManageOutcome, MeshSession } from "./mesh-session.mjs";
-import { a as RevocationCheck } from "../tokens-CVyPoJ6l.mjs";
+import { a as RevocationCheck } from "../tokens-BVrgBeqF.mjs";
 //#region src/domain/room-rekey.d.ts
 /**
  * Builds a room.rekey command per room.cddl. The outer verb is room:member, the same "one resource, several inner verbs" pattern room.send/room.leave/room.members already establish -- not a new capability of its own.

package/dist/domain/room-token-verification.d.cts

@@ -1,2 +1,2 @@
-import { a as verifyRoomToken, i as VerifyRoomTokenOptions, n as RoomTokenVerdict, r as RoomTokenVerdictReason, t as ROOM_MEMBER_CAPABILITY } from "../room-token-verification-DpOfZOdl.cjs";
+import { a as verifyRoomToken, i as VerifyRoomTokenOptions, n as RoomTokenVerdict, r as RoomTokenVerdictReason, t as ROOM_MEMBER_CAPABILITY } from "../room-token-verification-D8HndWYM.cjs";
 export { ROOM_MEMBER_CAPABILITY, RoomTokenVerdict, RoomTokenVerdictReason, VerifyRoomTokenOptions, verifyRoomToken };

package/dist/domain/room-token-verification.d.mts

@@ -1,2 +1,2 @@
-import { a as verifyRoomToken, i as VerifyRoomTokenOptions, n as RoomTokenVerdict, r as RoomTokenVerdictReason, t as ROOM_MEMBER_CAPABILITY } from "../room-token-verification-BdtM1rQ4.mjs";
+import { a as verifyRoomToken, i as VerifyRoomTokenOptions, n as RoomTokenVerdict, r as RoomTokenVerdictReason, t as ROOM_MEMBER_CAPABILITY } from "../room-token-verification-Dv1O6-FV.mjs";
 export { ROOM_MEMBER_CAPABILITY, RoomTokenVerdict, RoomTokenVerdictReason, VerifyRoomTokenOptions, verifyRoomToken };

package/dist/domain/room.d.cts

@@ -1,8 +1,8 @@
-import { Dt as RoomPath, Et as RoomNoticeClaims, Tt as RoomNotice, p as CapabilityToken, q as MessageRef } from "../protocol-CNFRVx9w.cjs";
-import { t as IdentityPort } from "../identity-CUkDHCRK.cjs";
+import { At as RoomPath, Ot as RoomNotice, kt as RoomNoticeClaims, p as CapabilityToken, q as MessageRef } from "../protocol-PhUVprXA.cjs";
+import { t as IdentityPort } from "../identity-CmD4l_Mp.cjs";
 import { t as Clock } from "../clock-DiSx-WKM.cjs";
-import { a as RevocationCheck } from "../tokens-Cl8sQo7o.cjs";
-import { r as RoomTokenVerdictReason } from "../room-token-verification-DpOfZOdl.cjs";
+import { a as RevocationCheck } from "../tokens-DIPzZ9JJ.cjs";
+import { r as RoomTokenVerdictReason } from "../room-token-verification-D8HndWYM.cjs";
 //#region src/domain/room.d.ts
 export type RoomNoticeVerdictReason = "malformed" | "wrong_room" | "bad_signature" | "wrong_poster" | "content_expired" | "key_epoch_mismatch" | RoomTokenVerdictReason;
 export type RoomNoticeVerdict = {

package/dist/domain/room.d.mts

@@ -1,8 +1,8 @@
-import { Dt as RoomPath, Et as RoomNoticeClaims, Tt as RoomNotice, p as CapabilityToken, q as MessageRef } from "../protocol-CNFRVx9w.mjs";
-import { t as IdentityPort } from "../identity-9TmmK7vP.mjs";
+import { At as RoomPath, Ot as RoomNotice, kt as RoomNoticeClaims, p as CapabilityToken, q as MessageRef } from "../protocol-PhUVprXA.mjs";
+import { t as IdentityPort } from "../identity-BXrJ6_YM.mjs";
 import { t as Clock } from "../clock-DiSx-WKM.mjs";
-import { a as RevocationCheck } from "../tokens-CVyPoJ6l.mjs";
-import { r as RoomTokenVerdictReason } from "../room-token-verification-BdtM1rQ4.mjs";
+import { a as RevocationCheck } from "../tokens-BVrgBeqF.mjs";
+import { r as RoomTokenVerdictReason } from "../room-token-verification-Dv1O6-FV.mjs";
 //#region src/domain/room.d.ts
 export type RoomNoticeVerdictReason = "malformed" | "wrong_room" | "bad_signature" | "wrong_poster" | "content_expired" | "key_epoch_mismatch" | RoomTokenVerdictReason;
 export type RoomNoticeVerdict = {

package/dist/domain/shard-manifest.d.cts

@@ -1,4 +1,4 @@
-import { D as DeviceId } from "../protocol-CNFRVx9w.cjs";
+import { D as DeviceId } from "../protocol-PhUVprXA.cjs";
 import { PresentedShard, ShardConfig } from "./erasure-coding.cjs";
 //#region src/domain/shard-manifest.d.ts
 /** The content-type a core/data entry carrying a shard manifest declares. */

package/dist/domain/shard-manifest.d.mts

@@ -1,4 +1,4 @@
-import { D as DeviceId } from "../protocol-CNFRVx9w.mjs";
+import { D as DeviceId } from "../protocol-PhUVprXA.mjs";
 import { PresentedShard, ShardConfig } from "./erasure-coding.mjs";
 //#region src/domain/shard-manifest.d.ts
 /** The content-type a core/data entry carrying a shard manifest declares. */

package/dist/domain/tokens.d.cts

@@ -1,2 +1,2 @@
-import { _ as verifyRevocationEntry, a as RevocationCheck, c as TokenVerdict, d as VerifyRevocationEntryOptions, f as canGrant, g as verifyCapabilityToken, h as sig1ToBeSigned, i as MintVerdict, l as TokenVerdictReason, m as mintRevocationEntry, n as MintRefusalReason, o as RevocationEntryVerdict, p as mintCapabilityToken, r as MintRevocationEntryOptions, s as RevocationEntryVerdictReason, t as MintCapabilityTokenOptions, u as VerifyCapabilityTokenOptions } from "../tokens-Cl8sQo7o.cjs";
+import { _ as verifyRevocationEntry, a as RevocationCheck, c as TokenVerdict, d as VerifyRevocationEntryOptions, f as canGrant, g as verifyCapabilityToken, h as sig1ToBeSigned, i as MintVerdict, l as TokenVerdictReason, m as mintRevocationEntry, n as MintRefusalReason, o as RevocationEntryVerdict, p as mintCapabilityToken, r as MintRevocationEntryOptions, s as RevocationEntryVerdictReason, t as MintCapabilityTokenOptions, u as VerifyCapabilityTokenOptions } from "../tokens-DIPzZ9JJ.cjs";
 export { MintCapabilityTokenOptions, MintRefusalReason, MintRevocationEntryOptions, MintVerdict, RevocationCheck, RevocationEntryVerdict, RevocationEntryVerdictReason, TokenVerdict, TokenVerdictReason, VerifyCapabilityTokenOptions, VerifyRevocationEntryOptions, canGrant, mintCapabilityToken, mintRevocationEntry, sig1ToBeSigned, verifyCapabilityToken, verifyRevocationEntry };

package/dist/domain/tokens.d.mts

@@ -1,2 +1,2 @@
-import { _ as verifyRevocationEntry, a as RevocationCheck, c as TokenVerdict, d as VerifyRevocationEntryOptions, f as canGrant, g as verifyCapabilityToken, h as sig1ToBeSigned, i as MintVerdict, l as TokenVerdictReason, m as mintRevocationEntry, n as MintRefusalReason, o as RevocationEntryVerdict, p as mintCapabilityToken, r as MintRevocationEntryOptions, s as RevocationEntryVerdictReason, t as MintCapabilityTokenOptions, u as VerifyCapabilityTokenOptions } from "../tokens-CVyPoJ6l.mjs";
+import { _ as verifyRevocationEntry, a as RevocationCheck, c as TokenVerdict, d as VerifyRevocationEntryOptions, f as canGrant, g as verifyCapabilityToken, h as sig1ToBeSigned, i as MintVerdict, l as TokenVerdictReason, m as mintRevocationEntry, n as MintRefusalReason, o as RevocationEntryVerdict, p as mintCapabilityToken, r as MintRevocationEntryOptions, s as RevocationEntryVerdictReason, t as MintCapabilityTokenOptions, u as VerifyCapabilityTokenOptions } from "../tokens-BVrgBeqF.mjs";
 export { MintCapabilityTokenOptions, MintRefusalReason, MintRevocationEntryOptions, MintVerdict, RevocationCheck, RevocationEntryVerdict, RevocationEntryVerdictReason, TokenVerdict, TokenVerdictReason, VerifyCapabilityTokenOptions, VerifyRevocationEntryOptions, canGrant, mintCapabilityToken, mintRevocationEntry, sig1ToBeSigned, verifyCapabilityToken, verifyRevocationEntry };

package/dist/domain/webrtc-signaling.d.cts

@@ -1,6 +1,6 @@
-import { $t as WebrtcOffer, H as ManageCommandParams, Mt as SfuTrackEntry, Nt as SfuTrackMap, Qt as WebrtcIceCandidate, V as ManageCommand, Zt as WebrtcAnswer, f as CapabilityScope, z as IceCandidateInit } from "../protocol-CNFRVx9w.cjs";
+import { Ft as SfuTrackEntry, H as ManageCommandParams, It as SfuTrackMap, V as ManageCommand, en as WebrtcAnswer, f as CapabilityScope, nn as WebrtcOffer, tn as WebrtcIceCandidate, z as IceCandidateInit } from "../protocol-PhUVprXA.cjs";
 import { IncomingManageRequest } from "./mesh-session.cjs";
-import { u as VerifyCapabilityTokenOptions } from "../tokens-Cl8sQo7o.cjs";
+import { u as VerifyCapabilityTokenOptions } from "../tokens-DIPzZ9JJ.cjs";
 //#region src/domain/webrtc-signaling.d.ts
 /** The one capability verb gating every core/webrtc message shape: an authority over this node's own signaling as a whole, not three separate resources, mirroring how core/exec's exec:pty gates all of its own inner verbs. webrtc.sfu-track-map is gated by this same verb (see spec/webrtc.cddl's own comment): an SFU able to shape a negotiation can already misreport whose media is on which mid, so a separate capability over the track-map itself would guard nothing a client doesn't already have to trust the SFU for. */
 export declare const WEBRTC_SIGNAL_VERB = "webrtc:signal";

package/dist/domain/webrtc-signaling.d.mts

@@ -1,6 +1,6 @@
-import { $t as WebrtcOffer, H as ManageCommandParams, Mt as SfuTrackEntry, Nt as SfuTrackMap, Qt as WebrtcIceCandidate, V as ManageCommand, Zt as WebrtcAnswer, f as CapabilityScope, z as IceCandidateInit } from "../protocol-CNFRVx9w.mjs";
+import { Ft as SfuTrackEntry, H as ManageCommandParams, It as SfuTrackMap, V as ManageCommand, en as WebrtcAnswer, f as CapabilityScope, nn as WebrtcOffer, tn as WebrtcIceCandidate, z as IceCandidateInit } from "../protocol-PhUVprXA.mjs";
 import { IncomingManageRequest } from "./mesh-session.mjs";
-import { u as VerifyCapabilityTokenOptions } from "../tokens-CVyPoJ6l.mjs";
+import { u as VerifyCapabilityTokenOptions } from "../tokens-BVrgBeqF.mjs";
 //#region src/domain/webrtc-signaling.d.ts
 /** The one capability verb gating every core/webrtc message shape: an authority over this node's own signaling as a whole, not three separate resources, mirroring how core/exec's exec:pty gates all of its own inner verbs. webrtc.sfu-track-map is gated by this same verb (see spec/webrtc.cddl's own comment): an SFU able to shape a negotiation can already misreport whose media is on which mid, so a separate capability over the track-map itself would guard nothing a client doesn't already have to trust the SFU for. */
 export declare const WEBRTC_SIGNAL_VERB = "webrtc:signal";

package/dist/generated/protocol.cjs

@@ -37,6 +37,7 @@ const manageCommandParamsSchema = zod.z.lazy(() => zod.z.union([
 	zod.z.object({}).catchall(zod.z.unknown()),
 	zod.z.lazy(() => capabilityRequestSchema),
 	zod.z.lazy(() => capabilityGrantSchema),
+	zod.z.lazy(() => pathTraceSchema),
 	zod.z.union([
 		zod.z.lazy(() => roomSendSchema),
 		zod.z.lazy(() => roomReadSchema),
@@ -155,6 +156,7 @@ const execSessionInfoSchema = zod.z.lazy(() => zod.z.object({
 const frameVariantSchema = zod.z.lazy(() => zod.z.union([
 	zod.z.lazy(() => handshakeFrameSchema),
 	zod.z.lazy(() => pingFrameSchema),
+	zod.z.lazy(() => pongFrameSchema),
 	zod.z.lazy(() => closeFrameSchema),
 	zod.z.lazy(() => gossipFrameSchema),
 	zod.z.lazy(() => candidatesFrameSchema),
@@ -259,6 +261,12 @@ const revocationAnnounceFrameSchema = zod.z.lazy(() => zod.z.object({
 	"type": zod.z.literal("revocation-announce"),
 	"entries": zod.z.array(zod.z.lazy(() => revocationEntrySchema))
 }));
+const pathTraceSchema = zod.z.lazy(() => zod.z.object({ "verb": zod.z.literal("path.trace") }));
+const pathTraceOkSchema = zod.z.lazy(() => zod.z.object({
+	"result": zod.z.literal("ok"),
+	"relayed": zod.z.boolean(),
+	"hub-address": zod.z.string().optional()
+}).catchall(zod.z.unknown()));
 const roomPathSchema = zod.z.lazy(() => zod.z.union([zod.z.lazy(() => ownerNamedRoomPathSchema), zod.z.lazy(() => dmRoomPathSchema)]));
 const deviceIdHexSchema = zod.z.lazy(() => zod.z.string().regex(/* @__PURE__ */ new RegExp("[0-9a-f]{64}")));
 const ownerNamedRoomPathSchema = zod.z.lazy(() => zod.z.string().regex(/* @__PURE__ */ new RegExp("[0-9a-f]{64}/[A-Za-z0-9_-]+")));
@@ -440,6 +448,7 @@ const tokenClaimsSchema = zod.z.lazy(() => zod.z.object({
 	"conditions": zod.z.instanceof(Uint8Array).optional()
 }).catchall(zod.z.unknown()));
 const pingFrameSchema = zod.z.lazy(() => zod.z.object({ "type": zod.z.literal("ping") }));
+const pongFrameSchema = zod.z.lazy(() => zod.z.object({ "type": zod.z.literal("pong") }));
 const closeFrameSchema = zod.z.lazy(() => zod.z.object({
 	"type": zod.z.literal("close"),
 	"reason": zod.z.string().optional()
@@ -583,9 +592,12 @@ exports.namespacedCapabilitySchema = namespacedCapabilitySchema;
 exports.namespacedDomainIdSchema = namespacedDomainIdSchema;
 exports.observedAddressFrameSchema = observedAddressFrameSchema;
 exports.ownerNamedRoomPathSchema = ownerNamedRoomPathSchema;
+exports.pathTraceOkSchema = pathTraceOkSchema;
+exports.pathTraceSchema = pathTraceSchema;
 exports.peerAdvertSchema = peerAdvertSchema;
 exports.peerIdentitySchema = peerIdentitySchema;
 exports.pingFrameSchema = pingFrameSchema;
+exports.pongFrameSchema = pongFrameSchema;
 exports.privateUseCapabilitySchema = privateUseCapabilitySchema;
 exports.privateUseDomainIdSchema = privateUseDomainIdSchema;
 exports.procKillSchema = procKillSchema;