zhu1090093659/dsh-web v0.4.12

dsh-web v0.4.12

on GitHub

This release repairs two contracts that break an existing profile on upgrade: the session archive's settings section returns to its own namespace, and dsh-agents stops writing host core packages into its runtime dependencies. The pet and Workshop installer staging no longer shows up in the registry, the remote channel fixes one silent path each in the follow subscription and in the single-question ask, and the task board gathers the whole label rule onto the corner question mark and adds a rule that clears a task's labels once every one of them has settled. The four satellite repositories align to 0.4.12 in this version, and the aggregate and the market artifacts are rebuilt in the same batch.

The session archive's settings section id becomes dsh-session-archive: the plugin used to claim the official archived-sessions section id, and the settings shell refuses a second registration of the same id at the same priority (default 0) while order only sorts the rows, so two archive plugins were bound to collide: one registration throws, or one of the two entries silently disappears. This version moves it to the plugin's own namespace dsh-session-archive, so it holds its own row beside the official Archived sessions page and any third-party archive plugin, with the nav position 25 unchanged. What moves is the nav item's key and the deep links built from the old id; it is not a persisted key, and no manual migration is needed.
dsh-agents moves host core packages from runtime dependencies to development dependencies: @deepseek-ai/dsh-brand, @deepseek-ai/dsh-session-persistence and @deepseek-ai/dsh-session-projection move from dependencies down to devDependencies. The plugin manager installs that dependencies section into the user profile, and a profile copy loads ahead of the host, so a prerelease range like ^0.2.1-rc.3 became a version switch the user never pressed: when the host moved to the next rc, sessionProjections failed to register, agent-loop could not activate, and the whole plugin set went down with it. The runtime copy always comes from the host, and scripts/family-host-dependencies.test.mjs is that gate (issue #1966).
The four satellite repositories align to 0.4.12: the satellites publish first and this repository second; all four resolve from the registry, and the aggregate's dependency ranges, the workspace's minimum-release-age exemptions and the market pins move to 0.4.12 together:

• Skin center (dsh-skins, ee16f91bf9e0edd44eb3da6814de33f2550a8105): @linxin666/dsh-client-ui-skin-center@0.4.12
• Pet (dsh-pet, 9ccb048c82b4ac4f6cc52fbb3ca92323b42c799b): @linxin666/dsh-pet@0.4.12
• Community plugin index (dsh-community-plugins, 3b0673de59b5c4ad803ffec9cd0159cda8613fb2): @linxin666/dsh-client-ui-community-plugins@0.4.12
• Preset center (dsh-presets, 92c3154252fc076f5fe7d4b123fc6dfc3186314d): @linxin666/dsh-client-ui-preset-center@0.4.12
  An automatic upgrade needs no migration: the only persisted or wire-protocol identifier this version touches is the session archive's section id, which is not a persisted key and is written into no archive; configuration keys, localStorage keys, control-plane API paths, the wire protocol minor (still MINOR 21) and the aggregate's rows all keep their 0.4.11 values. The three entry points keep their 0.4.11 semantics: the plugin-manager update is the only migrating path, with preflight and a version assertion (including the legacy aggregate name @linxin666/dsh-web-ui-all branch); the Doctor pre-launch migration path no longer exists in this repository, where dsh-doctor is only a tombstone that cannot be installed and has no launcher consumer; and a direct dsh web installs nothing, preflights nothing and does no registry version migration, so an old profile stays exactly as it is. To recover by hand, run dsh plugin --profile <name> add @linxin666/dsh-web-all@0.4.12.
  The remote channel: follow subscriptions and the silence of a session family: a follow subscription that has already advanced no longer answers with a snapshot baseline but opens a new stream for the latest window; a turn-completion push waits until the whole session family goes quiet, so a child session is not announced on its own; and a single-question ask gets a 15-second ceiling, so a question without an answer is asked again instead of staying silent forever.
  The task board: the label rule moves onto the corner question mark: the label manager's whole rule moves onto the question mark in the title corner, painted as a bubble rather than used as a title, opening rightwards with locale margin, and in a narrow modal the modal title shrinks instead of sitting under the corner mark. The rule itself gains one line: a task's labels are cleared once every one of them has settled.

New Features

• [task-board] The label manager's whole rule moves onto the corner question mark
• [task-board] The corner question mark carries the clear-label rule
• [task-board] A task's labels are cleared once all of them have settled
• [remote-web-ui] The named tunnel's ingress port follows the setting
• [ssh] Terminals support multiple tabs

Bug Fixes

• [remote-bridge] A follow subscription that already advanced answers with a new stream instead of a snapshot baseline
• [dsh-agents] Host core packages are no longer shipped as runtime dependencies
• [git-graph] The branch popover no longer misplaces or clips itself
• [remote-bridge] A single-question ask gets a 15-second ceiling and asks again instead of staying silent
• [remote-bridge] A turn-completion push waits for the whole session family to go quiet
• [task-board] The rule bubble narrows to leave locale margin
• [task-board] The rule bubble opens rightwards, so a card cannot clip it
• [task-board] The label manager's rule is painted as a bubble, not a title
• [task-board] A modal title shrinks instead of overlapping the corner mark
• [dsh-agents] The settled command record is read instead of the handler result
• [liangshen] Activations dispatched from inside a program are replayed
• [dsh-agents] An unbound squad runs in the Host default directory
• [liangshen] tool_activate pages from the catalog's published partition
• [skins] The atelier skin's accessibility contrast improves
• [market] Installer staging stays out of the pet registry
• [session-archive] The session archive's settings section returns to its own namespace
• [agents] The agentTeams runtime is no longer started twice
• [liangshen] The goal command is exposed in the preset
• [settings] A typed settings draft settles once and keeps its not-exposed notice
• [market] The deploy lane retries a throttled Cloudflare API

Other Changes

• [market] The 2026-10-28 satellite merges are pinned and the store artifacts are rebuilt
• [test] The standards debt this sync surfaced is cleared
• [dsh-agents] The workspace registry resolution is pinned at the apply seam
• [task-board] What the corner question mark actually reaches is written down
• [liangshen] The regression test's shared scope is stated precisely
• [ci] The coverage baseline the CI runner measures is recorded
• [docs] The market deploy 429 evidence is archived
• [ci] Each package is measured on the code it owns
• [readme] The contributor list is synced from the GitHub API

Generated automatically by the release pipeline (scripts/release-notes.mjs).