master sc delete --manifest exists: dry-run by default, identity verified in
BOTH directions (a permalink that now resolves to a different sc_id is a
refusal, not a warning), public tracks refused, a reason required per entry
because a deletion without provenance is not allowed, batch capped before any
API call, and a receipt that keeps every field plus the on-disk paths of the
archived artwork and the source FLAC. The old test-namespace gate was not
widened — a second gate was added beside it, and a test proves the old one is
unreachable from the new path.
Dry run: 14 deletable, 0 refused. All private, all uploaded in the same minute
on 2026-08-12, and every one still has its FLAC in Opal26_master/tracks/, so
deleting them loses a URL and not a recording. --go is NOT approved yet.
Two caveats recorded loudly rather than buried. The delete TRANSPORT is
unproven: no DELETE has ever been issued from this codebase against api-v2, and
a clean dry run is not evidence the deletes will land. And the generator's first
version lined stale uploads against the newest cut BY TRACK NUMBER — dropping
Desire renumbered REVOLUTION from 15 to 14, so the manifest confidently compared
Desire against REVOLUTION's duration. An unnamed reference, again.
Also logged: four of my own commits landed on a concurrent session's branch
because the shared checkout moved under me, and 'git push origin master' from a
non-master HEAD is a silent no-op that exits 0. Recovered via worktree
cherry-pick without touching their branch or the live tree. The worktree rule in
CLAUDE.md has no orchestrator exemption, which is what I had assumed.
two sessions, one working tree,
and a push that said yes to a question
it had never actually been asked.
