31 lines
1.2 KiB
Markdown
31 lines
1.2 KiB
Markdown
---
|
|
model: openai/gpt-5.6-sol
|
|
service: opencode
|
|
timestamp: 2026-09-03T19:27:44Z
|
|
git_ref: wkt/replay_provider_e2e
|
|
diff_cmd: git diff HEAD~1..HEAD
|
|
---
|
|
|
|
## Generated document
|
|
|
|
> `git diff HEAD~1..HEAD -- plans/opencode/live-backend-chart-e2e-review.md`
|
|
|
|
Reviews the original replay-centered phase order against the actual
|
|
Qt/Trio host, chart startup, real backend, runtime isolation, and test
|
|
harness machinery. It parks replay, promotes the nonblocking production
|
|
application seam and live Kraken chart journey, defines exact isolation
|
|
and teardown expectations, and records package-entry-point migration for
|
|
any future replay resumption.
|
|
|
|
## Review conclusions
|
|
|
|
- Replay is not a technical prerequisite for Qt/Trio lifecycle work.
|
|
- `run_qtractor()` blocking, discarded guest outcomes, pytest-qt app
|
|
shutdown, process-wide close SIGINT, and missing readiness are the
|
|
immediate blockers.
|
|
- Existing XDG, config, Qt, and registry isolation is reusable.
|
|
- A public Kraken chart can exercise real REST, WebSocket, datad,
|
|
samplerd, SHM, paper EMS, rendering, input, and teardown machinery.
|
|
- Replay should return only for a concrete captured payload, race,
|
|
network-free CI requirement, or fault-control regression.
|