docs: plasma/output integration guide for game and sim integrators

Lamp address map by functional group (keypads have no lamps), 112x32 plasma
model with auto-fit font rules and update semantics, rate-budget guidance,
and recipes: rumble config, DCS Export.lua, SimHub, log tailing, vRIO/vPlasma
bench testing. Cross-linked from FEEDBACK.md (now the wire reference) and
README; corrects the lamp count there (72, per CockpitPanel, not 96).

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

docs/FEEDBACK.md

@@ -1,11 +1,16 @@
 # Game feedback endpoint (game → RIOJoy → cockpit)
 
 Phase 9 lets external programs drive the cockpit's **output** hardware through
-the running RIOJoy tray app: the 96 lamps (with board-side flash) and the
-plasma/VFD text display. Anything that can write a line of text to a named pipe
-or a UDP socket can use it — a DCS `Export.lua`, a SimHub plugin, a game mod, a
-PowerShell one-liner. XInput **rumble** is mapped separately (no client needed;
-see [Rumble → lamps](#rumble--lamps)).
+the running RIOJoy tray app: the 72 button lamps (with board-side flash) and
+the plasma/VFD text display. Anything that can write a line of text to a named
+pipe or a UDP socket can use it — a DCS `Export.lua`, a SimHub plugin, a game
+mod, a PowerShell one-liner. XInput **rumble** is mapped separately (no client
+needed; see [Rumble → lamps](#rumble--lamps)).
+
+This page is the wire-protocol reference. For the integrator's view — which
+lamp addresses map to which physical buttons, the plasma display's geometry
+and fonts, and per-game recipes — see
+[OUTPUT-INTEGRATION.md](OUTPUT-INTEGRATION.md).
 
 ## Endpoints