dsh-cherry-bridge 0.1.7 → 0.1.9

package/src/defaults.ts

@@ -81,6 +81,24 @@ export const DEFAULT_CONTENT_READ_BUDGET_PER_SECOND = 256
  */
 export const DEFAULT_TRANSPORT_RETRY_WAIT_MS = 5_000
 
+/**
+ * How long a DEVICE TOOL waits for an establishment attempt that is already in
+ * flight (`state === 'connecting'`) before judging the device.
+ *
+ * WHY THIS EXISTS: the connection pool builds a `DeviceConnection` on FIRST
+ * TOUCH and that constructor dials immediately, so every tool called in the
+ * same tick as the first touch — and every tool called during a reconnect —
+ * observed `connecting` and answered `device-unavailable` about a connection
+ * that comes up a moment later. The state is a transient, not a verdict.
+ *
+ * It is deliberately NOT a reconnect budget: an `offline` device is parked in
+ * its backoff, where waiting cannot change anything, so the tools answer at
+ * once. Five seconds is ~15x a LAN dial plus handshake; a bound longer than
+ * that only delays the unavoidable answer, and the tool call is the caller's
+ * unit of patience.
+ */
+export const DEVICE_SETTLE_WAIT_MS = 5_000
+
 /** 2 MiB of event text cached per session (spec §3.5). */
 export const DEFAULT_PER_SESSION_CACHE_BYTES = 2 * 1024 * 1024
 
@@ -151,5 +169,10 @@ export const LIST_PAGE_CLAMP = 16
  * BOUND instead of being split, hashed and carried to the peer, and so both
  * parameters can declare `maxLength` honestly. ONE number for both faces: it
  * bounds caller INPUT, not what a token means.
+ *
+ * The emit side enforces it too (#76): a stop point whose token would exceed
+ * this is not named at all, because a token this tool refuses to replay is
+ * worse than no token — `truncated` still says the walk was cut. One number,
+ * judged in both directions.
  */
 export const MAX_RESUME_TOKEN_CHARS = 4_096