---
model: openai/gpt-5.6-sol
service: opencode
session: 8737d0a9-98da-4fa1-ba35-ca8a3a42bbc9
timestamp: 2026-09-03T19:27:44Z
git_ref: wkt/replay_provider_e2e
scope: docs
substantive: true
raw_file: 20260903T192744Z_aadfd1cf_prompt_io.raw.md
---

## Prompt

Perform a deep review of the human-facing E2E plan against real broker
and application machinery. Prioritize booting production charts against
mostly continuous live backends, isolate tests from any production Piker
instance on the host, put replay entirely on hold, and provide immediate
practical next steps for Qt plus Trio application testing.

Record the package-entry-point replay move as a follow-up if replay is
ever resumed.

## Response summary

Reorients the roadmap around the actual application blockers and a live
Kraken vertical slice. The review separates test boundary from data
source, defines exact runtime isolation, specifies a nonblocking
`QtractorSession`, and defers replay until a real regression supplies a
concrete reason for controlled input.

## Files changed

- `plans/opencode/live-backend-chart-e2e-review.md` - record the revised
  live-backend-first roadmap, lifecycle seam, isolation contract, and
  replay/plugin resumption design.

## Human edits

The human rejected deterministic replay as the organizing prerequisite
for E2E, prioritized failures observable through real broker and chart
machinery, selected the Qt/Trio lifecycle as immediate work, approved a
live Kraken chart journey followed by real interactions and installed
process coverage, and required replay to remain parked unless motivated
by a concrete regression. The human also required the future replay
move to use general package-entry-point backend support and explicitly
approved provenance capture for this design document.