dsh-ears imports TypertLookupFailure from @deepseek-ai/dsh-typert-protocol, but no published protocol version exports it

[wh1te-sn0w]

Summary

npx @deepseek-ai/dsh web fails at boot because dsh-ears still imports TypertLookupFailure, which @deepseek-ai/dsh-typert-protocol no longer exports.

Reproduction

npx @deepseek-ai/dsh web

Fails with:

Error: dsh: plugin tree failed to load: failed to apply loader entry include (cordis:include): failed to import loader entry dsh-ears (dsh-ears): The requested module '@deepseek-ai/dsh-typert-protocol' does not provide an export named 'TypertLookupFailure'

file:///C:/Users/jackdai/.dsh/profiles/web/node_modules/dsh-ears/lib/index.js:5
import { TypertLookupFailure, TypertRemoteService } from "@deepseek-ai/dsh-typert-protocol";
         ^^^^^^^^^^^^^^^^^^^
SyntaxError: The requested module '@deepseek-ai/dsh-typert-protocol' does not provide an export named 'TypertLookupFailure'

Versions involved

Package	Version
@deepseek-ai/dsh (CLI, latest)	0.1.5-rc.2
@deepseek-ai/dsh-typert-protocol (resolved by the above)	0.1.5-rc.2
dsh-ears (loaded into the web profile)	0.2.2

Evidence

1. dsh-ears@0.2.2 lib/index.js:5 imports the removed symbol:

   import { TypertLookupFailure, TypertRemoteService } from "@deepseek-ai/dsh-typert-protocol";

2. @deepseek-ai/dsh-typert-protocol@0.1.5-rc.2 has zero occurrences of LookupFailure across lib/ (grep -r LookupFailure lib/ → 0 matches). Its value exports are:

   RemoteError, remoteErrorOf, Remote, RemoteScope, TypertRemoteService, bindTypertRemote, isTypertRemoteSegment, remoteMethods, typertOwnedValue, isTypertOwnedValue, TYPERT_OWNED_VALUE (plus type-only exports).

3. The failure vocabulary was collapsed: TypertLookupFailure and TypertRemoteFailure were replaced by RemoteError<Code> — see packages/typert/protocol/src/index.ts and the design note .agents/notes/implemented/architecture/2026-08-28-ctx-remote-failure-vocabulary.md (status: implemented). Neither 0.1.5-rc.2 nor the also-published 0.1.6-alpha.2 exports TypertLookupFailure.

Expected

dsh-ears@0.2.2 was published against the older failure vocabulary and is incompatible with the latest dsh release. Either:

• republish dsh-ears against the RemoteError API, or
• have @deepseek-ai/dsh@latest pin a compatible dsh-ears version.

Environment

• OS: Windows 11
• Node: v24.14.1

[PerryLink]

Your protocol-side analysis is correct, but the target is wrong: dsh-ears is not a DSH package,
and the fix is already published.

1. This repository cannot pin it

git grep -n "dsh-ears" HEAD returns nothing. dsh-ears is a third-party plugin
(github.com/WizisCool/dsh-ears, maintainer wiziscool) installed into your web profile. Nothing
in @deepseek-ai/dsh depends on it or constrains it, so there is no version for the harness to
pin.

2. Your diagnosis of the protocol side is right

TypertLookupFailure was a named runtime export of the protocol barrel, and it was deliberately
removed on 2026-08-28 by 804b1ff, "refactor(api): converge the Remote failure vocabulary and
client surface", which replaced TypertRemoteFailure/TypertLookupFailure with RemoteError<Code>.
Before that commit it is at packages/typert/protocol/src/index.ts:25; at HEAD the barrel exports
RemoteError and remoteErrorOf instead.

I checked the published tarballs rather than trusting the changelog. The boundary is:

exports it: through 0.1.1-rc.2 (last one)
does not: 0.1.2-alpha.2 onward, including 0.1.5-rc.2 and 0.1.6-alpha.2

So "no published protocol version exports it" is true for every version you could resolve against
@deepseek-ai/dsh@latest (0.1.5-rc.2 -> protocol 0.1.5-rc.2), but not literally true of the whole
history.

3. The mechanism, for anyone hitting the general case

dsh-ears@0.2.2 declared "@deepseek-ai/dsh-typert-protocol": "*". A wildcard peer range accepts
a host that dropped the symbol, so nothing fails at install time. Its bundle is ESM, and a missing
named export is a link-time error: SyntaxError: The requested module ... does not provide an export named 'TypertLookupFailure', thrown before your plugin ever runs. That is why one stale
plugin takes down the whole plugin tree at boot rather than failing on its own.

4. The fix is one line on your side

dsh-ears@0.3.0 already replaced the import with remoteErrorOf and narrowed the peer range to
>=0.1.2-rc.1; 0.3.2 is current. Upgrade the plugin and the boot failure goes away. Reproducing
with 0.2.2 is expected, not a DSH regression.

5. One trap worth knowing

The protocol package's own npm latest tag is still 0.1.0-rc.6, which does export the old
symbol, while @deepseek-ai/dsh@latest resolves the protocol to 0.1.5-rc.2, which does not. A bare
npm i @deepseek-ai/dsh-typert-protocol therefore lands on an incompatible surface. Version skew
here is on the plugin axis, not the protocol axis.

I did not install dsh-ears to reproduce the boot failure, and I checked 11 of the 21 published
protocol versions -- the boundary is confirmed at both ends, but a few intermediate versions were
not opened.