[MyPrototypeWhat]

What ships (0.3.0)

The release combines two lines of work:

1. refkit core 0.10. These commits (fbec6e9, f364a81, b7b78d2) come from the in-progress 0.3.0 work on feat/refkit-0.10:

   • the source naming;
   • the modality-union references;
   • durations, album art and video posters on the card;
   • the new polyhaven-hdri source (24 sources in all);
   • the review follow-ups.

   The breaking changes are listed in the CHANGELOG.

2. dsh 0.2.1-rc.2 support, alongside 0.1.7-rc.2.

   • engines.dsh and the dsh-* peers are now ^0.1.7-rc.2 || ^0.2.1-rc.2. dsh 0.2.1 decides compatibility from engines.dsh alone, and it refuses 0.2.0's ^0.1.7-rc.2 peers outright. That makes today's npm latest impossible to install on the dsh that npm now ships as latest.
   • Dev pins move to 0.2.1-rc.2. src/ compiles unchanged and the built lib/ is identical; only two test fixtures follow the 0.2.1 contracts.
   • package-meta checks that engines.dsh and every dsh-* peer name the same range.
   • The READMEs (en/zh) and the CHANGELOG describe the support and the upgrade path from 0.2.0 (remove, then add again).

Verification

• typecheck, lint, test (173 passed), check:lib and check:client all pass on 0.2.1 dev pins.
• Isolated live run on both hosts. Each host had its DSH_HOME set to a scratch directory, so neither the global install nor ~/.dsh was touched. The candidate was the packed 0.3.0 tarball, built before b7b78d2.
  • dsh 0.2.1-rc.2:
    • Installing @refkit/dsh-plugin@0.2.0 is refused: "incompatible with dsh 0.2.1-rc.2".
    • 0.3.0 installs and shows up under Installed plugins with its zh title, description and icon. The component shows as running.
    • The settings page renders, and saving limit writes cordis.patch.yml (mode 0600). The value survives a reload.
    • plugin remove, then add again, works.
  • dsh 0.1.7-rc.2 (the global binary): it installs, loads, renders the settings page and saves a setting.
  • Not covered: no model turn was run (there was no API key in the test environment). The tool path is unchanged and is covered by the unit tests.

After merge

1. Push tag v0.3.0; release.yml publishes it to npm as latest.
2. Once npm latest is 0.3.0, submit the plugin to the awesome-dsh-plugin registry. The Discover tab in dsh 0.2.1 and the dshmarket plugin market both read that registry, and its index lists npm latest plus engines.dsh.

[MyPrototypeWhat]

Superseded by #6: 0.3.0 was released from #4 while this was open, so the dsh 0.2.1 support ships as 0.3.1.