fix(preview): draw video layers, unlink Play from Loop, geometry last

Three reports from the creator, plus two bugs the real clip exposed.

1. A video layer was INVISIBLE in the preview. The pane's per-layer Image is Collapsed by
   default and switched on by a whitelist of DataTriggers; MediaSource matched none, so the clip
   decoded into a bitmap that nothing displayed. Same defect the alert box hit on 2026-09-26 and
   the scoreboard after it — now recorded at the top of docs/ai/ui-surface.md with a test that
   asserts the bound Image is Visible (`MediaPreviewDisplayTests`).

2. Play is no longer tied to Loop: the button is always enabled (creator ruling — Loop must not
   toggle Play). Loop still restarts a finished clip, which is the behaviour that was broken.

3. Geometry is now the LAST section of the properties list for every draggable element, with
   opacity at the top; the web source's duplicate geometry block is gone (it now uses the shared
   one, which had been sitting above the media panel).

4. The physical mouse-drag test is deleted. It injected real cursor movement, hijacked whatever
   machine ran it, and failed whenever the desktop was busy. The arithmetic it covered now lives
   in `Helpers/DragReorderMath.cs` — pure, and covered by `DragReorderMathTests` (threshold,
   up/down moves, no-op and out-of-range). The two persistence tests were already synthetic.

5. Real-clip check (creator's `test_greenscreen_moving_subject.mp4`, 1920×1080): the detector
   REJECTED it — a fully saturated green sits at value 1.0 and the detector's 0.98 brightness
   ceiling threw it away. White highlights are excluded by the saturation floor, which is the
   property that actually separates them, so the ceiling is gone. With it fixed, the clip is
   detected as green (high confidence), and keyed through our own pipe 97.8% of pixels go
   transparent. Measured: keying with the canonical #00B140 keys 0.0% of this clip — which is why
   the key colour comes from the measured screen.

Tests: 567 passed, 0 failed, clean build 0 warnings. The gate's scope check flags
`Assets/Videos/test_greenscreen_moving_subject.mp4` — the creator's working copy, deliberately not
committed; the fixture lives under ytLive.Tests/Fixtures.

Services/ChromaKeyDetector.cs

@@ -45,7 +45,11 @@ public static class ChromaKeyDetector
     // count against an otherwise perfect screen.
     private const double MinSaturation = 0.35;
     private const double MinValue = 0.15;
-    private const double MaxValue = 0.98;
+
+    // No upper brightness bound ON PURPOSE (found on a real clip 2026-11-05): a clean painted
+    // screen is fully saturated, so its value sits at ~1.0 and a 0.98 ceiling rejected the
+    // greenest possible screen. White highlights are excluded by the SATURATION floor instead,
+    // which is the property that actually separates them from a screen.
 
     // The screen's own pixels must agree with each other: a painted surface is flat, a lawn
     // is not. This is what keeps "green field" from being keyed.
@@ -82,7 +86,7 @@ public static class ChromaKeyDetector
                 if (frame.BgraPixels[i + 3] < 8) continue; // transparent: not the backdrop
 
                 var (hue, saturation, value) = ToHsv(r, g, b);
-                if (saturation < MinSaturation || value < MinValue || value > MaxValue) continue;
+                if (saturation < MinSaturation || value < MinValue) continue;
 
                 considered++;
                 if (hue is >= GreenHueFrom and <= GreenHueTo) green++;