dsh-connect-workbuddy 5.3.1 → 5.5.0

package/lib/{host-heartbeat-BHESQ6Ah.js → host-heartbeat-CVnH8S3J.js}

@@ -1784,6 +1784,16 @@ const GLOBAL_CONFIG_PATH = "/v3/config";
 * host- and identity-insensitive on the CN side (measured 2026-10-21 on all
 * three CN hosts, under both the CLI and the app user agent: byte-identical),
 * so it is asked as the chat channel's own identity.
+*
+* IT DOES NOT EXIST ON THE GLOBAL GATEWAY. Measured 2026-10-22: this exact POST
+* against `www.workbuddy.ai` answers 404 `Route Not Found` (as do the four
+* neighbouring spellings tried under both POST and GET), while the same
+* credential reads that gateway's `/v3/config` normally and finds no load field
+* on any model. {@link WorkBuddyUpstreamClient.fetchModelBusy} is therefore
+* expected to THROW for that region — `withBusyLevels` in `src/index.ts` catches
+* it and ships the roster without levels. Kept as-is rather than region-gated:
+* the day upstream adds it, this needs no change, and the cost today is one
+* 404 per refresh that never blocks anything.
 */
 const MODEL_BUSY_PATH = "/v2/chat/busy";
 /**
@@ -2018,21 +2028,21 @@ const CONTEXT_OVERFLOW_MARKER = "prompt is too long (upstream code 11115)";
 */
 const CHANNEL_REJECT_MARKERS = ["unapproved channel", "illegal api invocation"];
 /**
-* The other gates that answer the SAME business code.
+* The wordings that identify the OTHER two members of the `11128` family.
 *
-* Excluded explicitly so a body that also carries the channel wording can never
-* be read as the prompt rule: a confidently wrong diagnosis is worse here than
-* the generic `client` reply, because it sends the user to rewrite a system
-* prompt that is not at fault.
+* Used ONLY to NAME a member ({@link channelGateMemberOf}), never to exclude a
+* body from the family. The old code used them as an exclusion list, which is
+* how issue #113's misreported refusal was kept out of the plugin's retry
+* ladder: the upstream wrote `conversation id missing` over a content refusal,
+* and the exclusion believed it.
 *
-* Each is also exported as its own predicate ({@link isConversationIdGateBody},
+* Each is exported as its own predicate ({@link isConversationIdGateBody},
 * {@link isFirstMessageGateBody}) so the reply can NAME the gate instead of
 * relaying the upstream's `displayTips` — which is the SAME misleading
 * sentence for all three members of the `11128` family.
 */
 const CONVERSATION_ID_GATE_MARKER = "conversation id missing";
 const FIRST_MESSAGE_GATE_MARKER = "first message is not system prompt";
-const OTHER_CHANNEL_CODE_GATES = [CONVERSATION_ID_GATE_MARKER, FIRST_MESSAGE_GATE_MARKER];
 /**
 * Whether a failure body is the MODEL-scoped throttle rather than an account
 * limit.
@@ -2054,20 +2064,50 @@ function isModelBusyBody(body) {
 	return body.includes(MODEL_BUSY_CODE);
 }
 /**
-* Whether a failure body is the gateway's CHANNEL gate rather than the other
-* `11128` ({@link conversationHeaders}' `conversation id missing`).
+* Whether a failure body belongs to the `11128` gate family AT ALL.
 *
-* Both halves are required. The code alone would claim the conversation-id gate
-* too, and its reply would then blame the prompt's opening for a request-header
-* problem the plugin already fixed — a confidently wrong diagnosis is worse
-* here than the generic `client` reply, because it sends the user to rewrite a
-* system prompt that is not at fault.
+* The code is matched in its quoted-key form (`"code":11128`): a request id is
+* hexadecimal and can contain the digits `11128` by coincidence, and a bare
+* substring search over an arbitrary failure body is how a red herring gets
+* promoted into a diagnosis.
+*/
+function isChannelGateFamilyBody(body) {
+	return body.includes(CHANNEL_REJECT_CODE);
+}
+/**
+* Whether a failure body is the gateway's CHANNEL gate — i.e. whether it
+* belongs to the `11128` FAMILY.
+*
+* ISSUE #113, AND WHY THIS NOW ANSWERS "IS IT THE FAMILY" RATHER THAN "IS IT
+* THE PROMPT MEMBER". The family has three members (prompt fingerprint,
+* missing conversation id, missing system head) sharing one business code and
+* one `displayTips` sentence, so the `msg` wording used to be the only thing
+* that could tell them apart — and the wording is NOT reliable. Issue #113
+* measured a CN refusal whose `msg` read `conversation id missing` while the
+* three conversation-id headers were all present and correct; the refusal was
+* about the request's CONTENT.
+*
+* The old rule required the channel wording AND the absence of the sibling
+* wordings, so such a body was excluded from the channel gate entirely and
+* filed as a plain `client`. That was not cosmetic: `client` never enters the
+* plugin's two-step retry ladder (`forceNeutralHead`, then the invisible
+* perturbation), so the rescue path that exists for precisely this refusal
+* never ran. That is very likely why the reporters in issue #98's thread found
+* that upgrading changed nothing.
+*
+* Every member of this family is a CHANNEL-verification refusal — the
+* upstream's own shared sentence says so — so acting on the family is correct
+* whoever the member is. Which member it is decides only what the reply
+* ADVISES, and that is {@link channelGateMemberOf}'s job, decided by the
+* plugin's own evidence rather than by a wording the upstream may misreport.
+*
+* The code is matched in its quoted-key form (`"code":11128`): a request id is
+* hexadecimal and can contain the digits `11128` by coincidence, and a bare
+* substring search over an arbitrary failure body is how a red herring gets
+* promoted into a diagnosis.
 */
 function isChannelRejectBody(body) {
-	if (!body.includes(CHANNEL_REJECT_CODE)) return false;
-	const lower = body.toLowerCase();
-	if (OTHER_CHANNEL_CODE_GATES.some((marker) => lower.includes(marker))) return false;
-	return CHANNEL_REJECT_MARKERS.some((marker) => lower.includes(marker));
+	return isChannelGateFamilyBody(body);
 }
 /**
 * Whether a failure body is the CONVERSATION-ID gate (`11128`).
@@ -2110,6 +2150,46 @@ function isFirstMessageGateBody(body) {
 	return lower.includes(CHANNEL_REJECT_CODE) && lower.includes(FIRST_MESSAGE_GATE_MARKER);
 }
 /**
+* Which member of the `11128` family a body is, decided by the plugin's OWN
+* evidence rather than by the upstream's wording.
+*
+* THE EVIDENCE, IN ORDER OF STRENGTH.
+*
+* 1. The body carries the channel wording (`unapproved channel` /
+*    `illegal api invocation`). That is the upstream naming the PROMPT gate
+*    explicitly, so it is trusted.
+* 2. The body says `conversation id missing`. The wording is only believable
+*    when the request did NOT carry the conversation-id triple; the plugin's
+*    `chatHeaders` adds it to every chat request, so in practice it is always
+*    there and the wording is always a misreport — which is issue #113's
+*    exact measurement. The refusal is then about the CONTENT, i.e. the
+*    PROMPT gate, which is also the only member the plugin can act on.
+* 3. The body names the first-message gate. That gate is about the request's
+*    SHAPE, and `ensureSystemHead` guarantees a `system` head whenever the
+*    request carries messages, so it is only reported as that gate when the
+*    request genuinely had none.
+* 4. Otherwise: `unknown`. The family is still the family — the retry ladder
+*    applies — but the reply says it cannot name the member rather than
+*    guessing, because a confidently wrong diagnosis sends the user to edit a
+*    prompt that is not at fault.
+*
+* @param body The failure body.
+* @param request What the plugin knows about the request it just sent.
+*/
+function channelGateMemberOf(body, request) {
+	const lower = body.toLowerCase();
+	if (CHANNEL_REJECT_MARKERS.some((marker) => lower.includes(marker))) return "prompt";
+	if (lower.includes(CONVERSATION_ID_GATE_MARKER)) {
+		if (request?.hasConversationHeaders === false) return "headers";
+		return "prompt";
+	}
+	if (lower.includes(FIRST_MESSAGE_GATE_MARKER)) {
+		if (request?.hasSystemHead === false) return "first_message";
+		return "unknown";
+	}
+	return "unknown";
+}
+/**
 * The OPENINGS of the `system` messages in a prepared request body.
 *
 * REMOVED in favour of {@link systemOpeningEvidenceOfBody}, which answers the
@@ -2124,7 +2204,15 @@ const SYSTEM_OPENING_LIMIT = 120;
 function clip(text, limit) {
 	return text.length <= limit ? text : `${text.slice(0, limit - 1)}…`;
 }
-/** Classify an upstream failure from its HTTP status and body excerpt. */
+/**
+* Classify an upstream failure from its HTTP status and body excerpt.
+*
+* The `11128` family is classified BY ITS CODE, not by the `msg` wording —
+* see {@link isChannelRejectBody} and {@link channelGateMemberOf}. Which
+* member of the family it is decides the ADVICE in the reply, never the
+* classification: every member is a channel-verification refusal that no
+* account, region or top-up can change.
+*/
 function classifyUpstreamError(status, body) {
 	if (status === 402) return "hard_credit";
 	const lower = body.toLowerCase();
@@ -2176,6 +2264,7 @@ function parseUpstreamErrorDetail(body) {
 	const detail = {};
 	if (typeof raw.code === "number") detail.upstreamCode = raw.code;
 	if (typeof raw.requestId === "string") detail.requestId = raw.requestId;
+	if (typeof raw.msg === "string" && raw.msg !== "") detail.rawMsg = raw.msg;
 	if (displayMsg !== void 0) detail.displayMsg = displayMsg;
 	if (tips !== void 0) detail.tips = tips;
 	const ext = raw.extError;
@@ -2654,6 +2743,28 @@ function forceNeutralHead(bodyJson) {
 */
 const ZERO_WIDTH_SPACE = "​";
 /**
+* Where an invisible break is inserted INSIDE a capitalised word pair, so a
+* bare product name stops matching as an exact substring.
+*
+* WHY THE PUNCTUATION RULE IS NOT ENOUGH. The boundary rules above only land
+* where there is a `.`, `!`, `?`, `,`, `;` — so a scanned message that ends
+* with a bare product name and no trailing punctuation (``… powered by
+* DeepSeek Harness ``, the host's own agent line, ending at end-of-text) is
+* left COMPLETELY UNCHANGED. `perturbChannelFingerprints` then answers
+* `undefined`, the shim spends no retry, and the fingerprint survives the
+* rescue — measured, and it is the shape issue #113's reporter is most likely
+* to hit, because that line is the first line of every DSH agent prompt.
+*
+* This rule breaks between a capitalised word and the following capitalised
+* word (“DeepSeek|Harness”, “Visual|Studio”), which covers product names
+* without touching ordinary prose: a sentence rarely has two capitalised
+* words adjacent UNLESS they are a proper name, and breaking a proper name is
+* exactly the intent. The model reads straight through U+200B, so what it
+* understands is unchanged — that is the whole point of using it for this
+* rather than rewriting the text.
+*/
+const WORD_INTERNAL_BREAK = /([A-Z][A-Za-z0-9]*)(\s+)(?=[A-Z][A-Za-z0-9])/gu;
+/**
 * A body whose scanned message TEXT is perturbed just enough to break an exact
 * content fingerprint.
 *
@@ -2709,7 +2820,7 @@ function perturbChannelFingerprints(bodyJson) {
 	let changed = false;
 	const perturb = (text) => {
 		if (text.includes(ZERO_WIDTH_SPACE)) return void 0;
-		const next = text.replace(/([.!?])(\s+)/gu, `$1${ZERO_WIDTH_SPACE}$2`).replace(/([。！？])/gu, `$1${ZERO_WIDTH_SPACE}`).replace(/([,;])(\s+)/gu, `$1${ZERO_WIDTH_SPACE}$2`);
+		const next = text.replace(/([.!?])(\s+)/gu, `$1${ZERO_WIDTH_SPACE}$2`).replace(/([。！？])/gu, `$1${ZERO_WIDTH_SPACE}`).replace(/([,;])(\s+)/gu, `$1${ZERO_WIDTH_SPACE}$2`).replace(WORD_INTERNAL_BREAK, (whole, head, tail) => `${head}${ZERO_WIDTH_SPACE}${tail}`);
 		return next === text ? void 0 : next;
 	};
 	for (const value of messages) {
@@ -3278,6 +3389,57 @@ function withPromos(models, data) {
 	return promos.length === 0 ? models : attachPromos(models, promos);
 }
 /**
+* What the plugin can tell about the request it just sent, for telling the
+* `11128` family apart.
+*
+* TWO FACTS, both read from the request body rather than from the upstream's
+* `msg` — which issue #113 measured to be unreliable (a content refusal
+* reported as `conversation id missing`).
+*
+* - `hasSystemHead`: does the request open with a `system` message? The
+*   plugin guarantees it does whenever the request carries messages
+*   (`ensureSystemHead`), so a body claiming the first-message gate is only
+*   believable when this is false.
+* - `hasConversationHeaders`: did the request carry the conversation-id
+*   triple? `chatHeaders` always adds it, so this is true in practice — and
+*   that is exactly what makes a `conversation id missing` wording
+*   unbelievable.
+*
+* Never throws: a body that cannot be read answers "unknown", which is the
+* safe direction (the wording is then believed).
+*/
+function requestEvidenceOf(bodyJson) {
+	const hasConversationHeaders = true;
+	let parsed;
+	try {
+		parsed = JSON.parse(bodyJson);
+	} catch {
+		return {
+			hasSystemHead: false,
+			hasConversationHeaders
+		};
+	}
+	if (typeof parsed !== "object" || parsed === null || Array.isArray(parsed)) return {
+		hasSystemHead: false,
+		hasConversationHeaders
+	};
+	const messages = parsed["messages"];
+	if (!Array.isArray(messages)) return {
+		hasSystemHead: false,
+		hasConversationHeaders
+	};
+	const first = messages[0];
+	if (typeof first !== "object" || first === null || Array.isArray(first)) return {
+		hasSystemHead: false,
+		hasConversationHeaders
+	};
+	const role = first["role"];
+	return {
+		hasSystemHead: role === "system" || role === "developer",
+		hasConversationHeaders
+	};
+}
+/**
 * Upstream HTTP client. One instance serves the whole plugin; requests take
 * the credential explicitly so token refreshes apply on the next call.
 */
@@ -5804,7 +5966,7 @@ function generationOf(version) {
 //#endregion
 //#region src/version.ts
 /** The npm package version this build was produced from. */
-const WORKBUDDY_CONNECT_VERSION = "5.3.1";
+const WORKBUDDY_CONNECT_VERSION = "5.5.0";
 //#endregion
 //#region src/host-heartbeat.ts
 /**
@@ -5962,4 +6124,4 @@ async function clearHostHeartbeat() {
 	await rm(workbuddyHostHeartbeatPath(), { force: true });
 }
 //#endregion
-export { regionOf as $, parseWorkBuddyAuth as A, hostPeersInfo as At, forceNeutralHead as B, defaultDesktopAuthCandidates as C, isEncryptedFieldWrapper as Ct, isEncryptedCredentialError as D, openEncryptedField as Dt, hasEncryptedCredentialFields as E, macosNestedAppBundles as Et, WORKBUDDY_FALLBACK_SYSTEM_PROMPT as F, knownRegionOf as G, isConversationIdGateBody as H, WorkBuddyCredentialRejectedError as I, parseCreditMultiplier as J, modelIdOfBody as K, WorkBuddyUpstreamClient as L, workbuddyOwnAuthPath as M, withFileLock as Mt, CONTEXT_OVERFLOW_MARKER as N, writeFileAtomic as Nt, isVaultAccountId as O, readAtRestKey as Ot, CREDENTIAL_REJECTED_CODE as P, prepareChatBody as Q, classifyUpstreamError as R, authFileName as S, findWorkbuddyAppExecutableWithSource as St, defaultDesktopAuthPath as T, macosBundleExecutable as Tt, isCredentialRejectedError as U, isContextTooLongBody as V, isFirstMessageGateBody as W, parseUpstreamModel as X, parseReasoning as Y, perturbChannelFingerprints as Z, ENCRYPTED_CREDENTIAL_CODE as _, clearAtRestKeyCache as _t, readHostHeartbeat as a, offRefused as at, WorkBuddyCredentialStore as b, fetchAtRestKeyPayload as bt, WORKBUDDY_CONNECT_VERSION as c, DEFAULT_IMAGE_SIZE as ct, FALLBACK_WORKBUDDY_MODELS_GLOBAL as d, parseQueueAnswer as dt, attachBusyLevels as et, WorkBuddyCatalog as f, queueNoticeText as ft, withoutRouters as g, WORKBUDDY_APP_EXECUTABLE_ENV as gt, fallbackModelsFor as h, nativeModalityOf as ht, processStartTimeMs as i, offDefaultFor as it, workbuddyAccountId as j, resolveDshHome as jt, legacyWorkbuddyOwnAuthPath as k, workbuddyAppExecutableCandidates as kt, piAiRuntimeInfo as l, WorkBuddyImageError as lt, deriveCatalog as m, imageDefaultFor as mt, clearHostHeartbeat as n, defaultOffModelIds as nt, workbuddyHostHeartbeatPath as o, recordRefusal as ot, applyContextBudgets as p, NATIVE_MODALITY_BY_MODEL_ID as pt, openingEvidenceOfBody as q, isHeartbeatProcessAlive as r, lastRefusalFor as rt, writeHostHeartbeat as s, withEffectiveOff as st, WORKBUDDY_HOST_HEARTBEAT_FILENAME as t, REFUSES_OFF_MODEL_IDS as tt, FALLBACK_WORKBUDDY_MODELS as u, pickImageModel as ut, WORKBUDDY_AUTH_FILENAME as v, deriveAtRestKey as vt, defaultDesktopAuthDirs as w, isWorkbuddyBundle as wt, WorkBuddyEncryptedCredentialError as x, findWorkbuddyAppExecutable as xt, WORKBUDDY_AUTH_FILE_ENV as y, deriveAtRestKeyId as yt, declaredTools as z };
+export { prepareChatBody as $, parseWorkBuddyAuth as A, readAtRestKey as At, declaredTools as B, defaultDesktopAuthCandidates as C, findWorkbuddyAppExecutable as Ct, isEncryptedCredentialError as D, macosBundleExecutable as Dt, hasEncryptedCredentialFields as E, isWorkbuddyBundle as Et, WORKBUDDY_FALLBACK_SYSTEM_PROMPT as F, writeFileAtomic as Ft, isFirstMessageGateBody as G, isContextTooLongBody as H, WorkBuddyCredentialRejectedError as I, openingEvidenceOfBody as J, knownRegionOf as K, WorkBuddyUpstreamClient as L, workbuddyOwnAuthPath as M, hostPeersInfo as Mt, CONTEXT_OVERFLOW_MARKER as N, resolveDshHome as Nt, isVaultAccountId as O, macosNestedAppBundles as Ot, CREDENTIAL_REJECTED_CODE as P, withFileLock as Pt, perturbChannelFingerprints as Q, channelGateMemberOf as R, authFileName as S, fetchAtRestKeyPayload as St, defaultDesktopAuthPath as T, isEncryptedFieldWrapper as Tt, isConversationIdGateBody as U, forceNeutralHead as V, isCredentialRejectedError as W, parseReasoning as X, parseCreditMultiplier as Y, parseUpstreamModel as Z, ENCRYPTED_CREDENTIAL_CODE as _, nativeModalityOf as _t, readHostHeartbeat as a, lastRefusalFor as at, WorkBuddyCredentialStore as b, deriveAtRestKey as bt, WORKBUDDY_CONNECT_VERSION as c, recordRefusal as ct, FALLBACK_WORKBUDDY_MODELS_GLOBAL as d, WorkBuddyImageError as dt, regionOf as et, WorkBuddyCatalog as f, pickImageModel as ft, withoutRouters as g, imageDefaultFor as gt, fallbackModelsFor as h, NATIVE_MODALITY_BY_MODEL_ID as ht, processStartTimeMs as i, defaultOffModelIds as it, workbuddyAccountId as j, workbuddyAppExecutableCandidates as jt, legacyWorkbuddyOwnAuthPath as k, openEncryptedField as kt, piAiRuntimeInfo as l, withEffectiveOff as lt, deriveCatalog as m, queueNoticeText as mt, clearHostHeartbeat as n, attachBusyLevels as nt, workbuddyHostHeartbeatPath as o, offDefaultFor as ot, applyContextBudgets as p, parseQueueAnswer as pt, modelIdOfBody as q, isHeartbeatProcessAlive as r, REFUSES_OFF_MODEL_IDS as rt, writeHostHeartbeat as s, offRefused as st, WORKBUDDY_HOST_HEARTBEAT_FILENAME as t, requestEvidenceOf as tt, FALLBACK_WORKBUDDY_MODELS as u, DEFAULT_IMAGE_SIZE as ut, WORKBUDDY_AUTH_FILENAME as v, WORKBUDDY_APP_EXECUTABLE_ENV as vt, defaultDesktopAuthDirs as w, findWorkbuddyAppExecutableWithSource as wt, WorkBuddyEncryptedCredentialError as x, deriveAtRestKeyId as xt, WORKBUDDY_AUTH_FILE_ENV as y, clearAtRestKeyCache as yt, classifyUpstreamError as z };

package/lib/index.d.ts

@@ -792,6 +792,22 @@ interface WorkBuddyPromo {
  * `/v3/config`, this endpoint is not channel-sensitive, so the plugin asks it as
  * the CLI agent it already is on the chat path — no product identity needed.
  *
+ * THE GLOBAL GATEWAY DOES NOT HAVE IT (measured 2026-10-22, and the reason the
+ * README says "CN only"). `www.workbuddy.ai` answers that same POST with
+ * `404 {"error_msg":"404 Route Not Found"}`, and so do `/v3/chat/busy`,
+ * `/v2/models/busy`, `/v2/chat/model/busy` and `/v1/chat/busy` under both POST
+ * and GET — twelve path/method pairs, twelve 404s. The credential is fine: the
+ * SAME token reads that gateway's `/v3/config` (200, 28 models), and none of
+ * those models carries a field whose name mentions busy / load / queue / wait /
+ * level / pressure. So this is not a wrong path, a wrong identity or a
+ * permission problem — upstream never published the fact for that region. The
+ * probe therefore fails there on every refresh; it is caught (see
+ * `withBusyLevels` in `src/index.ts`), logged once, and the roster ships with
+ * no levels, which the card renders as no badge. Deliberately NOT "fixed" by
+ * inferring a level from latency or credits: a made-up load badge is worse than
+ * no badge, and the plugin's whole rule here is to never state a fact the
+ * upstream did not state.
+ *
  * THE LEVELS ARE THE APP'S OWN ENUM, and anything outside it is `unknown`:
  * `idle` / `normal` / `busy` / `congested` / `unavailable`. The app's own words
  * (from its `im-channels` bundle, `chatInput.modelSelector.busy.*`) are
@@ -1118,7 +1134,15 @@ interface WorkBuddyProbeAnswer {
   /** The live stream, only when `ok` is true. The caller drains and discards it. */
   response?: Response;
 }
-/** Classify an upstream failure from its HTTP status and body excerpt. */
+/**
+ * Classify an upstream failure from its HTTP status and body excerpt.
+ *
+ * The `11128` family is classified BY ITS CODE, not by the `msg` wording —
+ * see {@link isChannelRejectBody} and {@link channelGateMemberOf}. Which
+ * member of the family it is decides the ADVICE in the reply, never the
+ * classification: every member is a channel-verification refusal that no
+ * account, region or top-up can change.
+ */
 declare function classifyUpstreamError(status: number, body: string): UpstreamErrorKind;
 /** Structured fields lifted out of a JSON upstream failure body. */
 interface UpstreamErrorDetail {
@@ -1126,6 +1150,17 @@ interface UpstreamErrorDetail {
   upstreamCode?: number;
   /** Upstream request id — the handle support asks for. */
   requestId?: string;
+  /**
+   * The upstream's RAW `msg`, kept beside {@link displayMsg}.
+   *
+   * On the `11128` family this is the DIAGNOSTIC half — it is what names which
+   * gate fired ("conversation id missing", "first message is not system
+   * prompt"), while `displayMsg` is the user-facing sentence the plugin must
+   * NOT use as a diagnosis (issue #113 measured it to mislabel a content
+   * refusal). Keeping both means a reply can echo what arrived AND say why it
+   * is or is not believable, without one overwriting the other.
+   */
+  rawMsg?: string;
   /** Best human-facing message: `displayMsg.zh`, falling back to `.en`, then `msg`. */
   displayMsg?: string;
   /**
@@ -1578,6 +1613,7 @@ interface CliBridgeSettings {
   allowUnattended?: boolean;
   maxReplyChars?: number;
   injectResult?: boolean;
+  sessionContinuity?: string;
   maxTurnsPerSessionHour?: number;
   maxTurnsPerHour?: number;
 }
@@ -3783,6 +3819,16 @@ interface WorkBuddyStatusRouteOptions {
    * probe.
    */
   accountUsable?(region: WorkBuddyRegion, account: WorkBuddyRecoveryCandidate): Promise<boolean>;
+  /**
+   * The CLI route's live turns, for the composer readout.
+   *
+   * A READ of the bridge's in-memory board, not a computation: the route exists
+   * so a turn that is still running has somewhere to be observed from, and the
+   * board is the only thing that knows. Absent (the bridge is switched off, or
+   * this Host mounted the status routes without it) means "no live turns", which
+   * the chip renders as nothing at all.
+   */
+  cliLive?(): unknown;
   /**
    * Why each of the region's accounts cannot serve right now, keyed by account
    * id. Absent key (or an absent dep) means "no reason known" — the composer