From 666f36c258ecf5a9c555f4cf9718a1e4520be751 Mon Sep 17 00:00:00 2001 From: Claude Date: Fri, 31 Jul 2026 10:59:38 -0400 Subject: [PATCH] Record lance.blue as the domain, and a future regression-test task Domain is purchased: lance.blue. Replaces the open "pick a name" item. Notes the two consequences that follow - player handles become callsign.lance.blue, so the AppView must serve ATProto handle resolution for subdomains and TLS needs a wildcard cert. Adds a deferred task to regression-test against a MegaMek built from source rather than the pinned 0.51.0 release. Today there is no signal for upstream breakage: patches silently failing to apply, the Webswing incompatibilities returning, or new heavyweight AWT components appearing. Explicitly future work, not scheduled now. Co-Authored-By: Claude Opus 5 --- TODO.md | 12 ++++++++++-- 1 file changed, 10 insertions(+), 2 deletions(-) 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. -- 2.51.2