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

docs(i18n): bilingual pair for the web e2e lane Agent Note

Browse Source 
Chinese counterpart translated per the terminology table and the
2026-07-18 TUI note's register; switcher lines added on both sides; pair
recorded. doc-sync 24/24.
This commit is contained in:
Tianyi Cui
2026-07-24 21:06:54 +08:00
parent d08050ab69
commit 8f97f95d7b
3 changed files with 98 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
.agents/notes/implemented/testing/2026-07-24-web-gui-browser-e2e-lane.md
View File

@@ -2,6 +2,8 @@
Status: implemented
English | [中文](2026-07-24-web-gui-browser-e2e-lane.zh.md)
## Problem
The web GUI ships as a real assembled chain — chromium page → client plugin bundles → HTTP unary RPC + two SSE streams → `toFetchHandler`/apiproxy → `bootHost`'s agent loop, tools, and JSONL persistence — and no test exercised that chain keylessly and deterministically. The [GUI testing system](../process/2026-07-20-gui-testing-system.md) covers tier 1 (wire isomorphism in node), tier 2 (object-layer state machines), and tier-3 smokes, but the keyless smoke drives `FixtureApiClient` — no host, no wire, no agent loop — while the full-chain smoke needs `DEEPSEEK_API_KEY` and a live model, so it is nondeterministic and self-skips in keyless CI. The snapshot philosophy of [docs/testing.md](../../../../docs/testing.md) — record once with a key, replay forever keyless, refresh on format churn — already covers the ACP, headless `stream-json`, and TUI transcript surfaces; the web surface was the one assembled product shape without it. The gap is exactly where the two confirmed GUI P0s hid: the wire carriage chain the fixture client short-circuits.