KB: camera-seat/broadcast system investigated -- cameras\ data missing

The CameraShip spectator system is engine-complete (CameraDirector
auto-follows the score leader, CAMSHIP cuts between fixed map camera
positions like TV coverage, ranking window flashes 10s/15s + final
30s), but the per-map cameras\<mapname> notation files are absent from
the archive -- added to the get-from-Nick list with the reconstruction
alternatives (author our own / chase-cam fallback) and the two code
gaps (stubbed ranking-window draw, camera vehicle never boot-tested).

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

context/open-questions.md

@@ -28,6 +28,14 @@ authentic path scoped.
   ERMLaser_2/3 (back gun ports) are the only rear weapons in the roster; see [[combat-damage]].
   Remaining: bind the side/down look views to keys (only 'V' look-back is bound); pod look-button
   mappings for Phase 8.
+- **The `cameras\` directory (per-map camera-network files)** — the CameraShip spectator/broadcast
+  system (2026-07-18 investigation) is engine-complete (DIRECTOR.cpp auto-follows the score
+  leader; CAMSHIP.cpp cuts between FIXED map camera positions like TV coverage), but the data is
+  missing: `CameraInstanceManager::ReadNotationFile` loads `cameras\<mapname>` (name = the map
+  resource's, CAMMGR.cpp:390-415) and our archive has NO cameras directory. Without it a camera
+  seat has no shot network. Alternatives if lost: author our own per map, or a chase-cam
+  fallback. Also unreconstructed: the ranking-window draw (L4VIDRND.cpp:3016 visibility calls
+  stubbed) + `vehicle=camera` never boot-tested. Status: OPEN.
 
 ## Pod-hardware readiness gaps (Phase 8 assessment, 2026-07-17) [[pod-hardware]]
 Everything below EXISTS in the tree but has NEVER run against real pod hardware.  Mechanism