dsh-connect-trae 2.2.0 → 2.3.1

package/lib/client.js

@@ -165,10 +165,8 @@ window.__ModuleLoader__.load({
 .dsm-plugin-card-head{flex-direction:column;flex:1;gap:4px;min-width:0;display:flex}
 .dsm-plugin-card-title{color:var(--dsw-alias-label-primary,#e6e6e6);font-size:15px;font-weight:600;line-height:1.4}
 .dsm-plugin-card-description{color:var(--dsw-alias-label-tertiary,#999);font-size:13px;line-height:1.5}
-/* Pure-CSS caret: the host primitives' chevron icon names differ per DSH line
-   (0.1.5 IconChevronDownOutline14 vs 0.1.7 IconChevronDownOutlineRegular),
-   so no static import can serve both — importing the 0.1.5 name makes the
-   client bundle fail to resolve on 0.1.7, taking the whole card down. A border
+/* Pure-CSS caret: the host primitives' chevron icon names are not part of any
+   stable contract across DSH releases, so no static import is used — a border
    caret in the plugin's own CSS is version-proof. */
 .dsm-plugin-card-chevron{color:var(--dsw-alias-label-tertiary,#999);flex:none;width:16px;height:16px;position:relative;transition:transform .16s}
 .dsm-plugin-card-chevron::before{content:"";display:block;position:absolute;left:4px;top:5px;width:7px;height:7px;border-right:1.6px solid currentColor;border-bottom:1.6px solid currentColor;transform:rotate(45deg)}
@@ -267,6 +265,10 @@ window.__ModuleLoader__.load({
 .dsm-trae-checkin-label{color:var(--dsw-alias-label-primary,#e6e6e6);font-size:13px;line-height:18px;font-weight:600}
 .dsm-trae-checkin-hint{color:var(--dsw-alias-label-tertiary,#9aa0a8);font-size:12px;line-height:17px}
 .dsm-trae-checkin-button{flex:none}
+/* The "this machine already used today's check-in" note is INFORMATIONAL, not
+   an error: it is Trae's one-per-device-per-day rule, and the day is simply
+   spent. Rendering it in the error colour would read as a plugin fault. */
+.dsm-trae-checkin-note{margin:8px 0 0;font-size:12px;line-height:18px;color:var(--dsw-alias-label-secondary,#c6c9d0)}
 `;
 		//#endregion
 		//#region src/client/TraeUsageCard.tsx
@@ -295,11 +297,11 @@ window.__ModuleLoader__.load({
 		/**
 		* Write one settings field and confirm the value actually landed.
 		*
-		* `settingsScope.set()` / `configForms.set()` resolving is NOT proof that
-		* anything was stored. On DSH 0.1.7 a write can be accepted by the transport
-		* and still not materialize — a rejected write reloads Host state and merely
-		* RETURNS, so the caller's `await` succeeds while the document is unchanged.
-		* The 0.1.7 form also answers with an explicit boolean for exactly this reason.
+		* `configForms.set()` resolving is NOT proof that anything was stored: a write
+		* can be accepted by the transport and still not materialize — a rejected
+		* write reloads Host state and merely RETURNS, so the caller's `await`
+		* succeeds while the document is unchanged. The form answers with an explicit
+		* boolean for exactly this reason.
 		*
 		* Either way the caller must not report success on an unpersisted write: the
 		* user would see the control flip and then silently revert.
@@ -391,6 +393,14 @@ window.__ModuleLoader__.load({
 			/** Last claim refusal, shown until the next successful refresh. */
 			const [claimError, setClaimError] = (0, react.useState)(void 0);
 			/**
+			* Whether this MACHINE has spent today's check-in while the selected account
+			* has not been paid — the "switched account" state. Kept separate from
+			* `claimError` because it is not a failure: it is the upstream's one-per-
+			* device-per-day rule, and rendering it through the "签到失败：…" line would
+			* present a normal rule as a plugin fault.
+			*/
+			const [deviceSpentNotice, setDeviceSpentNotice] = (0, react.useState)(false);
+			/**
 			* A refused or unpersisted settings write, surfaced instead of silently
 			* reverting. On 0.1.7 a rejected write resolves normally, so without this
 			* the control would flip and then quietly snap back on the next snapshot.
@@ -471,6 +481,7 @@ window.__ModuleLoader__.load({
 			*/
 			(0, react.useEffect)(() => {
 				setClaimError(void 0);
+				setDeviceSpentNotice(false);
 			}, [activeRegion]);
 			(0, react.useEffect)(() => {
 				if (!open || !activeRegionOn || status.status !== "signed-in") return;
@@ -538,13 +549,21 @@ window.__ModuleLoader__.load({
 			* (it stops an obviously pointless click), not the protection.
 			*
 			* A refusal is not thrown away: the route answers `claimed: false` with the
-			* upstream's business code and message, and the card shows it. The upstream
-			* also reports success for an already-claimed day, so `alreadyCheckedIn`
-			* refreshes the state without pretending a new reward landed.
+			* upstream's business code and message, and the card shows it. Three answers
+			* are distinguished rather than collapsed into "failed":
+			*
+			*  - `alreadyCheckedIn` — this ACCOUNT was already paid today; show it as
+			*    claimed and refresh, never as an error.
+			*  - `deviceCheckedIn` (code 9095) — this MACHINE already spent today's
+			*    check-in, so this account cannot claim here today. That is the normal
+			*    outcome after switching accounts, and saying "check-in failed" would
+			*    blame the plugin for an upstream rule.
+			*  - anything else — a real refusal, reported verbatim.
 			*/
 			const claimCheckin = async () => {
 				setClaiming(true);
 				setClaimError(void 0);
+				setDeviceSpentNotice(false);
 				try {
 					const response = await fetch(withTraeRegion(TRAE_CHECKIN_PATH, activeRegion), {
 						method: "POST",
@@ -553,6 +572,11 @@ window.__ModuleLoader__.load({
 					});
 					const body = await response.json().catch(() => void 0);
 					if (!response.ok) throw new Error(body?.error ?? `HTTP ${response.status}`);
+					if (body?.claimed === false && body.deviceCheckedIn === true) {
+						await refreshUsage(activeRegion);
+						if (mounted.current) setDeviceSpentNotice(true);
+						return;
+					}
 					if (body?.claimed === false && body.alreadyCheckedIn !== true) throw new Error(body.message === void 0 || body.message === "" ? t("row.checkinRefused", { code: String(body.code ?? "") }) : `${t("row.checkinRefused", { code: String(body.code ?? "") })}: ${body.message}`);
 					await refreshUsage(activeRegion);
 				} catch (error) {
@@ -957,10 +981,11 @@ window.__ModuleLoader__.load({
 									children: t("row.creditsError", { message: status.creditsError })
 								}),
 								status.checkin === void 0 ? null : (() => {
-									const done = status.checkin.checkedIn || status.checkin.didCheckedIn;
+									const accountClaimed = status.checkin.checkedIn;
+									const deviceSpent = !accountClaimed && (status.checkin.didCheckedIn || deviceSpentNotice);
 									const reward = formatNumber(status.checkin.credits);
 									const bonus = status.checkin.extraCredits === void 0 ? "" : ` + ${formatNumber(status.checkin.extraCredits)}`;
-									return /* @__PURE__ */ (0, react_jsx_runtime.jsxs)("div", {
+									return /* @__PURE__ */ (0, react_jsx_runtime.jsxs)(react_jsx_runtime.Fragment, { children: [/* @__PURE__ */ (0, react_jsx_runtime.jsxs)("div", {
 										className: "dsm-trae-checkin",
 										children: [/* @__PURE__ */ (0, react_jsx_runtime.jsxs)("span", {
 											className: "dsm-trae-checkin-copy",
@@ -969,18 +994,22 @@ window.__ModuleLoader__.load({
 												children: t("row.checkinLabel")
 											}), /* @__PURE__ */ (0, react_jsx_runtime.jsxs)("span", {
 												className: "dsm-trae-checkin-hint",
-												children: [t("row.checkinReward", { reward: `${reward}${bonus}` }), done ? ` · ${t("row.checkinDoneHint")}` : ""]
+												children: [t("row.checkinReward", { reward: `${reward}${bonus}` }), accountClaimed ? ` · ${t("row.checkinDoneHint")}` : ""]
 											})]
 										}), /* @__PURE__ */ (0, react_jsx_runtime.jsx)("button", {
 											type: "button",
 											className: "dsm-btn dsm-btn-primary dsm-trae-checkin-button",
-											disabled: !status.checkin.enabled || done || claiming,
+											disabled: !status.checkin.enabled || accountClaimed || deviceSpent || claiming,
 											onClick: () => {
 												claimCheckin();
 											},
-											children: claiming ? t("row.checkinClaiming") : done ? t("row.checkinClaimed") : t("row.checkinClaim")
+											children: claiming ? t("row.checkinClaiming") : accountClaimed ? t("row.checkinClaimed") : t("row.checkinClaim")
 										})]
-									});
+									}), deviceSpent ? /* @__PURE__ */ (0, react_jsx_runtime.jsx)("p", {
+										className: "dsm-trae-checkin-note",
+										role: "status",
+										children: t("row.checkinDeviceSpent")
+									}) : null] });
 								})(),
 								status.checkin !== void 0 && !status.checkin.enabled ? /* @__PURE__ */ (0, react_jsx_runtime.jsx)("p", {
 									className: "dsm-trae-usage-error",
@@ -1212,6 +1241,7 @@ window.__ModuleLoader__.load({
 			"row.checkinDoneHint": "come back tomorrow",
 			"row.checkinRefused": "Trae refused the check-in (code {code})",
 			"row.checkinError": "Check-in failed: {message}",
+			"row.checkinDeviceSpent": "This machine already used today's check-in — Trae allows one per device per day, so this account cannot claim here today. Claim it on another device or from the account that checked in, or come back tomorrow.",
 			"row.checkinDisabled": "This account has no check-in activity available.",
 			"row.regionCn": "CN",
 			"row.regionAi": "International",
@@ -1290,6 +1320,7 @@ window.__ModuleLoader__.load({
 			"row.checkinDoneHint": "明天再来",
 			"row.checkinRefused": "Trae 拒绝了本次签到（业务码 {code}）",
 			"row.checkinError": "签到失败：{message}",
+			"row.checkinDeviceSpent": "本机今日的签到已用掉——Trae 按「每台设备每天一次」限制，所以当前账号在本机今天无法再签。可换一台设备领取，或用今天已签到的那台设备/账号，或明天再来。",
 			"row.checkinDisabled": "该账号当前没有可用的签到活动。",
 			"row.regionCn": "国内版",
 			"row.regionAi": "国际版",
@@ -1332,12 +1363,11 @@ window.__ModuleLoader__.load({
 		/**
 		* Client services required by the Plugin configuration contribution.
 		*
-		* Deliberately only the two services that exist on BOTH host lines. Cordis'
-		* dependency gate is hard: any `inject` entry the running line does not provide
-		* keeps `apply` from ever running at all — which is exactly how this plugin
-		* ended up `pending (waiting for service: settingsScope)` on 0.1.7. Probing the
-		* settings surface through `ctx.get()` (which returns undefined, never throws,
-		* for an absent service) is what lets one build serve both lines.
+		* Deliberately only the two services the 0.1.7 line provides unconditionally:
+		* `slots` (card injection) and `locale` (copy). The settings surface is probed
+		* through `ctx.get()` (which returns undefined, never throws, for an absent
+		* service), so the card degrades to read-only rather than failing to load if
+		* configForms is not served yet.
 		*/
 		const inject = ["slots", "locale"];
 		/**
@@ -1364,27 +1394,85 @@ window.__ModuleLoader__.load({
 				}), "dsh-connect-trae: settings copy");
 				const t = ctx.locale.bind(namespace);
 				const softGet = (name) => ctx.get(name);
-				let settingsScope;
 				const forms = softGet("configForms");
-				const legacy = softGet("settingsScope");
-				if (forms !== void 0) {
-					let ns = "trae";
-					try {
-						const served = (forms.describe().getSnapshot().view?.namespaces ?? []).find((entry) => entry.ns === "trae" || /trae/i.test(entry.ns));
-						if (served !== void 0) ns = served.ns;
-					} catch {}
-					settingsScope = forms.get(ns);
-				} else if (legacy !== void 0) settingsScope = legacy.bind({ namespace: "trae" });
+				/**
+				* The card's settings scope, bound to whichever namespace the Host actually
+				* serves — resolved from the describe mirror, and RE-BOUND whenever the
+				* mirror changes.
+				*
+				* The mirror answers asynchronously relative to this plugin's `apply()`
+				* (and, on a profile reload, may gain namespaces that did not exist at
+				* boot — this plugin's entry is exactly such a case). Resolving the
+				* namespace ONCE at apply time and falling back to the declared constant
+				* is a real failure: the form controller is bound to its namespace forever,
+				* so a card whose entry appeared after the mirror's first load writes to
+				* `trae` — a namespace the host does not serve — and every write is
+				* refused (`No configurable plugin entry "trae"`), while the controls stay
+				* enabled (the mirror reports global `writable` even when the namespace is
+				* missing).
+				*
+				* The scope therefore forwards every read/write to the CURRENT controller:
+				* once the mirror lists the trae namespace (any name matching `/trae/i`,
+				* e.g. `dsh-connect-trae` or `include:dsh-connect-trae`), the card lands on
+				* the right namespace and re-renders through its own subscription. Before
+				* the mirror answers, the scope reports `writable: false` so the card is
+				* read-only rather than offering controls that cannot save.
+				*/
+				const settingsScope = (() => {
+					let current;
+					let currentOff;
+					let refreshedOnce = false;
+					const listeners = /* @__PURE__ */ new Set();
+					const notify = () => {
+						for (const listener of [...listeners]) listener();
+					};
+					const scope = {
+						getSnapshot: () => current?.getSnapshot() ?? {
+							status: "unavailable",
+							value: void 0,
+							writable: false
+						},
+						subscribe: (listener) => {
+							listeners.add(listener);
+							return () => {
+								listeners.delete(listener);
+							};
+						},
+						set: (field, value) => current !== void 0 ? current.set(field, value) : Promise.resolve(false)
+					};
+					const rebind = () => {
+						let served;
+						try {
+							served = (forms?.describe().getSnapshot().view?.namespaces ?? []).find((entry) => entry.ns === "trae" || /trae/i.test(entry.ns));
+						} catch {}
+						const next = served === void 0 || forms === void 0 ? void 0 : forms.get(served.ns);
+						if (next !== current) {
+							currentOff?.();
+							current = next;
+							currentOff = current?.subscribe(notify);
+							notify();
+						}
+						if (next === void 0 && !refreshedOnce) {
+							refreshedOnce = true;
+							try {
+								(forms?.describe()).load?.();
+							} catch {}
+						}
+					};
+					rebind();
+					forms?.describe().subscribe?.(rebind);
+					return scope;
+				})();
 				const registerCard = (slotName, key) => {
 					try {
 						ctx.slots.inject(slotName, () => ctx.slots.register({
 							name: slotName,
 							key,
 							priority: 30,
-							inject: () => settingsScope === void 0 ? { t } : {
+							inject: () => ({
 								t,
 								settingsScope
-							}
+							})
 						}, TraeUsageCard));
 					} catch (error) {
 						console.error(`[dsh-connect-trae] card slot "${slotName}" failed to register (host provider unaffected):`, error);
@@ -1392,7 +1480,6 @@ window.__ModuleLoader__.load({
 				};
 				registerCard("plugins.bundle.config", "dsh-connect-trae");
 				registerCard("plugins.row.config", "dsh-connect-trae#dsh-connect-trae");
-				registerCard("settings.plugin.item", "trae");
 			} catch (error) {
 				console.error("[dsh-connect-trae] client card failed to load (host provider unaffected):", error);
 			}

package/lib/index.d.ts

@@ -46,6 +46,15 @@ interface TraeStorageCandidate {
   path: string;
   source: TraeCredentialSource;
 }
+/**
+ * One edition's plausible Windows directory spellings, in probe order.
+ *
+ * Exported so the identity reader and the credential scanner probe the SAME
+ * names: the two resolve different files (the install's `product.json` vs the
+ * per-user `storage.json`) but they describe one installation, and a spelling
+ * that works for one but not the other is a bug rather than a preference.
+ */
+declare function traeWindowsAppNames(edition: TraeEdition): readonly string[];
 declare function traeStorageCandidates(platform?: NodeJS.Platform, home?: string, env?: NodeJS.ProcessEnv): TraeStorageCandidate[];
 //#endregion
 //#region src/region.d.ts
@@ -175,6 +184,13 @@ interface TraeWireModel {
   contextWindow?: number;
   maxTokens?: number;
   reasoning?: TraeReasoningCapability;
+  /**
+   * Effective (post-discount) credit multiplier, read from the row's
+   * `display_contact_config` — the figure the Trae IDE renders (see
+   * `wireCreditMultiplier` in solo.ts). Wins over the Remote directory's own
+   * `consumption_rate`, which reports the undiscounted value.
+   */
+  creditMultiplier?: number;
   /**
    * The `get_detail_param` function this config_name came from. Trae splits its
    * callable roster across several functions (SOLO modes), and a model is only
@@ -191,12 +207,19 @@ interface TraeWireModel {
  * skeleton: it supplies the display id, display name, context windows, credit
  * multiplier, reasoning and multimodal flags. `wire` (from `get_detail_param`)
  * supplies the real `llm_utils_chat` `config_name` — the only id the chat
- * endpoint actually accepts. A remote row is only callable when it maps to a
- * wire `config_name`, so a remote row with no wire match is DROPPED (it would
- * otherwise be sent as an invalid `config_name` and rejected with 4001
- * "param is invalid"). Verified 2026-08-30: the Remote directory advertises
- * `Doubao-Seed-Code` and `glm-5.3`, neither of which is a current `config_name`;
- * both fail every request, so they must not be exposed.
+ * endpoint actually accepts — plus the authoritative post-discount credit
+ * multiplier when `display_contact_config` carries one. A remote row is only
+ * callable when it maps to a wire `config_name`, so a remote row with no wire
+ * match is DROPPED (it would otherwise be sent as an invalid `config_name` and
+ * rejected with 4001 "param is invalid"). Verified 2026-08-30: the Remote
+ * directory advertises `Doubao-Seed-Code` and `glm-5.3`, neither of which is a
+ * current `config_name`; both fail every request, so they must not be exposed.
+ *
+ * Credit multiplier precedence: the wire's `display_contact_config` rate wins
+ * whenever present (it is the post-discount figure the Trae IDE renders — the
+ * Remote directory can report up to 10x the undiscounted value, see
+ * `wireCreditMultiplier` in solo.ts); the Remote `consumption_rate` is the
+ * fallback when the wire row carries none.
  *
  * Joining is two-tier, in priority order:
  *  1. `wire.id` (the `config_name`) equals the remote id — the model's display
@@ -562,6 +585,8 @@ interface TraeObservedModelConfig {
 declare function parseObservedModelConfig(line: string): TraeObservedModelConfig | undefined;
 //#endregion
 //#region src/model-cache.d.ts
+/** Basename of the SQLite cache sitting beside the credential document. */
+declare const TRAE_STATE_DB_FILENAME = "state.vscdb";
 interface TraeCachedModelConfig {
   name: string;
   customConfig?: Record<string, unknown>;
@@ -580,11 +605,54 @@ interface TraeCachedModelReadOptions {
   home?: string;
   /** Environment override for testing; defaults to process.env. */
   env?: NodeJS.ProcessEnv;
+  /**
+   * The credential candidate whose account is being read. Supplying it pins the
+   * lookup to the installation the credential actually came from, which is the
+   * only way to stay correct when several editions are installed: `storage.json`
+   * and `state.vscdb` live in the SAME `globalStorage` directory, so the cache
+   * belongs to whichever candidate yielded the sign-in.
+   */
+  candidate?: TraeStorageCandidate;
+  /** Injectable for tests; defaults to node:fs existsSync. */
+  exists?: (path: string) => boolean;
+  /**
+   * Injectable `sqlite3` runner for tests; defaults to promisified `execFile`.
+   * Mirrors the `fetchImpl` injection used elsewhere in this plugin, and exists
+   * so a test can assert the exact argv — in particular WHICH database path was
+   * chosen, which no assertion on the candidate list alone can prove.
+   */
+  runSqlite?: (database: string, sql: string) => Promise<{
+    stdout: string;
+  }>;
 }
+/**
+ * The cache paths to try, most-specific first.
+ *
+ * `state.vscdb` is a SIBLING of the credential document (both sit in
+ * `globalStorage`), so a candidate's own path is the authority for its cache —
+ * this is why the database is derived from {@link traeStorageCandidates} rather
+ * than re-spelled here.
+ *
+ * It previously hardcoded the single macOS spelling `Trae CN`, which was wrong
+ * in two ways on Windows: `paths.ts` probes `Trae CN` AND `trae-cn`, and the
+ * edition actually installed is often SOLO (`TRAE SOLO CN`). This module would
+ * then point at a directory that does not exist. That went unnoticed only
+ * because the Windows `sqlite3` dependency is absent, so the lookup failed and
+ * callers fell back — masking the wrong path behind a different error. Sharing
+ * one path table means a spelling that works for sign-in also works for the
+ * cache.
+ */
+declare function traeStateDatabaseCandidates(options?: TraeCachedModelReadOptions): string[];
 /**
  * Read Trae's own current user's model map via sqlite3 without exposing
  * secrets. The sqlite3 command line is a macOS prerequisite; on Windows it is
  * typically absent, so the call fails and callers fall back gracefully.
+ *
+ * Every candidate database is tried in order and the first that EXISTS is
+ * queried. Existence is checked before spawning because a missing file and a
+ * missing `sqlite3` binary are different problems: choosing the wrong directory
+ * would otherwise surface as a confusing `sqlite3` failure, hiding a path bug
+ * behind a dependency error.
  */
 declare function readTraeCachedModel(functionName: string, modelName: string, userId: string, options?: TraeCachedModelReadOptions): Promise<TraeCachedModelConfig | undefined>;
 //#endregion
@@ -620,6 +688,55 @@ interface TraeModelDetailRequest {
 /** Build the exact request shape observed in successful current Trae CN logs. */
 declare function buildTraeModelDetailRequest(configName?: string, custom?: boolean): TraeModelDetailRequest;
 //#endregion
+//#region src/redact.d.ts
+/**
+ * Redaction helpers for diagnostics that a user may paste into a public issue.
+ *
+ * A verification report is only useful if it can be shared, and it is only safe
+ * to share if it carries no personal identifiers. Paths are the hard case:
+ * `C:\Users\<real name>\AppData\Roaming\Trae CN\...` contains both a real
+ * account name AND the single most diagnostic token in the whole report (the
+ * Trae data directory spelling). Redacting the whole path would make the report
+ * worthless; printing it whole would leak the user's name. So the user segment
+ * is replaced and the meaningful tail is preserved.
+ *
+ * @module dsh-connect-trae/redact
+ */
+/**
+ * Replace the user segment of a path with `<user>`, keeping the rest intact.
+ *
+ * Handles the shapes a Trae install can produce:
+ *   - `C:\Users\<name>\...` and `C:\Documents and Settings\<name>\...` (Windows)
+ *   - `/Users/<name>/...` and `/home/<name>/...` (macOS / Linux)
+ *
+ * Anything after that segment — edition directory, `User\globalStorage`,
+ * `storage.json` — is preserved verbatim, because that is what a report is
+ * actually read for. Cross-platform on purpose: the function is called by
+ * Windows-focused diagnostics, but the same helpers run in tests and on other
+ * hosts, and a report from the wrong platform must not leak either.
+ */
+declare function maskUserPath(path: string): string;
+/**
+ * Describe a name by shape instead of by value: a character count, plus whether
+ * it is purely numeric.
+ *
+ * This is the deliberate middle ground for account names. A Trae account name
+ * is often a real name or a phone number, so it must never be printed; but the
+ * report still needs to show that an account WAS resolved, and the shape
+ * distinguishes a real nickname from a generated `用户<n>` id — which is the
+ * only thing a reader needs to judge whether account discovery worked.
+ */
+declare function describeNameShape(name: unknown): string;
+/**
+ * Describe an identifier by shape instead of by value.
+ *
+ * A device id (`x-device-id`) is a stable installation identifier and is
+ * directly tied to the upstream's per-device rules, so it is never printed.
+ * Its shape still proves which resolution path ran: a real `icube-dc` id is
+ * 15 digits, while the fallback is a 32-character hex hash.
+ */
+declare function describeIdShape(value: unknown): string;
+//#endregion
 //#region src/protocol.d.ts
 declare const TRAE_CN_AGENT_TASK_PATH = "/api/agent/v3/create_agent_task";
 declare const TRAE_CN_TITLE_PATH = "/api/agent/v3/llm_utils_chat";
@@ -1054,6 +1171,8 @@ interface TraeSoloModel {
   contextWindow?: number;
   maxTokens?: number;
   reasoning?: TraeReasoningCapability;
+  /** Effective (post-discount) credit multiplier, as the Trae IDE shows it. */
+  creditMultiplier?: number;
   /** The directory function that listed this config (replayed when calling it). */
   function?: string;
 }
@@ -1223,15 +1342,32 @@ interface TraeUsageSnapshot {
   packs: TraeUsagePack[];
 }
 interface TraeCheckinStatus {
+  /**
+   * Whether the account's REWARD PACK for today already exists. This is the
+   * account-wide answer and it is the one that decides whether there is
+   * anything left to claim: a day with `checkedIn: true` has already been paid
+   * out, whichever device produced it.
+   */
   checkedIn: boolean;
   /** Reward for one check-in, as reported by the upstream (`credits`). */
   credits: number;
   enabled: boolean;
   /**
-   * Whether today's reward was claimed in a previous session. The upstream
-   * reports `did_checked_in` separately from `checked_in`: the app uses the
-   * former to keep the claim button disabled for the rest of the Beijing day
-   * even when the status read happens to report `checked_in: false`.
+   * Whether THIS device's claim for today was already recorded. The upstream
+   * keys this on the `x-device-id` the request carries — not on the account —
+   * so it answers `true` for the device that claimed and `false` for the same
+   * account and day read from any other device.
+   *
+   * Measured 2026-09-26 on a live CN account whose claim had succeeded minutes
+   * earlier: `did_checked_in` was `true` with the claiming device id and
+   * `false` with the header omitted, with a synthetic id, and with another
+   * install's id. Repeating the read never flips it, so it is not "have I seen
+   * you before" state either — only an actual claim sets it.
+   *
+   * It is therefore NOT a "today is done" signal on its own (claiming again
+   * answers the upstream's own 9095 "该设备今日已参与签到" refusal); it is
+   * evidence that this exact device is already accounted for, which is what
+   * makes a claim safe to skip.
    */
   didCheckedIn: boolean;
   /** Bonus credit granted on top of the base reward, when the upstream reports one. */
@@ -1307,6 +1443,12 @@ declare class TraeUsageClient {
   /**
    * Daily check-in status. Read-only, and answered with or without the device
    * header — the claim is what needs it.
+   *
+   * The read DOES carry the header whenever this installation has one, and
+   * that is deliberate rather than incidental: `did_checked_in` is answered
+   * per device, so omitting the header would make a device that already claimed
+   * today look identical to one that never has (measured 2026-09-26, see
+   * {@link TraeCheckinStatus.didCheckedIn}).
    */
   checkinStatus(signal?: AbortSignal): Promise<TraeCheckinStatus>;
   /**
@@ -1386,11 +1528,22 @@ interface TraeWebModel {
 /**
  * Daily check-in state rendered below the credit stats.
  *
- * `didCheckedIn` is not redundant with `checkedIn`: the upstream reports them
- * separately, and the official client keeps the claim button disabled for the
- * rest of the Beijing day off `did_checked_in` even when a status read comes
- * back `checked_in: false`. The card mirrors that rule so a stale-looking
- * status cannot invite a pointless second claim.
+ * The two booleans answer DIFFERENT questions and must never be collapsed into
+ * one "done" flag — doing that was a shipped bug (see CHANGELOG 2.3.1):
+ *
+ *  - `checkedIn` is ACCOUNT-level: today's reward pack exists for this account,
+ *    so there is nothing left to claim and the balance already includes it.
+ *  - `didCheckedIn` is DEVICE-level: this MACHINE already spent its one
+ *    check-in for the day, whichever account spent it. The upstream keys it on
+ *    the `x-device-id` in the request and answers it per device, not per
+ *    account (measured 2026-09-26: the same account and Beijing day answered
+ *    `false` with the header omitted, with a synthetic id, and with another
+ *    install's id, and `true` for the device that actually claimed).
+ *
+ * So `didCheckedIn && !checkedIn` is the "switched account" case: the device's
+ * daily check-in is used up, but THIS account was never rewarded. Claiming
+ * again is refused upstream (business code 9095, "该设备今日已参与签到"), so
+ * the card disables the button — but it must say that, not "claimed today".
  */
 interface TraeWebCheckin {
   checkedIn: boolean;
@@ -1403,8 +1556,19 @@ interface TraeWebCheckin {
 interface TraeWebCheckinClaim {
   /** False when the upstream answered a non-zero business code (e.g. 9004). */
   claimed: boolean;
-  /** True when today was already claimed, so nothing was sent upstream. */
+  /**
+   * True only when THIS ACCOUNT's reward for today already exists, so nothing
+   * was sent upstream. Distinct from {@link TraeWebCheckinClaim.deviceCheckedIn}:
+   * a device that already claimed for another account leaves this false.
+   */
   alreadyCheckedIn: boolean;
+  /**
+   * True when today's check-in was already spent on this DEVICE (by this or
+   * another account), so no claim was sent or the upstream refused it with
+   * 9095. Not an error: it is the truthful answer to "can this account claim
+   * here today?" — no, and the reason is the machine, not the account.
+   */
+  deviceCheckedIn?: boolean;
   code?: number;
   message?: string;
   /** The refreshed check-in state, present whenever the claim path ran. */
@@ -1598,13 +1762,30 @@ declare const name = "dsh-connect-trae";
 declare const inject: string[];
 /**
  * Settings namespace, as a plain lowercase literal. DSH 0.1.2 removed the
- * `settingsNamespace` brand constructor from the npm package (the Desktop
- * host still ships it as a legacy shim), and every consumer of this constant —
- * `registerModelDiscovery`, `registerConfigurableProviders`,
- * `settings.installSection`, the settings test — takes it as a kebab string,
- * so no branding is needed for either host generation.
+ * `settingsNamespace` brand constructor from the npm package, and every
+ * consumer of this constant takes it as a kebab string — so no branding is
+ * needed. It is the FALLBACK namespace; the namespace the host actually serves
+ * comes from {@link settingsNamespaceOf} (0.1.7 keys settings by the Loader
+ * entry id, which a profile patch may mount as `dsh-connect-trae` or
+ * `include:dsh-connect-trae`).
  */
 declare const TRAE_SETTINGS_NS = "trae";
+/**
+ * The namespace the HOST actually serves this plugin under.
+ *
+ * On DSH 0.1.7 `SettingsForms.describe()` keys every namespace by the Loader
+ * entry id, and the harness looks a provider's namespace up by EXACT match —
+ * advertising `trae` while the host serves `include:dsh-connect-trae` made the
+ * provider read as "not configured": its configure affordance and model
+ * discovery both silently went dead.
+ *
+ * `ctx.fiber.entry` is added by the Loader, not by Cordis itself, so it is not
+ * in Cordis's public types and is absent on hosts that mount a plugin without a
+ * Loader entry (a test harness, or `ctx.plugin()` called directly). Hence the
+ * probe plus the documented fallback, mirroring the first-party plugins:
+ * `const settingsNs = ctx.fiber.entry?.options.id ?? NS`.
+ */
+declare function settingsNamespaceOf(ctx: unknown): string;
 /** One region's saved model state: its own directory and the user's selection within it. */
 interface TraeRegionState {
   /**
@@ -1681,26 +1862,21 @@ declare function regionStateOf(config: Config, region: TraeRegion): TraeRegionSt
  */
 declare function regionEnabled(config: Config, region: TraeRegion): boolean;
 /**
- * Mark a schema's field as volatile on the DSH lines that support it.
+ * Mark a schema's field as volatile.
  *
- * `volatile()` exists from schemastery 3.18.3 (the DSH 0.1.7 line, which is the
- * only line whose settings write gate reads the marker). Older pinning (3.18.2,
- * the 0.1.5 line) has no such method, and the schema must stay byte-identical
- * to the unmarked original there: hand-writing `meta.volatile = true` would
- * bypass schemastery's own `validateVolatileSchema` checks and produce a schema
- * no 0.1.5 consumer understands — so on that line this degrades to an identity
- * no-op.
+ * `volatile()` exists from schemastery 3.18.3; since 2.3.0 the peer range
+ * requires `>=3.18.4`, so it is always present on a supported host. The probe
+ * is kept as a safety net for a consumer that resolves an older schemastery
+ * anyway (where the helper must degrade to identity — hand-writing
+ * `meta.volatile = true` would bypass schemastery's own `validateVolatileSchema`
+ * checks) and to keep both arms deterministically testable.
  *
  * Without the marker, 0.1.7's settings write gate REJECTS every write with
  * `Plugin entry "trae" has no volatile fields` while the scope's `set()` still
  * resolves — so the card would look like it saved and silently revert.
- *
- * Exported so BOTH arms are testable on any machine: the capability is decided
- * by whichever schemastery the dependency tree resolves, so without a seam the
- * no-op arm would silently stop being exercised the moment the pin moved up.
  */
 declare function asVolatile<S>(schema: S): S;
 declare const Config: z<Config>;
 declare function apply(ctx: Context, config: Config): void;
 //#endregion
-export { Config, FALLBACK_TRAE_MODELS, FALLBACK_TRAE_MODELS_AI, REGION_GATEWAYS, type RawChatDelta, type RawChatMessage, type RawChatTool, SseDecoder, type SseEvent, TRAE_AI_PROVIDER, TRAE_CHECKIN_PATH, TRAE_CN_AGENT_TASK_PATH, TRAE_CN_TITLE_PATH, TRAE_MODEL_DETAIL_FUNCTIONS, TRAE_MODEL_DETAIL_PATH, TRAE_PAY_BASE, TRAE_PROVIDER, TRAE_PROVIDERS, TRAE_PROVIDER_DISPLAY_NAMES, TRAE_RAW_CHAT_V1_PATH, TRAE_RAW_CHAT_V2_PATH, TRAE_REASONING_EFFORTS, TRAE_REGIONS, TRAE_REGION_PARAM, TRAE_SETTINGS_NS, TRAE_SOLO_CHAT_PATH, TRAE_SOLO_FUNCTION, TRAE_SOLO_MODELS_PATH, TRAE_SOLO_REMOTE_BASE, TRAE_STREAM_IDLE_TIMEOUT_MS, TRAE_USAGE_PATH, TRAE_VERSION_CODE_FALLBACK, type TraeActivityRule, type TraeAdapter, type TraeCachedModelConfig, TraeCatalog, type TraeChatResult, type TraeCheckinClaim, type TraeCheckinStatus, type TraeContextBudget, type TraeCredential, TraeCredentialStore, TraeDelegatingUpstreamClient, type TraeDiscoveredModel, type TraeDiscoveredReasoning, type TraeEdition, TraeFallbackUpstreamClient, type TraeFallbackUpstreamOptions, type TraeFusionRawChatEnvelope, TraeGatedUpstreamClient, type TraeGatedUpstreamOptions, type TraeIdentity, type TraeInputModality, type TraeModelDetailRequest, type TraeModelInfo, type TraeObservedModelConfig, TraeRawCapabilityController, type TraeRawCapabilityControllerOptions, type TraeRawCapabilitySnapshot, TraeRawCapabilityState, type TraeRawChatBehaviorConfig, type TraeRawChatCapability, type TraeRawChatClientOptions, type TraeRawChatConfig, type TraeRawChatFailureReason, type TraeRawChatRuntimeConfig, TraeRawChatUpstreamClient, type TraeRawDiagnostic, type TraeRawDiagnosticState, type TraeRawGateway, type TraeRawGatewayOptions, type TraeRawResolverResult, type TraeReasoningCapability, type TraeReasoningEffort, type TraeRefreshDevice, type TraeRegion, type TraeRegionGateways, TraeRegionState, type TraeShim, TraeSoloBridge, type TraeSoloClientOptions, TraeSoloRemoteCatalogClient, type TraeSoloRemoteCatalogOptions, TraeSoloUpstreamClient, type TraeStorageCandidate, type TraeStreamEvent, type TraeUpstreamClient, TraeUsageClient, type TraeUsageOptions, type TraeUsagePack, type TraeUsageRouteOptions, type TraeUsageSnapshot, type TraeUsageSummary, type TraeUsageView, type TraeWebActivity, type TraeWebCheckin, type TraeWebCheckinClaim, type TraeWebCredits, type TraeWebUsage, type TraeWireModel, UnconfiguredTraeUpstreamClient, apply, applyContextBudgets, applyImageSelection, applyReasoningEffort, asVolatile, bridgeTraeSoloStream, buildTraeAgentTaskBody, buildTraeCnHeaders, buildTraeFusionRawChatEnvelope, buildTraeModelDetailRequest, buildTraeRawChatDraft, buildTraeRawChatRuntimeConfig, classifyTraeRawChatFailure, createTraeAdapter, createTraeRawGateway, createTraeShim, decodeRawChatChunk, decodeTraeEvent, decryptTraeStorageValue, deriveCatalog, discoveredCatalog, fallbackModelsFor, hashTraeRawChatArg, identityHeaders, inject, legacyTraeOwnAuthPath, mergeTraeModelSources, name, nextRegionEnabled, nextRegionSlots, normalizeTraeCredential, normalizeTraeVersionCode, parseObservedModelConfig, parseReasoningCapability, parseTraeAuthValue, parseTraeCachedModel, parseTraeModelExtraConfigLogLine, parseTraeRawChatBehaviorConfig, parseTraeRemoteModel, parseTraeStorageDocument, pickTraeStorageIdentity, prepareSoloBody, probeTraeRawChatCapability, rawCapabilityDiagnostic, rawCapabilityFingerprint, readTraeCachedModel, readTraeCliIdentity, readTraeIdentity, refreshTraeCredential, regionEnabled, regionEnabledOf, regionOfCredential, regionOfEdition, regionOfHost, regionOfTraeProvider, regionOfTraeStatusUrl, regionOfUserRegion, regionStateOf, registerTraeUsageRoute, resolveTraeIdentity, resolveTraeRawRuntime, sanitizeCatalog, traeEndpoint, traeInputModalities, traeModelDisplayName, traeOwnAuthPath, traeRawChatExtraInfo, traeStorageCandidates, traeWebUsage, unwrapVolatile, unwrapVolatileDeep, withTraeRegion };
+export { Config, FALLBACK_TRAE_MODELS, FALLBACK_TRAE_MODELS_AI, REGION_GATEWAYS, type RawChatDelta, type RawChatMessage, type RawChatTool, SseDecoder, type SseEvent, TRAE_AI_PROVIDER, TRAE_CHECKIN_PATH, TRAE_CN_AGENT_TASK_PATH, TRAE_CN_TITLE_PATH, TRAE_MODEL_DETAIL_FUNCTIONS, TRAE_MODEL_DETAIL_PATH, TRAE_PAY_BASE, TRAE_PROVIDER, TRAE_PROVIDERS, TRAE_PROVIDER_DISPLAY_NAMES, TRAE_RAW_CHAT_V1_PATH, TRAE_RAW_CHAT_V2_PATH, TRAE_REASONING_EFFORTS, TRAE_REGIONS, TRAE_REGION_PARAM, TRAE_SETTINGS_NS, TRAE_SOLO_CHAT_PATH, TRAE_SOLO_FUNCTION, TRAE_SOLO_MODELS_PATH, TRAE_SOLO_REMOTE_BASE, TRAE_STATE_DB_FILENAME, TRAE_STREAM_IDLE_TIMEOUT_MS, TRAE_USAGE_PATH, TRAE_VERSION_CODE_FALLBACK, type TraeActivityRule, type TraeAdapter, type TraeCachedModelConfig, TraeCatalog, type TraeChatResult, type TraeCheckinClaim, type TraeCheckinStatus, type TraeContextBudget, type TraeCredential, TraeCredentialStore, TraeDelegatingUpstreamClient, type TraeDiscoveredModel, type TraeDiscoveredReasoning, type TraeEdition, TraeFallbackUpstreamClient, type TraeFallbackUpstreamOptions, type TraeFusionRawChatEnvelope, TraeGatedUpstreamClient, type TraeGatedUpstreamOptions, type TraeIdentity, type TraeInputModality, type TraeModelDetailRequest, type TraeModelInfo, type TraeObservedModelConfig, TraeRawCapabilityController, type TraeRawCapabilityControllerOptions, type TraeRawCapabilitySnapshot, TraeRawCapabilityState, type TraeRawChatBehaviorConfig, type TraeRawChatCapability, type TraeRawChatClientOptions, type TraeRawChatConfig, type TraeRawChatFailureReason, type TraeRawChatRuntimeConfig, TraeRawChatUpstreamClient, type TraeRawDiagnostic, type TraeRawDiagnosticState, type TraeRawGateway, type TraeRawGatewayOptions, type TraeRawResolverResult, type TraeReasoningCapability, type TraeReasoningEffort, type TraeRefreshDevice, type TraeRegion, type TraeRegionGateways, TraeRegionState, type TraeShim, TraeSoloBridge, type TraeSoloClientOptions, TraeSoloRemoteCatalogClient, type TraeSoloRemoteCatalogOptions, TraeSoloUpstreamClient, type TraeStorageCandidate, type TraeStreamEvent, type TraeUpstreamClient, TraeUsageClient, type TraeUsageOptions, type TraeUsagePack, type TraeUsageRouteOptions, type TraeUsageSnapshot, type TraeUsageSummary, type TraeUsageView, type TraeWebActivity, type TraeWebCheckin, type TraeWebCheckinClaim, type TraeWebCredits, type TraeWebUsage, type TraeWireModel, UnconfiguredTraeUpstreamClient, apply, applyContextBudgets, applyImageSelection, applyReasoningEffort, asVolatile, bridgeTraeSoloStream, buildTraeAgentTaskBody, buildTraeCnHeaders, buildTraeFusionRawChatEnvelope, buildTraeModelDetailRequest, buildTraeRawChatDraft, buildTraeRawChatRuntimeConfig, classifyTraeRawChatFailure, createTraeAdapter, createTraeRawGateway, createTraeShim, decodeRawChatChunk, decodeTraeEvent, decryptTraeStorageValue, deriveCatalog, describeIdShape, describeNameShape, discoveredCatalog, fallbackModelsFor, hashTraeRawChatArg, identityHeaders, inject, legacyTraeOwnAuthPath, maskUserPath, mergeTraeModelSources, name, nextRegionEnabled, nextRegionSlots, normalizeTraeCredential, normalizeTraeVersionCode, parseObservedModelConfig, parseReasoningCapability, parseTraeAuthValue, parseTraeCachedModel, parseTraeModelExtraConfigLogLine, parseTraeRawChatBehaviorConfig, parseTraeRemoteModel, parseTraeStorageDocument, pickTraeStorageIdentity, prepareSoloBody, probeTraeRawChatCapability, rawCapabilityDiagnostic, rawCapabilityFingerprint, readTraeCachedModel, readTraeCliIdentity, readTraeIdentity, refreshTraeCredential, regionEnabled, regionEnabledOf, regionOfCredential, regionOfEdition, regionOfHost, regionOfTraeProvider, regionOfTraeStatusUrl, regionOfUserRegion, regionStateOf, registerTraeUsageRoute, resolveTraeIdentity, resolveTraeRawRuntime, sanitizeCatalog, settingsNamespaceOf, traeEndpoint, traeInputModalities, traeModelDisplayName, traeOwnAuthPath, traeRawChatExtraInfo, traeStateDatabaseCandidates, traeStorageCandidates, traeWebUsage, traeWindowsAppNames, unwrapVolatile, unwrapVolatileDeep, withTraeRegion };