dsh-global-todo 0.7.0 → 0.7.1

package/CHANGELOG.md

@@ -1,3 +1,14 @@
+## [0.7.1] — 2026-10-20
+
+Documentation for the one piece of layout that cannot be "cleaned up".
+
+- **`docs/DESIGN.md` now records why the wide-screen detail card is `position: fixed`**, with the
+  measurements from the failed attempts (an absolute card came out 348×3051 at 1440; container
+  queries make the panel the containing block for fixed descendants), the real cause (the panel
+  scrolls with the host page, not `.gt-groups`), and the rules for changing it safely.
+- `/api/global-todo/review` added to both README route tables (it shipped in 0.7.0 without its
+  row).
+
 ## [0.7.0] — 2026-10-20
 
 An agent's "done" becomes a claim a person confirms, instead of a fact.

package/README.md

@@ -268,6 +268,7 @@ fence when that service is present, and by a strict loopback check otherwise.
 | POST | `/api/global-todo/status` | `{ id, status, by?: human\|agent }` |
 | POST | `/api/global-todo/remove` | `{ id }` |
 | POST | `/api/global-todo/restore` | `{ todo }` — put a removed record back verbatim (undo) |
+| POST | `/api/global-todo/review` | `{ id, decision: confirm\|reject }` — answer an agent's completion |
 | POST | `/api/global-todo/link` | `{ id, add?: [...], remove?: [value \| index] }` |
 | POST | `/api/global-todo/dispatch` | `{ id, mode?: auto\|bound\|new\|current, sessionId?, dir? }` |
 | POST | `/api/global-todo/assign` | `{ ids, items?, target?, dir? }` — hand several todos over in one call; an id that matches nothing comes back instead of being sent elsewhere |

package/README.zh.md

@@ -164,6 +164,7 @@ dsh plugin --profile web remove dsh-global-todo
 | POST | `/api/global-todo/status` | `{ id, status, by?: human\|agent }` |
 | POST | `/api/global-todo/remove` | `{ id }` |
 | POST | `/api/global-todo/restore` | `{ todo }` —— 原样还原被删除的记录（撤销） |
+| POST | `/api/global-todo/review` | `{ id, decision: confirm\|reject }` —— 回答 Agent 的完成声明 |
 | POST | `/api/global-todo/link` | `{ id, add?: [...], remove?: [值 或 下标] }` |
 | POST | `/api/global-todo/dispatch` | `{ id, mode?: auto\|bound\|new\|current, sessionId?, dir? }` |
 | POST | `/api/global-todo/assign` | `{ ids, items?, target?, dir? }`——一次把多条交给 Agent；配不上的 id 原样报回，不擅自送到别处 |

package/docs/DESIGN.md

@@ -60,15 +60,51 @@ $DSH_HOME/global-todo/todos.json     ← { version: 1, todos: [ … ] }
 ## On a wide window, the detail stands beside the list
 
 Expanding a row inline is right on a narrow window and wrong on a wide one: the list jumps, the
-row you were reading slides away, and the rest of the screen sits empty. Above 1100px the open
-row's detail is lifted out of the flow into a card bracketed between the toolbar and the footer
-at the panel's right edge; only the list gives way (the toolbar keeps full width), and the list gets
-padding equal to that card. The card's offsets are measured from the panel's own column on mount
-and on resize — the slot does not always fill the window, so a viewport-derived offset put the card
-over the list inside the real GUI. This is a CSS-only override over unchanged markup
-(`.gt-root[data-wide-detail]` plus one media query) precisely so there is still exactly one
-detail implementation — a second render path for wide screens would drift from the inline one at
-the first field change.
+row you were reading slides away, and the rest of the screen sits empty. When the panel itself is
+at least 960px wide, the open row's detail is lifted out of the flow into a card at the panel's
+right edge; only the list gives way (the header and toolbar keep full width), and the list gets
+360px of right padding equal to the card. The breakpoint follows the **panel's** measured width,
+not the viewport: the slot is ~265px narrower than the window, so a viewport query opened the
+two-column layout while the panel still had no room for it. This is a CSS-only override over
+unchanged markup (`.gt-root[data-wide]` / `[data-wide-detail]`) precisely so there is still
+exactly one detail implementation — a second render path for wide screens would drift from the
+inline one at the first field change.
+
+### Why the card is `position: fixed` and not `sticky`
+
+Three ways to do this were tried; only one survives the host's layout.
+
+1. **`position: sticky`** — the card is a child of the row, so sticky is bounded by the row's
+   box: it never leaves the 72–94px tall item. Moving the card out of the row would mean a second
+   detail render path.
+2. **`position: absolute` inside a positioned wrapper around the list** — measured on
+   2026-10-20: at 1440 the card came out **348 × 3051px**, at 1280 **348 × 3203px**. The card
+   stretched to the full height of the list's *content* and scrolled away with the page. Reason:
+   **the scrolling ancestor of this panel is the host page, not `.gt-groups`** — the panel is a
+   column in someone else's scroller, so `.gt-groups` never scrolls and an absolutely positioned
+   box is bracketed by the whole content column instead of the visible area.
+3. **`container-type: inline-size` + container queries** — wanted, because the breakpoint would
+   then be CSS. But inline-size containment applies `contain: layout`, which makes the panel the
+   containing block for `position: fixed` descendants. The card (and the settings popover) would
+   silently switch from viewport-anchored to panel-anchored and land in the wrong place.
+
+So: **`position: fixed` plus one measurement of the panel and list boxes**, taken when a row
+opens and again on resize (and on a `ResizeObserver` of the column, because collapsing the host
+sidebar changes the panel's width without a window resize). The measured values land in
+`--gt-detail-top/right/bottom`; the CSS fallbacks assume the centred 1040px column, which is what
+the static previews render.
+
+### Changing this safely
+
+- Keep **one** detail implementation: if a change needs different markup for wide screens, it is
+  the wrong change.
+- Keep the breakpoint on the **panel** width (960px). A viewport media query was already shipped
+  once and put a 360px card over a 416px list at 1100.
+- Never let the card cover the list: it is `.gt-groups` padding that reserves the room, and the
+  two numbers (360 padding / 348 card + 12 gap) have to move together.
+- Verify in the real GUI, not the preview, at **1440 / 1280 / 1100**: the card must be ≈348px wide,
+  the list must end before it, and the open row must stay visible next to it. The preview cannot
+  catch this class of bug — it is server-rendered, so no measurement effect ever runs there.
 ## A shared file changes without asking
 
 The list is deliberately portable — a notes repo, a synced folder, a NAS — so another machine

package/lib/index.js

@@ -36,7 +36,7 @@ import { createStore, resolveStorePath } from './store.js'
 import { createTools } from './tools.js'
 
 /** Must equal `package.json`'s version; `npm run check` enforces that. */
-export const VERSION = '0.7.0'
+export const VERSION = '0.7.1'
 
 /** Plugin id. Also the Loader row id in `cordis.patch.yml`. */
 export const name = 'dsh-global-todo'

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "dsh-global-todo",
-  "version": "0.7.0",
+  "version": "0.7.1",
   "icon": "./docs/icon.svg",
   "description": "Global, cross-session todos for DeepSeek Harness: one list owned by the human and the agent together, with creation time, attached documents and links, and one-click hand-off to an agent session. 全局待办：跨会话一份清单，记录加入时间，可挂文档与地址，可一键交给 Agent 继续干。",
   "type": "module",