diff options
Diffstat (limited to 'listen-handover-2026-09-21.md')
| -rw-r--r-- | listen-handover-2026-09-21.md | 35 |
1 files changed, 35 insertions, 0 deletions
diff --git a/listen-handover-2026-09-21.md b/listen-handover-2026-09-21.md new file mode 100644 index 0000000..bb26798 --- /dev/null +++ b/listen-handover-2026-09-21.md @@ -0,0 +1,35 @@ +--- +name: listen-handover-2026-09-21 +description: State of the Listen app as of 2026-09-21 end of session — artwork/player/queue-reorder committed but unverified on-device; publish blocked on host name +metadata: + node_type: memory + type: project + originSessionId: 0e4bffd6-5847-4b40-9037-6bfb9055e654 + modified: 2026-09-21T22:00:48.962Z +--- + +Commit `7f634ca` ("Add artwork, a real player screen, and queue drag-reorder") landed on `main`, +gate-green (COVERAGE_EXCEPTION used for the expected Media3-glue drop, matching the four prior +uses in `listen/CLAUDE.md`). Implements the plan at Phase 2 pre-work Peter chose: artwork +(Coil3, pinned to 3.3.0 — later versions need a newer Kotlin/Compose than this project runs), +a real player screen (scrubbing, per-show persisted speed), and queue drag-and-drop reorder +(`sh.calvin.reorderable`). Android Auto real-car verification is still deliberately deferred. + +**Not yet done, pick up here:** +- **Never verified on a device.** No phone was connected this session (`adb devices` empty). + Build succeeded (`assembleDebug`), but nobody has actually looked at artwork rendering, + scrubbing, per-show speed persistence, or drag-reorder in the app. Do this first. +- **Not published.** `/workspace/devtools/bin/publish-apk` refused: it's hard-gated to a host + named `tungsten` (the deploy box), and this session ran on `fedora`. That gate is deliberate + (its own comment: bypassing it once caused a "deploy to a sandbox" mistake). This needs a + decision from Peter — publish from wherever `tungsten` actually is, or explicitly add `fedora` + to the allowlist in `/workspace/devtools/bin/publish-apk` — not something to route around + silently. + +**Why:** the session hit its weekly limit mid-flow; Peter needed to reboot to get device access +working and asked to just get the code built and committed rather than wait. +**How to apply:** next session, check `adb devices` first — if a phone is present, sideload via +`android-launch-check` and actually exercise the four features before considering this done. + +See also [[fedora-android-build-setup]] (still the environment this all ran under) and +[[workspace-layout]]. |