listen-handover-2026-09-21.md


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

---
name: listen-handover-2026-09-21
description: "SUPERSEDED — 2026-09-21 handover (artwork/player/queue-reorder); both its open items are resolved, see project_listen_tier3_fingerprinting.md for current state"
metadata:
  node_type: memory
  type: project
  originSessionId: 0e4bffd6-5847-4b40-9037-6bfb9055e654
  modified: 2026-09-27T00:51:05.003Z
---

**Superseded as of 2026-09-26.** This originally recorded two open items from the artwork/
player-screen/queue-reorder commit (`84ec886`); both are now resolved and this file is kept only
for the historical note on the amended-commit SHA mismatch, which cost a future session real time
once already.

- The artwork/player/drag-reorder work was verified on-device in a later tungsten session (see
  [[project_listen_android_auto]] and the Phase 2 commits that followed — Phase 2 as a whole,
  including Tier 3 fingerprinting, is now complete).
- `publish-apk` no longer needs to run on `tungsten` itself: it now takes `PUBLISH_SSH=tungsten`
  from another machine (Fedora) and sends the file over ssh, verified working
  2026-09-26 (published `listen-debug.apk` from Fedora successfully). See `devtools/README.md`
  for usage; no memory entry needed beyond this pointer since the capability is documented in
  the repo itself.

**Historical note, still worth keeping:** a commit made this session was recorded here as
`7f634ca`, which turned out not to exist in the repo — it had been amended before pushing, and
the real SHA was `84ec886`. A future session hunting for a commit that was never actually pushed
under the SHA a handover cites should suspect this class of mismatch, not assume the memory is
simply wrong about which repo it's in.

See [[workspace-git-remotes]] and [[project_listen_tier3_fingerprinting]] for current state.