1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
|
---
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 `84ec886` ("Add artwork, a real player screen, and queue drag-reorder") landed on `main`,
(recorded here as `7f634ca` originally — that SHA is not in the repo, so the commit was
amended before pushing; `84ec886` is the one that exists)
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]].
|
