zhu1090093659/dsh-web v0.4.7

dsh-web v0.4.7

on GitHub

This release advances the family's official cohort to 0.2.1-rc.2 and raises the host floor with it, adds dsh-remote-bridge so a paired phone can use host sessions over protocol v1, brings a pinned private bash to Windows x64 sessions, gives the task board reasoning effort, automatic subtask teams and new-card defaults, and has the plugin manager prune stale per-row overrides on update while updating through the same remove-then-install path the official manager uses. The skill explorer gains an enable switch for plugin-provided skills, and the remote Web GUI lets you choose the pairing network source when connecting.

Important change (the host floor moves to >=0.2.1-rc.2): every family package and the plugin scaffold now declares dsh.engines.dsh >=0.2.1-rc.2 (the previous release declared >=0.2.0-rc.2), with the matching host peer kept in step. npm latest for the official CLI is still 0.2.0-rc.2 and 0.2.1-rc.2 is only on the next tag, so a user on the stable CLI cannot auto-update through the plugin manager: the update is refused with 412 and a message that the target requires DSH >=0.2.1-rc.2 (with the current version), telling them to upgrade DSH first. Recovery: install the 0.2.1-rc.2 CLI first, then update the family.
Only one entry point really migrates: updating through the plugin manager (including the legacy aggregate-name migration branch) preflights, asserts the resulting version and can roll back. This release has no Doctor pre-launch migration — the doctor package is only a tombstone today and the launcher consumer legacy-migration.ts refers to does not exist here — and starting the host with a direct dsh web performs no install and no preflight, so an old profile stays exactly as it is until the user updates through the plugin manager. Update through the plugin manager, or run dsh plugin --profile <name> add @linxin666/dsh-web-all@0.4.7 by hand; do not expect a start to upgrade anything.
The fourth path is weaker: the dsh-update family plugin runs a package-manager update inside the profile with no backup, no preflight, no rollback, and it does not prune the stale row override either. Prefer the plugin-manager path.
Retiring a plugin row no longer leaves a stale per-row override behind: on update the plugin manager prunes overrides whose row id the composed profile no longer declares, backs the patch file up first, and writes nothing when there is nothing to prune.
@linxin666/dsh-client-ui-model-capabilities is retired and its cordis row id web-ui-model-capabilities is gone: a profile that recorded that row gets the pruning behaviour above instead of a permanent warning on every start.
The four satellites already published 0.4.7 before this tag, and the family consumes them by semver:

• Skin center (dsh-skins) 0.4.7
• Pet (dsh-pet) 0.4.7
• Community plugin index (dsh-community-plugins) 0.4.7
• Preset center (dsh-presets) 0.4.7
  Known limitation (upgrading 0.4.6 to 0.4.7): the code that prunes a stale per-row override runs only inside the plugin manager update job, and the update that takes a host from 0.4.6 to 0.4.7 is performed by the 0.4.6 code already loaded in that host, so it cannot prune the web-ui-model-capabilities override it retires. The composition itself stays correct, but every dsh --dump-config run and every CLI log shows a patch: entry "web-ui-model-capabilities" not found diagnostic, and no .bak-plugin-manager backup is written. The next update through the plugin manager runs under 0.4.7 code and clears it as part of that run; until then you can do it by hand: back the file up, then edit $DSH_HOME/profiles/<profile>/cordis.patch.yml and remove the entry whose id is web-ui-model-capabilities. Pruning after boot ships in the next version.

New Features

• [remote-bridge] New dsh-remote-bridge package: the host half serves session roster, history and prompting to a paired phone over protocol v1, pairing by a one-shot token plus a P-256 challenge-response
• [remote-bridge] A sidebar pairing panel in the Web GUI renders that one-shot token as a QR symbol, with the token endpoint admitted only from this machine
• [remote-bridge] The roster and history baseline ride the protocol, session titles and metadata arrive with them, and a delegated session is addressed through its parent
• [remote-bridge] The host's questions reach a paired phone, and the phone and the desktop answer the same question
• [remote-bridge] Composer parity with the host, an opening snapshot bounded by the same 512 KiB page budget, and a 10 MiB frame cap
• [remote-bridge] The pairing code carries the public origin so the phone can pick its connection entry
• [win-bash] Windows x64 sessions get a pinned private bash: its own Git for Windows MinGit payload, one persistent process per session, and no fallback to a bash on PATH
• [win-bash] win_bash results surface truncation and support background jobs
• [win-bash] Served sessions stop seeing the host pwsh, narrowed by a visibility-only ladder that yields only where win_bash cannot serve; every refusal routes to the native shell and the plugin declares danger-full-access only
• [win-bash] Mounted by the aggregate, with win_bash availability gated on the liangshen preset
• [liangshen] Resync the dispatcher rules to upstream 0.24.6 and append the local interview discipline
• [liangshen] Widen the run_code mandate to countable triggers, with a misuse nudge
• [liangshen] Split the guard retry safety and curate the tool summaries
• [task-board] Cards carry a reasoning effort, and a subtask team can assemble automatically
• [task-board] A new-card defaults topic in settings pre-fills the agent preset, permission, model and reasoning level a new card starts from, pinning nothing when left blank
• [skill-explorer] Plugin-provided skills get an enable switch
• [remote-web-ui] Choose the pairing network source when connecting, with narrower LAN candidates (#1878)

Bug Fixes

• [plugin-manager] The update transaction prunes the manager's own stale row overrides against the composed profile, backing up first, writing nothing when there is nothing to prune, and failing the job when the write cannot land
• [plugin-manager] Update as remove-then-install, the same path the official manager takes
• [plugin-manager] Settle a failed CLI spawn instead of taking the host down
• [remote-bridge] The phone and the desktop answer the same question, the phone is told when its question card is over, and a reconnecting phone gets the question it missed
• [remote-bridge] Name the owner peer on the question answer call so the answer reaches the right side
• [remote-bridge] Read the upgraded socket so protocol frames are answered, and stop a refused upgrade from taking the host down on Linux
• [remote-web-ui] Reopen a plain-HTTP LAN phone through the device landing
• [liangshen] Normalize a legacy both presentation to ptc on startup
• [task-board] Leave finished subtasks out of a cascade run
• [task-board] Reach a freshly saved new-card default without a reload
• [task-board] Resume a cold session before command dispatch on reuse (#1861)
• [task-board] Arm the schedule timer for a card created with one instead of waiting for the next edit
• [session-archive] Read the projcache fallback under both id spellings
• [relay] Cache content-hashed /assets/* immutably at the relay hop while leaving unhashed names, API and non-200 responses alone
• [win-bash] Add sleep and seq to the pinned payload
• [scripts] Let the shard test spawn pnpm on Windows

Other Changes

• [sdk] Advance the family's official cohort to 0.2.1-rc.2, retiring the ./invariant companion export and adopting the new plugin-subpath display metadata read
• [perf] Pace a run group's session burst through an admission queue, and stop re-reading a cleared history on every inspection poll
• [refactor] Resolve the client store through the supported platform, decode runtime imports with a library lexer and single-source the market ZIP writer behind one pure helper
• [ci] Run the required checks as parallel lanes with a native toolchain, keep the install ahead of the text rules and guard the pinned CLI
• [market] Follow the satellites' merges in the skin, pet and community-plugin pins, and drop dsh-annotation from the Workshop editor picks
• [satellites] Move the four satellites' gitlinks to their 0.4.7 release commits
• [libs] Rebuild the aggregate bundles and refresh their sourcemaps and recorded fingerprints
• [test] Cover the remote-bridge timeout identity, the Russian i18n key count, the real ACL confinement of win-bash and the relay's hashed-asset cache
• [docs] Record the 0.4.7 auto-upgrade audit, the 0.4.6 release validation snapshot, the measured CI parallel-lane numbers and several decision notes, and sync the README search keywords and contributor list