@furayoshi/dsh-widechat 0.7.0 → 0.8.0

package/README.md

@@ -1,6 +1,14 @@
 # @furayoshi/dsh-widechat
 
-A [DeepSeek Harness](https://github.com/deepseek-ai/deepseek-harness) plugin that widens the conversation column past the shipped 748px cap, right-aligns the session stats strip, and caps the composer card so long inputs do not hide the conversation above. Adds a settings row to the General page so all of these can be tuned without restarting DSH.
+A [DeepSeek Harness](https://github.com/deepseek-ai/deepseek-harness) plugin that widens the conversation column past the shipped cap, right-aligns the session stats strip, caps the user-message bubble, and caps the composer's inner scroll so long inputs do not hide the conversation above. Adds a settings row to the General page so all of these can be tuned without restarting DSH.
+
+**Compatibility**
+| DSH version  | min version |
+| :--- | :--- |
+| `0.1.2-rc.1` | `0.8`       |
+| `0.1.1-rc.1` | `<0.8`      |
+
+**NOTE**: as at the current state, this packages has been heavily vibecoded, including most of this README. I might rewrite it at the later date, but you have been warned :)
 
 ![widechat ui](media/widechat-ui.webp)
 
@@ -8,14 +16,14 @@ A [DeepSeek Harness](https://github.com/deepseek-ai/deepseek-harness) plugin tha
 
 ## What it does
 
-The shipped DSH web UI caps the chat content at `--dsh-chat-content-width: 748px` and centers the column with `margin: 0 auto`. On any monitor wider than ~1024px this leaves large empty gutters on both sides and a narrow reading area. This plugin widens that cap to leave only the configured gutter, right-aligns the user-message bubble (the shipped default is narrow on wide viewports), and caps the composer card to a percentage of the viewport so long inputs do not eat the conversation above.
+The shipped DSH web UI caps the chat content with `--dsh-chat-content-width` (a fixed pixel value on pre-0.1.2 hosts, a `clamp()` of the column width on 0.1.2+) and centers the column with `margin: 0 auto`. On any monitor wider than ~1024px this leaves large empty gutters on both sides and a narrow reading area. This plugin widens that cap to leave only the configured gutter, caps the user-message bubble to a share of the column (the shipped default is narrow on wide viewports), and caps the composer's inner scroll to a percentage of the viewport so long inputs do not eat the conversation above.
 
 A small row in the **General** settings page lets you tune four values:
 
 - **Chat column gutter** — a slider, 0–10% of the cell on each side. The shipped default is `1 %`. The column is sized to leave this much whitespace on each side.
 - **Session-stats alignment** — a three-way toggle (left / center / right). The shipped default is `right`. The session-stats line under the composer (token counts, duration, etc.) lines up accordingly.
 - **Your message bubble width** — a slider, 30–100% of the chat column. The shipped default is `75 %`. Your outgoing messages are right-aligned at this width; the assistant's messages fill the rest of the column.
-- **Composer max height** — a slider, 20–80% of the viewport. The shipped default is `50 %`. The composer card and its inner textarea are both capped at this height, so long inputs do not push the conversation off-screen.
+- **Composer max height** — a slider, 20–80% of the viewport. The shipped default is `50 %`. The composer's inner textarea scroll is capped at this height (with a 52 px floor), so long inputs do not push the conversation off-screen.
 
 If a saved value is out of range or of the wrong type, the plugin falls back to the default and logs a `console.warn` with the offending field. The page never refuses to render.
 
@@ -23,7 +31,7 @@ If a saved value is out of range or of the wrong type, the plugin falls back to
 
 DSH's `plugin` subcommand forwards pnpm commands into the profile directory and reconciles the profile's `dsh.profile.bundles` array against the installed packages. So `dsh plugin --profile web add <spec>` is the canonical install path: it runs `pnpm add <spec>`, then automatically appends the package to `bundles` if (and only if) the installed `package.json` declares a `dsh.bundle.patch` — which this package does.
 
-### From npm (after this repo is published)
+### From npmjs
 
 ```sh
 dsh plugin --profile web add @furayoshi/dsh-widechat
@@ -41,7 +49,7 @@ The `github:<owner>/<repo>` spec is pnpm's shorthand for `https://github.com/<ow
 
 ```sh
 # A specific tag
-dsh plugin --profile web add @furayoshi/dsh-widechat@github:FraYoshi/dsh-widechat#v0.7.0
+dsh plugin --profile web add @furayoshi/dsh-widechat@github:FraYoshi/dsh-widechat#v0.8.0
 
 # A branch (e.g. main)
 dsh plugin --profile web add @furayoshi/dsh-widechat@github:FraYoshi/dsh-widechat#main
@@ -102,27 +110,32 @@ If you want to edit the source, the build is `npm run build` (which calls `tsc`
 
 The plugin is two halves:
 
-- **Host** (`lib/index.js`) registers a settings namespace `dsh-widechat` with a `z.object` schema (`chatGutterPct`, `statsAlign`, `userBubblePct`, `composerMaxHeightPct`). The schema's bounds match the slider ranges exactly.
+- **Host** (`lib/index.js`) registers the settings namespace `dsh-widechat` on the host `settings` service via `ctx.settings.register("dsh-widechat", schema)` with a `z.object` schema (`chatGutterPct`, `statsAlign`, `userBubblePct`, `composerMaxHeightPct`). The schema's bounds match the slider ranges exactly.
 - **Client** (`lib/client/index.js`) binds a `SettingsScope` to that namespace, re-injects a small CSS override on every scope change, and registers a row in the `settings.general.item` slot.
 
-The CSS override is intentionally minimal — it touches four things, one per setting:
+The CSS override is intentionally minimal — it touches three things, one per setting (hashes as of DSH 0.1.2-rc.1; the column, bubble and stats hashes live in `dsh-client-ui-chat`, the rest in `dsh-client-ui-conversation`):
 
 ```css
 :root, .wSkVaW_root, [data-phase] {
   --dsh-chat-content-width:        calc(100% - 2 × <chatGutterPct>%) !important;
   --dsh-composer-card-max-width:   calc(100% - 2 × <chatGutterPct>%) !important;
 }
-.gdEzaW_userStack { max-width: <userBubblePct>% !important; }
-.uV2eYG_card     { max-height: <composerMaxHeightPct>vh !important; overflow: hidden !important; }
-.uV2eYG_scroll   { max-height: calc(<composerMaxHeightPct>vh - 64px) !important; }
-.FJxK0a_root     { text-align: <statsAlign> !important; }
+.Sixlwa_userStack { max-width: <userBubblePct>% !important; }
+.uV2eYG_scroll   {
+  min-height: 52px !important;                                  /* floor, see below */
+  max-height: calc(<composerMaxHeightPct>vh - 64px) !important; /* ceiling on the textarea */
+}
+.uV2eYG_hero .uV2eYG_scroll { max-height: calc(<composerMaxHeightPct>vh - 132px) !important; }
+.-NDN2W_root     { text-align: <statsAlign> !important; }
 ```
 
 `chatGutterPct` and `userBubblePct` are **percentages of the cell**; `composerMaxHeightPct` is a **percentage of the viewport**. The cell grows when the sidebar collapses to the rail (56px from 280px), so the column and the bubble grow with it — and the gutter stays at the same percentage. The composer cap, in contrast, is absolute to the viewport so the conversation above is always visible regardless of the sidebar state.
 
-The reason there are two rules for the composer (`uV2eYG_card` and `uV2eYG_scroll`) is that the shipped card has *no* max-height and the shipped inner scroll has `max-height: var(--dsh-composer-text-max-height)` (336px by default). Without overriding the inner scroll too, the user's `composerMaxHeightPct` slider would only take effect at values that allow the inner 336px cap to grow, which is values ≥ 19% on a 1914px viewport — the slider would feel broken above 20% on smaller viewports. The inner override (`- 64px` leaves room for the card's padding and accessory row) makes the slider's effect span the full 20–80 range.
+The composer card itself has **no** `max-height` and **no** `overflow: hidden` override. The card grows naturally to fit its inner scroll (capped above) plus the card's chrome (accessory row, trigger row, padding, gaps). Earlier versions did enforce `max-height: <cap>vh; overflow: hidden;` on the card — but the popover menus (model picker, permission presets, …) open upward from the trigger row inside the card via `bottom: calc(100% + 8px)`, and the card's `overflow: hidden` clipped any portion of the menu that extended above the card top. With the card free to overflow, the menus extend above the card into the conversation area and are fully visible. The conversation scroll above the composer shrinks to make room for the taller card.
 
-DSH's shipped rules are left untouched. The column is still `width: 100%`, `max-width: var(--dsh-chat-content-width)`, `margin: 0 auto`. Toggle, scroll, resize — all the DSH default behavior. The plugin only changes the values of variables (and a few hard caps on the composer) that DSH's CSS already reads.
+The `min-height: 52px` on `.uV2eYG_scroll` mirrors the shipped hero variant's mirror floor. Without it, on a small viewport with a low cap, the scroll collapses to ~28 px and the trigger row below it ends up visually overlapping the typing area. The 52 px floor keeps the textarea usable in that case; below it, the slider value is a no-op for the cap (the scroll holds at 52 px and does not get any smaller).
+
+DSH's shipped rules are left untouched. The column is still `width: 100%`, `max-width: var(--dsh-chat-content-width)`, `margin: 0 auto`. Toggle, scroll, resize — all the DSH default behavior. The plugin only changes the values of variables (and a few caps on the composer's inner scroll) that DSH's CSS already reads.
 
 ## Configuration
 
@@ -143,9 +156,13 @@ Invalid values are dropped to the defaults and a `console.warn` is logged with t
 
 ### This plugin overrides internal CSS-module class hashes
 
-`.wSkVaW_root`, `.Md3f7G_column`, `.uV2eYG_card`, `.uV2eYG_scroll`, `.gdEzaW_userStack`, `.FJxK0a_root` are CSS-Modules-generated class names from `@deepseek-ai/dsh-client-ui-conversation`. Their hashes (the part after the underscore) are recomputed every time that package is rebuilt. Any release of `dsh-client-ui-conversation` can therefore silently break this plugin — specifically, if the shipped rule that reads the variable or has the matching class name changes shape, our override no longer reaches it.
+`.wSkVaW_root`, `.EvIC1a_column`, `.uV2eYG_card`, `.uV2eYG_scroll`, `.Sixlwa_userStack`, `.-NDN2W_root` are CSS-Modules-generated class names from the DSH UI packages — since 0.1.2 the root and composer hashes come from `@deepseek-ai/dsh-client-ui-conversation` and the column, bubble and stats hashes from the new `@deepseek-ai/dsh-client-ui-chat`. Their hashes (the part after the underscore) are recomputed every time the owning package is rebuilt. Any release of those packages can therefore silently break this plugin — specifically, if the shipped rule that reads the variable or has the matching class name changes shape, our override no longer reaches it.
+
+After upgrading DSH, check whether the chat column widens, the user bubble stays right-aligned at the configured width, the composer's inner scroll caps at the configured height (and never gets smaller than 52 px), and the stats line still aligns. If any of those regress, the upstream CSS-module hashes changed; see "Updating" below.
+
+### The slider wins over DSH's drag-to-resize (0.1.2+)
 
-After upgrading `@deepseek-ai/dsh-client-ui-conversation`, check whether the chat column widens, the user bubble stays right-aligned at the configured width, the composer is capped at the configured height, and the stats line still aligns. If any of those regress, the upstream CSS-module hashes changed; see "Updating" below.
+DSH 0.1.2 added drag handles on the chat column that persist a width in `localStorage` (`dsh.conversation.contentWidth`) and write it inline as `--dsh-chat-user-width`. This plugin's `!important` override of `--dsh-chat-content-width` takes precedence over that inline value, so the gutter slider stays the source of truth and dragging the handles is effectively a no-op while the plugin is installed.
 
 ### The `chatGutterPct` is interpreted against the cell, not the viewport
 
@@ -161,18 +178,18 @@ The package ships a `cordis.patch.yml` (in `files: ["lib", "cordis.patch.yml", "
 
 ## Updating
 
-When the upstream hashes change, the fix is mechanical but unavoidable until DSH exposes a stable public API for layout overrides. The plugin targets six CSS-module class hashes:
+When the upstream hashes change, the fix is mechanical but unavoidable until DSH exposes a stable public API for layout overrides. The plugin targets six CSS-module class hashes (as of DSH 0.1.2-rc.1):
 
-- `.wSkVaW_root` — the conversation root (defines the chat-content-width variable)
-- `.Md3f7G_column` — the chat column (reads the variable as max-width)
-- `.uV2eYG_card` — the composer card (we cap its max-height)
-- `.uV2eYG_scroll` — the composer's inner textarea scroll (we cap its max-height)
-- `.gdEzaW_userStack` — the user-message bubble stack (we set its max-width)
-- `.FJxK0a_root` — the session-stats line (we set its text-align)
+- `.wSkVaW_root` — the conversation root (defines the chat-content-width variable) — `dsh-client-ui-conversation`
+- `.EvIC1a_column` — the chat column (reads the variable as max-width) — `dsh-client-ui-chat`
+- `.uV2eYG_card` — the composer card (no override — see "How it works" for why) — `dsh-client-ui-conversation`
+- `.uV2eYG_scroll` — the composer's inner textarea scroll (we cap its max-height; we floor it at 52px so the trigger row stays below the typing area) — `dsh-client-ui-conversation`
+- `.Sixlwa_userStack` — the user-message bubble stack (we set its max-width) — `dsh-client-ui-chat`
+- `.-NDN2W_root` — the session-stats line (we set its text-align) — `dsh-client-ui-chat`
 
-All six appear in `dsh-client-ui-conversation/lib/client.js`. A regex search for `_module_css_default\s*=\s*{` will land you near the manifests. To update:
+The hashes live in `dsh-client-ui-conversation/lib/client.js` and `dsh-client-ui-chat/lib/client.js` (in the profile's `node_modules`). Since 0.1.2 the CSS is inlined as `const css$N = "..."` strings, so search for the rule you're overriding (e.g. `chat-content-width`) and read the class hash out of the selector. To update:
 
-1. Open the new `dsh-client-ui-conversation/lib/client.js` in your editor and search for each of the six names above. If a name has changed (the part after the underscore), update the corresponding name in `src/client/css.ts`. If a name has been removed (e.g. DSH restructured the composer), comment out the matching rule and the matching slider in `src/client/WideChatRow.tsx`, and update the README's Caveats and "How it works" sections to match.
+1. Search both `client.js` files for each of the six names above. If a name has changed (the part after the underscore), update the corresponding name in `src/client/css.ts`. If a name has been removed (e.g. DSH restructured the composer), comment out the matching rule and the matching slider in `src/client/WideChatRow.tsx`, and update this README's Caveats and "How it works" sections to match.
 2. `npm run build` to rebuild the host and client bundles.
 3. Bump the version in `package.json` (the user-facing change is a patch for a single-hash fix, minor for a class-set change, major for an API change).
 

package/lib/client/index.js

@@ -337,9 +337,18 @@ const dictionaries = {
 * toggle and window resize, exactly the way the user already knows.
 *
 * Class hashes are the CSS-modules-generated ones from
-* `@deepseek-ai/dsh-client-ui-conversation` and
-* `@deepseek-ai/dsh-client-ui-layout`. They are recomputed on every
-* upstream rebuild; when they change this file is what needs updating.
+* `@deepseek-ai/dsh-client-ui-conversation` (conversation root, composer
+* card/scroll) and `@deepseek-ai/dsh-client-ui-chat` (chat column,
+* user bubble, stats line). They are recomputed on every upstream
+* rebuild; when they change this file is what needs updating.
+*
+* Current targets (DSH 0.1.2-rc.1):
+*   wSkVaW_root      conversation root (dsh-client-ui-conversation)
+*   EvIC1a_column    chat column, max-width: var(--dsh-chat-content-width)
+*   uV2eYG_card      composer card
+*   uV2eYG_scroll    composer inner scroll
+*   Sixlwa_userStack user-message bubble stack (dsh-client-ui-chat)
+*   -NDN2W_root      session stats line (dsh-client-ui-chat)
 */
 /** Validate and clamp a single field. Returns `fallback` on any deviation. */
 function clampInt(value, min, max, fallback) {
@@ -381,18 +390,21 @@ function resolveConfig(raw, defaults) {
 /**
 * Build the override stylesheet for one resolved config.
 *
-* The chat column cap is widened from the shipped 748px to
-* `100% - 2*chatGutterPct%` of the conversation root. The column
-* itself keeps the shipped `width: 100%` and `margin: 0 auto`, so it
-* still reflows on sidebar toggle and window resize, exactly the way
-* the user already knows — the only change is that the column is no
-* longer capped at 748px and now leaves a configurable gutter on each
-* side.
+* The chat column cap is pinned to `100% - 2*chatGutterPct%` of the
+* conversation root via `--dsh-chat-content-width`. DSH 0.1.2-rc.1
+* ships the variable as an adaptive clamp
+* (`clamp(680px, column*0.64, 920px)`) that its drag-to-resize handles
+* can override through `--dsh-chat-user-width` (written inline on the
+* root); our `!important` class declaration wins over that, so the
+* slider stays the source of truth. The column itself
+* (`EvIC1a_column`) keeps the shipped `width: 100%` and
+* `margin: 0 auto`, so it still reflows on sidebar toggle and window
+* resize, exactly the way the user already knows.
 *
 * The composer card inherits the same cap through
 * `--dsh-composer-card-max-width`, which the shipped composer CSS
 * already reads. The stats line aligns to the user's choice via
-* `.FJxK0a_root { text-align: ... }`.
+* `.-NDN2W_root { text-align: ... }`.
 */
 function buildStylesheet(config) {
 	const cap = `calc(100% - ${config.chatGutterPct * 2}%)`;
@@ -406,40 +418,49 @@ function buildStylesheet(config) {
   --dsh-composer-card-max-width: ${cap} !important;
 }
 
-/* User-message bubble width. The shipped cap is
- * max-width: min(525px, 82%), which keeps user bubbles narrow on wide
- * columns. We replace the cap with the configured userBubblePct of
- * the chat column, so the bubble scales with the column. The shipped
- * align-items: flex-end on .gdEzaW_userRow keeps the bubble pinned
- * to the right edge. */
-.gdEzaW_userStack {
+/* User-message bubble width. The shipped cap (DSH 0.1.2-rc.1) is
+ * max-width: min(calc(var(--dsh-chat-content-width,748px) * .702), 82%),
+ * which keeps user bubbles narrow on wide columns. We replace the cap
+ * with the configured userBubblePct of the chat column, so the bubble
+ * scales with the column. The shipped align-items: flex-end on
+ * .Sixlwa_userRow keeps the bubble pinned to the right edge. */
+.Sixlwa_userStack {
   max-width: ${ub} !important;
 }
 
-/* Composer card max height. The shipped card has no max-height, so on
- * long inputs the textarea + accessory row can grow to eat most of
- * the screen and hide the conversation above. We cap the card at the
- * configured percentage of the viewport; the inner scroll keeps the
- * textarea usable, and the user always sees the rest of the conversation.
+/* Composer card height. The shipped card has no max-height, so on long
+ * inputs the textarea + accessory row grow until they eat most of the
+ * screen and hide the conversation above. We cap the inner textarea
+ * scroll at the configured percentage of the viewport (minus the card's
+ * chrome — accessory row, trigger row, padding, gaps) so the textarea
+ * itself stops growing. The card's natural height follows the inner
+ * scroll's cap; the conversation scroll above the composer shrinks to
+ * make room.
  *
- * The shipped .uV2eYG_scroll inside the card has its own
- * max-height (--dsh-composer-text-max-height, 336px by default) that
- * silently limits the textarea. We override that too so the user's
- * outer cap actually takes effect: the inner scroll gets the card's
- * cap minus the card's chrome (padding, accessory row, border —
- * roughly 64px) so the textarea can grow with the rest of the card. */
-.uV2eYG_card {
-  max-height: ${cmh} !important;
-  overflow: hidden !important;
-}
+ * Note: we deliberately do NOT set overflow:hidden on the card.
+ * Earlier versions did, to enforce a hard cap on the card's visible
+ * box, but that clipped the popover menus (model picker, permission
+ * presets, …) which open upward from the trigger row inside the card.
+ * The menus are absolutely positioned descendants of an element inside
+ * the card, so the card's overflow clipping killed them. With the card
+ * free to overflow, the menus extend above the card into the
+ * conversation area and are fully visible. */
 .uV2eYG_scroll {
+  /* min-height mirrors the shipped hero variant's input floor
+   * (.uV2eYG_hero .uV2eYG_input { min-height: 52px }), so the typing
+   * area stays usable even when the cap falls below the natural
+   * height of its content. Without this, on a small viewport with a
+   * low cap, the scroll collapses to ~28px and the trigger row below
+   * it visually sits on top of the typing area. */
+  min-height: 52px !important;
   max-height: calc(${cmh} - 64px) !important;
 }
 .uV2eYG_hero .uV2eYG_scroll {
+  min-height: 52px !important;
   max-height: calc(${cmh} - 132px) !important;
 }
 
-.FJxK0a_root {
+.-NDN2W_root {
   text-align: ${config.statsAlign} !important;
 }
 `;

package/lib/index.d.ts

@@ -1,3 +1,31 @@
+/**
+ * Host half of `@furayoshi/dsh-widechat`. Registers a settings namespace
+ * under `dsh-widechat` whose schema the browser half binds to via
+ * `ctx.settingsScope.bind({ namespace: "dsh-widechat" })`. The browser
+ * writes here, this registration makes those writes durable, and the browser
+ * reads them back through the same scope on every settings change.
+ *
+ * Loaded by the DSH Cordis Loader on the host. The companion `cordis.patch.yml`
+ * inserts this row into the host composition so the registration actually
+ * runs; the npm install flow also needs the bundle-patch row for the same
+ * reason (`dsh.bundle.patch`).
+ *
+ * The constants, defaults, and field keys live in `./settings.ts` so the
+ * client half can import them without pulling `@deepseek-ai/schemastery`
+ * into the browser bundle (where the loader has no module table entry for
+ * it and would refuse to resolve).
+ *
+ * DSH >= 0.1.2-rc.1: the settings service (`ctx.settings`, a
+ * `SettingsProvider` from `@deepseek-ai/dsh-settings`) registers
+ * namespaces with a plain lowercase-hyphenated string:
+ *
+ *   ctx.settings.register("dsh-widechat", schema)
+ *
+ * The pre-0.1.2 `settingsNamespace()` helper export no longer exists in
+ * `@deepseek-ai/dsh-settings`; a static import of it fails the whole
+ * plugin tree at boot with
+ * `SyntaxError: ... does not provide an export named 'settingsNamespace'`.
+ */
 import z from "@deepseek-ai/schemastery";
 /**
  * Durable settings schema. The browser half binds a scope to this same
@@ -16,6 +44,12 @@ export declare const WideChatSettingsSchema: z<Schemastery.ObjectS<{
     userBubblePct: z<number, number>;
     composerMaxHeightPct: z<number, number>;
 }>>;
-/** Host plugin body. Registers the namespace with the host settings service. */
+/**
+ * Host plugin body. Registers the namespace with the host settings service.
+ *
+ * The namespace is passed as a plain string (DSH >= 0.1.2-rc.1 API). All
+ * fields are optional, so a stored section with no values resolves to an
+ * empty object and the client half applies its own bundled defaults.
+ */
 export declare function apply(ctx: any): void;
 export { WIDE_CHAT_SETTINGS_NAMESPACE, CHAT_GUTTER_PCT_FIELD, STATS_ALIGN_FIELD, STATS_ALIGN_VALUES, CHAT_GUTTER_PCT_MIN, CHAT_GUTTER_PCT_MAX, USER_BUBBLE_PCT_FIELD, USER_BUBBLE_PCT_MIN, USER_BUBBLE_PCT_MAX, COMPOSER_MAX_HEIGHT_PCT_FIELD, COMPOSER_MAX_HEIGHT_PCT_MIN, COMPOSER_MAX_HEIGHT_PCT_MAX, DEFAULTS, } from "./settings.js";

package/lib/index.js

@@ -11,11 +11,21 @@
  * reason (`dsh.bundle.patch`).
  *
  * The constants, defaults, and field keys live in `./settings.ts` so the
- * client half can import them without pulling `@deepseek-ai/dsh-settings`
- * and `@deepseek-ai/schemastery` into the browser bundle (where the loader
- * has no module table entry for them and would refuse to resolve).
+ * client half can import them without pulling `@deepseek-ai/schemastery`
+ * into the browser bundle (where the loader has no module table entry for
+ * it and would refuse to resolve).
+ *
+ * DSH >= 0.1.2-rc.1: the settings service (`ctx.settings`, a
+ * `SettingsProvider` from `@deepseek-ai/dsh-settings`) registers
+ * namespaces with a plain lowercase-hyphenated string:
+ *
+ *   ctx.settings.register("dsh-widechat", schema)
+ *
+ * The pre-0.1.2 `settingsNamespace()` helper export no longer exists in
+ * `@deepseek-ai/dsh-settings`; a static import of it fails the whole
+ * plugin tree at boot with
+ * `SyntaxError: ... does not provide an export named 'settingsNamespace'`.
  */
-import { settingsNamespace } from "@deepseek-ai/dsh-settings";
 import z from "@deepseek-ai/schemastery";
 import { CHAT_GUTTER_PCT_FIELD, CHAT_GUTTER_PCT_MAX, CHAT_GUTTER_PCT_MIN, COMPOSER_MAX_HEIGHT_PCT_FIELD, COMPOSER_MAX_HEIGHT_PCT_MAX, COMPOSER_MAX_HEIGHT_PCT_MIN, STATS_ALIGN_FIELD, STATS_ALIGN_VALUES, USER_BUBBLE_PCT_FIELD, USER_BUBBLE_PCT_MAX, USER_BUBBLE_PCT_MIN, WIDE_CHAT_SETTINGS_NAMESPACE, } from "./settings.js";
 /**
@@ -42,10 +52,16 @@ export const WideChatSettingsSchema = z.object({
         .max(COMPOSER_MAX_HEIGHT_PCT_MAX)
         .required(false),
 });
-/** Host plugin body. Registers the namespace with the host settings service. */
+/**
+ * Host plugin body. Registers the namespace with the host settings service.
+ *
+ * The namespace is passed as a plain string (DSH >= 0.1.2-rc.1 API). All
+ * fields are optional, so a stored section with no values resolves to an
+ * empty object and the client half applies its own bundled defaults.
+ */
 export function apply(ctx) {
     ctx.inject(["settings"], (settingsCtx) => {
-        settingsCtx.settings.register(settingsNamespace(WIDE_CHAT_SETTINGS_NAMESPACE), WideChatSettingsSchema);
+        settingsCtx.settings.register(WIDE_CHAT_SETTINGS_NAMESPACE, WideChatSettingsSchema);
     });
 }
 export { WIDE_CHAT_SETTINGS_NAMESPACE, CHAT_GUTTER_PCT_FIELD, STATS_ALIGN_FIELD, STATS_ALIGN_VALUES, CHAT_GUTTER_PCT_MIN, CHAT_GUTTER_PCT_MAX, USER_BUBBLE_PCT_FIELD, USER_BUBBLE_PCT_MIN, USER_BUBBLE_PCT_MAX, COMPOSER_MAX_HEIGHT_PCT_FIELD, COMPOSER_MAX_HEIGHT_PCT_MIN, COMPOSER_MAX_HEIGHT_PCT_MAX, DEFAULTS, } from "./settings.js";

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@furayoshi/dsh-widechat",
-  "version": "0.7.0",
+  "version": "0.8.0",
   "description": "DeepSeek Harness plugin: widens the conversation column, sets the user-bubble width and composer max height, and right-aligns the session stats strip, with a settings-row UI to tune all four. Built for the DSH client plugin slot `settings.general.item`.",
   "type": "module",
   "main": "lib/index.js",
@@ -46,7 +46,6 @@
     "client": {
       "platform": "web",
       "inject": [
-        "@deepseek-ai/dsh-client-runtime",
         "@deepseek-ai/dsh-client-ui-settings",
         "@deepseek-ai/dsh-client-ui-settings-general",
         "@deepseek-ai/dsh-client-locale"
@@ -61,17 +60,16 @@
   },
   "peerDependencies": {
     "@deepseek-ai/cordis": ">=4.0.1",
-    "@deepseek-ai/dsh-settings": ">=0.1.0-rc.8"
+    "@deepseek-ai/dsh-settings": ">=0.1.2-rc.1"
   },
   "dependencies": {
     "@deepseek-ai/schemastery": "^3.18.1"
   },
   "devDependencies": {
-    "@deepseek-ai/cordis": "4.0.1",
-    "@deepseek-ai/dsh-client-runtime": "0.1.0-rc.8",
+    "@deepseek-ai/cordis": "4.0.2",
     "@deepseek-ai/dsh-client-ui-primitives": "0.1.0-rc.8",
     "@deepseek-ai/dsh-client-ui-slots": "0.1.0-rc.8",
-    "@deepseek-ai/dsh-settings": "0.1.0-rc.8",
+    "@deepseek-ai/dsh-settings": "0.1.2-rc.1",
     "@types/node": "^22.15.0",
     "@types/react": "^19.2.18",
     "react": "^18.3.1",