docs(tasks): archive the #50/#52 LED tail so the board shows only live work

armada/tasks/completed-archive.md

@@ -916,3 +916,20 @@ lessons: read identifiers, don't guess them; and a tool must not offer the reade
 choice it can make itself. `a4dc37b` makes the report decide from DATA RECENCY (not
 a process match, since `pgrep -f` has its own false-positive problem) and print
 either `● RECORDING NOW` or `the recorder was KILLED`.
+
+### #50 / #52 — LED colour tail (archived late, 2026-07-29)
+Two small completed LED tasks that never got an archive entry and were cluttering
+the board. Recorded here for completeness rather than value.
+
+**#50 — Value-reactive LED colour for gF1/gF2/gF3 (now that DJF audio is fixed).**
+A duplicate of #48, filed when the DJF audio bug was fixed and it became worth
+doing "for real". Superseded by the settled colour language in #11/#76 and by
+`81aecc9`, which corrected the report to model BOTH filter halves — see the
+`reference_djf_two_halves_and_event_lag` memory: hard right is an 8 kHz high-pass,
+not "open", so any value-reactive colour for row C must be bipolar.
+
+**#52 — Fix button-LED reverting to factory yellow on repeat press.**
+The "factory yellow" was never the device's default: it was a real Midi-Through
+feedback loop echoing note velocity 127 back as an LED colour byte
+(`reference_lcxl_midi_feedback_loop`). It regenerates on a Tidal reboot, so the
+symptom returning is not a regression in the LED code.