Pine/deepseek-harness
1
0
Fork 0
Code Issues Pull Requests Actions 1 Packages Projects Releases 1 Wiki Activity

docs(connection): describe native export handoff accurately

Browse Source 
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.
This commit is contained in:
Tianyi Cui
2026-08-11 17:46:25 +08:00
parent c626d5f53c
commit d1aae98895
1 changed files with 2 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files
packages/client/connection/src/client/fixture.ts
+2 -2
View File
@@ -2835,8 +2835,8 @@ function createFixtureWorld(options: FixtureOptions): FixtureWorld {
return Promise.resolve({ accepted: true }) return Promise.resolve({ accepted: true })
}, },
// Satisfies the ApiProxy contract type only: the browser export button // Satisfies the ApiProxy contract type only: the browser export button
// fetches GET /api/session.export directly (window.fetch), so this stub is // hands GET /api/session.export to the native download manager, so this
// never reached through the fixture's dispatch. // stub is never reached through the fixture's dispatch.
downloads: { downloads: {
sessionLog: () => Promise.resolve(new Response('fixture mode does not serve session export', { status: 404 })), sessionLog: () => Promise.resolve(new Response('fixture mode does not serve session export', { status: 404 })),
}, },