docs(log): 041 — perf redeploy landed, 183 Pulsar crashes to 0

PLN ran the root install at 20:06. Verified rather than assumed: the
deployed /usr/local/sbin/perf-audio md5 matches the repo copy, the bug's
fingerprints (nohup pulsar, SCRIPT_DIR) are absent from the deployed
script, and prioritization is retained.

Behavioural confirmation is the part worth keeping: the Bridge's perf
watcher still reasserts every cycle, but now only prioritizes -- no
launch attempts in the journal -- and the last Pulsar SIGABRT in
coredumpctl is 15:58:44, before the deploy. The counter that ran 183 deep
since 2026-08-19 has stopped.

armada/tasks/041-parked-gigup-rewire.md

@@ -65,10 +65,13 @@ replaces: one wrong click could kill a running Ardour during a set.
 - Three-state label so the click always says what it will do.
 
 ## Also outstanding (discovered, not parked code)
-- `perf.sh` fix is committed but **NOT LIVE**: needs
-  `sudo install -m755 -o root -g root perf.sh /usr/local/sbin/perf-audio`
-  (outside the sudoers whitelist, so PLN must run it). Dormant meanwhile — the
-  removed block only fired when no Pulsar was running.
+- ~~`perf.sh` fix committed but NOT LIVE~~ — **DONE 2026-09-05 20:06.** PLN ran the
+  redeploy; `/usr/local/sbin/perf-audio` md5 now matches the repo copy exactly,
+  `nohup pulsar`/`SCRIPT_DIR` are absent from the deployed script, and the Pulsar
+  prioritization is retained. Verified after: the Bridge's perf watcher reasserts
+  normally ("✓ Set Pulsar to HIGH priority" / "Ardour process not found -
+  skipping") with **no launch attempts**, and the last Pulsar SIGABRT of all time
+  is 15:58:44, before the deploy. Final count: **183 crashes → 0.**
 - `gig-up.sh` verdict was **NO-GO**, four pre-existing blockers unrelated to
   this session's changes: boot helpers (ghc error → `tools/check-boot.sh`),
   surface grid (`tools/check-drift.sh`), mute map