docs(spec): note project (boma) vs domain (wingu.me) in the naming scheme

Decided to keep the project named boma with wingu.me as its domain (boma was not
available as a domain). Record why the infra tier reads <host>.boma.wingu.me so it
isn't re-litigated; folds into the ADR-007 amendment.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

docs/superpowers/specs/2026-06-11-public-dns-gandi-migration-design.md

@@ -79,6 +79,10 @@ one-time purge + anti-spoof baseline.
 | Home / cluster services | `<service>.wingu.me` | internal zone (split-horizon) | only deliberate exceptions |
 | Off-site / VPS services | `<service>.askari.wingu.me` | Gandi LiveDNS | yes (askari has a stable public IP) |
 
+- **Project vs domain.** The project/homelab stays **`boma`** (ADR-007); **`wingu.me`** is
+  its domain. `<host>.boma.wingu.me` reads as "host in the `boma` compound, on the `wingu`
+  cloud" — kept distinct deliberately (`boma` wasn't available as a domain; the two layers
+  fit the self-hosting ethos). Folds into the ADR-007 amendment.
 - **`nyumbani` removed** — home is the default; only the exception (`askari`) needs naming.
 - **The mesh carries "internal" to road-warriors.** NetBird pushes `dns1`/`dns2` (over
   `wt0`) as resolver for the `wingu.me` match-domain → on-LAN-or-on-mesh resolves