docs: mark SDDM greeter conflict resolved in bring-up tracker

local/docs/REDBEAR-FULL-SDDM-BRINGUP.md

@@ -53,16 +53,14 @@ spawns `redox-drm` (priority-61 for virtio/Intel/AMD) → `/scheme/drm/card0`
 `redbear-compositor` → SDDM greeter Qt/Wayland UI. Needs `dbus`, `seatd`,
 `redbear-sessiond`, `redbear-authd` (all `requires_weak` on sddm).
 
-**CONFLICT (must resolve for a clean SDDM greeter):** three display entry points
-all fire as `oneshot_async`, each trying to own the GPU/card0/VT:
-- `20_display.service` → `redbear-session-launch` (KDE session, VT 4)
-- `20_greeter.service` → `redbear-greeterd` (custom RedBear greeter, VT 3)
-- `21_sddm.service` → `sddm` (the target)
-For the SDDM path, `20_display` and `20_greeter` should be disabled (GPU/DRM is
-single-owner). This is a service-removal decision → **needs operator sign-off**
-(policy: only the user authorizes removing services). Options: (a) disable the two
-competing units for the SDDM path, or (b) confirm SDDM is the chosen greeter and
-the others are legacy.
+**CONFLICT — RESOLVED (`9f528397`, operator: "SDDM is the only greeter"):** three
+display entry points fired as `oneshot_async`, each contending for the
+single-owner GPU/card0/VT: `20_display` (redbear-session-launch KDE session),
+`20_greeter` (redbear-greeterd), `21_sddm` (target). The first two are now gated
+off reversibly via `condition_path_exists = ["/etc/redbear/enable-legacy-greeter"]`
+(sentinel not installed; `touch` it to re-enable). `21_sddm` runs ungated.
+Post-login session launch is SDDM's job (`SessionDir=/usr/share/wayland-sessions`
+— note: no session `.desktop` is defined there yet; that's a post-prompt task).
 
 ## Build notes / deficiencies fixed
 - Full builds re-cooked llvm21 (~1-2h) on every base/relibc bump — fixed in Phase 0.