wire-mesh-core 1.8.0 → 1.9.0

package/dist/domain/mesh-session.cjs

@@ -357,12 +357,13 @@ function createSessionCore(identity, clock, reconnect, dial, onPeerAdvert, addre
 			setToken(token) {
 				currentToken = token;
 			},
-			async sendManageRequest(command, scope, targetDevice, token) {
+			async sendManageRequest(command, scope, targetDevice, token, timeoutMs) {
 				if (connection === null || state.status !== "connected") throw new Error("not connected");
 				if (targetDevice !== void 0) await ensureRelayPairing(targetDevice);
 				const frame = buildManageRequest(command, scope, token);
+				const requestId = frame["request-id"];
 				const outcome = new Promise((resolve, reject) => {
-					pendingManageRequests.set(frame["request-id"], {
+					pendingManageRequests.set(requestId, {
 						resolve,
 						reject
 					});
@@ -373,7 +374,15 @@ function createSessionCore(identity, clock, reconnect, dial, onPeerAdvert, addre
 				});
 				await transmit(frame, targetDevice !== void 0);
 				emit();
-				return outcome;
+				if (timeoutMs === void 0) return outcome;
+				return Promise.race([outcome, new Promise((resolve) => {
+					setTimeout(() => {
+						if (pendingManageRequests.delete(requestId)) resolve({
+							result: "error",
+							code: "timeout"
+						});
+					}, timeoutMs);
+				})]);
 			},
 			async sendRevocationAnnounce(entries) {
 				if (connection === null || state.status !== "connected") throw new Error("not connected");

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

@@ -81,8 +81,8 @@ export interface MeshSession {
   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. */
   sendRevocationAnnounce: (entries: readonly RevocationEntry[]) => Promise<void>;
-  /** Sends a manage-request and resolves with the matching manage-response's outcome, correlated by request-id. When targetDevice is given, the request is routed to that specific peer via an established relay-connect pairing (wrapped as relay-data) rather than sent directly over this session's own Connection -- relay-hub deliberately drops manage-request/manage-response frames sent to it directly, since routing between two connected peers is not the relay role's business, so a specific peer reachable only through a relay hub can only be addressed this way. Absent, this sends directly over the Connection exactly as before. When token is given, it is attached to this one request instead of whatever setToken last set -- a single session routinely needs a different token per request when its peer shares more than one scope with this side (e.g. several core/room memberships over one connection), and a session-global token can only ever be correct for one of them. Absent, this request carries setToken's own session-global token exactly as before. */
-  sendManageRequest: (command: ManageCommand, scope: Readonly<CapabilityScope>, targetDevice?: DeviceId, token?: CapabilityToken) => Promise<ManageOutcome>;
+  /** Sends a manage-request and resolves with the matching manage-response's outcome, correlated by request-id. When targetDevice is given, the request is routed to that specific peer via an established relay-connect pairing (wrapped as relay-data) rather than sent directly over this session's own Connection -- relay-hub deliberately drops manage-request/manage-response frames sent to it directly, since routing between two connected peers is not the relay role's business, so a specific peer reachable only through a relay hub can only be addressed this way. Absent, this sends directly over the Connection exactly as before. When token is given, it is attached to this one request instead of whatever setToken last set -- a single session routinely needs a different token per request when its peer shares more than one scope with this side (e.g. several core/room memberships over one connection), and a session-global token can only ever be correct for one of them. Absent, this request carries setToken's own session-global token exactly as before. When timeoutMs is given, the returned promise resolves with `{ result: "error", code: "timeout" }` rather than hanging forever if no manage-response arrives in time -- a held-open request (a human approval, a not-yet-online peer) otherwise has no way for the caller to give up on it. Absent, this request waits exactly as before, with no time limit of its own. */
+  sendManageRequest: (command: ManageCommand, scope: Readonly<CapabilityScope>, targetDevice?: DeviceId, token?: CapabilityToken, timeoutMs?: number) => Promise<ManageOutcome>;
   close: () => Promise<void>;
 }
 export declare function createMeshSession(transport: Readonly<Transport>, identity: Readonly<IdentityPort>, clock?: Readonly<Clock>, reconnect?: ReconnectPolicy | null,

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

@@ -81,8 +81,8 @@ export interface MeshSession {
   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. */
   sendRevocationAnnounce: (entries: readonly RevocationEntry[]) => Promise<void>;
-  /** Sends a manage-request and resolves with the matching manage-response's outcome, correlated by request-id. When targetDevice is given, the request is routed to that specific peer via an established relay-connect pairing (wrapped as relay-data) rather than sent directly over this session's own Connection -- relay-hub deliberately drops manage-request/manage-response frames sent to it directly, since routing between two connected peers is not the relay role's business, so a specific peer reachable only through a relay hub can only be addressed this way. Absent, this sends directly over the Connection exactly as before. When token is given, it is attached to this one request instead of whatever setToken last set -- a single session routinely needs a different token per request when its peer shares more than one scope with this side (e.g. several core/room memberships over one connection), and a session-global token can only ever be correct for one of them. Absent, this request carries setToken's own session-global token exactly as before. */
-  sendManageRequest: (command: ManageCommand, scope: Readonly<CapabilityScope>, targetDevice?: DeviceId, token?: CapabilityToken) => Promise<ManageOutcome>;
+  /** Sends a manage-request and resolves with the matching manage-response's outcome, correlated by request-id. When targetDevice is given, the request is routed to that specific peer via an established relay-connect pairing (wrapped as relay-data) rather than sent directly over this session's own Connection -- relay-hub deliberately drops manage-request/manage-response frames sent to it directly, since routing between two connected peers is not the relay role's business, so a specific peer reachable only through a relay hub can only be addressed this way. Absent, this sends directly over the Connection exactly as before. When token is given, it is attached to this one request instead of whatever setToken last set -- a single session routinely needs a different token per request when its peer shares more than one scope with this side (e.g. several core/room memberships over one connection), and a session-global token can only ever be correct for one of them. Absent, this request carries setToken's own session-global token exactly as before. When timeoutMs is given, the returned promise resolves with `{ result: "error", code: "timeout" }` rather than hanging forever if no manage-response arrives in time -- a held-open request (a human approval, a not-yet-online peer) otherwise has no way for the caller to give up on it. Absent, this request waits exactly as before, with no time limit of its own. */
+  sendManageRequest: (command: ManageCommand, scope: Readonly<CapabilityScope>, targetDevice?: DeviceId, token?: CapabilityToken, timeoutMs?: number) => Promise<ManageOutcome>;
   close: () => Promise<void>;
 }
 export declare function createMeshSession(transport: Readonly<Transport>, identity: Readonly<IdentityPort>, clock?: Readonly<Clock>, reconnect?: ReconnectPolicy | null,

package/dist/domain/mesh-session.mjs

@@ -356,12 +356,13 @@ function createSessionCore(identity, clock, reconnect, dial, onPeerAdvert, addre
 			setToken(token) {
 				currentToken = token;
 			},
-			async sendManageRequest(command, scope, targetDevice, token) {
+			async sendManageRequest(command, scope, targetDevice, token, timeoutMs) {
 				if (connection === null || state.status !== "connected") throw new Error("not connected");
 				if (targetDevice !== void 0) await ensureRelayPairing(targetDevice);
 				const frame = buildManageRequest(command, scope, token);
+				const requestId = frame["request-id"];
 				const outcome = new Promise((resolve, reject) => {
-					pendingManageRequests.set(frame["request-id"], {
+					pendingManageRequests.set(requestId, {
 						resolve,
 						reject
 					});
@@ -372,7 +373,15 @@ function createSessionCore(identity, clock, reconnect, dial, onPeerAdvert, addre
 				});
 				await transmit(frame, targetDevice !== void 0);
 				emit();
-				return outcome;
+				if (timeoutMs === void 0) return outcome;
+				return Promise.race([outcome, new Promise((resolve) => {
+					setTimeout(() => {
+						if (pendingManageRequests.delete(requestId)) resolve({
+							result: "error",
+							code: "timeout"
+						});
+					}, timeoutMs);
+				})]);
 			},
 			async sendRevocationAnnounce(entries) {
 				if (connection === null || state.status !== "connected") throw new Error("not connected");

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "wire-mesh-core",
-  "version": "1.8.0",
+  "version": "1.9.0",
   "type": "module",
   "packageManager": "pnpm@10.33.0",
   "repository": {