dsh-quick-actions 0.2.0-rc.2 → 0.2.0-rc.3

package/README.en.md

@@ -28,7 +28,7 @@ This release has **no insert action** (insert at the selection, keep the editing
 | DSH UI primitives (browser side) | `>=0.1.7-alpha.2`, also supplied by the module table |
 | Platform | `web` profile only |
 
-Nothing is capability-detected at install or at runtime, so there is no feature tiering that varies with the DSH version: either the whole plugin installs and runs, or it does not.
+The send and Settings contracts have no legacy compatibility layer. **`0.2.0-rc.3`** also supports the optional `conversation.composer.footer`: a locally patched core places the bar below the statistics row, with the action group centered within the input's width; an unpatched core keeps the existing placement. Official `0.1.7-rc.2` does not include this slot, and installing the plugin alone does not add it.
 
 The floor is the DSH release whose Settings form this plugin reads. **Do not run it against anything older**: `0.1.7-alpha.1` rewrote Settings — plugins no longer register namespaces of their own, and user data became the plugin's own Config, written into the profile. This release reads and writes the new model only, and on the `0.1.5` and `0.1.6` lines its Client never starts. For those lines, install this plugin's `0.1.0`.
 
@@ -45,7 +45,7 @@ No upper bound is declared, but **that is not a promise of forward compatibility
 dsh plugin --profile web add dsh-quick-actions@next
 ```
 
-**Keep the `@next`.** DSH's own npm `latest` still points at the `0.1.5` line, so this release is published under the `next` dist-tag. Without the tag you get `0.1.0` from `latest`, which supports only the `0.1.5` and `0.1.6` lines and fails to activate on `0.1.7`. Once DSH moves `0.1.7` to `latest`, this plugin moves back to `latest` with it.
+**Keep the `@next`.** The plugin's `0.2.0` line remains a prerelease and uses the `next` dist-tag. Without the tag you get the plugin's `0.1.0` from `latest`, which supports only DSH `0.1.5` and `0.1.6` and fails to activate on `0.1.7`. DSH's own `latest` is now `0.1.7-rc.2`, but that does not automatically change this plugin's release channel. This release has not been verified against the DSH `0.2.0` prerelease line.
 
 Then restart the web profile. One package is the whole thing: it carries `dsh.bundle.patch`, which inserts its Host half into the profile, while its `dsh.client` declaration makes the web app load the browser half.
 
@@ -54,7 +54,7 @@ Then restart the web profile. One package is the whole thing: it carries `dsh.bu
 ```sh
 mkdir -p /tmp/quick-actions
 pnpm --filter dsh-quick-actions pack --pack-destination /tmp/quick-actions
-dsh plugin --profile web add /tmp/quick-actions/dsh-quick-actions-0.2.0-rc.2.tgz
+dsh plugin --profile web add /tmp/quick-actions/dsh-quick-actions-0.2.0-rc.3.tgz
 ```
 
 The `--filter` form works from anywhere in the repository; from the package directory itself, `pnpm pack --pack-destination /tmp/quick-actions` is the same thing.
@@ -134,7 +134,7 @@ Layout is a global persisted setting, switched in the management panel:
 | Value | Name | Where |
 |---|---|---|
 | `ribbon` (default) | Action ribbon | One row above the input, matching its width |
-| `bar` | Action bar | One row under the input, beside DSH's own usage info, as wide as its content and at most as wide as the input card; whatever does not fit folds into "more" |
+| `bar` | Action bar | With the footer core patch: a separate row below statistics, with controls centered within the input's width. Without it: the existing placement beside usage info. Actions that do not fit fold into "more" |
 | `launcher` | Single launcher | One entry button opening a searchable panel |
 
 `bar` and `launcher` share the same searchable panel, and the search matches labels and texts only. The management panel is where you reorder, hide, restore and clone presets, create, edit, enable and delete custom actions, and switch layout.

package/README.md

@@ -28,7 +28,7 @@
 | DSH UI primitives（浏览器侧） | `>=0.1.7-alpha.2`，同样由模块表提供 |
 | 平台 | 只支持 `web` profile |
 
-安装与运行都不检测 DSH 能力，因此不存在随版本变化的功能分档：要么整个插件能装能跑，要么装不上。
+发送与 Settings 契约不做旧版兼容。**`0.2.0-rc.3`** 另支持可选的 `conversation.composer.footer`：带本地核心补丁的 DSH 将 bar 放到统计行下方、动作组水平居中；未打补丁的核心保留原位置。该挂载点不是官方 `0.1.7-rc.2` 自带能力，也不会仅因安装插件而出现。
 
 下界取的是本插件读取其 Settings 表单的那个 DSH 版本。**不要在更低版本上使用**：`0.1.7-alpha.1` 重写了 Settings——插件不再自己注册命名空间，用户数据改为插件自己的 Config、写进 profile。本版只按新模型读写，在 `0.1.5`、`0.1.6` 线上 Client 根本不会启动。要在那两条线上用，请装本插件的 `0.1.0`。
 
@@ -45,7 +45,7 @@
 dsh plugin --profile web add dsh-quick-actions@next
 ```
 
-**`@next` 不能省。** DSH 自己的 npm `latest` 还停在 `0.1.5` 线，所以本版发在 `next` dist-tag 上；不带 tag 装到的是 `latest` 上的 `0.1.0`，它只支持 `0.1.5`、`0.1.6` 线，在 `0.1.7` 上激活失败。等 DSH 把 `0.1.7` 推上 `latest`，本插件跟着回到 `latest`。
+**`@next` 不能省。** 插件 `0.2.0` 仍处于预发布阶段，本版使用 `next` dist-tag；不带 tag 装到的是插件 `latest` 上的 `0.1.0`，它只支持 DSH `0.1.5`、`0.1.6` 线，在 `0.1.7` 上激活失败。DSH 的 `latest` 已是 `0.1.7-rc.2`，但这不会自动改变插件的发布通道。本版尚未验证 DSH `0.2.0` 预发布线。
 
 然后重启 web profile。一个包就是全部：它自带 `dsh.bundle.patch` 把自己的 Host 半边插进 profile，`dsh.client` 声明让 web 端加载浏览器半边。
 
@@ -54,7 +54,7 @@ dsh plugin --profile web add dsh-quick-actions@next
 ```sh
 mkdir -p /tmp/quick-actions
 pnpm --filter dsh-quick-actions pack --pack-destination /tmp/quick-actions
-dsh plugin --profile web add /tmp/quick-actions/dsh-quick-actions-0.2.0-rc.2.tgz
+dsh plugin --profile web add /tmp/quick-actions/dsh-quick-actions-0.2.0-rc.3.tgz
 ```
 
 上面的 `--filter` 形式在仓库任意位置都能用；如果你已经在包目录里，`pnpm pack --pack-destination /tmp/quick-actions` 即可。
@@ -134,7 +134,7 @@ pnpm 有一条供应链策略：拒绝发布时间在冷却窗口内（默认 24
 | 值 | 名称 | 位置 |
 |---|---|---|
 | `ribbon`（默认） | 上方动作带 | 输入框上方一行，与输入框等宽 |
-| `bar` | 下方操作栏 | 输入框下方一行，与 DSH 自己的用量信息并排，宽度随内容、最多与输入卡片同宽，装不下的折进「更多」 |
+| `bar` | 下方操作栏 | 带 footer 核心补丁时：统计行下方独占新行，动作组在输入框宽度内居中；未打补丁时：保留与用量信息并排的原位置。装不下的动作折进「更多」 |
 | `launcher` | 单入口面板 | 一个入口按钮，点开可搜索的动作面板 |
 
 `bar` 与 `launcher` 共用同一个可搜索面板，搜索只匹配标签和文本。管理面板里可以给预置排序、隐藏、恢复、克隆，增删改自定义动作并启停它们，以及切换布局。

package/lib/client.js

@@ -2058,7 +2058,7 @@ window.__ModuleLoader__.load({
 		* | layout     | Slot                        | body                                                        |
 		* |------------|-----------------------------|-------------------------------------------------------------|
 		* | `ribbon`   | `conversation.input.dock`   | title, the actions in shared order, and "manage" on one line |
-		* | `bar`      | `conversation.composer.dock`| the leading actions that fit, then "more", then "manage"     |
+		* | `bar`      | composer footer (dock fallback) | the leading actions that fit, then "more", then "manage" |
 		* | `launcher` | `conversation.input.dock`   | one compact entry carrying the Composer projection's count   |
 		*
 		* Three rules hold across all of them:
@@ -3273,7 +3273,7 @@ window.__ModuleLoader__.load({
 		//#endregion
 		//#region src/client/surfaces/entries.tsx
 		/**
-		* The two dock Slot entries (spec 7.3, 8.1).
+		* The dock entries and optional composer footer (spec 7.3, 8.1, 23).
 		*
 		* Both are always registered; which one renders the layout is decided at render
 		* time from the authoritative Settings snapshot, and both render nothing at all
@@ -3281,12 +3281,14 @@ window.__ModuleLoader__.load({
 		*
 		* - `conversation.composer.dock` is the residency beacon. Its mount is DSH's own
 		*   statement that this Session's composer is in its resident variant, so it
-		*   marks the Session while mounted and additionally renders the `bar` layout.
+		*   marks the Session while mounted and renders `bar` only without a footer.
+		* - `conversation.composer.footer`, when provided by the local core patch,
+		*   renders `bar` on its own row and suppresses that Session's dock fallback.
 		* - `conversation.input.dock` renders `ribbon` or `launcher`, but only while the
 		*   beacon's mark stands — that Slot also mounts on the blank-session hero, and
 		*   the first release must never appear there.
 		*
-		* A third entry rides the same input dock: the centralized management overlay,
+		* Another entry rides the same input dock: the centralized management overlay,
 		* which spec 8.1 requires to be registered independently of the layout entries.
 		* It is a separate Slot cell with its own id, order and error boundary, so a
 		* failure in the management panel cannot take a Composer layout down with it and
@@ -3387,8 +3389,9 @@ window.__ModuleLoader__.load({
 		}
 		/** Build both Slot entry components over one set of fiber-owned dependencies. */
 		function createQuickActionDockEntries(deps) {
+			const footers = createResidentComposerRegistry();
 			function Body(props) {
-				const { owns, ...slot } = props;
+				const { owns, footer, ...slot } = props;
 				const client = useControllerState(deps.controller);
 				const projection = client.projection;
 				const onRetry = (0, react.useCallback)(() => {
@@ -3400,12 +3403,16 @@ window.__ModuleLoader__.load({
 					onRetry
 				}) : null;
 				if (!owns.includes(projection.layout)) return null;
-				return /* @__PURE__ */ (0, react_jsx_runtime.jsx)(SessionSurface, {
+				const surface = /* @__PURE__ */ (0, react_jsx_runtime.jsx)(SessionSurface, {
 					...slot,
 					deps,
 					layout: projection.layout,
 					actions: projection.composer
 				});
+				return footer ? /* @__PURE__ */ (0, react_jsx_runtime.jsx)("div", {
+					className: "dsh-cqa-footer",
+					children: surface
+				}) : surface;
 			}
 			function InputDock(props) {
 				const resident = useResident(deps.residency, props.sessionId);
@@ -3419,15 +3426,29 @@ window.__ModuleLoader__.load({
 			}
 			function ComposerDock(props) {
 				const { sessionId } = props;
+				const hasFooter = useResident(footers, sessionId);
 				(0, react.useLayoutEffect)(() => deps.residency.mark(sessionId), [sessionId]);
 				return /* @__PURE__ */ (0, react_jsx_runtime.jsx)(SurfaceErrorBoundary, {
 					t: props.t,
-					children: /* @__PURE__ */ (0, react_jsx_runtime.jsx)(Body, {
+					children: hasFooter ? null : /* @__PURE__ */ (0, react_jsx_runtime.jsx)(Body, {
 						...props,
 						owns: COMPOSER_DOCK_LAYOUTS
 					})
 				});
 			}
+			function FooterDock(props) {
+				const { sessionId } = props;
+				const ready = useResident(footers, sessionId);
+				(0, react.useLayoutEffect)(() => footers.mark(sessionId), [sessionId]);
+				return /* @__PURE__ */ (0, react_jsx_runtime.jsx)(SurfaceErrorBoundary, {
+					t: props.t,
+					children: ready ? /* @__PURE__ */ (0, react_jsx_runtime.jsx)(Body, {
+						...props,
+						owns: COMPOSER_DOCK_LAYOUTS,
+						footer: true
+					}) : null
+				});
+			}
 			/**
 			* The centralized management overlay (spec 8.1, 8.3).
 			*
@@ -3450,6 +3471,7 @@ window.__ModuleLoader__.load({
 			return {
 				InputDock,
 				ComposerDock,
+				FooterDock,
 				ManagerDock
 			};
 		}
@@ -3481,7 +3503,11 @@ window.__ModuleLoader__.load({
 		* — the same cap the composer card uses — and is centred, so its left and right
 		* edges coincide with the input box exactly rather than approximately.
 		*
-		* `.dsh-cqa-bar` makes no such claim. Since DSH 0.1.6-alpha.2 the composer dock is
+		* In the optional composer footer, the core owns card alignment and the bar
+		* fills that row; its control group is centred (spec 23.1). The rules below
+		* still apply to the fallback for unpatched cores.
+		*
+		* `.dsh-cqa-bar` in that fallback makes no such claim. Since DSH 0.1.6-alpha.2 the composer dock is
 		* a row under the card that DSH centres and sizes to its content, shared with
 		* DSH's own stats pills and context meter, so the bar is a content-sized member of
 		* that row (spec 22.9). It only has to stay inside it: `min-width: 0` lets it
@@ -3510,6 +3536,24 @@ window.__ModuleLoader__.load({
   width: var(--dsh-composer-card-max-width);
 }
 
+/* The optional footer is already aligned to the card by its core owner.
+   Only this plugin's row shrinks and centres the whole control group. */
+.dsh-cqa-footer {
+  width: 100%;
+  min-width: 0;
+}
+.dsh-cqa-footer > .dsh-cqa-bar {
+  width: 100%;
+}
+.dsh-cqa-footer .dsh-cqa-row {
+  width: fit-content;
+  max-width: 100%;
+  margin-inline: auto;
+}
+.dsh-cqa-footer [data-quick-actions-overflow] .dsh-cqa-row {
+  width: 100%;
+}
+
 .dsh-cqa-row {
   display: flex;
   align-items: center;
@@ -4016,7 +4060,7 @@ window.__ModuleLoader__.load({
 			}, "composer-quick-actions: client controller");
 			ctx.effect(() => ctx.locale.register(QUICK_ACTIONS_LOCALE_NAMESPACE, quickActionsDictionaries), "composer-quick-actions: dictionaries");
 			ctx.effect(installQuickActionStyles, "composer-quick-actions: surface styles");
-			const { InputDock, ComposerDock, ManagerDock } = createQuickActionDockEntries({
+			const { InputDock, ComposerDock, FooterDock, ManagerDock } = createQuickActionDockEntries({
 				controller,
 				sessions,
 				residency,
@@ -4039,6 +4083,12 @@ window.__ModuleLoader__.load({
 				order: DOCK_ORDER,
 				locale: QUICK_ACTIONS_LOCALE_NAMESPACE
 			}, ComposerDock));
+			ctx.slots.inject("conversation.composer.footer", () => ctx.slots.register({
+				name: "conversation.composer.footer",
+				id: "composer-quick-actions",
+				order: DOCK_ORDER,
+				locale: QUICK_ACTIONS_LOCALE_NAMESPACE
+			}, FooterDock));
 		}
 		//#endregion
 		exports.apply = apply;