dsh-cherry-bridge 0.1.6 → 0.1.8

package/src/defaults.ts

@@ -137,3 +137,24 @@ export const INTERACTIONS_LIST_PAGE_CLAMP = Math.floor(
 
 /** Items per every other aggregated list page (agents/sessions/messages). */
 export const LIST_PAGE_CLAMP = 16
+
+/**
+ * Hard ceiling on ONE resume token (issues #70 and #74), in characters.
+ *
+ * BOTH faces take a token back from the caller — `cursor` on the four list
+ * tools, `messagesResumeCursor` on `cherry_read` — and both tail it with a
+ * peer-supplied position whose length we do not control: the desktop's session
+ * cursor is `entity:<orderKey>:<uuid>` (~57 characters), a message cursor
+ * `<ms>:<uuid>`, the numeric `pageOf` faces a handful of digits, and a future
+ * desktop may use something longer — but nothing legitimate comes near this.
+ * The bound exists so a hand-built or model-mangled string is refused by a
+ * 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