dsh-zen-remote 1.1.16 → 2.0.0

package/lib/types/client/locales.d.ts

@@ -12,7 +12,7 @@ export declare const zh: {
     readonly allWorkspaces: "全部";
     readonly switchWorkspace: "切换工作区";
     readonly newSession: "新建会话";
-    readonly noSessions: "还没有会话，点右下角加号开始";
+    readonly noSessions: "暂无会话，点击右下角加号新建";
     readonly homeStatusOngoing: "运行中";
     readonly homeStatusWarning: "待处理";
     readonly homeStatusDone: "已完成";
@@ -67,7 +67,7 @@ export declare const zh: {
     readonly shareErrProbe: "当前浏览器无法生成分享图";
     readonly shareErrRender: "生成分享图失败，请重试";
     readonly shareErrSliceBudget: "分享图单段内容超出画布上限，请缩小分享范围后重试";
-    readonly shareErrEmpty: "会话还没有可分享的内容";
+    readonly shareErrEmpty: "会话暂无可分享的内容";
     readonly shareStitchUnsupported: "当前浏览器暂不支持合成单张长图，已导出为多张图片";
     readonly shareStitchFailed: "合成单张长图失败，已改为多张图片导出";
     readonly settings: "设置";
@@ -75,6 +75,191 @@ export declare const zh: {
     readonly chipSsh: "SSH";
     readonly chipUsage: "用量";
     readonly chipCustomize: "自定义入口";
+    readonly 'settings.summary': "远程访问的配对、设备、网关与推送设置";
+    readonly 'settings.unavailable': "当前部署未开放这项配置。";
+    readonly 'settings.readOnly': "当前部署的设置为只读。";
+    readonly 'settings.saveFailed': "保存未被接受；草稿已保留，可修改后重试。";
+    readonly 'settings.save': "保存";
+    readonly 'settings.saving': "保存中…";
+    readonly 'settings.overridden': "已覆盖";
+    readonly 'settings.reset': "重置";
+    readonly 'settings.roleTitle': "角色";
+    readonly 'settings.role': "运行角色";
+    readonly 'settings.roleHint': "本 DSH 进程在远程访问体系中的角色。";
+    readonly 'settings.roleHost': "主服务端（host）";
+    readonly 'settings.roleClient': "子客户端（client）";
+    readonly 'settings.reloadNote': "保存后插件会自动重载，网关短暂中断";
+    readonly 'settings.gatewayTitle': "网关与反代";
+    readonly 'settings.gatewayRunning': "运行中 · 端口 {port} · 转发到 {target}";
+    readonly 'settings.gatewayDown': "网关未运行";
+    readonly 'settings.gatewayAbnormal': "网关回应异常（HTTP {code}）";
+    readonly 'settings.fieldHost': "监听地址";
+    readonly 'settings.fieldHostHint': "网关子进程绑定的地址，默认 127.0.0.1；反代部署保持本机回环。留空清除。";
+    readonly 'settings.fieldHostNote': "必须包含本机回环地址（填 127.0.0.1 或 0.0.0.0）。设置页通过回环地址管理网关，只填局域网 IP 会导致配对与设备管理不可用。";
+    readonly 'settings.fieldPort': "网关端口";
+    readonly 'settings.fieldPortHint': "网关子进程监听的端口，1–65535 的整数，默认 3088。";
+    readonly 'settings.fieldTrustedProxies': "可信代理";
+    readonly 'settings.fieldTrustedProxiesHint': "逗号分隔的反代 IP 列表，网关据此信任 X-Forwarded-* 头。留空清除。";
+    readonly 'settings.fieldRateLimit': "限流（次/分钟）";
+    readonly 'settings.fieldRateLimitHint': "尚未配对的请求每分钟允许的次数（按客户端 IP 计，已配对设备不受限），正整数。";
+    readonly 'settings.fieldVapidSubject': "推送联系人";
+    readonly 'settings.fieldVapidSubjectHint': "VAPID subject，mailto: 或 https: 地址。留空清除。";
+    readonly 'settings.invalidPort': "需要 1–65535 的整数";
+    readonly 'settings.invalidPositiveInt': "需要正整数";
+    readonly 'settings.pushTitle': "推送";
+    readonly 'settings.fieldPushSummary': "推送内容摘要";
+    readonly 'settings.fieldPushSummaryHint': "在推送正文中包含回合的最终文本或待回答的问题。";
+    readonly 'settings.fieldPushTurnEnd': "回合结束推送";
+    readonly 'settings.fieldPushTurnEndHint': "每个顶层回合结束时都推送；默认仅在需要处理时推送。";
+    readonly 'settings.fieldPushTool': "注册 push_notify 工具";
+    readonly 'settings.fieldPushToolHint': "允许模型主动发送通知。";
+    readonly 'settings.fieldPushDebounceMs': "防抖间隔（毫秒）";
+    readonly 'settings.fieldPushDebounceMsHint': "两次推送之间的最小间隔，不小于 0 的整数。";
+    readonly 'settings.fieldLang': "通知语言";
+    readonly 'settings.fieldLangHint': "推送与配对页文案的语言；auto 跟随请求方。";
+    readonly 'settings.langAuto': "自动（auto）";
+    readonly 'settings.langZh': "中文（zh）";
+    readonly 'settings.langEn': "English（en）";
+    readonly 'settings.invalidNonNegativeInt': "需要不小于 0 的整数";
+    readonly 'settings.pushTestLabel': "测试推送";
+    readonly 'settings.pushTestRun': "发送测试推送";
+    readonly 'settings.pushTestRunning': "发送中…";
+    readonly 'settings.pushTestOk': "已发送：成功 {sent} 条，失败 {failed} 条";
+    readonly 'settings.pushTestFail': "测试推送发送失败";
+    readonly 'settings.pairingTitle': "配对";
+    readonly 'settings.pairingWebGuide': "适用于手机、平板及各类浏览器。通过网关地址访问，可查看并操作服务端的全部会话。";
+    readonly 'settings.pairingDesktopGuide': "适用于已安装 DSH 桌面端、并启用 zen-remote 子客户端角色的计算机。配对后，服务端已开启远程连接的会话将显示在该计算机的侧边栏中，其余会话不可见。";
+    readonly 'settings.pairingGenerate': "生成配对码";
+    readonly 'settings.pairingGenerating': "生成中…";
+    readonly 'settings.pairingCodeLabel': "配对码";
+    readonly 'settings.pairingRemaining': "剩余 {count} 秒";
+    readonly 'settings.pairingFail': "配对码生成失败";
+    readonly 'settings.devicesTitle': "设备";
+    readonly 'settings.devicesEmpty': "暂无已配对的设备";
+    readonly 'settings.deviceRoleWeb': "Web 应用端";
+    readonly 'settings.deviceRoleDesktop': "桌面应用端";
+    readonly 'settings.kindAuto': "自动";
+    readonly 'settings.kindPhone': "手机";
+    readonly 'settings.kindDesktop': "电脑";
+    readonly 'settings.deviceLastSeen': "最近在线 {time}";
+    readonly 'settings.devicePushOn': "已订阅推送";
+    readonly 'settings.devicePushOff': "未订阅推送";
+    readonly 'settings.deviceRename': "重命名";
+    readonly 'settings.renamePrompt': "设备新名称";
+    readonly 'settings.renameSave': "确定";
+    readonly 'settings.renameCancel': "取消";
+    readonly 'settings.deviceRevoke': "吊销";
+    readonly 'settings.deviceRoleSelect': "{name} 的角色";
+    readonly 'settings.deviceKindSelect': "{name} 的界面布局";
+    readonly 'settings.revokeConfirm': "吊销后该设备需要重新配对，确定继续？";
+    readonly 'settings.revokeAll': "全部吊销";
+    readonly 'settings.revokeAllConfirm': "将吊销全部已配对设备，确定继续？";
+    readonly 'settings.actionFail': "操作失败";
+    readonly 'settings.shareTitle': "远程共享";
+    readonly 'settings.shareListTitle': "已开启远程的会话";
+    readonly 'settings.shareListEmpty': "当前没有已开启远程的会话";
+    readonly 'settings.shareViewers': "{count} 台设备正在查看";
+    readonly 'settings.shareClose': "关闭远程";
+    readonly 'settings.shareCloseAll': "全部关闭";
+    readonly 'settings.shareCloseAllConfirm': "将关闭全部已开启远程的会话，确定继续？";
+    readonly 'settings.shareActionFail': "操作失败";
+    readonly 'settings.fieldServerName': "设备名称";
+    readonly 'settings.fieldServerNameHint': "其他设备远程访问时显示的名称，1–40 个字符，留空恢复默认。";
+    readonly 'settings.fieldServerNameHintClient': "配对时注册到服务端的名称，1–40 个字符。";
+    readonly 'settings.fieldIdleHours': "闲置休眠（小时）";
+    readonly 'settings.fieldIdleHoursHint': "超过该时长无新活动时，自动关闭远程连接。运行中或等待中的会话不计时。默认 48，取值大于 0 且不超过 8760。";
+    readonly 'settings.fieldAutoShare': "自动共享新会话";
+    readonly 'settings.fieldAutoShareHint': "新建的会话自动共享给已配对的设备。";
+    readonly 'settings.invalidName': "名称需要 1–40 个字符";
+    readonly 'settings.invalidHours': "需要大于 0 且不超过 8760 的数字";
+    readonly 'settings.remoteNotice': "配对与设备管理只能在服务端本机操作";
+    readonly 'settings.savedInvalid': "已保存的值无效，当前生效的是 {source} 的值";
+    readonly 'settings.sourceEnvBadge': "由环境变量锁定";
+    readonly 'settings.sourceFileBadge': "来自旧配置文件 lan-gate.config.json";
+    readonly 'settings.sourceEnv': "环境变量";
+    readonly 'settings.sourceFile': "旧配置文件 lan-gate.config.json";
+    readonly 'settings.sourceDefault': "默认值";
+    readonly 'settings.statusUnavailable': "无法读取插件状态（HTTP {code}）";
+    readonly 'settings.statusUnknown': "无法读取插件状态";
+    readonly 'settings.refreshFailed': "状态刷新失败，当前显示的是上一次成功的数据";
+    readonly 'settings.resetPreview': "保存后恢复为下一层的值";
+    readonly 'settings.client.connectTitle': "连接服务端";
+    readonly 'settings.client.serverUrl': "服务端地址";
+    readonly 'settings.client.serverUrlHint': "服务端网关地址，例如 http://192.168.1.10:3088 或 https://dsh.example.com。";
+    readonly 'settings.client.deviceNameDefault': "桌面应用端";
+    readonly 'settings.client.fixDeviceName': "请先修正设备名称";
+    readonly 'settings.client.pairingCode': "配对码";
+    readonly 'settings.client.pairingCodeHint': "在服务端设置页生成「桌面应用端」配对码后填入（8 位，自动转大写）。";
+    readonly 'settings.client.pair': "配对";
+    readonly 'settings.client.pairing': "配对中…";
+    readonly 'settings.client.failInvalid': "服务端地址不合法";
+    readonly 'settings.client.failInsecureHttp': "公网地址必须使用 https；http 只允许局域网或 Tailscale 地址";
+    readonly 'settings.client.failBadCode': "配对码错误或已过期";
+    readonly 'settings.client.failLocked': "尝试次数过多，请 {minutes} 分钟后再试";
+    readonly 'settings.client.failUnreachable': "无法连接服务端";
+    readonly 'settings.client.failRoleMismatch': "该配对码不适用于桌面应用端";
+    readonly 'settings.client.failUnexpected': "服务端回应无法识别，请确认服务端已安装 dsh-zen-remote 2.0.0";
+    readonly 'settings.client.failWrite': "配对成功，但本机保存令牌失败：设置存储不可用或只读";
+    readonly 'settings.client.statusTitle': "连接状态";
+    readonly 'settings.client.statusUnpaired': "未配对";
+    readonly 'settings.client.statusConnected': "已连接到 {serverUrl}";
+    readonly 'settings.client.statusRevoked': "令牌已被吊销，请重新配对";
+    readonly 'settings.client.statusUnreachable': "服务端当前不可达";
+    readonly 'settings.client.statusUnexpected': "服务端版本不支持远程会话（需要 dsh-zen-remote 2.0.0）";
+    readonly 'settings.client.statusInvalidUrl': "服务端地址无效或不安全，请重新配对";
+    readonly 'settings.client.statusRefresh': "刷新";
+    readonly 'settings.client.statusRefreshing': "刷新中…";
+    readonly 'settings.client.tokenSet': "设备令牌已保存";
+    readonly 'settings.client.unpair': "解除配对";
+    readonly 'settings.client.unpairBusy': "解除中…";
+    readonly 'settings.client.unpairConfirm': "本机将忘记已保存的服务端令牌（服务端的设备记录不受影响）。确定继续？";
+    readonly 'settings.client.unpairDone': "本机已忘记令牌；如需彻底失效，请在服务端设备列表中吊销该设备";
+    readonly shareRemoteOn: "开启远程";
+    readonly shareRemoteOff: "关闭远程";
+    readonly shareRemoteStateOff: "未开启远程";
+    readonly shareRemoteStateOn: "已开启远程";
+    readonly infoRemoteAccess: "远程访问";
+    readonly shareRemoteBusy: "运行中，不计时";
+    readonly shareRemoteRemainingHours: "剩余闲置时间 {count} 小时";
+    readonly shareRemoteRemainingMinutes: "剩余闲置时间 {count} 分钟";
+    readonly shareRemoteConfirmOn: "开启远程后，已配对的桌面应用端将可以查看并操作此会话。确定开启？";
+    readonly shareRemoteConfirmOff: "关闭后，桌面应用端将无法再访问此会话。确定关闭？";
+    readonly shareRemoteFailSubagent: "开启远程失败：子智能体会话不能单独开启";
+    readonly shareRemoteFailEmpty: "开启远程失败：会话暂无内容";
+    readonly shareRemoteFailGeneric: "操作失败，请稍后再试";
+    readonly 'settings.client.reconnect': "立即重连";
+    readonly 'settings.client.reconnectBusy': "重连中…";
+    readonly 'settings.client.statusConnectedName': "已连接到「{serverName}」";
+    readonly 'settings.client.statusOfflineRetry': "离线，将于 {seconds} 秒后重试";
+    readonly 'settings.client.statusOfflineRetrySoon': "离线，即将重试…";
+    readonly 'settings.client.statusIncompatible': "与服务端中继协议不兼容，请升级两端的 dsh-zen-remote";
+    readonly 'settings.client.diagTitle': "诊断";
+    readonly 'settings.client.diagLastError': "最近错误码：{code}";
+    readonly 'settings.client.diagInterceptInstalled': "请求拦截器已安装";
+    readonly 'settings.client.diagInterceptMissing': "请求拦截器未安装";
+    readonly 'settings.client.diagInterceptDisabled': "远程功能已停用：DSH 内部结构与预期不符";
+    readonly 'settings.client.diagRecentFailures': "最近的远程调用失败";
+    readonly 'settings.client.diagCompatGroups': "指纹有差异的组：{groups}";
+    readonly 'settings.client.diagCompatCalls': "最近的不兼容调用";
+    readonly remoteStatusOnline: "远程会话 · 已连接";
+    readonly remoteStatusOffline: "服务端离线，正在重连";
+    readonly remoteStatusMismatch: "与服务端版本不一致，部分功能可能不可用";
+    readonly remoteStatusRevoked: "令牌已吊销，请在设置页重新配对";
+    readonly remoteStatusUnpaired: "已解除配对";
+    readonly remoteBannerOffline: "服务端离线，远程会话暂时只读，恢复连接后自动可用";
+    readonly remoteBannerRevoked: "令牌已吊销，请在设置页重新配对";
+    readonly remoteBannerUnpaired: "已解除配对";
+    readonly remoteBannerClosedIdle: "远程已关闭：闲置超过设定时间，已自动休眠";
+    readonly remoteBannerClosedManual: "远程已关闭：服务端已关闭此会话的远程";
+    readonly remoteBannerClosedClient: "远程已关闭：已在本机关闭远程";
+    readonly remoteStatusUnshareConfirm: "关闭远程后，此会话将从本机的远程分组中移除，服务端上的会话不受影响。确定关闭？";
+    readonly remoteStatusOfflineClick: "服务端离线，无法操作";
+    readonly remoteStatusUnshareFail: "关闭远程失败，请稍后再试";
+    readonly remoteStatusUnshareFailCode: "关闭远程失败（{code}），请稍后再试";
+    readonly remoteGroupOffline: "（离线）";
+    readonly remoteGroupRevoked: "（令牌已吊销）";
+    readonly remoteGroupUnpaired: "（已解除配对）";
+    readonly remoteGroupMismatch: "（版本有差异）";
 };
 /** English dictionary, key-identical to the Chinese source of truth. */
 export declare const en: Record<MobileNavKey, string>;

package/lib/types/client/locales.d.ts.map

@@ -1 +1 @@
-{"version":3,"file":"locales.d.ts","sourceRoot":"","sources":["../../../src/client/locales.ts"],"names":[],"mappings":"AAAA,2DAA2D;AAC3D,eAAO,MAAM,EAAE,cAAc,CAAA;AAE7B,mEAAmE;AACnE,eAAO,MAAM,EAAE;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;CA0EL,CAAA;AAEV,wEAAwE;AACxE,eAAO,MAAM,EAAE,EAAE,MAAM,CAAC,YAAY,EAAE,MAAM,CA0E3C,CAAA;AAED,2EAA2E;AAC3E,MAAM,MAAM,YAAY,GAAG,MAAM,OAAO,EAAE,CAAA"}
+{"version":3,"file":"locales.d.ts","sourceRoot":"","sources":["../../../src/client/locales.ts"],"names":[],"mappings":"AAAA,2DAA2D;AAC3D,eAAO,MAAM,EAAE,cAAc,CAAA;AAE7B,mEAAmE;AACnE,eAAO,MAAM,EAAE;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;CAiRL,CAAA;AAEV,wEAAwE;AACxE,eAAO,MAAM,EAAE,EAAE,MAAM,CAAC,YAAY,EAAE,MAAM,CA6Q3C,CAAA;AAED,2EAA2E;AAC3E,MAAM,MAAM,YAAY,GAAG,MAAM,OAAO,EAAE,CAAA"}

package/lib/types/client/remote-fetch.d.ts

@@ -0,0 +1,51 @@
+/**
+ * The sub-client's plain-HTTP relay, browser half (T41b). The session page's
+ * changes / diff panel does not ride the typert gateway — it GETs
+ * `/api/changes.summary` and `/api/changes.diff` with the session id in the
+ * query (RT dsh-client-ui-deliverables/lib/client.js ~13-17, 90-109, 208:
+ * plain call-time `fetch(url, { signal })`, document-relative string URLs),
+ * so a remote session's virtual id would hit the LOCAL DSH and 404. This
+ * module wraps `window.fetch` ONCE: a same-origin GET whose path is exactly
+ * one of those two routes and whose `sessionId` parameter carries a virtual
+ * id (`zr~` prefix, virtual-id.ts's skeleton — the strict parse happens in
+ * the backend route) is rewritten to the sub-client relay route
+ * `/_dsh/zen-remote/client/http/<route>?<original query>`, `init` (the
+ * abort signal) passing through untouched. Every other request — local
+ * sessions, any other path, cross-origin, non-GET — reaches the original
+ * fetch unchanged, so a host-role deployment (whose session ids are never
+ * virtual) is bit-for-bit unintercepted.
+ *
+ * Not covered by THIS wrapper (each surface has its own channel since T51):
+ * the attachment upload's HTTP branch runs inside a Web Worker over XHR /
+ * Worker-scoped fetch — unreachable from `window.fetch`, so it is intercepted
+ * one layer down, at the host's exact-fetch-route table, by
+ * `src/fetch-route-intercept.ts` (which relays the bytes and likewise blocks
+ * the session export); `present.host` / `changes.open` / `present.open`
+ * belong to entries hidden on remote sessions rather than relayed. The
+ * complete not-relayed registry still lives beside the server's in
+ * src/relay-access.ts.
+ */
+/** Prefix of the sub-client backend route the rewritten calls land on. */
+export declare const CLIENT_HTTP_ROUTE_PREFIX = "/_dsh/zen-remote/client/http/";
+/** The fetch face this module wraps; injectable so tests drive a fake. */
+export interface FetchHost {
+    fetch(input: RequestInfo | URL, init?: RequestInit): Promise<Response>;
+    location: {
+        href: string;
+    };
+}
+/**
+ * The rewrite decision, pure: the relay URL for one fetch call, or
+ * `undefined` to pass through untouched. Only a GET, same-origin against
+ * `baseHref`, on one of the two exact paths, with a `zr~`-prefixed
+ * `sessionId` rewrites — every other shape of the world returns undefined.
+ */
+export declare function rewriteRemoteApiUrl(input: unknown, method: string, baseHref: string): string | undefined;
+/**
+ * Wrap the host's `fetch` exactly once and return the uninstaller. A call
+ * while a wrap is already live adopts it (no second layer, exactly one hop)
+ * and takes over its ownership. The wrapper reads `location.href` per call,
+ * not at install time.
+ */
+export declare function installRemoteApiFetch(host: FetchHost): () => void;
+//# sourceMappingURL=remote-fetch.d.ts.map

package/lib/types/client/remote-fetch.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"remote-fetch.d.ts","sourceRoot":"","sources":["../../../src/client/remote-fetch.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;;;;;;;;;;;;;;;;GA0BG;AAOH,0EAA0E;AAC1E,eAAO,MAAM,wBAAwB,kCAAkC,CAAA;AAEvE,0EAA0E;AAC1E,MAAM,WAAW,SAAS;IACxB,KAAK,CAAC,KAAK,EAAE,WAAW,GAAG,GAAG,EAAE,IAAI,CAAC,EAAE,WAAW,GAAG,OAAO,CAAC,QAAQ,CAAC,CAAA;IACtE,QAAQ,EAAE;QAAE,IAAI,EAAE,MAAM,CAAA;KAAE,CAAA;CAC3B;AAED;;;;;GAKG;AACH,wBAAgB,mBAAmB,CAAC,KAAK,EAAE,OAAO,EAAE,MAAM,EAAE,MAAM,EAAE,QAAQ,EAAE,MAAM,GAAG,MAAM,GAAG,SAAS,CAgBxG;AAqBD;;;;;GAKG;AACH,wBAAgB,qBAAqB,CAAC,IAAI,EAAE,SAAS,GAAG,MAAM,IAAI,CAiCjE"}

package/lib/types/client/remote-group-expansion.d.ts

@@ -0,0 +1,41 @@
+/** The storage face used, narrowed to the two methods (structurally typed:
+ * this module compiles under the client tsconfig with DOM lib, but tests
+ * inject stubs). */
+interface StorageLike {
+    getItem(key: string): string | null;
+    setItem(key: string, value: string): void;
+}
+/** One matched row: the group id, its current expansion, and the click. */
+interface RowHandle {
+    key: string;
+    expanded: boolean;
+    click(): void;
+}
+export interface RemoteGroupExpansionKeeperOptions {
+    /** Both storage reads and writes. Default: the page's localStorage; a
+     * broken or absent one makes every tick a no-op. */
+    storage?: StorageLike;
+    /** The role probe. Default: the shared cached client-config probe. */
+    probeRole?: () => Promise<'host' | 'client' | undefined>;
+    /** The sidebar's server group rows. Default: the real DOM query — rows
+     * without a readable `aria-expanded` are skipped. Tests inject fake rows
+     * with click recorders. */
+    queryRows?: () => RowHandle[];
+    /** The re-check interval; default 1000ms. */
+    intervalMs?: number;
+}
+/**
+ * Start the keeper loop. Returns the disposer (interval) the mounting
+ * effect calls on teardown.
+ */
+export declare function startRemoteGroupExpansionKeeper(options?: RemoteGroupExpansionKeeperOptions): () => void;
+/**
+ * Mount the keeper as one page-lifetime effect, beside the current-session
+ * reporter (T62): before the desktop-shell gate in apply(), same client-role
+ * probe, same 1s cadence — its own timer, its own file.
+ */
+export declare function mountRemoteGroupExpansionKeeper(ctx: {
+    effect(fn: () => () => void, name: string): void;
+}, options?: RemoteGroupExpansionKeeperOptions): void;
+export {};
+//# sourceMappingURL=remote-group-expansion.d.ts.map

package/lib/types/client/remote-group-expansion.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"remote-group-expansion.d.ts","sourceRoot":"","sources":["../../../src/client/remote-group-expansion.ts"],"names":[],"mappings":"AAgDA;;oBAEoB;AACpB,UAAU,WAAW;IACnB,OAAO,CAAC,GAAG,EAAE,MAAM,GAAG,MAAM,GAAG,IAAI,CAAA;IACnC,OAAO,CAAC,GAAG,EAAE,MAAM,EAAE,KAAK,EAAE,MAAM,GAAG,IAAI,CAAA;CAC1C;AAMD,2EAA2E;AAC3E,UAAU,SAAS;IACjB,GAAG,EAAE,MAAM,CAAA;IACX,QAAQ,EAAE,OAAO,CAAA;IACjB,KAAK,IAAI,IAAI,CAAA;CACd;AAED,MAAM,WAAW,iCAAiC;IAChD;wDACoD;IACpD,OAAO,CAAC,EAAE,WAAW,CAAA;IACrB,sEAAsE;IACtE,SAAS,CAAC,EAAE,MAAM,OAAO,CAAC,MAAM,GAAG,QAAQ,GAAG,SAAS,CAAC,CAAA;IACxD;;+BAE2B;IAC3B,SAAS,CAAC,EAAE,MAAM,SAAS,EAAE,CAAA;IAC7B,6CAA6C;IAC7C,UAAU,CAAC,EAAE,MAAM,CAAA;CACpB;AAED;;;GAGG;AACH,wBAAgB,+BAA+B,CAAC,OAAO,GAAE,iCAAsC,GAAG,MAAM,IAAI,CA+F3G;AAED;;;;GAIG;AACH,wBAAgB,+BAA+B,CAAC,GAAG,EAAE;IAAE,MAAM,CAAC,EAAE,EAAE,MAAM,MAAM,IAAI,EAAE,IAAI,EAAE,MAAM,GAAG,IAAI,CAAA;CAAE,EAAE,OAAO,GAAE,iCAAsC,GAAG,IAAI,CAEhK"}

package/lib/types/client/remote-share-css.d.ts

@@ -0,0 +1,19 @@
+/**
+ * Styles for the T33b session-sharing parts — the title-row remote icon's
+ * three states and nothing else (the menu item is an official
+ * MenuItemButton and needs no CSS; the settings list draws on the settings
+ * block's own zr-settings-* sheet). Injected as one
+ * `<style data-plugin="dsh-zen-remote-remote-share">` tag BEFORE apply's
+ * desktop gate: the desktop app IS the main server and its title row is
+ * where the icon lives. Every selector is scoped under the button's own
+ * attribute, so nothing here can reach host elements (the title row's
+ * layout especially — this box is a fixed 28px grid item and shrinks for
+ * nobody).
+ *
+ * On the phone shell the icon needs no rules of its own: the mobile
+ * stylesheet blanket-hides every child of the
+ * `conversation.session.header.actions` slot wrapper (styles/header.css.ts),
+ * which this entry is.
+ */
+export declare const REMOTE_SHARE_CSS = "\nbutton.zr-remote-toggle[data-zen-remote=\"remote-toggle\"] {\n  display: inline-flex;\n  align-items: center;\n  justify-content: center;\n  width: 28px;\n  height: 28px;\n  flex-shrink: 0;\n  padding: 0;\n  border: none;\n  border-radius: 6px;\n  background: transparent;\n  color: var(--dsw-alias-label-tertiary);\n  cursor: pointer;\n  position: relative;\n}\nbutton.zr-remote-toggle[data-zen-remote=\"remote-toggle\"]:hover {\n  background: var(--dsw-alias-interactive-bg-hover);\n}\nbutton.zr-remote-toggle[data-zen-remote=\"remote-toggle\"][data-state=\"on\"],\nbutton.zr-remote-toggle[data-zen-remote=\"remote-toggle\"][data-state=\"watched\"] {\n  color: var(--dsw-alias-state-business-primary, #4f6ef7);\n}\n/* The \"a desktop client is watching\" dot: a live signal outside the glyph's\n   box so it never collides with the 16px artwork. */\nbutton.zr-remote-toggle[data-zen-remote=\"remote-toggle\"][data-state=\"watched\"]::after {\n  content: '';\n  position: absolute;\n  top: 3px;\n  right: 3px;\n  width: 6px;\n  height: 6px;\n  border-radius: 50%;\n  background: var(--dsw-alias-state-success-primary, #16a34a);\n}\n";
+//# sourceMappingURL=remote-share-css.d.ts.map

package/lib/types/client/remote-share-css.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"remote-share-css.d.ts","sourceRoot":"","sources":["../../../src/client/remote-share-css.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;;;;;;GAgBG;AAEH,eAAO,MAAM,gBAAgB,onCAmC5B,CAAA"}

package/lib/types/client/remote-share-register.d.ts

@@ -0,0 +1,113 @@
+/**
+ * Registration for the T33b session-sharing parts — the work that must run
+ * BEFORE apply's desktop-shell gate (the desktop app IS the main server:
+ * its title row and session menus are exactly where these parts live),
+ * extracted so the Node-side desktop-gate test can drive it against a fake
+ * ctx (the components are .tsx; they arrive as parameters, keeping this
+ * module JSX-free and importable under Node's type stripping — the same
+ * trick register-settings.ts uses).
+ *
+ * Registers the title-row remote icon on
+ * `conversation.session.header.actions` (order 25, past the official jobs
+ * entry at 20 so the two never tie) and the remote toggle on
+ * `sidebar.workspaces.session.menu.item` (order 500, under the official
+ * archive row, behind a group hairline), plus the one stylesheet both
+ * surfaces need.
+ *
+ * The parts render and poll only on the HOST role (T33b-fix): this module
+ * wires the shares store's role from the SAME two-level decision the
+ * settings page makes (settings-form.ts's shared `settingsRoleOf`) — the
+ * configForms row document first, and while the row is silent the effective
+ * role probed from `/_dsh/mobile-nav/client-config` (T17: the route carries
+ * the merged role). The decision re-runs on every scope snapshot update, so
+ * a snapshot that resolves late — or a row whose role appears after the
+ * probe already answered — re-decides, and a deployment switched back to
+ * host recovers. The wiring hangs off a lazy `ctx.inject(['configForms'], …)`;
+ * where the settings service never arrives, one fallback probe wires the
+ * role on its own (guarded: a snapshot answer always wins over it).
+ *
+ * The `sidebar.workspaces.session.menu.item` SlotMap entry is declared here
+ * as a structural mirror: this package does not depend on
+ * dsh-client-ui-workspace (the slot's owner), whose type-only merges would
+ * normally provide it. The mirror records what the workspace browser
+ * actually hands its entries: the row props (`sessionId`, `displayTitle`),
+ * the `[open, setOpen]` pair it passes as the render occurrence's
+ * hookContext, and the list-level inject whose `menuOpenState` hook factory
+ * binds that pair — official rows call it `useMenuOpenState` and close the
+ * menu with it.
+ */
+import type { ReactNode } from 'react';
+import type { SessionId } from './compat/types.ts';
+import type { ClientContext } from './compat/types.ts';
+import type { SharesStore } from '../client-data/shares.ts';
+import type { RemoteHeaderIconProps } from './RemoteHeaderIcon.tsx';
+import type { RemoteShareMenuProps } from './RemoteShareMenu.tsx';
+/** The `[open, setOpen]` pair the workspace Menu hands every row entry. */
+export type SessionMenuOpenState = readonly [boolean, (open: boolean) => void];
+declare module '@deepseek-ai/dsh-client-ui-slots' {
+    interface SlotMap {
+        'sidebar.workspaces.session.menu.item': {
+            kind: 'list';
+            scope: 'root';
+            owner: {
+                sessionId: SessionId;
+                displayTitle: string;
+            };
+            hookContext: SessionMenuOpenState;
+            inject: {
+                hooks: {
+                    menuOpenState: (context: unknown) => () => SessionMenuOpenState;
+                };
+            };
+        };
+    }
+}
+/** The header icon component (a .tsx factory result; parameter for Node). */
+export type RemoteHeaderIconComponent = (props: RemoteHeaderIconProps) => ReactNode;
+/** The menu-item component (a .tsx factory result; parameter for Node). */
+export type RemoteShareMenuComponent = (props: RemoteShareMenuProps) => ReactNode;
+export declare function probeClientConfigRole(refetch?: boolean): Promise<'host' | 'client' | undefined>;
+/** How one probe is issued — the real route reader, or the check/test
+ * double. `refetch` mirrors {@link probeClientConfigRole}: true drops any
+ * cached answer and asks again. */
+export type ClientConfigProbe = (refetch?: boolean) => Promise<'host' | 'client' | undefined>;
+export interface WireSharesRoleOptions {
+    /** Called once a definite verdict was applied (the no-configForms
+     * fallback checks this before trusting its own probe). */
+    onVerdict?: () => void;
+    /** The probe to consult while the row document is silent. Defaults to
+     * the real client-config reader; tests inject a controllable double so
+     * they never depend on module-level probe state. */
+    probe?: ClientConfigProbe;
+}
+/**
+ * Wire a shares store's role off one configForms scope: the saved row role
+ * wins (settingsRoleOf), while the row is silent the client-config probe
+ * fills the gap, and every scope update re-decides. Verdicts of
+ * `'unknown'` — snapshot still loading, probe pending or FAILED — leave
+ * the store untouched: nothing polls and nothing renders (never a guessed
+ * host). A scope STATUS change (loading→ready, a mirror resync) drops the
+ * probe answer and probes again, the same two signals the settings page's
+ * probe effect re-runs on.
+ * @param scope - the plugin row's shared configuration form scope.
+ * @param store - the shares store whose role this wiring drives.
+ * @param options - verdict callback and probe injection.
+ * @returns disposer releasing the scope subscription.
+ */
+export declare function wireSharesRole(scope: {
+    getSnapshot(): {
+        status: 'loading' | 'ready' | 'unavailable';
+        value?: unknown;
+        user?: unknown;
+    };
+    subscribe(listener: () => void): () => void;
+}, store: Pick<SharesStore, 'setRole'>, options?: WireSharesRoleOptions): () => void;
+/**
+ * Register the stylesheet and the two sharing parts. Gate-independent by
+ * design — the caller (apply) places this before its desktop gate.
+ * @param ctx - client root context.
+ * @param headerIcon - the title-row icon component.
+ * @param menuItem - the session-menu toggle component.
+ */
+export declare function registerRemoteShareUi(ctx: ClientContext, headerIcon: RemoteHeaderIconComponent, menuItem: RemoteShareMenuComponent): void;
+//# sourceMappingURL=remote-share-register.d.ts.map

package/lib/types/client/remote-share-register.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"remote-share-register.d.ts","sourceRoot":"","sources":["../../../src/client/remote-share-register.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;GAqCG;AACH,OAAO,KAAK,EAAE,SAAS,EAAE,MAAM,OAAO,CAAA;AACtC,OAAO,KAAK,EAAE,SAAS,EAAE,MAAM,mBAAmB,CAAA;AAClD,OAAO,KAAK,EAAE,aAAa,EAAE,MAAM,mBAAmB,CAAA;AAEtD,OAAO,KAAK,EAAE,WAAW,EAAE,MAAM,0BAA0B,CAAA;AAM3D,OAAO,KAAK,EAAE,qBAAqB,EAAE,MAAM,wBAAwB,CAAA;AACnE,OAAO,KAAK,EAAE,oBAAoB,EAAE,MAAM,uBAAuB,CAAA;AAEjE,2EAA2E;AAC3E,MAAM,MAAM,oBAAoB,GAAG,SAAS,CAAC,OAAO,EAAE,CAAC,IAAI,EAAE,OAAO,KAAK,IAAI,CAAC,CAAA;AAE9E,OAAO,QAAQ,kCAAkC,CAAC;IAChD,UAAU,OAAO;QACf,sCAAsC,EAAE;YACtC,IAAI,EAAE,MAAM,CAAA;YACZ,KAAK,EAAE,MAAM,CAAA;YACb,KAAK,EAAE;gBAAE,SAAS,EAAE,SAAS,CAAC;gBAAC,YAAY,EAAE,MAAM,CAAA;aAAE,CAAA;YACrD,WAAW,EAAE,oBAAoB,CAAA;YACjC,MAAM,EAAE;gBAAE,KAAK,EAAE;oBAAE,aAAa,EAAE,CAAC,OAAO,EAAE,OAAO,KAAK,MAAM,oBAAoB,CAAA;iBAAE,CAAA;aAAE,CAAA;SACvF,CAAA;KACF;CACF;AAED,6EAA6E;AAC7E,MAAM,MAAM,yBAAyB,GAAG,CAAC,KAAK,EAAE,qBAAqB,KAAK,SAAS,CAAA;AACnF,2EAA2E;AAC3E,MAAM,MAAM,wBAAwB,GAAG,CAAC,KAAK,EAAE,oBAAoB,KAAK,SAAS,CAAA;AAiBjF,wBAAgB,qBAAqB,CAAC,OAAO,UAAQ,GAAG,OAAO,CAAC,MAAM,GAAG,QAAQ,GAAG,SAAS,CAAC,CAqB7F;AAED;;mCAEmC;AACnC,MAAM,MAAM,iBAAiB,GAAG,CAAC,OAAO,CAAC,EAAE,OAAO,KAAK,OAAO,CAAC,MAAM,GAAG,QAAQ,GAAG,SAAS,CAAC,CAAA;AAE7F,MAAM,WAAW,qBAAqB;IACpC;8DAC0D;IAC1D,SAAS,CAAC,EAAE,MAAM,IAAI,CAAA;IACtB;;wDAEoD;IACpD,KAAK,CAAC,EAAE,iBAAiB,CAAA;CAC1B;AAED;;;;;;;;;;;;;GAaG;AACH,wBAAgB,cAAc,CAC5B,KAAK,EAAE;IACL,WAAW,IAAI;QAAE,MAAM,EAAE,SAAS,GAAG,OAAO,GAAG,aAAa,CAAC;QAAC,KAAK,CAAC,EAAE,OAAO,CAAC;QAAC,IAAI,CAAC,EAAE,OAAO,CAAA;KAAE,CAAA;IAC/F,SAAS,CAAC,QAAQ,EAAE,MAAM,IAAI,GAAG,MAAM,IAAI,CAAA;CAC5C,EACD,KAAK,EAAE,IAAI,CAAC,WAAW,EAAE,SAAS,CAAC,EACnC,OAAO,GAAE,qBAA0B,GAClC,MAAM,IAAI,CA0CZ;AAED;;;;;;GAMG;AACH,wBAAgB,qBAAqB,CACnC,GAAG,EAAE,aAAa,EAClB,UAAU,EAAE,yBAAyB,EACrC,QAAQ,EAAE,wBAAwB,GACjC,IAAI,CA2CN"}

package/lib/types/client/remote-status-css.d.ts

@@ -0,0 +1,15 @@
+/**
+ * Styles for the T34 sub-client status parts — the title-row connection
+ * icon's states and the composer's readonly banner. Injected as one
+ * `<style data-plugin="dsh-zen-remote-remote-status">` tag BEFORE apply's
+ * desktop gate (a desktop app in the client role has remote sessions too; on
+ * a host the parts render nothing for local sessions, so the desktop stays
+ * pixel-identical).
+ *
+ * T34-fix: the input itself is disabled through the HOST's component
+ * capability — `ctx.conversation.blocks.set(sessionId, { reason })`, the
+ * composer-block contract — not through any CSS override; what remains here
+ * is scoped under the parts' own attributes and can reach nothing but them.
+ */
+export declare const REMOTE_STATUS_CSS = "\nbutton.zr-remote-status[data-zen-remote=\"remote-status\"] {\n  display: inline-flex;\n  align-items: center;\n  justify-content: center;\n  width: 28px;\n  height: 28px;\n  flex-shrink: 0;\n  padding: 0;\n  border: none;\n  border-radius: 6px;\n  background: transparent;\n  color: var(--dsw-alias-label-tertiary);\n  cursor: pointer;\n}\nbutton.zr-remote-status[data-zen-remote=\"remote-status\"]:hover {\n  background: var(--dsw-alias-interactive-bg-hover);\n}\nbutton.zr-remote-status[data-zen-remote=\"remote-status\"][data-state=\"online\"] {\n  color: var(--dsw-alias-state-business-primary, #4f6ef7);\n}\n/* offline / revoked / unpaired: the default grey is the state, dimmed a\n   little so a dead or unpaired link reads instantly */\nbutton.zr-remote-status[data-zen-remote=\"remote-status\"][data-state=\"offline\"],\nbutton.zr-remote-status[data-zen-remote=\"remote-status\"][data-state=\"revoked\"],\nbutton.zr-remote-status[data-zen-remote=\"remote-status\"][data-state=\"unpaired\"] {\n  color: var(--dsw-alias-label-tertiary);\n  opacity: 0.75;\n}\nbutton.zr-remote-status[data-zen-remote=\"remote-status\"][data-state=\"mismatch\"] {\n  color: var(--dsw-alias-state-warning-primary, #d97706);\n}\n\n/* The composer banner: a dock entry, so on desktop it is one full-width row\n   of the composer column (the slot anchor is display:contents and the\n   composer column is a flex column \u2014 the item stretches to the column\n   width WITHOUT an explicit width, which would stack with the side margins\n   and overflow the input column, T34-fix). Styled after the host's own\n   composer notice, standalone. */\n.zr-remote-banner[data-zen-remote=\"remote-banner\"] {\n  box-sizing: border-box;\n  margin: 0 max(16px, var(--dsh-composer-side-clearance, 16px));\n  border-radius: var(--dsw-radius-md, 8px);\n  background: var(--dsw-alias-interactive-bg-hover, rgba(0, 0, 0, 0.04));\n  color: var(--dsw-alias-label-secondary, inherit);\n  padding: 6px 10px;\n  font-size: 12px;\n  line-height: 18px;\n}\n";
+//# sourceMappingURL=remote-status-css.d.ts.map

package/lib/types/client/remote-status-css.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"remote-status-css.d.ts","sourceRoot":"","sources":["../../../src/client/remote-status-css.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;;GAYG;AAEH,eAAO,MAAM,iBAAiB,y+DAiD7B,CAAA"}

package/lib/types/client/remote-status-register.d.ts

@@ -0,0 +1,46 @@
+/**
+ * Registration for the T34 sub-client status parts — the work that must run
+ * BEFORE apply's desktop gate (a desktop app in the client role has remote
+ * sessions too), extracted so the Node-side desktop-gate test can drive it
+ * against a fake ctx (the components are .tsx; they arrive as parameters,
+ * keeping this module JSX-free and importable under Node's type stripping —
+ * the same trick register-settings.ts / remote-share-register.ts use).
+ *
+ * Registers the title-row connection icon on
+ * `conversation.session.header.actions` (order 26, past the T33b share icon
+ * at 25 so the two never tie) and the composer banner on
+ * `conversation.input.dock` (order 15, between the official todo panel at 0
+ * and the queue dock at 20), plus the one stylesheet both surfaces need.
+ *
+ * The banner's disable rides the HOST's composer-block contract (T34-fix):
+ * the inject face hands the component a per-session `setComposerBlock`
+ * binding over `ctx.conversation.blocks` (dsh-client-ui-conversation's
+ * `ComposerBlocks`, resolved lazily at call time — the row context may still
+ * be assembling when this registration runs, and the composer that consumes
+ * the block is the conversation plugin's own UI, so the service is there by
+ * the time a banner can stand). A composition without the service degrades
+ * to a no-op binding: the banner still renders, the disable is simply absent.
+ *
+ * No role wiring here, unlike the T33b parts: the store only polls while a
+ * part is SUBSCRIBED, and both parts gate the subscription itself on the
+ * virtual id (remote-status.ts's subscribeIfVirtual — a local session never
+ * opens one) — so a host page never polls, without needing the settings
+ * role to tell it apart.
+ */
+import type { ReactNode } from 'react';
+import type { ClientContext } from './compat/types.ts';
+import type { RemoteStatusIconProps } from './RemoteStatusIcon.tsx';
+import type { RemoteComposerBannerProps } from './RemoteComposerBanner.tsx';
+/** The icon component (a .tsx factory result; parameter for Node). */
+export type RemoteStatusIconComponent = (props: RemoteStatusIconProps) => ReactNode;
+/** The composer banner component (a .tsx factory result; parameter for Node). */
+export type RemoteComposerBannerComponent = (props: RemoteComposerBannerProps) => ReactNode;
+/**
+ * Register the stylesheet and the two status parts. Gate-independent by
+ * design — the caller (apply) places this before its desktop gate.
+ * @param ctx - client root context.
+ * @param icon - the title-row connection icon component.
+ * @param banner - the composer banner component.
+ */
+export declare function registerRemoteStatusUi(ctx: ClientContext, icon: RemoteStatusIconComponent, banner: RemoteComposerBannerComponent): void;
+//# sourceMappingURL=remote-status-register.d.ts.map

package/lib/types/client/remote-status-register.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"remote-status-register.d.ts","sourceRoot":"","sources":["../../../src/client/remote-status-register.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;;;;;;;;;;;;;;;;;;GA4BG;AACH,OAAO,KAAK,EAAE,SAAS,EAAE,MAAM,OAAO,CAAA;AACtC,OAAO,KAAK,EAAE,aAAa,EAAa,MAAM,mBAAmB,CAAA;AAIjE,OAAO,KAAK,EAAE,qBAAqB,EAAE,MAAM,wBAAwB,CAAA;AACnE,OAAO,KAAK,EAAE,yBAAyB,EAAE,MAAM,4BAA4B,CAAA;AAE3E,sEAAsE;AACtE,MAAM,MAAM,yBAAyB,GAAG,CAAC,KAAK,EAAE,qBAAqB,KAAK,SAAS,CAAA;AACnF,iFAAiF;AACjF,MAAM,MAAM,6BAA6B,GAAG,CAAC,KAAK,EAAE,yBAAyB,KAAK,SAAS,CAAA;AAuB3F;;;;;;GAMG;AACH,wBAAgB,sBAAsB,CACpC,GAAG,EAAE,aAAa,EAClB,IAAI,EAAE,yBAAyB,EAC/B,MAAM,EAAE,6BAA6B,GACpC,IAAI,CAgCN"}

package/lib/types/client/settings/SettingsSection.d.ts

@@ -0,0 +1,46 @@
+/**
+ * The dsh-zen-remote plugin row's settings block on the Plugins manager
+ * (T15 + T15-fix + T16 + T17): the staged row fields inside the official
+ * settings-form frame ending in its one save control, and BELOW the form —
+ * outside it, so they still render when the configuration namespace is not
+ * served — the instant-operation areas. Which areas render follows the row's
+ * SAVED role, read from the configForms snapshot's row document — never from
+ * a status body (T16-fix 3); when that document carries no role at all (the
+ * value lives only in `lan-gate.config.json`), the page probes the
+ * lightweight client-config route (both roles register it) for the EFFECTIVE
+ * role (T17). A host shows gateway status, pairing, device list and the push
+ * probe (POSTing the same-origin admin routes and re-reading `admin/status`);
+ * a client shows the server connection form, the connection status line and
+ * unpairing (against `client/status`, T16) and NEVER polls `admin/*` — on a
+ * client deployment those routes do not exist, and a stale kept body would
+ * pin the page to the old role. The poll choice waits out the snapshot's
+ * loading state — and the probe, when the row cannot answer — for the same
+ * reason. Only field edits stage and save through `ZenRemoteSettingsForm`.
+ *
+ * Status refreshes never clear what is already on screen (T15-fix 1): a
+ * failed refresh keeps the last ready data and says so in a banner — only a
+ * failed FIRST load enters the error state, because saving a restart-required
+ * field reloads the plugin row (T17) and the first post-save refresh can land
+ * inside that reload window (further pulls follow at 1.5s, and for a
+ * row-reloading save at 3s and 6s, T17b). Every status request carries a
+ * latest-wins ticket (T15-fix 4), so an earlier request that answers late
+ * cannot overwrite newer data.
+ *
+ * Opened through the gateway (`viaGateway`, i.e. on a phone or another
+ * browser) the server-local buttons disable and a notice says so — and until
+ * one status load answers from the server itself, they count as remote. The
+ * summary view renders its one-liner alone and never fetches a thing.
+ */
+import type { PropsLocale, PropsRuntime } from '@deepseek-ai/dsh-client-ui-slots';
+import type { ZenRemoteSettingsForm } from '../../client-data/settings-form.ts';
+import { NS } from '../locales.ts';
+import type { SharesStore } from '../../client-data/shares.ts';
+export interface SettingsSectionProps extends PropsRuntime<'plugins.row.config'>, PropsLocale<typeof NS> {
+    /** The staged configuration form (injected share). */
+    config: ZenRemoteSettingsForm;
+    /** The shared shares store (injected share, T33b) — the same singleton the
+     * title-row icon and the session menu read. */
+    shares: SharesStore;
+}
+export declare function SettingsSection(props: SettingsSectionProps): import("react").JSX.Element;
+//# sourceMappingURL=SettingsSection.d.ts.map

package/lib/types/client/settings/SettingsSection.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"SettingsSection.d.ts","sourceRoot":"","sources":["../../../../src/client/settings/SettingsSection.tsx"],"names":[],"mappings":"AAAA;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;GAgCG;AAIH,OAAO,KAAK,EAAE,WAAW,EAAE,YAAY,EAAE,MAAM,kCAAkC,CAAA;AAqBjF,OAAO,KAAK,EAUV,qBAAqB,EACtB,MAAM,oCAAoC,CAAA;AAC3C,OAAO,EAAE,EAAE,EAAE,MAAM,eAAe,CAAA;AAElC,OAAO,KAAK,EAAkB,WAAW,EAAE,MAAM,6BAA6B,CAAA;AAE9E,MAAM,WAAW,oBAAqB,SAAQ,YAAY,CAAC,oBAAoB,CAAC,EAAE,WAAW,CAAC,OAAO,EAAE,CAAC;IACtG,sDAAsD;IACtD,MAAM,EAAE,qBAAqB,CAAA;IAC7B;mDAC+C;IAC/C,MAAM,EAAE,WAAW,CAAA;CACpB;AA0DD,wBAAgB,eAAe,CAAC,KAAK,EAAE,oBAAoB,+BAW1D"}