v0.7.0

Host runtime 0.2.0-rc.1.

This release accepts DeepSeek Harness 0.2.0-rc.1 and no longer accepts 0.1.7-rc.2. Core peers are pinned to that tested prerelease. Cordis stays ~4.0.4 and the validator stays ~3.18.4.

Host tool schemas may include deferLoading. stable-proxy still removes deferred catalog tools from the assembled request. A tool that is already on the stable surface keeps the flag. Routes without tool updates strip the flag and send the full schema, so the plugin does not use it as the discovery path.

Validation: CI on f929e86 passed for Node 22.19.0 and Node 24. Local check passed 73 tests, and peer checks reported no conflicts.

Install:

• dsh plugin --profile web add npm:@everclear077/dsh-progressive-tools@0.7.0
• npm install @everclear077/dsh-progressive-tools@0.7.0 --registry https://registry.npmjs.org

0.6.0 remains installable only on host 0.1.7-rc.2.

The attached tarball SHA-256 is 60F326DD6D4FBA38E8746748E20827E46CECDA9203A8CBF04CD7FE9327371242.

v0.6.0

Host runtime 0.1.7-rc.2.

This release accepts DeepSeek Harness 0.1.7-rc.2 and no longer accepts 0.1.5-rc.1. Core peers are pinned to that tested prerelease. Cordis is ~4.0.4 and the validator is ~3.18.4.

Discovery initializes on agent/created. Resume reads the current tool-result message shape and still accepts older tool-result content blocks. PTC tests use ctx.ptcRuntime.

Validation: 73 tests passed against host 0.1.7-rc.2. Peer checks reported no conflicts.

Install:

• dsh plugin --profile web add npm:@everclear077/dsh-progressive-tools@0.6.0
• npm install @everclear077/dsh-progressive-tools@0.6.0 --registry https://registry.npmjs.org

0.5.1 remains installable only on host 0.1.5-rc.1.

The attached tarball SHA-256 is 6F2C4FE5F44CB8490EF7782168746FAEDE31BF26638EF681D553EB675A4A980C.

v0.5.1

Scoped npm package for host runtime 0.1.5-rc.1.

The unscoped name dsh-progressive-tools is already owned by another account. This release publishes @everclear077/dsh-progressive-tools. Plugin behavior is unchanged from v0.5.0.

Install:

• dsh plugin --profile web add github:everclear077/dsh-progressive-tools#v0.5.1
• npm install @everclear077/dsh-progressive-tools@0.5.1 --registry https://registry.npmjs.org

The attached tarball SHA-256 is 83283D7A5EA381BFC9BF3BF4A92598749AAA6049F26F39344339BE35E405DF00.

v0.5.0

Smaller discovery and dispatch results for host runtime 0.1.5-rc.1.

Default search results use dsh-progressive-tools/v3. An exact name returns that tool only, and each family member table appears once. tool_dispatch returns { protocol, tool, value } without copying rendered content. Set legacyResults to true to restore the previous envelopes.

Optional result budgets, coding and auto profiles, and small-catalog autoload stay off unless configured. estimatedSavedTokens estimates omitted top-level definitions. It is not a bill.

Validation: 73 tests passed. Type checking, lint, build, package validation, and peer checks passed. No paid task-cost comparison is claimed. PTC coverage uses a binding fixture, not language interpreters.

Install:

• dsh plugin --profile web add github:everclear077/dsh-progressive-tools#v0.5.0
• npm: dsh-progressive-tools@0.5.0

The attached tarball SHA-256 is C6AD9701258A0A1F8A2A891BECDA73C4281FBA2F6451162AA364F9BEBE514C34.

v0.4.0 - Runtime 0.1.5-rc.1 compatibility

v0.4.0 — Runtime compatibility and maintenance documentation

This release adapts progressive discovery to host runtime 0.1.5-rc.1.
Earlier host baselines are no longer supported by this version. Core peers
are pinned to the tested prerelease; later prereleases need separate validation.

Changes

• Migrate invocation IDs to ToolCallId and session access to snapshotEvents().
• Restore current PTC discovery logs and historical nested logs retained as ignorable events.
• Update asynchronous agent initialization and session projection setup in integration tests.
• Assert the real leading system message and serialized tool definitions across requests.
• Add PTC/both-mode regressions for both SDK languages, direct-call denial,
  argument validation, and discovery restoration after plugin reload.
• Align the existing validator dependency and test-time peer graph.
• Add onboarding, migration, troubleshooting, test scope, coding workflow,
  release/rollback instructions, roadmap, and contribution templates.

The 0.3.0 discovery capabilities remain: family-wide discovery, catalog
browsing, optional status grants, multilingual lexical matching, and compact
rendered discovery increments with cumulative recovery metadata.

Validation

• 46 tests pass across five suites.
• Type checking, lint, build, and package validation pass.
• No peer dependency conflicts in the release validation environment.

PTC tests use the real host dispatch bridge with a binding runtime fixture;
they do not run language interpreters. No live provider cache, cost, or task
success benchmark is claimed.

Upgrade

Use a host profile on 0.1.5-rc.1, install this plugin at tag v0.4.0, inspect
the profile config dump, and verify a fresh session before testing resume.
Options retain their names and defaults. Back up existing sessions: host
storage migration is separate from plugin discovery replay.

See migration, getting started,
and testing. The release includes a built package tarball
and SHA-256 checksum alongside the source archives. This GitHub Release does
not publish the package to an npm registry.