The /pre-compact ritual archives completed board tasks somewhere durable before
clearing them, so the learnings survive the task disappearing. armada/tasks/
completed-archive.md already does this — but its header scopes it explicitly to
L'Armada, the media/marketing toolbox. Gig prep is a different thread, and mixing
two documentary trails in one file makes both worse to mine later. Same discipline,
separate file.
Seven finished tasks captured in the established description/done/learnings/deps
shape: #15 runbook, #21 mute-bomb, #32 recorder, #19 disk archive, #9 launcher,
#27 highlight jitter, #5 HUD version control.
The learnings are the point, not the inventory. The ones worth re-reading:
- #21: a fix that lives only in a running process is not a fix. The gF rewrite was
correct and live-validated for a full day while still being one SuperCollider
reboot away from silently rearming. "Live-confirmed" and "durable" are different
states and the gap between them is where this class of bug hides. The deeper
design lesson: make rest position == no effect. The bug was never really the
missing djfbus, it was that the hardware's DEFAULT state sent an EXTREME value.
- #9: order beats retry. The MIDI dance was a race symptom; gating on observable
readiness (three independent checks, not a sleep) removed the race rather than
automating the workaround. And idempotence is the property you want from anything
you might run while panicking.
- #15: a frozen Pulsar does not stop the audio — patterns live in ghci, not the
renderer — which inverts the instinct to panic-kill the editor.
- #19: du-deleted (436GB) vs df-freed (160GB) disagreed sharply; btrfs zstd + reflink
sharing explains it, df is authoritative, don't chase the gap.
- #27: border participates in layout and reflows text, outline does not — for any
decoration toggling at performance rates, outline is the correct primitive.
- #5: the HUD, pulsar-tidalcycles, and ~/.pulsar/styles.less are three separate
version-control domains (the last untracked entirely, as user config). One visual
bug can need coordinated edits across all three, which is exactly what #35 hit.
