codsh-cli@0.26.0

Minor Changes

• 2cac3f5: Run on DeepSeek Harness 0.2.0-rc.2. dsh 0.1.7 and later skipped the codsh bundle as incompatible and disabled every plugin it composed, so codsh on a current dsh started without its surface. codsh now requires dsh 0.2.0-rc.2 or newer, and the launcher refuses an older dsh with the command that installs a new one.

  • The code-cli preset is a dsh preset declaration (presets/code-cli.patch.yml) mounted through the new agent-preset-registry. codsh no longer copies it into $DSH_HOME/.agent-presets, and an existing copy there is ignored, because dsh no longer reads directory presets.
  • Workflows run on the workflow-ptc engine, and Code Mode uses the PTC runtime that dsh-base now provides, replacing the retired worker-thread and code-runtime packages.
  • Turns the surface writes for you (/init, custom commands, /ship children, the vision sidecar) carry a coding-cli message source, because dsh dropped the shared plugin kind.
  • Third-party endpoints are configured in the code profile's own $DSH_HOME/profiles/code/cordis.patch.yml (an llm-pi-ai entry). dsh imports a leftover settings.yaml once and then renames it, and the README now shows the profile patch form.
  • pnpm run sync:dsh checks every package the bundle's patches insert and every patch file the bundle lists. It ignores stale pnpm store entries, and keeps co-released cordis packages on the versions the selected harness resolves.

Patch Changes

• 90bbfaf: pnpm run sync:dsh no longer selects a harness release that drops a package codsh depends on (0.1.7 renamed dsh-agent-presets). It falls back to the newest release in the current range and names what blocked the newer one, and co-released cordis packages now follow the selected harness instead of their own latest tag.