Tianyi Cui d1aae98895 docs(connection): describe native export handoff accurately ...

The fixture comment still said the Trajectory action used window.fetch after the implementation moved to a temporary download anchor. That wording implied client-side response handling and buffering which the browser-download design deliberately avoids.\n\nDescribe the actual native download-manager handoff while retaining the important contract: the fixture download stub only satisfies the host type and is unreachable through fixture dispatch.

2026-08-11 17:46:25 +08:00

..

client

docs(connection): describe native export handoff accurately

2026-08-11 17:46:25 +08:00

api-path.ts

feat(web): move connection downlinks to WebSocket

2026-08-04 16:07:35 +08:00

api-request-trust.ts

feat(connection): dispatch TypeRT remotes through shared API

2026-08-07 21:47:15 +08:00

http-bridge.ts

Merge remote-tracking branch 'origin/master' into worktree/web-multimodal-image-input

2026-08-08 01:56:29 +08:00

index.ts

build(vendor): rescope the vendored Cordis packages into @deepseek-ai

2026-08-10 22:04:13 +08:00

invariant.ts

build(vendor): rescope the vendored Cordis packages into @deepseek-ai

2026-08-10 22:04:13 +08:00

loopback-hostname.ts

refactor(client): expose loopback state through connection

2026-08-03 18:35:26 +08:00

rpc-host.ts

build(vendor): rescope the vendored Cordis packages into @deepseek-ai

2026-08-10 22:04:13 +08:00

rpc.ts

feat(connection): dispatch TypeRT remotes through shared API

2026-08-07 21:47:15 +08:00

websocket-downlink.ts

fix(web): quiesce websocket teardown

2026-08-04 16:42:50 +08:00