# Implementation Plans

Generated by the improve skill on 2026-06-12. Execute in the order below unless
dependencies say otherwise. Each executor: read the assigned plan fully before
starting, honor its STOP conditions, run every verification command, push
through the no-mistakes gate, and update your row when done.

## Execution Order & Status

| Plan | Title | Priority | Effort | Depends on | Status |
|------|-------|----------|--------|------------|--------|
| 001 | Establish Reproducible Verification Baseline | P1 | M | - | DONE |
| 002 | Validate CLI And Playlist Playback Inputs | P1 | M | 001 | DONE |
| 003 | Make Audio Selection Session-Scoped | P2 | M | 001 | DONE |
| 004 | Make Browser Render Loop Idempotent | P2 | S | 001 | DONE |

Status values: TODO | IN PROGRESS | DONE | BLOCKED (with one-line reason) |
REJECTED (with one-line rationale).

## Dependency Notes

- 001 must land first because the other plans rely on a dependency manifest and
  a one-command test path.
- 002 can run before or after 003/004 once 001 is done.
- 003 and 004 both touch playback synchronization surfaces. If one has already
  landed, the other executor must re-run drift checks and compare the app.js and
  stream_server.py excerpts before editing.

## no-mistakes Workflow For Executors

The operator requested this gate for implementation work. Use it after local
verification and before asking for review.

1. From repo root, run `rtk git remote get-url no-mistakes` to check whether the
   gate remote already exists.
2. If the remote is missing, run `rtk no-mistakes init`.
3. Work on a `codex/NNN-short-slug` branch unless the operator assigned another
   branch.
4. After local verification passes, run `rtk git push no-mistakes HEAD`.
5. Run `rtk no-mistakes` and review the active gate run.
6. Address gate findings inside the plan scope, or mark the plan BLOCKED if the
   gate requires out-of-scope changes.
7. Do not push to `origin`, merge, or open a PR unless the operator explicitly
   asks.

If `rtk` is unavailable in a future executor environment, run the same commands
without the `rtk` prefix.

## Findings Considered And Rejected Or Deferred

- Static root exposure via `/static`: intentionally ignored for now by the
  operator because this is a personal/self-hosted project. Reconsider only if
  the server is exposed beyond trusted local devices or sensitive local files
  are stored beside the app.
- License wording: real documentation/distribution issue, but lower leverage
  than runtime correctness and verification.
- Resize selection-layer drift: real UI issue, but lower priority than playback
  validation and audio/render synchronization.
- Pre-encoded frame cache, installable CLI package, and LLM-ready export path:
  direction options, not selected for this plan batch.