dsh-zen-remote 2.2.7 → 2.2.9

package/src/relay-client.ts

@@ -57,6 +57,9 @@ const RELAY_PROTOCOL = 1
 const HANDSHAKE_PATH = '/_dsh/zen-remote/relay/v1/handshake'
 const INVOKE_PATH = '/_dsh/zen-remote/relay/v1/invoke'
 const STREAM_PATH = '/_dsh/zen-remote/relay/v1/stream'
+/** the relay's existing authenticated health route
+ * (`GET …/relay/ping`, answers `{ok:true}`). Used by probeHealth() only. */
+const PING_PATH = '/_dsh/zen-remote/relay/ping'
 const UNSHARE_PATH = '/_dsh/zen-remote/relay/v1/unshare'
 const EVENT_RESULT_PATH = '/_dsh/zen-remote/relay/v1/event-result'
 const HTTP_PATH = '/_dsh/zen-remote/relay/v1/http'
@@ -318,6 +321,18 @@ export interface RelayClient {
    * ladder (the settings page's 立即重连). Answers whether an attempt was
    * started — the reconnect route turns a false into a 409. */
   reconnect(): boolean
+
+  /** ONE lightweight authenticated health probe
+   * (`GET /ping`). Never changes `state`; de-duplicated while in flight;
+   * resolves false on any refusal. NOT a poller — call it on a real signal. */
+  probeHealth(): Promise<boolean>
+
+  /** a CONTROLLED fast-path for a reliable
+   * "network is back" signal. Fires only from `offline`, refuses within
+   * NETWORK_HINT_MIN_GAP_MS of the previous hint (no storm), and otherwise
+   * behaves exactly like reconnect(). connect() de-duplicates concurrent
+   * attempts via connectInFlight. Answers whether an attempt started. */
+  networkRestored(): boolean
   /** Notify that the credentials source may have changed (the loader's
    * volatile-update for the row): a pending reconnect wait is cancelled and,
    * with credentials present, one immediate attempt runs with the new
@@ -1308,6 +1323,62 @@ export function createRelayClient(options: CreateRelayClientOptions): RelayClien
     return true
   }
 
+  /**
+   * one authenticated `GET /ping` — the independent
+   * health confirmation a restored link needs when no business traffic is
+   * flowing. Never throws, never moves `state`, de-duplicated in flight.
+   */
+  let healthProbeInFlight: Promise<boolean> | undefined
+  async function probeHealth(): Promise<boolean> {
+    if (healthProbeInFlight !== undefined) return healthProbeInFlight
+    const attempt = (async (): Promise<boolean> => {
+      let creds: { url: string, token: string }
+      try {
+        creds = requireCredentials()
+      } catch {
+        return false
+      }
+      const ac = new AbortController()
+      const timer = setTimeout(() => ac.abort(), Math.min(requestTimeoutMs, 8_000))
+      if (typeof timer.unref === 'function') timer.unref()
+      try {
+        const response = await fetchImpl(`${creds.url}${PING_PATH}`, {
+          method: 'GET',
+          headers: {
+            authorization: `Bearer ${creds.token}`,
+            accept: 'application/json',
+          },
+          redirect: 'manual',
+          signal: ac.signal,
+        })
+        return response.ok
+      } catch {
+        return false
+      } finally {
+        clearTimeout(timer)
+      }
+    })()
+    healthProbeInFlight = attempt
+    try {
+      return await attempt
+    } finally {
+      if (healthProbeInFlight === attempt) healthProbeInFlight = undefined
+    }
+  }
+
+  /** controlled fast-path; see the interface note. */
+  const NETWORK_HINT_MIN_GAP_MS = 3_000
+  let lastNetworkHintAt = 0
+  function networkRestored(): boolean {
+    if (stopped || state !== 'offline') return false
+    const now = clock.now()
+    if (now - lastNetworkHintAt < NETWORK_HINT_MIN_GAP_MS) return false
+    lastNetworkHintAt = now
+    cancelRetry()
+    void connect().catch(() => {})
+    return true
+  }
+
   /**
    * The credentials source moved (a pairing write, an unpair, a hand edit
    * committed by the loader): drop any pending wait — the ladder belongs to
@@ -1907,6 +1978,11 @@ export function createRelayClient(options: CreateRelayClientOptions): RelayClien
     queueDeviceName,
     connect,
     reconnect,
+    // the two new surfaces. `probeHealth` is the
+    // authenticated GET /ping health check (never moves `state`);
+    // `networkRestored` is the controlled fast-path (offline-only + 3s gap).
+    probeHealth,
+    networkRestored,
     credentialsChanged,
     stop,
     invoke,

package/lib/types/client/host-attach.d.ts

@@ -1,38 +0,0 @@
-/**
- * The host composer's own hidden file picker, when the running DSH ships one.
- *
- * DSH 0.1.5 grew a native attachment flow (dsh-attachment / dsh-client-file-
- * upload): the official tool row carries a second `_add` paperclip whose click
- * drives an `<input type="file" hidden>` that is a DIRECT sibling of the
- * buttons inside `_tools`. That input is the one structural, locale-free
- * proof that the host implements composer attachment upload — the button
- * itself can only be told apart from the "+" command menu by its localized
- * aria-label, and the capability prop (`addFiles`) lives on the composer
- * bar's own inject face, which never reaches `conversation.input.left`
- * registrants. Scoped to `_tools` children so a third-party plugin parking
- * its own file input somewhere else in the composer cannot be misread as
- * the official feature; `:not([data-mobile-nav])` keeps OUR picker
- * (`attach-picker`) out of the match.
- */
-export declare const HOST_ATTACH_INPUT = "[data-slot=\"conversation.composer.bar\"] [class$=\"_tools\"] > input[type=\"file\"]:not([data-mobile-nav])";
-/** Synchronous read: does this host's composer ship its own attach picker? */
-export declare function hostAttachPresent(): boolean;
-/**
- * True while OUR attachment UI should mount (the host has none of its own).
- *
- * The rule this encodes (2026-09-11): where the host implements attachment
- * upload, the phone composer shows exactly ONE attach control — the host's —
- * and this plugin's S7 button and chips row stand down; on a host without
- * one (DSH ≤ 0.1.2), both load as they always have.
- *
- * `useLayoutEffect`, not `useEffect`: on the composer's very first mount our
- * slot child renders in the same React pass as the host's tool row, so the
- * state initializer below reads the DOM BEFORE either exists — the layout
- * effect re-checks after the commit and before the browser paints, so the
- * demotion to hidden (or, on an old host, the decision to stay) never
- * reaches the screen as a flash. The MutationObserver covers the lifetime
- * after that: the picker's existence only really changes with the page, but
- * a dynamic host plugin or a reload must not strand a stale verdict.
- */
-export declare function useOwnAttachUi(): boolean;
-//# sourceMappingURL=host-attach.d.ts.map

package/lib/types/client/host-attach.d.ts.map

@@ -1 +0,0 @@
-{"version":3,"file":"host-attach.d.ts","sourceRoot":"","sources":["../../../src/client/host-attach.ts"],"names":[],"mappings":"AAEA;;;;;;;;;;;;;;;GAeG;AACH,eAAO,MAAM,iBAAiB,gHAC2E,CAAA;AAEzG,8EAA8E;AAC9E,wBAAgB,iBAAiB,IAAI,OAAO,CAE3C;AAED;;;;;;;;;;;;;;;;GAgBG;AACH,wBAAgB,cAAc,IAAI,OAAO,CAUxC"}

package/src/client/host-attach.ts

@@ -1,54 +0,0 @@
-import { useLayoutEffect, useState } from 'react'
-
-/**
- * The host composer's own hidden file picker, when the running DSH ships one.
- *
- * DSH 0.1.5 grew a native attachment flow (dsh-attachment / dsh-client-file-
- * upload): the official tool row carries a second `_add` paperclip whose click
- * drives an `<input type="file" hidden>` that is a DIRECT sibling of the
- * buttons inside `_tools`. That input is the one structural, locale-free
- * proof that the host implements composer attachment upload — the button
- * itself can only be told apart from the "+" command menu by its localized
- * aria-label, and the capability prop (`addFiles`) lives on the composer
- * bar's own inject face, which never reaches `conversation.input.left`
- * registrants. Scoped to `_tools` children so a third-party plugin parking
- * its own file input somewhere else in the composer cannot be misread as
- * the official feature; `:not([data-mobile-nav])` keeps OUR picker
- * (`attach-picker`) out of the match.
- */
-export const HOST_ATTACH_INPUT =
-  '[data-slot="conversation.composer.bar"] [class$="_tools"] > input[type="file"]:not([data-mobile-nav])'
-
-/** Synchronous read: does this host's composer ship its own attach picker? */
-export function hostAttachPresent(): boolean {
-  return document.querySelector(HOST_ATTACH_INPUT) !== null
-}
-
-/**
- * True while OUR attachment UI should mount (the host has none of its own).
- *
- * The rule this encodes (2026-09-11): where the host implements attachment
- * upload, the phone composer shows exactly ONE attach control — the host's —
- * and this plugin's S7 button and chips row stand down; on a host without
- * one (DSH ≤ 0.1.2), both load as they always have.
- *
- * `useLayoutEffect`, not `useEffect`: on the composer's very first mount our
- * slot child renders in the same React pass as the host's tool row, so the
- * state initializer below reads the DOM BEFORE either exists — the layout
- * effect re-checks after the commit and before the browser paints, so the
- * demotion to hidden (or, on an old host, the decision to stay) never
- * reaches the screen as a flash. The MutationObserver covers the lifetime
- * after that: the picker's existence only really changes with the page, but
- * a dynamic host plugin or a reload must not strand a stale verdict.
- */
-export function useOwnAttachUi(): boolean {
-  const [own, setOwn] = useState(() => !hostAttachPresent())
-  useLayoutEffect(() => {
-    const check = (): void => setOwn(!hostAttachPresent())
-    const observer = new MutationObserver(check)
-    observer.observe(document.body, { childList: true, subtree: true })
-    check()
-    return () => observer.disconnect()
-  }, [])
-  return own
-}