v0.6.0

Support DeepSeek Harness 0.2.0-rc.2

v0.5.0

Supports DeepSeek Harness 0.1.7-rc.2 alongside 0.1.1-rc.2, 0.1.2-rc.1, and 0.1.5-rc.2 — one build, no per-version install.

0.1.7-rc.2 replaced the settings architecture on both planes, which broke plugin activation:

• Host. SettingsProvider.installSection gave way to SettingsForms, which derives editable configuration from the Config fields a plugin marks .volatile() and hands them to apply as live references. The three fields are now marked volatile through a version-guarded call (a no-op on the schemastery shipped before 0.1.7), their references are read at use time, and the schema-generated page is declined with ctx.settings.configure({ auto: false }, ctx.fiber).
• Browser. ctx.settingsScope and the settings.plugin.item slot are gone. The card now registers on the sidebar Plugins page's plugins.bundle.config slot over ctx.configForms, writes apiKeyEnv/baseURL with one mutate per save, and keeps the API key staged in the credentials domain. The pre-0.1.7 scope card remains as the fallback, so both surfaces ship in one bundle.

ctx.web, credentials (ctx.remote.credentials), the launch environment, invariants, and the dsh.bundle.patch profile layer are unchanged through 0.1.7-rc.2. Existing credentials keep working; on 0.1.7 the endpoint moves to the Plugins page, since the old web-search-synthetic settings section does not map to this plugin's entry id.

Verified with npm run verify (27 tests) and by booting the shipped web profile against a real 0.1.7-rc.2 harness with this build.

0.4.0

Adds DeepSeek Harness 0.1.5-rc.2 to the supported versions.

• Peer ranges widened to ^0.1.1-rc.2 || ^0.1.2-rc.1 || ^0.1.5-rc.2 after a seam-by-seam diff of the dsh-v0.1.2-rc.1 and dsh-v0.1.5-rc.2 tags.
• The audit found no breaking change on any surface the plugin touches: the ctx.web seam, window.__ModuleLoader__, the dsh.client manifest fields, the settingsScope and slots contracts, ctx.remote.credentials, the legacy ctx.connection.api face, credentialRef, the launch environment, and the dsh.bundle.patch profile layer are unchanged through 0.1.5-rc.2.
• No runtime detection changes were needed; the 0.1.2-rc.1 shapes cover 0.1.5-rc.2.

0.3.1

Documentation

• README restructured to the standard-readme specification: badges, Table of Contents, Background, Install, Usage, and the required Maintainers / Thanks / Contributing / License sections. No code changes since 0.3.0.

The dual-harness compatibility notes now cover 0.3.1: the plugin supports DeepSeek Harness 0.1.1-rc.2 and 0.1.2-rc.1 with runtime detection (settings seam shape, ctx.remote credentials face, plugin-owned card styles).

0.3.0

Compatibility

• Supports DeepSeek Harness 0.1.2-rc.1 and 0.1.1-rc.2 with one build: the plugin detects the settings seam shape at load time and calls whichever wiring the running harness provides (SettingsProvider.installSection on 0.1.2, the legacy free installSettingsSection before it).
• The Settings card resolves its credentials face per call: the 0.1.2-rc.1 ctx.remote service first, then the legacy ctx.connection.api face.
• The card ships its own stylesheet (synws-* classes) instead of mirroring upstream hashed CSS-module names, which 0.1.2-rc.1 regenerates, so it stays styled on both versions.
• Peer ranges widened to ^0.1.1-rc.2 || ^0.1.2-rc.1.
• Fixed invalid YAML in examples/synthetic.cordis.yml (stray merge artifact).

Everything else — the ctx.web seam, error codes, credential resolution, launch environment, the bundle patch mechanism, and the settings.plugin.item slot — is unchanged between the two versions.

v0.2.4

Full Changelog: v0.2.3...v0.2.4

0.2.3

• Automate npm publishing: a published GitHub release now tests, builds, and publishes the package. Prereleases publish under the npm dist-tag next; stable releases publish under latest.
• Publish over npm trusted publishing (OIDC): no stored npm token is needed.
• Verify that the release tag matches package.json before publishing.
• README: describe the Git install as available, document the Accept and User-Agent request headers, and list the WEB_PROVIDER_CREDENTIAL_MISSING error.