PLN opened the session hearing badly-cut begin/end on the private OPAL
uploads. Measured all three render generations against what the board
recorded on the account: /take-five-drops sits at 6:57 = 417 s, which is
exactly the Aug-12 first cut — four days and two boundary revisions before
the ear-verified v4. The complaint had a mechanical cause.
Ruled out before believing anything: tracks_v4_streaming matches
segments_v4.json to the millisecond on all 14 (CRIME's 2s rest and
REVOLUTION's reverb tail included), the upload plan's titles/files/durations
are aligned and exact, and the ear file's 19:33 mtime is the signoff record
being written, not a later boundary edit. Nothing needs re-cutting; the
approved audio is already on disk. This is a re-upload problem.
Two things stand in the way and one of them is PLN's call: SCW.delete() is
hard-gated to the test namespace so we cannot remove our own stale uploads,
and SoundCloud skips rather than replaces an existing permalink. Also: no
sc_state.json was ever written, so the account is the only record of what
landed — sc pull --artwork recovers ids, permalinks, durations AND the covers
PLN asked to save, read-only, in one pass.
Plus the catalog answer he asked for (generated.json is 2 gigs stale behind
the view, 14 gigs uncatalogued), www's OPAL tracks.json still on segments_v3
where Slopmotion reads it, the CLAUDE.md next/ path that no longer exists,
and two stale-opens git says already shipped.
