# Changelog

All notable changes to this repository are recorded here.

This repository tracks the published package `dsh-run-speed`. Because the package is extracted from the
`deepseek-harness` monorepo, entries also record deliberate deviations between a released npm tarball and the
artifacts committed here.

## 0.1.3

**Breaking: the package identity changed.** The plugin was renamed from `@yjc15/dsh-run-speed` to `dsh-run-speed`,
which changes three load-bearing strings at once: the npm package name, the `cordis.patch.yml` entry id
(`yjc15-run-speed` to `run-speed`), and the browser slot id registered by `src/client/index.ts`. A copy installed from
the previous release is a *different* plugin to DSH, so remove the old entry before installing this one. The Host
command, the `Run speed` menu, the three modes, and the guidance text are all unchanged.

### Changed

- npm package name is now `dsh-run-speed` (previously the scoped `@yjc15/dsh-run-speed`), so the tarball is named
  `dsh-run-speed-0.1.3.tgz` and installs to `node_modules/dsh-run-speed`.
- `cordis.patch.yml` contributes `id: run-speed` / `name: 'dsh-run-speed'`.
- The browser slot `id` is now the single lowercase segment `dsh-run-speed`, matching how first-party DSH plugins
  register slots instead of using an npm scope as an identifier.
- `tsdown.config.ts` passes the new bundle name, so the emitted CSS region tag and `data-plugin` marker follow it.
- Rebuilt `lib/` from source under the new identity. `lib/client.js` still carries no build-machine path, and
  `lib/client.js.map` still points its `sources` at in-repo `src/client/*`.

### Fixed

- Repository URLs in `package.json` and `README.md` were being rewritten to a non-existent `github.com/925925/...`
  owner during the rename; they point at the real owner again.

## 0.1.2

Initial public repository for the `0.1.2` line. Package behaviour is unchanged from the `0.1.2` build; the
differences below are repository packaging fixes only.

### Added

- Full TypeScript sources under `src/`, the Vitest suite under `tests/`, and the build configuration
  (`tsdown.config.ts`, `tsconfig.json`, `tsconfig.host.json`, `tsconfig.client.json`) that produced the shipped
  artifacts. The npm tarball previously excluded all of these.
- `package-lock.json`, generated by `npm install` against the public registry, so the upstream versions this artifact
  was built against stay pinned and inspectable.
- `LICENSE` and `NOTICE`.
- Repository metadata in `package.json`: `publishConfig.access`, `repository`, `homepage`, `bugs`, `keywords`, and
  `engines`.

### Fixed

- **Removed a build-machine absolute path from the browser bundle.** `lib/client.js` carried the emitting machine's
  full Windows checkout path verbatim inside a `//#region \0dsh-css:` comment. The region name is now the
  machine-independent `dsh-css: src/client/RunSpeedControl.module.css`. The comment is inert for execution — the
  stylesheet is already inlined into `const css` on the next line — so no runtime behaviour changes.
- **Made the browser bundle's source map resolvable and machine-independent.** `lib/client.js` references
  `client.js.map`, but the npm tarball omitted every `.map`, so browser developer tools requested a file that was not
  shipped. This repository ships `lib/client.js.map` and points its `sources` at the in-repo `src/client/*` paths
  instead of the emitting machine's checkout-relative paths.
- **Corrected the `test` script.** It previously named a monorepo-internal path
  (`vitest run --root ../../.. packages/client/ui-run-speed/tests/run-speed.client.spec.ts`) that cannot resolve from
  the package root; it is now `vitest run tests/run-speed.client.spec.ts`. The suite still runs from the monorepo,
  where `vitest` is provided.
- **Widened the npm `files` allowlist** to ship the stylesheet, the raw sources, and the declaration maps alongside the
  prebuilt artifacts. The `tests/` directory is deliberately *not* part of the published tarball.

### Known limitations carried forward

- Selection is process-local: it resets to Standard when DSH restarts.
- There is no standalone build yet. The build and type-check configuration reaches into `deepseek-harness` monorepo
  scaffolding, and `vitest`/`tsdown` are inherited from the monorepo root rather than declared here. See `README.md`
  § Development.
- The plugin requests parallel execution rather than guaranteeing wall-clock improvement.