dsh-browser 0.3.5 — the bridge plugin and the extension

dsh-browser 0.3.5 — the bridge plugin and the extension

Two artifacts, same release:

• dightendless-dsh-bridge-browser-0.3.5.tgz — the DSH plugin (bridge-browser), prebuilt,
  with the extension bundled inside it.
• dsh-browser-extension-0.3.5.zip — the Chrome/Edge extension, already built, for the
  manual route. Unzip it, then load the folder through Load unpacked.

dsh plugin --profile web add https://github.com/DightEndless/dsh-browser/releases/download/v0.3.5/dightendless-dsh-bridge-browser-0.3.5.tgz

The plugin is also on npm — npm i @dightendless/dsh-bridge-browser — for setups that resolve
plugins from a registry rather than from a release asset.

What changed since 0.3.4

The author field was wrong, and this release fixes it.

Every manifest in this repository was inherited from the upstream project this fork came from,
and all of them still carried "author": "Yuxiang Lin". That is not a cosmetic string: it is
what npm prints on the package page, and it is what a catalog that reads the manifest displays
next to the plugin. The listing on deepseek.stream has therefore been crediting someone who has
nothing to do with this fork. It now reads DightEndless in the bridge package, the extension
package, and the workspace root.

LICENSE is deliberately untouched. It carries the upstream MIT copyright line, and the fork
has no standing to reassign it.

There is no code change in this release. No source file, no behaviour, no dependency. The
extension bytes are identical to 0.3.4 apart from the manifest version, and the plugin code is
identical. This release exists only to correct what a package page and a catalog listing say
about who wrote the plugin.

Do I need to upgrade?

• If you install from npm or from the release asset: only if the author attribution matters
  to you. Nothing about how it runs has changed, so staying on 0.3.4 costs you nothing
  functionally.
• If you already run the extension: you can leave it alone. The plugin ships the same
  extension build, and a second startup recognises the installed copy as current.
• A catalog entry only picks up a new manifest on its next edit. A manifest field is a
  snapshot taken when the entry is submitted, not a live reference, so a listing that shows the
  old author will keep showing it until that entry is edited.

Requirements

Chrome 116+ (or Edge); and DSH 0.2.0-rc.2 or newer within 0.2.x, including the 0.2.1-alpha
line. The source-installer route additionally needs Node.js 22+ with pnpm.

Three ways to install

1. Plugin from this release (one command, nothing to build) — the line above, or
   npm i @dightendless/dsh-bridge-browser. Then open the panel and follow the four steps to
   load the extension it just unpacked.
2. Extension only — download dsh-browser-extension-0.3.5.zip, unzip, then
   chrome://extensions → Load unpacked → pick the unzipped folder.
3. Everything from source — the installer in the README clones the repository, builds both
   halves and registers the plugin bundle.

Then open the side panel on any page and ask: the model sees a numbered inventory of what is on
screen and acts through those numbers.