@zephinel/dsh-power-suite 0.0.0-stage → 0.1.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (95) hide show
  1. package/CHANGELOG.md +824 -0
  2. package/LICENSE +21 -0
  3. package/NOTICE +16 -0
  4. package/PRODUCT.md +50 -0
  5. package/README.md +231 -2
  6. package/assets/readme-annotation.webp +0 -0
  7. package/assets/readme-artifacts.webp +0 -0
  8. package/assets/readme-composer-gallery.webp +0 -0
  9. package/assets/readme-composer.webp +0 -0
  10. package/assets/readme-overview.webp +0 -0
  11. package/cordis.patch.yml +7 -0
  12. package/docs/README.md +46 -0
  13. package/docs/architecture.md +869 -0
  14. package/docs/assets/annotation-collection.png +0 -0
  15. package/docs/assets/annotation-idle.png +0 -0
  16. package/docs/assets/annotation-inserted.png +0 -0
  17. package/docs/assets/annotation-mode.png +0 -0
  18. package/docs/assets/annotation-selection.png +0 -0
  19. package/docs/assets/artifacts-filter-menu.png +0 -0
  20. package/docs/assets/artifacts-guide.png +0 -0
  21. package/docs/assets/artifacts-panel.png +0 -0
  22. package/docs/assets/artifacts-quicklook.png +0 -0
  23. package/docs/assets/card-acknowledged.png +0 -0
  24. package/docs/assets/card-activity-before.png +0 -0
  25. package/docs/assets/card-activity-ledger.png +0 -0
  26. package/docs/assets/card-child-actions.png +0 -0
  27. package/docs/assets/card-current-glow-dark.png +0 -0
  28. package/docs/assets/card-current-glow-reduced.png +0 -0
  29. package/docs/assets/card-current-glow.png +0 -0
  30. package/docs/assets/card-fullrow-hover.png +0 -0
  31. package/docs/assets/card-interrupted-rest-hover.png +0 -0
  32. package/docs/assets/card-interrupted.png +0 -0
  33. package/docs/assets/card-row-actions.png +0 -0
  34. package/docs/assets/card-shared-ack.png +0 -0
  35. package/docs/assets/card-unread-dot.png +0 -0
  36. package/docs/assets/dynamic-workspaces-hover.png +0 -0
  37. package/docs/assets/dynamic-workspaces.png +0 -0
  38. package/docs/assets/icon-preview.png +0 -0
  39. package/docs/assets/pending-flags.png +0 -0
  40. package/docs/assets/prompt-history-preview.png +0 -0
  41. package/docs/assets/prompt-history-search.png +0 -0
  42. package/docs/assets/settings-page.png +0 -0
  43. package/docs/assets/sidebar-interrupted-current-hover.png +0 -0
  44. package/docs/assets/sidebar-interrupted-hover.png +0 -0
  45. package/docs/demo/implicit-continue-after.png +0 -0
  46. package/docs/demo/implicit-continue-before.png +0 -0
  47. package/docs/demo/implicit-continue.html +230 -0
  48. package/docs/development.md +235 -0
  49. package/docs/draft-attachments.md +116 -0
  50. package/docs/dynamic-workspaces.md +1431 -0
  51. package/docs/icon-brief.md +72 -0
  52. package/docs/interrupted-sessions.md +252 -0
  53. package/docs/limitations.md +718 -0
  54. package/docs/overview.md +68 -0
  55. package/docs/prompt-history.md +194 -0
  56. package/docs/reference-libraries.md +79 -0
  57. package/docs/session-artifacts.md +363 -0
  58. package/docs/settings.md +109 -0
  59. package/docs/sidebar-width.md +296 -0
  60. package/docs/ui-annotation.md +3052 -0
  61. package/docs/update-check.md +225 -0
  62. package/docs/usage.md +268 -0
  63. package/docs/verification.md +3033 -0
  64. package/docs/workspace-default-presets.md +86 -0
  65. package/icon.png +0 -0
  66. package/locale/en.json +6 -0
  67. package/locale/zh.json +6 -0
  68. package/package.json +82 -4
  69. package/release-notes/0.1.0.en.md +12 -0
  70. package/release-notes/0.1.0.md +12 -0
  71. package/release-notes/README.md +53 -0
  72. package/src/client.js +24756 -0
  73. package/src/features/interrupted-sessions/host.js +486 -0
  74. package/src/features/interrupted-sessions/turns.js +187 -0
  75. package/src/features/prompt-history/history.js +68 -0
  76. package/src/features/prompt-history/host.js +61 -0
  77. package/src/features/read-acks/host.js +132 -0
  78. package/src/features/read-acks/store.js +245 -0
  79. package/src/features/session-activity/host.js +397 -0
  80. package/src/features/session-activity/store.js +343 -0
  81. package/src/features/session-artifacts/artifact-index.js +494 -0
  82. package/src/features/session-artifacts/host.js +544 -0
  83. package/src/features/session-pins/host.js +106 -0
  84. package/src/features/session-pins/store.js +275 -0
  85. package/src/features/settings/host.js +80 -0
  86. package/src/features/settings/store.js +239 -0
  87. package/src/features/sidebar-width/host.js +135 -0
  88. package/src/features/sidebar-width/store.js +202 -0
  89. package/src/features/update-check/checker.js +219 -0
  90. package/src/features/update-check/host.js +30 -0
  91. package/src/features/update-check/release-notes.js +97 -0
  92. package/src/features/update-check/version.js +63 -0
  93. package/src/features/workspace-presets/host.js +204 -0
  94. package/src/features/workspace-presets/store.js +188 -0
  95. package/src/index.js +57 -0
package/CHANGELOG.md ADDED
@@ -0,0 +1,824 @@
1
+ # Changelog
2
+
3
+ All notable changes to this repository are documented here. The format follows
4
+ [Keep a Changelog](https://keepachangelog.com/en/1.1.0/) and the project uses
5
+ [Semantic Versioning](https://semver.org/).
6
+
7
+ ## [Unreleased]
8
+
9
+ ## [0.1.0] - 2026-11-17
10
+
11
+ First public release. This package had no previous release: the earlier
12
+ development snapshots — `0.1.0` (2026-11-09), `0.1.1` (2026-11-11), and an
13
+ undated `0.2.0` — were internal only, never tagged and never released, and the
14
+ `0.1.0-rc.0` bootstrap prerelease is not a release. Their history is
15
+ consolidated into this first release together with the current work.
16
+
17
+ ### Added
18
+
19
+ - **Dynamic Workspaces** — the native Workspaces browser is augmented, never
20
+ replaced: it gains **Active Projects** and **Inactive Projects** buckets that
21
+ follow running and recently active Sessions, reorder live in both directions,
22
+ fold independently with persisted state, and hide in rail mode. The plugin
23
+ inserts sibling nodes and inline flex order only, so native search, context
24
+ menus, the add-workspace flow, drag reordering, chevron folds, dialogs,
25
+ Session rows, the New Session button, and modified clicks keep working, and
26
+ unloading restores the surface. A Workspace is Active while one of its
27
+ Sessions is running or was active inside the configurable Active-project
28
+ retention window. Above the native header a **Running & recent** card lists
29
+ running Sessions with the shell's own status dot and observed durations, keeps
30
+ recently finished Sessions for the same window, nests recent direct subagent
31
+ Sessions under their parent behind a disclosure chevron (indented under a
32
+ guide line, each opening its own Session), and opens a Session from any row.
33
+ Both windows are Host-wide settings — finished Sessions 1/2/6/12/24 hours
34
+ (default 2) and Active projects 1/3/7/14/30 days (default 7) — edited on the
35
+ bundle's Plugins page; version-1 settings files migrate to the default
36
+ windows, and running Sessions ignore both windows. Workspace default agent
37
+ presets remain reachable from the Workspace context menu.
38
+ - **Running & recent native figures** — for the hovered Session (parent or
39
+ nested subagent row) the hover card appends **Session statistics**
40
+ (`{turns} turns {steps} steps`, LLM time, tool time, average TTFT, TPS in the
41
+ native duration/speed recipes), **Token usage** (exact grouped total = billed
42
+ input + output, honest cache-hit percentage that never rounds a partial hit to
43
+ 100, uncached/cached/cache-write/output exact counts), and **Context usage**
44
+ (`{percent} of context used`, `~used / window`, and `~`-prefixed System
45
+ prompt / Tool definitions / Messages composition rows). Values come from the
46
+ existing `sessions` inject's `projectionsBySession` — live Sessions are
47
+ push-seeded and need no request; a cold (persisted) Session gets exactly one
48
+ deduplicated `refreshProjections` read on first hover, and the card fills the
49
+ figures in as they land with no loading state. Each section is omitted
50
+ entirely when its data is absent, so an empty Session keeps the plain card.
51
+ The card grows to 320 px and clamps at `min(560px, 100vh - 16px)`; subagent
52
+ cards gain a compact Session-title line. While a **live** Session's card
53
+ stays open the figures keep refreshing in place from the pushed projection
54
+ frames (the panel's 1 s clock re-reads the live snapshot; no extra polling or
55
+ network). The **native sidebar session hover card** renders the same Session
56
+ statistics, Token usage, and context sections through the shell's
57
+ `sidebar.session.row.hover` slot, reusing the same strings, formatter
58
+ recipes, live projections, and one-shot cold projection read, and contributing
59
+ no nodes for a Session without figures (the native card is not restyled,
60
+ widened, or reordered). The running-card hover status dot is a **perfect
61
+ circle** (`corner-shape: round`, because the shell's global
62
+ `superellipse(1.5)` painted the dot as a squircle).
63
+ - **Running & recent pinning** — main Session rows in the card carry a
64
+ hover-revealed **Pin** control that keeps that main Session on top of
65
+ **Running & recent** past the finished-retention window. The slot collapses
66
+ when the button is hidden (the title sits next to the leading glyph); hover or
67
+ keyboard focus expands the slot before the button fades in, and leaving fades
68
+ the button out before the slot collapses (220 ms expand/collapse, 160 ms
69
+ fades; pinned rows keep the marker and its space permanently). The pin is the
70
+ card's **own** state, deliberately independent of the native sidebar's
71
+ project-organisation pin (never read, written, or surfaced here), and it is
72
+ **Host-shared for cross-device use**: a new authenticated
73
+ `GET|POST /api/power-suite.session-pins` route persists a bounded document
74
+ (`$DSH_HOME/dsh-power-suite/session-pins.json`, `{version, rev, pinned}`, max
75
+ 500 ids with the oldest dropped first, atomic writes, last write wins, `rev`
76
+ bumping only on a real change) that every browser and device using the same
77
+ `$DSH_HOME` converges on. The client keeps a versioned `localStorage` cache
78
+ (`{version, rev, pinned, pending, migrated}`) with a queued-operation replay
79
+ for instant first paint, optimistic toggles and offline/local-only use, GETs
80
+ the Host document on mount/focus/visibility/every 30 s, merges cached pins
81
+ into the Host on first contact (so pre-route pins are not lost) and POSTs
82
+ queued pin/unpin operations; when the route is absent the card runs local-only
83
+ until the Host is restarted with the route, with no UI breakage. Pinned main
84
+ Sessions sort first, newest activity first, and never retire with time: a
85
+ pinned finished Session stays listed with its original
86
+ title/Workspace/path and last-activity time (no re-timing), unpin immediately
87
+ returns the row to the ordinary queue under the normal retention rules, and
88
+ pinned rows show a filled violet pin glyph plus a subtle violet tint (a single
89
+ highlight layer — the body pill inside the row no longer paints a second
90
+ tint); subagent child rows keep no pin control, and blank, archived, or
91
+ unknown Session ids cannot be pinned.
92
+ - **Running & recent row menu** — top-level card rows expose the shell's
93
+ Session actions behind a "…" trigger in the 48 px time slot: every top-level
94
+ row (the current rainbow row included) keeps its time at rest, and row
95
+ hover/keyboard focus hides the time and shows the trigger — the swap stays
96
+ while the menu is open and leaving restores the time. The trigger keeps the
97
+ ordinary soft hover paint (plus the keyboard `focus-visible` ring); only the
98
+ rainbow row suppresses it, with the same `brightness(1.2)` lift as the other
99
+ current-row controls. The popup is the shell's **native shared context-menu
100
+ popup** — the same surface the native Session row's own "…" trigger opens —
101
+ opened against a plugin-owned captured-target kind and filled by delegating to
102
+ the native Session action contributions
103
+ (`ctx.contextMenus.resolve({ kind: 'session', value: { sessionId, displayTitle } })`),
104
+ so Rename, Fork, Copy Session ID, Show in Finder, Archive and any
105
+ plugin-contributed action keep their native behavior and rendering, including
106
+ native labels, keyed icons, shortcut hints, separators and the Archive footer.
107
+ The **Pin/Unpin entry is the only one filtered out** (the title-left pin
108
+ button is the only pin owner), and keyboard navigation, focus restoration and
109
+ dismissal come from the shell. Subagent rows have no trigger.
110
+ - **Running & recent pending-interaction flags** — when a Session other than
111
+ the one open in the main view is waiting on `ask_user_question` (question or
112
+ plan review) or an approval (`SessionStatus.pendingInteraction`), its row
113
+ shows a small amber Remix `flag-fill` in its fixed leading cell — the card
114
+ replaces the 16 px state-glyph cell, the native Workspaces row puts the flag
115
+ in its fixed leading slot (title x unchanged; a before-`_title` insert is only
116
+ the no-slot fallback). It is the same amber as the native question prompt, is
117
+ decorative (clicking still opens the Session and the native composer card
118
+ answers), flags every waiting Session (no cap), and disappears
119
+ automatically when the Session becomes current, the interaction settles, or
120
+ the Session is archived. Client-only: no Host route, store, popup or extra
121
+ click target.
122
+ - **Prompt history** — the configured modifier + ↑/↓ recalls prompts already
123
+ sent in this Session; plain arrows keep their original behavior. A vertical
124
+ rail inside the native turn-rail frame, below its marks and separated by a
125
+ short divider, lists the current Session's sent prompts as
126
+ **native-style tick marks** in reading order — the oldest prompt is the top
127
+ tick and the newest sits at the bottom, and the rail keeps the newest tick in
128
+ view when the list loads or grows. Hover or keyboard focus shows the full
129
+ prompt in a native-style card to the left, click copies it silently into the
130
+ composer draft, and a pinned search button below the marks reveals a floating
131
+ substring filter (the search card opens directly below the magnifier or flips
132
+ to its left when there is no room above the composer; it dismisses on a blank
133
+ outside click or Escape). The native TurnNavigator renders nothing for fewer
134
+ than two turn items, so a one-turn Session keeps the ⌘↑/⌘↓ recall but has no
135
+ rail; otherwise the rail reuses the native frame's column, sticky band and
136
+ narrow hiding. A long history caps at the native band/space below the frame
137
+ (and at most 420 px), clips its chrome so it cannot paint over the composer,
138
+ scrolls its ticks behind 24 px fade masks with hidden scrollbars, and keeps
139
+ the search button pinned at the foot. The route
140
+ returns `{ seq, text, at }` for every prompt, where `at` is the Session event
141
+ time in epoch milliseconds or `null` when the event has no usable time; the
142
+ rail and hover card show the times, and a Host that predates the field has
143
+ them hidden instead of rendered empty. The rail appears only while the
144
+ Session has sent prompts, and requests are generation-scoped so a slow
145
+ Session cannot write into another Session.
146
+ - **Session artifacts** — an **Artifacts** card in the right Sidebar's Start
147
+ page lists the current Session's created and delivered files **and the
148
+ images/files the user attached to their prompts**. The provided rows come
149
+ from the image and file blocks of human `user/message` events (source kind
150
+ `user` only), deduped by attachment id with the newest occurrence winning and
151
+ a 1-based prompt ordinal, served by the verified
152
+ `GET|HEAD /api/session-artifacts.attachment` route with the same
153
+ no-store/nosniff/sandbox-CSP headers. Every image artifact shows a 40 px
154
+ rounded lazy thumbnail, and the panel header carries an All/Generated/
155
+ Provided source-filter dropdown with per-option counts. Rows support
156
+ in-browser open, download, **Copy content**, and LAN link copy: text-like
157
+ artifacts are fetched through their inline URL and copied verbatim; images
158
+ use a three-step chain — a real PNG clipboard item in a secure context
159
+ (HTTPS/localhost), the legacy HTML-image clipboard on insecure origins (hidden
160
+ `<img>` + `execCommand('copy')`, so rich editors paste the picture while
161
+ plain-text targets may get nothing/alt), and only then the inline image URL as
162
+ text; other binaries have no content action, and a successful copy shows the
163
+ row's check acknowledgement for 1.6 s.
164
+ - **Hover Quick Look** — a shared hover preview for Artifacts rows (generated
165
+ files plus provided images and text-like attachments) and the native
166
+ Workspace files tree: Markdown, syntax-highlighted code, images, audio/video,
167
+ PDF, and HTML, with drag-to-resize, animated file switching, safe hover
168
+ traversal, outside-click dismissal, and a remembered or user-resized size.
169
+ The card opens at a 570 x 360 default with an explicit content height and no
170
+ dependency on a finished animation, so content is visible on the first hover.
171
+ Provided images and media render through the verified attachment route,
172
+ text-like provided files are fetched read-only and clipped at 64 KiB with a
173
+ truncation note, and other provided types show the unavailable state.
174
+ - **Draft attachment memory** — browser-owned attachments in a draft (pasted
175
+ images, dropped or picked files) are remembered per Session and re-introduced
176
+ through the composer's own paste intake when the Session is shown again, so
177
+ switching away and back no longer restores the text while silently dropping
178
+ the files. The cache is page-lifetime (8 Sessions / 20 files), clears on send
179
+ and on explicit removal of every restored attachment, and never attempts
180
+ persistence; the shell persists only the draft's text and reference chips.
181
+ - **Composer image gallery** — when a composer holds two or more pasted images,
182
+ clicking a thumbnail opens a continuous client-only viewer instead of the
183
+ shell's single-image lightbox: the clicked image first, an `N / M` counter,
184
+ previous/next buttons disabled at the ends (no wrap), ←/→ keys, one mouse-wheel
185
+ gesture per image with a 260 ms momentum cooldown, and Esc/backdrop/close with
186
+ focus returned to the opening thumbnail. Removing an image while the viewer is
187
+ open clamps it to the remaining set and removing every image closes it; a
188
+ single image is left entirely to the native lightbox, and page/Markdown images
189
+ are never intercepted. The overlay uses the shell's tooltip/elevation tokens
190
+ in both themes, is instant under reduced motion, and closes on Session
191
+ composer unmount or empty attachment rail (and on plugin unload), without
192
+ adding a URL or history entry.
193
+ - **Interrupted sessions** — Sessions whose last turn did not finish are marked
194
+ in the sidebar and can be continued. Detection covers **every unfinished turn
195
+ ending**, not only Host restarts/crashes: any `turn/end` reason `error`
196
+ (quota/usage limit, request timeout, transport/network failure, rate limit,
197
+ malformed response, missing credential), `max-tokens`, `interrupted`, and
198
+ `aborted` with the `disposed` or legacy cause mark the Session as unfinished;
199
+ deliberate endings (`completed`, `blocked`, `forked`, user/parent/hook
200
+ cancellation) stay unmarked. An **amber mark** sits left of the title, and
201
+ hovering the row keeps the shell's normal hover surface (title visible) while
202
+ revealing an inline **Continue** triangle in the status cell (the native
203
+ status cell widens with `width: auto` so the title slides right instead of
204
+ being masked). Opening that Session turns the composer's send control into a
205
+ **play triangle**; continuing is **implicit** — it resumes through a non-human
206
+ context source instead of inserting a visible "Continue the interrupted
207
+ task." user prompt, the continuation row is hidden, prompt history ignores it,
208
+ and a missing Session controller leaves the badge in place. State is
209
+ Host-owned and cross-device: a Host **SSE stream**
210
+ (`GET /api/power-suite.interrupted-events`) pushes
211
+ `turn/start`/`turn/end` invalidations (`{sessionId, parentSession, event}`) to
212
+ every connected browser page, so badges/Continue/triangle state update
213
+ immediately instead of waiting for the 20 s poll; the stream has a 25 s
214
+ heartbeat, `retry: 10000`, one cleanup-safe connection per tab, no event
215
+ replay, and polling/focus/visibility/reconnect cues remain the fallback when
216
+ EventSource or the stream is unavailable.
217
+ - **UI element annotation** — a floating launcher toggles a client-only
218
+ annotation mode that makes room for a responsive right rail by shrinking the
219
+ shell frame's `padding-right` (`clamp(188px, 11.6vw, 236px)`, no CSS
220
+ transform) and falls back to an overlay rail on narrow viewports. Hover
221
+ outlines the candidate element; the picker treats **floating surfaces**
222
+ (body-level DSH hover preview cards, and this plugin's own hover card while
223
+ annotation mode pins it) as selectable targets *and* lets the Parent/Child
224
+ controls drill into their inner text blocks and controls, with a paint layer
225
+ raised above native hover cards (inline `z-index:150`, exact value/priority
226
+ restored on exit) and a 60 ms mutation-triggered hover recompute for surfaces
227
+ that appear while the pointer is stationary. A click selects the element and
228
+ opens the requirement popover: element name, locator summary, live resolution
229
+ status, ancestor level up/down, requirement textarea, and **Mark
230
+ requirement** / **Update requirement**, **Delete annotation** (5 s undo
231
+ toast), and **Quick reference** actions. Every annotation is stored as a
232
+ **v2 record** capturing a uniquely verified CSS selector, ≤3 sanitized
233
+ ancestors, surface/ephemeral flags, Session id plus Workspace cwd/label, a
234
+ query-free route, the bounds and viewport, and a text digest — never
235
+ outerHTML, input values, JS paths, XPath, or computed styles. Records persist
236
+ in browser `localStorage` (`power-suite.ui-annotation.annotations`, schema
237
+ version 2, 100-record cap with a visible refusal), survive a reload, and
238
+ re-resolve their Resolved/Matches several/No longer resolves/Content changed
239
+ statuses live. Annotated elements keep a page mark with a numbered
240
+ requirement-summary badge; hovering it opens a draggable detail card with the
241
+ requirement full text, locator, position, Session/Workspace, status,
242
+ surface/ephemeral marker, and **Copy locator** / **Relocate** / **Open in
243
+ composer** actions. References are inserted as **native composer inline
244
+ reference chips** through the shell's input-trigger seam (dynamic
245
+ `conversation` + `inputTriggers` injection; an `@` source with
246
+ current-Session candidates, no empty group): one chip for a single reference
247
+ and one grouped `UI annotations × N` chip for a batch, serialized at send time
248
+ through the existing reference/batch serializers (deleted members are skipped
249
+ with an honest removed-count line, and a missing single record invalidates the
250
+ chip so the send is blocked), with a plain-text fallback plus explanation when
251
+ the chip services are unavailable. Multi-select is a **batch group** flow:
252
+ after the selection settles a single batch popover opens with the selected
253
+ items and ONE shared Requirement; committing saves one group containing every
254
+ selected element (each keeps its locator/metadata, no per-item requirements),
255
+ and the group inserts as one `UI annotations × N` chip whose serialization is
256
+ one request (shared requirement + numbered references with honest status
257
+ lines). The persisted document is v3 (singles + groups, tolerant v2 migration,
258
+ cap counts singles + group items, visible refusal) and the right rail's
259
+ collection view is a real managed **annotation sidebar** (widened to
260
+ `clamp(320px, 24vw, 420px)`, status/settings views stay compact): an
261
+ **Annotations** header with a total badge and subtitle, **All / Singles /
262
+ Groups** filters with live counts, a unified scrollable list of single rows
263
+ and group cards (count badge, collapse/expand, shared-requirement editing,
264
+ always-visible edit/delete/insert actions), per-item metadata (Selector,
265
+ Page/Area, Session/Workspace, updated time), empty/filter-empty states, and a
266
+ footer with **Add annotation** and **Cancel Annotation** at equal widths (the
267
+ danger action confirms and clears all annotations on exit). The list is the
268
+ rail's default body on activation (the intermediate status/Collection/Settings
269
+ rows are gone; a compact **settings-line** icon in the header opens settings,
270
+ Back/Esc returns), with the selection hint in the header. The floating
271
+ launcher is hidden while the mode is active (no docked/flight copy) and only
272
+ fades/scales back in at its remembered position after a full exit
273
+ (reduced-motion instant). Leaving the mode (header X, Cancel Annotation or the
274
+ final Esc step) asks for confirmation and then clears all annotation records,
275
+ so a re-entry starts empty; a group keeps ONE ordinal shared by all of its
276
+ items (page marks show the group's number, never an incrementing sequence).
277
+ Page pointer events are consumed in the capture phase so native controls
278
+ cannot act while annotating; the configurable multi-select modifier toggles
279
+ selection or starts a marquee, and the configurable pass-through modifier
280
+ restores real native mouse and context-menu behavior without synthesizing
281
+ clicks. The annotation note fields, the prompt-history search field, and the
282
+ settings choices use the shared rainbow track focus ring instead of solid
283
+ focus borders; the launcher position, rail-collapsed state, and two modifiers
284
+ persist in browser `localStorage`, while annotation records use their own v3
285
+ document. The browser-only feature adds no Host route, service, or profile
286
+ change, cleans up every listener, layout marker, and DOM node on exit and
287
+ HMR, and ships a pure test seam plus a live-page CDP acceptance harness (seam
288
+ generation 66; see [verification.md](docs/verification.md) for the honest
289
+ per-scenario record — the known late-run headless S6/S8 stalls mean no single
290
+ all-green full-suite run is claimed).
291
+ - **UI element annotation precision** — picking is **leaf-first**
292
+ (DevTools-inspect style) on ordinary pages and inside floating surfaces:
293
+ hover and click target the deepest eligible element under the pointer
294
+ (titles, subtitles, timestamps, token counters, inline SVG icons/paths, then
295
+ rows/buttons), walking up only for the plugin's own UI, structural tags, or
296
+ zero-size nodes, and never escaping a floating surface's root. The popover's
297
+ Parent/Child controls walk the full hovered ancestor chain (Child back to the
298
+ deepest element, Parent up to the surface/page container), and the whole
299
+ surface stays selectable via its background/padding or Parent. Selection
300
+ outlines and popover anchoring use the picked live element so any leaf keeps
301
+ correct geometry; records keep honest locators/status for weak (e.g. SVG)
302
+ targets. Limits (bare text nodes resolve to their parent element, CSS
303
+ pseudo-elements aren't elements, `pointer-events:none` targets fall back to
304
+ the nearest ancestor) are documented.
305
+ - **Workspace default presets** — a Workspace context-menu submenu sets the
306
+ default agent preset for new Sessions created in that Workspace.
307
+ - **Settings** — the bundle's Plugins page carries its own configuration
308
+ section: the prompt-history modifier (⌘/Ctrl, ⌥/Alt, Ctrl, Shift, or Off) and
309
+ the two Dynamic Workspaces retention windows, under the **Prompt history** and
310
+ **Active & recent** groups. The section hides the page's auto-rendered package
311
+ README document while mounted and restores it on unmount; settings are
312
+ Host-owned (schema version 2) and shared by every browser on its next load.
313
+ - **Host-shared read acknowledgements** — a durable
314
+ `$DSH_HOME/dsh-power-suite/read-acks.json` document (schema v1, sanitized,
315
+ per-id max-merge, 1000-entry cap, atomic writes) is served by an authenticated
316
+ `GET/POST /api/power-suite.read-acks` route; every browser using the same
317
+ `$DSH_HOME` syncs the same baselines (local cache + 30 s/focus/visibility
318
+ sync, one-time migration of old local marks, 250 ms debounced push). Read
319
+ state is derived as `baseline >= activity - 1000 ms`, so a transient status
320
+ flag can no longer resurrect a stale green dot. Profiles sharing a home
321
+ **share the file with no profile isolation and no read-merge across writers**
322
+ (the design assumes one Host process plus overlapping HMR), and the old
323
+ per-browser `localStorage['dsh-power-suite.acked-sessions']` document is now
324
+ only the fast/offline cache, migrated to the Host on first use.
325
+ - **Event-sourced activity ledger** — the Host subscribes to committed
326
+ `session/event` times under an explicit `ACTIVITY_EVENT_TYPES` allowlist
327
+ covering known activity-bearing families (turns, steps, messages/attempts,
328
+ tools incl. PTC dispatch, jobs, commands, compaction, subagent state,
329
+ goal/todo, approvals and selection actions, workspace/deliverable/schedule
330
+ changes, team traffic, image/offload, feedback, inbox splice, LLM retry,
331
+ tool-workflow progress); the explicit `NON_ACTIVITY_EVENT_TYPES` metadata
332
+ (request headers/context, titles and their LLM requests, end seeds, delivery
333
+ acknowledgements, web search requests), seed variants, and unknown
334
+ future/plugin types never count. It persists
335
+ `$DSH_HOME/dsh-power-suite/session-activity.json`
336
+ (`{version:1, sessions:{id:lastActivityAt}}`, max-merge, 5000-Session cap,
337
+ debounced atomic writes) and seeds a one-time projection-cache baseline for
338
+ pre-install Sessions (never overwriting newer live events; header `createdAt`
339
+ when there is no cache document). Writes are **best-effort
340
+ read-merge-writes**: sequential external writes are preserved, but
341
+ interleaving writers can lose one side (TOCTOU; no cross-process lock).
342
+ `flush()` awaits the full serialized chain and drains during-write events;
343
+ `dispose()` stops the debounce, flushes, awaits the chain and is idempotent.
344
+ A read-only `GET /api/power-suite.session-activity` keeps the
345
+ `{sessions}` contract and serves the live ledger (no per-request document
346
+ scan, no-store) after a bounded `waitForSeeded(5000 ms)`; the client merges
347
+ activity per-id monotonically and prunes only against a non-empty catalog, so
348
+ partial/empty responses cannot drop known activity. Activity is exact only
349
+ for allowlisted events the Host observed; pre-install Sessions rely on the
350
+ baseline approximation, and the native sidebar keeps catalog times. The card
351
+ folds activity in via `max(catalog updatedAt, activity)` for retention,
352
+ ordering, relative times, bucket recency, child rows, and read-baseline
353
+ raising: a turn that ran for hours keeps its real activity time and stays in
354
+ the recent window instead of vanishing when it stops.
355
+ - **Update notice (new)** — an in-app card when a newer stable version of the
356
+ bundle is published on npm. The Host answers
357
+ `GET /api/power-suite.update?lang=<locale id>` with
358
+ `{ current, latest, updateAvailable, highlights }`, reading the npm `latest`
359
+ dist-tag and the release notes pinned to the published `v<latest>` tag;
360
+ the browser checks once per page load after a 1.5 s delay and renders a fixed
361
+ bottom-right `shell.overlay` card (never a sidebar node) with the version
362
+ line, up to six `## Highlights`, **更新**, **下次再说**, and
363
+ **查看更新内容 / 收起**. **更新** calls
364
+ `pluginNavigation.openBundle('@zephinel/dsh-power-suite')` to open the
365
+ Plugin detail page — DSH's plugin manager performs the update — and does not
366
+ write silence state; **下次再说** counts per version and after three clicks
367
+ exposes **不再提醒**, which silences only the current version; Escape or an
368
+ outside click is "later". State is browser-local
369
+ (`localStorage['power-suite.update-prompt']`, schema 1), the prompt clears
370
+ itself when the route proves there is no update, and the feature stays silent
371
+ on any failure. It becomes visible to 0.1.0 installs only after 0.2.0 is
372
+ published. See [docs/update-check.md](docs/update-check.md).
373
+ - **Sidebar width persistence and atmosphere repaint** — the native left
374
+ sidebar's dragged width is now a Host-owned preference instead of page memory:
375
+ `$DSH_HOME/dsh-power-suite/sidebar-width.json` (schema 1,
376
+ `{ version, sidebarWidth }`, integer 264–420 px or `null`) is served by
377
+ `GET/POST /api/power-suite.sidebar-width`, and the browser keeps a per-origin
378
+ `localStorage` cache (`power-suite.sidebar-width`, `pending` flag) that it
379
+ applies before first paint, debounces drag changes into a 300 ms POST, and
380
+ re-syncs on focus/visibility (plus a 30 s retry while pending). The width
381
+ survives reloads, new tabs, and a Host restart; every browser/profile on the
382
+ same `$DSH_HOME` shares one last-write-wins value; collapsing never stores `0`
383
+ and reopening re-applies the stored width instead of the native 280 px default.
384
+ The rainbow-atmosphere Canvas renderer now reports a real backing-store resize
385
+ and repaints synchronously after it (same task, before paint, independent of
386
+ reduced motion) and paints once at mount, instead of waiting for its 33 ms
387
+ animation throttle, so dragging the sidebar no longer blanks or strobes the
388
+ current-Session highlight. See [docs/sidebar-width.md](docs/sidebar-width.md).
389
+
390
+ ### Changed
391
+
392
+ - **Release gates now match the intelligent-ui repository: owner-approved notes and a package-level release check.** `node scripts/release-notes-approval.mjs` hashes the version plus `release-notes/<version>{,.en}.md` and verifies a `Release-Notes-Review: sha256=<hash>` line in the release commit body; `publish.yml` recomputes the hash from the tagged commit and refuses a missing, duplicated or mismatched approval, so an unapproved notes edit can no longer publish. `npm run check:release` (`scripts/release-check.mjs`) packs the artifact, installs it into a throwaway `$DSH_HOME`, and verifies every packed file's byte identity against the checkout and the installed copy, the mounted `power-suite` Loader row, the boot graph and served client bundle, then clean uninstall (requires `dsh` + `pnpm`; intentionally not in CI). Final gate: `npm run check` passed (24 modules, 22 test files, **364/364** tests, docs links 26 files, release-notes 0.1.0 6+6), pack **95 files**, `npm run check:release` **PASS** (95 files), and the approval round-trip is covered by `test/release-notes-approval.test.js`.
393
+
394
+ - **Running & recent row-menu affordance** — the 48 px time column is now also
395
+ the row-actions slot for **every top-level row**: at rest the row keeps its
396
+ time, and hover/focus hides the time and shows the "…" trigger; the swap
397
+ stays while the menu is open (`data-menu-open`) and leaving restores the
398
+ time. The trigger keeps the ordinary soft hover paint (plus the keyboard focus
399
+ ring); only the rainbow row suppresses it (transparent background + the same
400
+ `brightness(1.2)` icon lift as the other current-row controls). Subagent rows
401
+ keep the time slot and have no trigger. The trigger opens a card-owned popup
402
+ rendering the native Session action contributions (native labels plus local
403
+ action glyphs) without the Pin/Unpin
404
+ entry, while the restored title-left pin button remains the pin owner.
405
+ - **Running & recent row layout** — rows and the header share one fixed trailing
406
+ grid: title (right-edge gradient fade while clipped) → **time 48 px**
407
+ (right-aligned, tabular numerals) → **New session action 22 px**
408
+ (hover/focus-revealed) → **disclosure chevron 24 px**, so parent and nested
409
+ subagent rows right-align their times on one column and no title can push the
410
+ controls; a flexible spacer between the content-paced title control and the
411
+ trailing grid keeps that grid right-anchored at every card/sidebar width.
412
+ Every row (main and nested child, ordinary and current) is 34 px tall — the
413
+ measured height of the native Workspace project rows — and gets a clear
414
+ vertical gap (5 px between items, 4 px parent→first child, 5 px
415
+ child↔child) so the current-row atmosphere never touches its neighbours while
416
+ the 1 px subagent trunk and its last-child end mask stay coherent. The title's
417
+ first character is centred on the child status-dot column through a measured
418
+ per-row offset (first-glyph advance width + a 2 px right bias), so the tree
419
+ line, pin column, child dots and first character share one centre line; every
420
+ main row's leading glyph sits in a fixed 16 px cell (14 px state dots centred,
421
+ the read-row sparkle enlarged to 16 px), the child-tree trunk is centred under
422
+ that cell, and the pin control is centred on the child status-dot column with
423
+ equal 9 px gaps on both sides.
424
+ - **Running & recent row actions** — rows gained a fixed trailing cluster with
425
+ **New session** (a blank Session in the row's own directory, falling back to
426
+ the Workspace New Session) and, for interrupted rows, an amber warning badge
427
+ plus a **Continue** action that reuses the interrupted-session continuation
428
+ flow. Slots are reserved and revealed on hover/keyboard focus without layout
429
+ shift, and the row's hover card anchors to the activity panel's right edge so
430
+ it never covers the row or its buttons.
431
+ - **Current-Session rainbow atmosphere** — the animated conic rainbow ring that
432
+ marked the open Session is replaced by a vivid animated rainbow
433
+ **atmosphere painted inside the row's own rounded-rectangle highlight**, with
434
+ the row's real content layered above it under a faint contrast scrim. The
435
+ renderer uses source-over saturated blobs (vibrance 1.72, intensity .64,
436
+ `saturate(1.5)` plus per-theme multiply/screen blending and a lightened
437
+ scrim) so the pill reads as saturated rainbow gas rather than a grey wash
438
+ (measured blob-core saturation ~0.40–0.43, static ~0.30–0.34 under reduced
439
+ motion). It applies to the current Session's card row (parent and nested
440
+ child rows), the owning native Workspace row, and the native sidebar Session
441
+ row of the open Session (`data-psd-current-session`), is clipped to each
442
+ row's own radius, is `pointer-events: none`, changes no column/geometry,
443
+ animates only the highlighted rows, and draws a static rainbow fill under
444
+ `prefers-reduced-motion`. Opening a Session from the card, the sidebar, or
445
+ anywhere else moves the highlight with the
446
+ Activity/Workspace/Session association. Atmosphere rows no longer receive the
447
+ ordinary row-body hover pill or the native sidebar row's own hover/selected
448
+ background (the extra rounded highlight read as a misaligned second
449
+ highlight): the affordance is a brightness lift on the row's own text/icons
450
+ (`filter: brightness(1.15)`, `1.5` on keyboard hover/focus, 140 ms, disabled
451
+ under reduced motion), with the same rule for trailing controls (New session,
452
+ disclosure, pin, Continue, native sidebar actions) and keyboard focus rings
453
+ unchanged.
454
+ - **Running & recent identity glyphs** — the panel header's all-complete
455
+ indicator paints the DeepSeek brand glyph (`deepseek-fill`) and an
456
+ acknowledged finished parent row paints the sparkling-line glyph; sizes,
457
+ scales, colours, glyph columns, the running pulse dot, the unread green dot,
458
+ and the nested subagent robot glyph are unchanged, as is all state logic. The
459
+ card header's leading indicator has the blue pulsing business-primary dot
460
+ while any listed Session is running and the white sparkling-line icon when
461
+ everything is complete, both centred on the row glyph column.
462
+ - **Running & recent row hover card** — the card now matches the live native
463
+ sidebar session hover-card oracle (left edge flush with the sidebar's right
464
+ edge, top aligned to the row, borderless, 16 px radius, 12×16 padding and
465
+ native title/secondary type), grows to 320 px for the figure rows, and clamps
466
+ to `min(560px, 100vh - 16px)`. **All plugin tooltip-like floating cards**
467
+ (the row card, Artifact Quick Look, prompt-history preview/search cards, and
468
+ the annotation requirement popover/detail card/expanded note editor) paint
469
+ the native hover-card surface — a fixed `#2C2C2E` (`--dsw-hovercard-bg`) in
470
+ both light and dark themes rather than the theme-flipping tooltip token, with
471
+ no border and the shell's native panel elevation. The panel's plugin chrome
472
+ inherits the shell font family/size/weight and shows title-case **Active
473
+ Projects** / **Inactive Projects** bucket labels instead of uppercase.
474
+ - **Theme-following surfaces and light-mode readability** — Dynamic Workspaces
475
+ session hovercards follow the active theme: light mode uses a white surface
476
+ with the light label tokens (title `#0f1115`, secondary `#61666b`, tertiary
477
+ `#81858c`) for the plugin's `.psd-hovercard`/`.psp-*`/`.dsa-quicklook` cards
478
+ plus a minimal scoped override for the native shell session-info hover card,
479
+ while dark mode stays byte-identical (`#2C2C2E` + white). The native override
480
+ depends on shell module class hashes and degrades gracefully to the native
481
+ dark card. The native Workspace session-info hover card uses the plugin
482
+ card's 320 px width in both themes (scoped shell-hash override with graceful
483
+ fallback). Rainbow atmosphere rows are readable in light mode through a
484
+ brighter pastel canvas, a white readability veil instead of the dark scrim,
485
+ and lifted secondary text/icons on highlighted rows (card title
486
+ 5.51:1→14.72:1, time/icons 1.08:1→4.52:1, native Workspace worst text
487
+ 15.45:1), with the sidebar E2E pinning the light thresholds; dark mode is
488
+ unchanged. Running-panel icons match the native Workspace icon weight in
489
+ light mode (row actions, disclosure/chevrons, status and child glyphs lifted
490
+ from `label-tertiary` #81858c to `label-secondary` #61666b; brand/sparkle
491
+ stays `label-primary`). The reported dark document-preview panel was found
492
+ shell-owned and not reproducible (the plugin defines no `--dsw-*` variables;
493
+ only the shell diff sub-palette is low-contrast) and is documented as a
494
+ shell-side limitation with no broad override.
495
+ - **Prompt-history rail matches the native turn rail** — right-aligned 20 x 2 px
496
+ tick marks on the native column (60 % width at rest, growing on hover, brand
497
+ hairline on keyboard focus), a horizontal 32 x 1 px divider, a native-style
498
+ line-clamped preview card, and a pinned 20 x 22 px magnifier whose centre sits
499
+ on the visible resting tick column (the toggle overhangs the rail edge by
500
+ 4 px); copying a prompt is silent (the confirmation chip, check icon, and
501
+ animation are gone while the exact draft text and composer focus remain). The
502
+ rail's order was reversed to reading order (oldest top, newest bottom) and it
503
+ keeps the newest tick in view.
504
+ - **Borderless floating surfaces** — the annotation launcher and its count
505
+ badge, the annotation rail (docked and overlay), the exit-confirmation dialog,
506
+ the feedback and undo toasts, and the Running & recent panel card no longer
507
+ paint an outer border; the launcher is a perfect circle
508
+ (`corner-shape: round`) and every borderless surface uses a ring-free soft
509
+ shadow, so the elevation token's 0.5 px hairline cannot read as a border in
510
+ either theme; separation comes from background and shadow, inner controls
511
+ keep their own borders.
512
+ - **Plugin input focus treatment** — a shared animated rainbow track focus ring
513
+ replaces solid-color focus outlines/borders on plugin text inputs (annotation
514
+ note fields, prompt-history search field, settings choice pills); it fades in
515
+ in 140 ms, rotates and hue-drifts, keeps a static ring under reduced motion,
516
+ and falls back to the system `Highlight` outline under forced colors. The ring
517
+ is parameterised and the prompt-history search card paints a deliberately
518
+ calmer variant around the whole floating card when its input is focused
519
+ (opacity 0.58, desaturated 2.5 px glow, 1.5 px track, slower 4.6 s/20 s drift;
520
+ the inner input itself is ringless). The rainbow ring now hugs the wrapped
521
+ control's border box on all four edges (the inline-level baseline gap that
522
+ exposed the control's bottom border is fixed).
523
+ - **UI element annotation settings** — the rail header's settings gear/settings
524
+ view is replaced by an **info (i) icon** that opens a small borderless
525
+ hovercard-style popover with the two modifier rows; each row is a **custom
526
+ segmented control** (`role=radiogroup` with four `role=radio` segments
527
+ Alt/Ctrl/Meta/Shift, roving tabindex, arrow/Home/End/Enter/Space selection,
528
+ persistence + inline conflict feedback, glass track, primary-accent checked
529
+ segment, rainbow focus ring on the checked radio). The old settings
530
+ view/Back path and the dropdown/listbox implementation (and its seam helpers)
531
+ are removed — no native `<select>` or OS menu remains. Segments show the
532
+ modifier-key symbols (`⌥ Alt`, `⌃ Ctrl`, `⌘ Meta`, `⇧ Shift`) with full
533
+ localized aria-labels, equal widths, and no truncation; document-level Esc
534
+ closes the menu first, then the popover, with the mode staying on.
535
+ - **UI element annotation composer interaction** — the current Session's
536
+ composer stays natively clickable/typable while the mode is active (and is no
537
+ longer an annotation target), so an inserted reference chip can be edited and
538
+ sent; the sidebar footer primary becomes **Insert all into composer** when the
539
+ collection is non-empty and no page selection is pending; the multi-selection
540
+ batch popover is draggable by its header and both popovers clamp with their
541
+ measured size so their buttons stay inside the window; Active/Inactive
542
+ Projects headings match the native Workspaces heading (14 px / 400).
543
+ - **UI element annotation launcher placement** — the round launcher floats only
544
+ while the mode is off; activating the mode fades/scales it out in place (no
545
+ docked or flying copy in the rail header), and a full exit (header X, Cancel
546
+ Annotation, or the final Esc step) restores it with a fade/scale animation at
547
+ the remembered floating position (drag and position persistence are idle-only;
548
+ reduced-motion users get the instant state).
549
+ - **Artifacts source filter** — the filter is a custom dropdown in the panel
550
+ header immediately left of Refresh: a `filter-line` funnel trigger with the
551
+ current option label/count and a rotating caret opens a themed, right-aligned
552
+ `menu`/`menuitemradio` popup listing All/Generated/Provided with their counts
553
+ and a check on the selected option (focus moves to the selected option on
554
+ open; outside press or Escape closes; Escape returns focus to the trigger).
555
+ - **Plugins-page settings section** — the bundle's Plugins page shows only the
556
+ suite's real controls while its settings section is mounted: the
557
+ auto-rendered package README document above the configuration is hidden and
558
+ restored on unmount, and the section carries the **Prompt history** group plus
559
+ the **Active & recent** group with the two retention rows.
560
+ - **Running & recent fold persistence** — the Active/Inactive bucket fold state
561
+ is restored on the first observable paint using a persisted bucket
562
+ classification cache and then corrected by live data, so a collapsed bucket
563
+ no longer paints expanded for the hydration window; native section
564
+ re-renders cannot clobber a fold.
565
+
566
+ ### Fixed
567
+
568
+ - **Prompt-history rail anchoring** — the rail was a separately positioned
569
+ fixed overlay: it measured the native turn rail's marks and re-measured on
570
+ scroll/drag, so it could drift by one mark while scrolling, trailed then
571
+ snapped while dragging a dock/right sidebar, and stayed visible after the
572
+ native rail had hidden in a narrow conversation. It now renders **inside the
573
+ native turn-rail frame** (directly below its marks, same 28 px column and
574
+ right edge, native band height) so the shell's own sticky positioning,
575
+ drag tracking and narrow-container hiding apply with no JS catch-up; the
576
+ hover preview and search cards remain body-portaled and viewport-fixed.
577
+ - **Interrupted-session refresh and timing** — badges repull automatically after
578
+ a Host restart (Connection generation reset), on focus/visibility/online, and
579
+ on a 20 s poll instead of waiting for a Session click; parent Sessions whose
580
+ delegated subagent was interrupted after the parent's last completed turn are
581
+ marked interrupted, including nested delegations (a live child remains live
582
+ work); subagent interruption timing uses the child's turn start as well as its
583
+ last event, covering children that go silent before a Host restart. After a
584
+ reconnect, an interrupted Session no longer keeps the native green "running"
585
+ spinner until opened — the plugin decorates rows whose native status is stale,
586
+ replacing the spinner with the amber mark. Forced badge refreshes keep the
587
+ current ready value until the new answer arrives (no flash through `loading`);
588
+ the Host interruption cache uses per-Session event epochs so a slow log read
589
+ cannot overwrite a newer turn event. Continue validates JSON content type,
590
+ current interruption/running state, and per-Session in-flight admission;
591
+ duplicates are rejected instead of queued.
592
+ - **Sidebar interrupted hover geometry** — hovering an interrupted native
593
+ Session row keeps the shell's normal hover surface and its title visible (the
594
+ shell still replaces the time with the trailing hover actions, as on any
595
+ Session row) and reveals the inline Continue triangle right after the warning
596
+ mark; the obsolete opaque `::before` hover mask (a leftover from the retired
597
+ trailing-edge CTA) is gone. The mask's positional `span:first-child` z-index
598
+ rule used to catch the injected rainbow-atmosphere wrapper on the current
599
+ Session row, which turned the background layer into an in-flow pill that
600
+ pushed the badge right and collapsed the title; the native status cell now
601
+ widens with `width: auto` so the triangle fits and the title slides right
602
+ instead.
603
+ - **Running & recent card geometry and hover fixes** — collapsing the
604
+ Continue/pin slots no longer leaves flex gaps behind: the head is gap-less and
605
+ the leading glyph cell carries the rest spacing, so an interrupted row's
606
+ title sits at the first-character-centred rest column again and slides right
607
+ only when hovered/focused (the pinned column stays at the documented
608
+ 9 + 16 + 9 px; the glyph-to-title gap is the 9 px cell margin plus the ~12 px
609
+ centring shift). The hover surface now covers the whole row like the native
610
+ sidebar rows instead of a content-paced inner pill that lit only the title;
611
+ the row body stays transparent so no second nested pill appears, pinned rows
612
+ keep their violet tint under the hover layer, and atmosphere rows keep their
613
+ transparent surface.
614
+ - **Sidebar review follow-ups** — the interrupted row's leading cell no longer
615
+ hides other plugins' leading-slot marks (schedule clock, liveshare fork) —
616
+ only the native status dots are hidden while the stale-spinner decorator is
617
+ active; the inline Continue triangle expands the native status cell instantly
618
+ instead of animating its width, so the shell's title marquee measures the
619
+ narrowed cell and no longer stops short; the card's keyboard focus surface is
620
+ gated on `html[data-input-modality="keyboard"]`, so a mouse click cannot leave
621
+ a stuck row surface; atmosphere-row control suppression is restored, scoped
622
+ with child combinators to the current row's own controls, and gated the same
623
+ way (nested child rows keep their normal hover block); pointer focus no
624
+ longer leaves the atmosphere rows' `brightness(1.5)` lift or the native
625
+ Continue triangle stuck after a mouse click; the card's Continue slot honours
626
+ reduced motion; the dead trailing-edge Continue component is removed; docs no
627
+ longer claim the time stays visible on native hover.
628
+ - **Read acknowledgements and activity-ledger robustness** — read-acks `load()`
629
+ is single-flight with forward-merge publication (`mergeAcked(state,
630
+ parsed)`), so a stale concurrent load cannot clobber a newer record;
631
+ non-ENOENT reads reset the cached promise and throw typed
632
+ `READ_ACKS_READ_FAILED`, GET/POST answer no-store `500 { code:
633
+ "store-read-failed" }`, empty is never cached, `record()` awaits the same load
634
+ in the serialized chain and `get()` returns current. A non-ENOENT
635
+ activity-ledger load keeps memory, resets its promise, throws typed
636
+ `ACTIVITY_READ_FAILED` (no empty rewrite; writes abort while unreadable;
637
+ ENOENT stays empty); the Host `ensureLoaded()` resets/rethrows,
638
+ `ensureSeeded()` resets the seed promise with the existing 30 s backoff, and
639
+ the route serves **`200` snapshot/empty, never 500** — after recovery the
640
+ next GET after the backoff retries load+seed and returns recovered entries,
641
+ while during the backoff a GET may serve current/empty memory. Ack pushes are
642
+ chunked (≤200 entries/~48 KiB, one in flight), body reads are capped at 64 KiB
643
+ of UTF-8 bytes, client requests time out after 8 s, and `401/403` join
644
+ network/5xx/408/425/429 as retryable ack-push failures (other permanent 4xx
645
+ drop only that batch immediately; local and pending maps each capped at
646
+ 1000). The activity route uses an 8 s `AbortController` timeout and the
647
+ client awaits pending ack pushes before fetching it. Ack flush/sync failures
648
+ are caught and bounded-logged, failed read-acks writes clean up their temp
649
+ sibling, and the read-acks `localStorage` migration runs per mount. Read-error
650
+ behavior is unit/`chmod`-tested only and the concurrency proof is store-level
651
+ stress (20 rounds of 4 concurrent get + 3 record), **not** a real
652
+ multi-process Host; client 401/403 classification has no browser node
653
+ harness.
654
+ - **Activity seed recovery** — an already-pending seed that times out keeps the
655
+ 30 s immediate-serve backoff while background seeding continues; a
656
+ failed/rejected seed may set that backoff but the Host resets the seed promise
657
+ so a later request retries load+seed, and seeded history can appear after
658
+ recovery (during the backoff a GET may serve current/empty memory `200`).
659
+ Selection families no longer list PTC mode (`ptc-mode` is a message-source
660
+ key; `tool/ptc-dispatch` remains activity).
661
+ - **UI element annotation resolution and identity** — resolution is two-phase:
662
+ per-candidate hit sets are collected and the first unique candidate (highest
663
+ stability tier/score) wins, so a non-unique high-tier candidate (e.g. a
664
+ duplicated `aria-label`) no longer short-circuits to Ambiguous when a
665
+ lower-tier structural/anchor candidate resolves uniquely; Ambiguous is
666
+ reserved for genuinely all-non-unique candidates, and weak XPath/text-position
667
+ ambiguity no longer terminates the text-quote fallback. CSS-module/hashed
668
+ class names are filtered by a word-like/generated-pattern heuristic, and
669
+ record identity uses the verified unique selector. Candidate resolution gains
670
+ an ordered stability ladder (data/ids/aria > role+name > label/role > class >
671
+ tag/nth) and a length penalty; text-bearing leaf records additionally capture
672
+ a bounded absolute XPath, a normalized text quote (exact + prefix/suffix), a
673
+ container-relative text position, and a `document.querySelector(...)` JS path.
674
+ Resolution falls back **CSS → text quote (position hint) → text position →
675
+ XPath last** (full XPath only with a live node, never fabricated), with a
676
+ `via` hint in the popover, detail card, and rail row and **Copy locator** /
677
+ **Copy XPath** / **Copy JS path** actions (live-node-first → saved-anchor →
678
+ honest-unavailable). Capture-time text-quote disambiguation is
679
+ occurrence-aware, bounded, uniqueness-verified, and drops misleading quotes;
680
+ one rendered-text pipeline (`<br>`/block boundaries → space + rendered→raw
681
+ offset map) keeps the text comparison honest; fallback resolution keeps a
682
+ single validation boundary (tag/digest/accessible name/proximity), scored
683
+ approximate matching (exact unique context resolves, small edits report
684
+ Content changed, ties Matches several), status/node caching keyed by
685
+ `(record id, DOM revision)` with bounded scans (400 elements / 32 candidates)
686
+ and a 400-entry node cache, and a **weak-identity gate** so icon-only/
687
+ tag-only records cannot falsely resolve via structural fallbacks (no wrong
688
+ marks/copies; they report Changed honestly).
689
+ - **UI element annotation descendant anchors and weak identity** — non-leaf
690
+ targets with meaningful descendant text capture a first-text-leaf rendered
691
+ quote/position plus `anchorTarget:'descendant'`, the leaf tag, the ancestor
692
+ tag chain and a stable-attribute signature; when CSS candidates go stale the
693
+ resolver falls back to the descendant text anchor and climbs to the closest
694
+ ancestor matching tag+signature (unique → Resolved, same-text/same-signature
695
+ decoys → Matches several with no mark, none → honest continue;
696
+ floating/ephemeral surfaces excluded). The recorded scope is authoritative: a
697
+ unique in-scope target resolves even when an identical out-of-scope duplicate
698
+ exists (the Workspaces-row vs Running & recent-title case no longer reports a
699
+ false "Matches several"), multiple distinct in-scope targets are **terminal
700
+ ambiguous**, and an empty/missing scope still re-anchors through the bounded
701
+ document fallback. Weak-identity structural outcomes keep the four statuses
702
+ but add `confidence:'weak'|'strong'` and present
703
+ "Unverifiable · weak identity" / "无法验证 · 弱身份" instead of Content
704
+ changed; a stale `uniqueVerified` selector no longer counts as identity
705
+ unless it still resolves to a single connected/visible element, structural
706
+ fallback hits must pass a quote assertion plus captured-ancestor
707
+ corroboration before Resolved, weak-identity records without a quote are
708
+ **Missing** (no mark or live-node copy on a same-tag look-alike), and removed
709
+ floating/ephemeral targets report **Missing** instead of Changed after reload.
710
+ Approximate matching recall mirrors the Hypothesis `matchQuote` bounds; the
711
+ capture scope-climb duplicate probe uses the rendered-text pipeline, fallback
712
+ scans/cache misses are instrumented for a test-only probe (repeat resolution
713
+ on unchanged DOM adds zero scans; host mutation re-resolves once), and docs
714
+ recommend host apps expose stable `data-testid`/`data-*`/accessible names for
715
+ position-sensitive elements.
716
+ - **UI element annotation follow-ups** — hovering a composer annotation
717
+ reference chip (single or grouped) shows the custom annotation detail
718
+ tooltip — requirement, locator, captured position box, Session/Workspace,
719
+ live status, or the group count/list — while clicking keeps its existing
720
+ behavior; chat-flow element picks anchor to the shell's real chat attributes
721
+ (`data-chat-node-key`/`data-chat-anchor-key`/`data-chat-group-key`/
722
+ `data-chat-turn`/`data-chat-flow-key`), so leaf targets in a
723
+ streaming/virtualized chat resolve across re-renders instead of reporting a
724
+ stale positional locator (annotations captured before this change are not
725
+ silently remapped — re-annotate them); hovering or focusing a single/grouped
726
+ annotation chip shows an own 16 px × that removes exactly that reference chip
727
+ through the composer editor in one undo step (other chips and text preserved,
728
+ never sent), while the chip hover tooltip stays read-only; the requirement
729
+ popover keeps its Delete action in the Requirement caption row (marked state
730
+ only) so the footer holds exactly the two primary buttons on one non-wrapping
731
+ row; the weak "Unverifiable · weak identity" label regained E2E coverage,
732
+ role+name got its own selector-stability tier, and the matchQuote
733
+ recall/role+name/length-penalty behavior is pinned by unit tests.
734
+ - **UI element annotation transient surfaces** — selecting an element inside a
735
+ hover-triggered floating surface (e.g. the subagent hover dropdown) no longer
736
+ loses its target when the pointer moves into the requirement popover: the
737
+ surface is pinned open for as long as that popover is active (pointer-leave
738
+ close events are suppressed for the pinned subtree and released on
739
+ close/selection clear/mode exit), the status stays Resolved while editing,
740
+ and the transient hint explains the keep-open-then-may-disappear behavior. If
741
+ a surface still closes (timer/scroll/keyboard path), the status changes
742
+ honestly but the locator summary stays the captured string instead of
743
+ switching to a look-alike element's label.
744
+ - **Hover Quick Look fixes** — the Quick Look no longer opens as an empty card:
745
+ it always receives an explicit height (570 x 360 default, clamped to the
746
+ viewport, with a remembered or user-resized size still winning) and its
747
+ content layer no longer depends on an inline opacity style or a finished
748
+ animation, so generated Markdown/code/image content is visible on the first
749
+ hover. Single-quoted code strings highlight correctly, the preview cache is
750
+ bounded with a TTL, and sidebar/chat observers are scoped to relevant
751
+ mutations.
752
+ - **Raw artifact media type and CSP** — raw artifact media type comes from the
753
+ real path and every raw response uses the native sandbox/default-src-none CSP;
754
+ the implicit continuation context and correlated turn-trigger row are hidden
755
+ in Chat.
756
+ - **UI element annotation NITs** — ephemeral/floating surface-gone now reports
757
+ **Missing** for every outcome through a single `annotationEphemeralOutcome`
758
+ gate (still-present surfaces keep honest outcomes; the conservative
759
+ transient-Changed policy is documented), deferred reference-conformance
760
+ limitations moved into the user docs, and the selector/popover copy states
761
+ were corrected.
762
+ - **Interrupted-state consistency for the card and stale-running native rows** —
763
+ the interrupted mark/Continue decision now follows the Host interruption
764
+ record alone instead of the shell's combined running flag, so a parent Session
765
+ whose own turn stopped on a provider transport/timeout error while delegated
766
+ subagent children still run keeps its amber mark, inline Continue and relative
767
+ last-activity time in the **Running & recent** card (interrupted child rows
768
+ show the amber glyph) instead of appearing as an unstoppable running row.
769
+ Native sidebar rows the shell still renders as running now get both the amber
770
+ badge and the hover Continue CTA, wired to the same continuation handshake as
771
+ idle rows, and every mark/CTA disappears once the continuation turn is running
772
+ (`running: true`). No Host route, payload or state shape changed.
773
+ - **Row "…" menu uses the native shared context-menu popup** — the card row
774
+ menu no longer renders a custom card-styled popup with a local glyph map and
775
+ no shortcut hints; it opens the shell's native shared context-menu surface
776
+ (the one the native DSH Session row opens) against a plugin-owned
777
+ captured-target kind, so its material, keyed native icons, live keyboard
778
+ shortcut hints, submenus, separators and the Archive `afterContent` footer
779
+ match the native menu. A registered contribution delegates the action list to
780
+ the native Session actions — Rename, Fork, Copy Session ID, Show in Finder,
781
+ Archive and any plugin-contributed action keep their native behavior — and
782
+ filters only the Pin/Unpin entry, because the card's title-left pin button
783
+ remains the pin owner. The old `DwSessionMenu` portal, its local icon map and
784
+ its custom `.psd-menu*` styles are removed; the trigger is focused before
785
+ opening so the shared popup restores focus to it, `data-menu-open` follows the
786
+ shared popup's active target, and a DSH build without the shared context-menu
787
+ service hides the trigger instead of falling back to the custom surface.
788
+
789
+ ### Removed
790
+
791
+ - Standalone Project detail page: the `project-view` feature is removed —
792
+ `src/features/project-view/{host.js,fold.js}`, the `//#region feature: project
793
+ view` browser region and its `installProjectView` call, the 24 project-view
794
+ tests, `docs/project-view.md`, the five `docs/assets/project-*.png`
795
+ screenshots, and the `GET /api/power-suite.project` route. Clicking a
796
+ Workspace's title in the sidebar performs the native expand/collapse again,
797
+ and the default agent preset stays available from the Workspace context menu.
798
+ Removing the page needs no data migration: it persisted no state.
799
+
800
+ ### Documentation
801
+
802
+ - Added [docs/update-check.md](docs/update-check.md): user-facing behavior, the
803
+ `GET /api/power-suite.update?lang=` contract, cache TTLs, version rules, the
804
+ browser prompt state, the tag-pinned release-notes source, and limitations.
805
+ - Added `release-notes/<version>.md` + `.en.md` files and their format rules,
806
+ plus `scripts/check-release-notes.mjs` and the `check:release-notes` gate
807
+ (also run from `npm run check` and the publish workflow), so the in-app update
808
+ notice can only read reviewed, tag-pinned Highlights.
809
+ - Added the tag-triggered `publish.yml` publish workflow (Trusted Publishing)
810
+ and replaced `check.yml` with `ci.yml` (docs-only fast path + verify job), and
811
+ added the `.agents/skills/release-power-suite` release procedure.
812
+ - Consolidated the never-published `[0.1.0] - 2026-11-09`, `[0.1.1] -
813
+ 2026-11-11`, and `[0.2.0] — undated development snapshot` sections into this
814
+ single first-release section, and reframed the README around the planned
815
+ first public release (0.1.0) instead of the old 0.2.0/0.3.0 snapshot
816
+ narrative.
817
+ - Rewrote the English README as a Bento landing page — icon header, three
818
+ badges, a one-line hook, a `[!NOTE]` status block, overview sections with four
819
+ composed WebP images in `assets/`, a scannable feature table, and install,
820
+ quick-start, prerequisite and gate sections. The images are produced by
821
+ `npm run build:readme-bento` (`scripts/build-readme-bento.mjs`) from local
822
+ live-GUI captures taken by the new `test/browser/sidebar.e2e.mjs
823
+ --readme-shots` mode; the capture and compose pipeline, including its privacy
824
+ masking rule, is documented in [docs/development.md](docs/development.md).