zhu1090093659/dsh-web v0.4.11

dsh-web v0.4.11

on GitHub

This release collects the settings page's extension surface into one entry and puts the family settings cards' interaction and copy on one set of rules. The first-level Web Extensions entry (web-ui-plugins) becomes the parent section of the family plugin cards, and the Workshop (dsh-workshop) and usage (dsh-usage) pages become keyed TABs under it, while the old ids and the deep links built from them still land on their own page. The settings page also unifies the card shape: family settings cards lay out as rows that apply at once, a bounded number shows its segment track and offers a coarse slider, a control column cap keeps a narrow card from squeezing its description into single characters, and the Workshop and usage pages become family cards with tighter copy. The most important fix is a tool rename: ui.present carried a dot that the request schema's ^[a-zA-Z0-9_-]+ does not allow, so a turn that carried it was rejected by validation and the tool never sent a single successful request; this version renames it to ui_present. The four satellite repositories align to 0.4.11 in this version, and the aggregate's lib fingerprint scope narrows to its own src.

The model tool is renamed ui_present, and the old name never sent a single successful request: ui.present carries a dot that the request schema's ^[a-zA-Z0-9_-]+ does not allow, so a whole turn that carried that name was rejected by validation and the tool never sent one successful request since it shipped. This version renames it to ui_present, and the keyed tool.call.toolview registration key follows the same name, so the desktop still draws the whole-page card inside the official tool row. Only the registration name and the wire tool name move: the two capability names ui.v1 and ui.list.v1, the ui.request topic, the ui.event and ui.list methods and every existing frame shape stay as they are.
The Workshop and usage pages move into keyed TABs of Web Extensions: the settings page's first-level entry is now web-ui-plugins (Web Extensions), which owns the keyed web-ui.extension slot; the Workshop takes the key dsh-workshop and usage takes dsh-usage, one TAB each. The equivalent path of the old first-level entries is settings -> Web Extensions -> Workshop and settings -> Web Extensions -> usage. The old first-level ids (dsh-workshop, dsh-usage) and the deep links built from them still land on the matching TAB: while the parent is present it selects that TAB by id, and without the parent the same component falls back to registering as its original first-level settings.section with the same id.
The four satellite repositories align to 0.4.11: the satellites publish first and this repository second; all four resolve from the registry, and the aggregate's dependency ranges move to 0.4.11 together with the market pins:

• Skin center (dsh-skins): @linxin666/dsh-client-ui-skin-center@0.4.11
• Pet (dsh-pet): @linxin666/dsh-pet@0.4.11
• Community plugin index (dsh-community-plugins): @linxin666/dsh-client-ui-community-plugins@0.4.11
• Preset center (dsh-presets): @linxin666/dsh-client-ui-preset-center@0.4.11
  An automatic upgrade needs no migration at all: this version changes no persisted or wire-protocol identifier — settings section ids, 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.10 values, and cordis.patch.yml is untouched. The three entry points keep their 0.4.10 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.11.
  Known issue: the Skin Center card copy says the page refreshes after applying, but applying does not refresh it: the card description promises a page refresh on apply, while apply takes the in-place path and does not reload the page; the copy is corrected in the next version, and the feature itself works in place.
  The gate's scope changes: the aggregate's lib fingerprint covers only its own src: the aggregate's lib/ fingerprint is taken over packages/dsh-web-all/src alone from now on, a child plugin's src no longer enters it, and a child's src change therefore moves only that child's own lib/. pnpm libs:check stays the single gate (issue #1901).

New Features

• [settings] The remaining plugin pages cut their description to one short sentence
• [dsh-usage] The usage page becomes a family card with tighter copy
• [dsh-market] The Workshop page becomes a family card with tighter copy
• [settings] A bounded number shows its segment track and offers a coarse slider
• [web-settings] The extensions page gets a header and its plugin rows are grouped
• [settings] Family settings cards lay out as rows that apply at once
• [settings] The extension pages merge into one Web Extensions entry
• [settings] The extension pages move under one Web Extensions section

Bug Fixes

• [remote-bridge] The model tool name drops its dot, so a turn is no longer rejected by request validation
• [dsh-market] The store grid's minimum column width follows its container
• [settings-card] A control column cap keeps a narrow card from squeezing its description into single characters

Other Changes

• [build] The aggregate lib fingerprint covers only its own src
• [agents] The UI toolview registration key is corrected to ui_present
• [satellites] The skin and pet gitlinks move and the market artifacts are rebuilt
• [ci] External PR commits are opened by a switch that can be rolled back
• [build] The lib fingerprints are refreshed after the tool-name fix merges
• [build] The lib fingerprints are refreshed
• [satellites] The skin and pet gitlinks move to their upstream commits
• [agents] A note records the control column cap and the site-wide copy style
• [agents] A note records the plugin page's card shape and copy style
• [dsh-i18n] The pet settings page's Russian dictionary follows the tighter copy
• [satellites] The skin and pet pins move to the settings interaction pass
• [settings] The sliding segment highlight is recorded
• [release] The measured legacy-profile upgrade result is recorded
• [readme] Build-script approval moves before the first install
• [release] The 0.4.10 install recovery guidance is corrected

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