@openmarket/rooms-client 0.7.0 → 0.7.1

package/dist/social-client.d.ts

@@ -450,13 +450,27 @@ export declare function markRoomUnread(config: RoomSocialConfig, room: string, s
  * one. The pinned ROOM_SET_ATTENTION frame (setRoomAttentionOnClient)
  * predates `untilMs` and stays the live-session path for permanent
  * postures; servers older than mute-with-duration strip the field and land
- * the mute permanent, so a requested `untilMs` the echo omits fail-closes:
- * the attention is reset and the call throws rather than leave an
- * unbounded mute the caller believes timed. Echoes the persisted
- * attention; `muteUntil` is the ISO expiry, null when none stands.
+ * the mute permanent, so a requested `untilMs` the echo omits is a DROPPED
+ * DEADLINE. By default that fail-closes here: the attention is reset and
+ * the call throws rather than leave an unbounded mute the caller believes
+ * timed. Callers with a richer fail-closed seam of their own opt out via
+ * `onDroppedDeadline: "resolve"` and own the handling (see the option).
+ * Echoes the persisted attention; `muteUntil` is the ISO expiry, null when
+ * none stands (which, under "resolve", is how a dropped deadline reads).
  */
 export declare function setRoomAttentionRest(config: RoomSocialConfig, room: string, attention: RoomTopicAttention, options?: {
     untilMs?: number | undefined;
+    /** What to do when a requested `untilMs` comes back without an echoed
+     *  `muteUntil` (the server predates timed mutes and landed the mute
+     *  PERMANENT). Default "undo-and-throw": reset attention to 'default'
+     *  and throw RoomSocialError 502, so no unbounded mute stands. Pass
+     *  "resolve" ONLY when the caller implements its own dropped-deadline
+     *  handling: the call then performs no undo write and no throw, and
+     *  resolves with `muteUntil: null` for the caller to act on. Canonical
+     *  example: the GUI session seam, which undoes to the last
+     *  WS-confirmed attention, richer than this library's
+     *  undo-to-default. */
+    onDroppedDeadline?: "undo-and-throw" | "resolve" | undefined;
 }): Promise<{
     attention: RoomTopicAttention;
     muteUntil: string | null;

package/dist/social-client.js

@@ -724,10 +724,13 @@ export async function markRoomUnread(config, room, seq) {
  * one. The pinned ROOM_SET_ATTENTION frame (setRoomAttentionOnClient)
  * predates `untilMs` and stays the live-session path for permanent
  * postures; servers older than mute-with-duration strip the field and land
- * the mute permanent, so a requested `untilMs` the echo omits fail-closes:
- * the attention is reset and the call throws rather than leave an
- * unbounded mute the caller believes timed. Echoes the persisted
- * attention; `muteUntil` is the ISO expiry, null when none stands.
+ * the mute permanent, so a requested `untilMs` the echo omits is a DROPPED
+ * DEADLINE. By default that fail-closes here: the attention is reset and
+ * the call throws rather than leave an unbounded mute the caller believes
+ * timed. Callers with a richer fail-closed seam of their own opt out via
+ * `onDroppedDeadline: "resolve"` and own the handling (see the option).
+ * Echoes the persisted attention; `muteUntil` is the ISO expiry, null when
+ * none stands (which, under "resolve", is how a dropped deadline reads).
  */
 export async function setRoomAttentionRest(config, room, attention, options = {}) {
     const body = { attention };
@@ -738,7 +741,9 @@ export async function setRoomAttentionRest(config, room, attention, options = {}
         body,
     });
     const muteUntil = typeof result.muteUntil === "string" ? result.muteUntil : null;
-    if (options.untilMs !== undefined && muteUntil === null) {
+    if (options.untilMs !== undefined &&
+        muteUntil === null &&
+        options.onDroppedDeadline !== "resolve") {
         // The undo cannot know the caller's prior attention, so it deliberately
         // lands 'default' (the same neutral a lapsed timed mute reads as, see
         // resolveTopicAttention) rather than leave the unbounded mute standing.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@openmarket/rooms-client",
-  "version": "0.7.0",
+  "version": "0.7.1",
   "description": "OM Rooms protocol client: wire types, WebSocket + REST clients, and chat view-models. Browser-safe (no node:/bun: imports).",
   "type": "module",
   "license": "Apache-2.0",

package/src/social-client.ts

@@ -1456,16 +1456,32 @@ export async function markRoomUnread(
  * one. The pinned ROOM_SET_ATTENTION frame (setRoomAttentionOnClient)
  * predates `untilMs` and stays the live-session path for permanent
  * postures; servers older than mute-with-duration strip the field and land
- * the mute permanent, so a requested `untilMs` the echo omits fail-closes:
- * the attention is reset and the call throws rather than leave an
- * unbounded mute the caller believes timed. Echoes the persisted
- * attention; `muteUntil` is the ISO expiry, null when none stands.
+ * the mute permanent, so a requested `untilMs` the echo omits is a DROPPED
+ * DEADLINE. By default that fail-closes here: the attention is reset and
+ * the call throws rather than leave an unbounded mute the caller believes
+ * timed. Callers with a richer fail-closed seam of their own opt out via
+ * `onDroppedDeadline: "resolve"` and own the handling (see the option).
+ * Echoes the persisted attention; `muteUntil` is the ISO expiry, null when
+ * none stands (which, under "resolve", is how a dropped deadline reads).
  */
 export async function setRoomAttentionRest(
   config: RoomSocialConfig,
   room: string,
   attention: RoomTopicAttention,
-  options: { untilMs?: number | undefined } = {},
+  options: {
+    untilMs?: number | undefined;
+    /** What to do when a requested `untilMs` comes back without an echoed
+     *  `muteUntil` (the server predates timed mutes and landed the mute
+     *  PERMANENT). Default "undo-and-throw": reset attention to 'default'
+     *  and throw RoomSocialError 502, so no unbounded mute stands. Pass
+     *  "resolve" ONLY when the caller implements its own dropped-deadline
+     *  handling: the call then performs no undo write and no throw, and
+     *  resolves with `muteUntil: null` for the caller to act on. Canonical
+     *  example: the GUI session seam, which undoes to the last
+     *  WS-confirmed attention, richer than this library's
+     *  undo-to-default. */
+    onDroppedDeadline?: "undo-and-throw" | "resolve" | undefined;
+  } = {},
 ): Promise<{ attention: RoomTopicAttention; muteUntil: string | null }> {
   const body: { attention: RoomTopicAttention; untilMs?: number } = { attention };
   if (options.untilMs !== undefined) body.untilMs = options.untilMs;
@@ -1479,7 +1495,11 @@ export async function setRoomAttentionRest(
     body,
   });
   const muteUntil = typeof result.muteUntil === "string" ? result.muteUntil : null;
-  if (options.untilMs !== undefined && muteUntil === null) {
+  if (
+    options.untilMs !== undefined &&
+    muteUntil === null &&
+    options.onDroppedDeadline !== "resolve"
+  ) {
     // The undo cannot know the caller's prior attention, so it deliberately
     // lands 'default' (the same neutral a lapsed timed mute reads as, see
     // resolveTopicAttention) rather than leave the unbounded mute standing.