feat(setbuilder): the picker now holds the catalog it already measured
The sweep evaluated all 703 tracks on Sunday night and found 597 that compile and emit. The picker still carried fourteen hand-written entries, so the page said the library was fourteen deep — the measurement existed and the surface that needed it did not have it. gen_setbuilder_catalog.py turns the sweep into the page's data, joined against two things the verdict alone does not tell you: how often the driver journal saw the track loaded (what the hands know), and how many of its sample banks the preload plan already warms (a cold bank is not a fault, it just hiccups on the first bar). Sample names come from setlist_samples.py, never a fresh regex. The sweep results now live in docs/ instead of a scratchpad that dies with the session — an artifact nobody can compare against is the preload.scd story. Ids are repo-relative paths, not stems. Sixteen stems collide across folders (major_nostalgia in chill and techno, all four FFF tracks in two trees) and a stem key merged each pair into one card, silently. Picks stored under the old stem keys are migrated on load where the stem is unambiguous. And the Thu-24 list is a candidate arc, not a locked set. It was exported from the builder, not decided at the desk; rehearsal decides.
Showing
armada/setbuilder-data.js
0 → 100644
docs/2026-09-22-catalog-playability.tsv
0 → 100644
tools/gen_setbuilder_catalog.py
0 → 100644
Please
register
or
sign in
to comment