diff --git a/TODO.md b/TODO.md
index e5acef8..959910b 100644
--- a/TODO.md
+++ b/TODO.md
@@ -38,8 +38,10 @@ theming.
 
 ## Next steps
 
-**Domain name** — avoid Topps/CGL marks. Note it becomes users' ATProto handle
-suffix (`natasha.example.gg`), so short and pronounceable matters.
+**Domain — `lance.blue`, purchased.** Trademark-safe ("lance" is generic
+military as well as a BattleTech formation). Player handles become
+`callsign.lance.blue`, so the AppView needs to serve ATProto handle resolution
+for subdomains, and TLS needs a wildcard cert.
 
 **Fargate architecture** — one match per task. Scenario via S3 presigned URL;
 player camo fetched from their PDS at challenge time and cached by CID, never
@@ -65,3 +67,9 @@ input the model is most sensitive to. Measure a few human 4v4s.
 - **Trimmed data dir unverified** — `slim-data/` (221MB vs 932MB) loads the unit
   cache but hangs before the game starts. Affects image size and cold start.
 - **Upstream both patches** — each is a latent MegaMek bug, not an adaptation.
+- **Regression-test against a local MegaMek build** *(future, not now)* — today
+  everything is pinned to release 0.51.0. There is no signal for when an upstream
+  change breaks us: patches failing to apply, the Webswing incompatibilities
+  returning, or new heavyweight AWT components appearing. Build MegaMek from
+  source and run the harness plus a scripted browser session against it, so
+  upstream breakage surfaces before a release pins it in.