Repository navigation
Run the #204 live-E2E scenarios on Orbit (adapter + entrypoint, not exercised) #209
Closed as not planned
Description
Follow-up to #204 (same pattern as #198: a planned integration, marked not exercised — nothing in this repo references Orbit's entrypoint yet).
#204 delivers app-independent scenario/fixture/assertion modules in dev/live-e2e/ plus the adapter contract (docs/interop/live-e2e-adapter.md) and one implementation: the FlyBot web adapter. Running the same four checks on Orbit needs:
- An Orbit adapter implementing the contract (uploadFile / sendTask / settle / deliveredFiles / openPreview / reload / conversation / screenshot) against Orbit's real UI.
- A runner wiring that adapter to the shared scenarios, with Orbit's own isolation and teardown.
- Evidence that a real run passed on Orbit's entrypoint (report in the Add real-model browser E2E nightly tests with reusable scenarios #204 schema).
Until both adapters have run the same scenarios, "the scenarios are reusable" is a design claim, not a verified fact.
Activity
Add the real-model browser E2E suite of #204
Add the real-model browser E2E suite of #204
Birfy commentedon Oct 18, 2026
Orbit live-E2E still out of scope for routine maintenance; leaving open.
Birfy commentedon Oct 19, 2026
Triage on main
7b9e90b, 2026-10-19 ~12:10 Asia/Shanghai: needs-human, not agent-ready. Needs an owner call: is the Orbit adapter in scope for FlyBot now, and who provides access to Orbit's entrypoint? Without that it cannot be developed or verified here.Birfy commentedon Nov 6, 2026
Written-by: Chief
移动端这一簇的分拣结论：关掉这一条，不派活。
dev/live-e2e/、docs/interop/live-e2e-adapter.md）不受影响，"场景可复用"的验证现在由 web 适配器和免 key 的 mock e2e（A browser E2E that runs without DEEPSEEK_API_KEY: drive the web UI against the scripted mock #2565）承担。等哪天 PWA 之外真的要接 Orbit，按 #204 的契约补一个适配器就是新 issue，不需要靠这条挂着。不同意这个结论就重开，我不再单独问。