Skip to content

v0.6.1 — DSH 0.2.0-rc.2 compatibility + A2A session-backend fix

Latest

Choose a tag to compare

@TimYuann TimYuann released this 29 Sep 18:21
· 11 commits to main since this release

orchestra-dsh v0.6.1

DSH 0.2.0-rc.2 compatibility + an A2A session-backend fix.

Why 0.6.0 could not be installed or booted on the current DSH

The host's bundle gate (@deepseek-ai/dsh-app-boot) compares the running DSH version against the
@deepseek-ai/dsh* peer ranges and rejects exact pins. 0.6.0 pinned 18 peers to exactly
0.1.7-alpha.1, so on 0.2.0-rc.2:

  • dsh plugin add refused the install (nothing was installed), and
  • even a hand-installed tgz was denied at boot — the whole bundle layer was skipped
    (skipping profile bundle "orchestra-dsh"), so no A2A tool ever registered.

0.6.1 declares ranges instead: >=0.1.7-alpha.1 <0.3.0 for the dsh-* packages, ^4.0.3 /
^1.0.8 / ^1.1.5 / ^1.0.4 for the cordis family, plus @deepseek-ai/cordis-plugin-group: ^1.0.4
(required by the cordis:group rows in the role presets). devDependencies moved to 0.2.0-rc.2.

Fixed: a2a_create(execution="session") failed on a stock deployment

Error: published permission "custom" does not match blueprint "workspace-write"

Every created session is pinned to approval: never (D2-a) after the permission preset is
applied, and the host derives the effective preset name from the live knob state — so any preset
that declares approval: ask (the stock read-only / workspace-write) stops naming a table entry.
The lightweight blueprint compared that derived name against the selected one, while the governed
path already had the effective-value accommodation. The commit now verifies the declared knobs
(declared sandbox + the pinned approval) and writes the declared sandbox explicitly, because the host
only writes a knob when it differs from the deployment default.

This defect is pre-existing (it is not an rc.2 regression); it was found by this round's live
verification.

Verification

  • tsc clean (host + client); 299/299 tests — 4 new regression tests, red without the fix.
  • npm pack: 81 files, @deepseek-ai/* never enters dependencies (only js-yaml).
  • Contract check against 0.2.0-rc.2 (npm packages + the shipped app bundle): every imported symbol,
    all 15 ctx.get services, the three events, and SESSION_FORMAT_VERSION (4 in both) unchanged;
    the cordis-family runtime JS is byte-identical across the version bump.
  • Live on DSH 0.2.0-rc.2 in isolated profiles: headless subagent round trip (A2A-PONG), headless
    session round trip (A2A-SESSION-PONG), web profile on port 4602 boots with orchestra-dsh/client.js
    in the boot module graph, and a GUI-driven session round trip (A2A-WEB-OK).

Scope of this release

A2A only, by instruction. The team / delivery layer is unchanged and still a draft plan; restart-surviving
role identity and Windows were not verified this round. Details: UPDATE-v0.6.1.md.