mesh: carry gateway_domain so peers can launch remote apps

The mesh payload didn't include a node's acme domain, so a peer had no way
to build launch URLs for another machine's exposed apps. Publish
gateway_domain in the MQTT registry payload and surface it per-deployment on
/mesh/deployments as `domain`. The dashboard palette and System Map now build
`https://<subdomain>.<domain>` for remote http-exposed apps (references use
their base_url), making primer's apps launchable from civil.

castle-api/src/castle_api/nodes.py

@@ -115,16 +115,18 @@ def _endpoints_of_registry(d: object) -> list[dict]:
 def mesh_deployments() -> dict:
     """Flattened remote (mesh-discovered) deployments with derived endpoints — the
     data the System Map needs to render other machines. Local node excluded (it's
-    already in /graph). Cross-node dependency *edges* need `requires` in the mesh
-    payload, which the registry doesn't carry yet."""
+    already in /graph). Each entry carries its node's `domain` (gateway acme domain)
+    so peers can build launch URLs `<subdomain>.<domain>` for exposed apps."""
     out: list[dict] = []
     for hostname, remote in mesh_state.all_nodes(include_stale=True).items():
+        domain = getattr(remote.registry.node, "gateway_domain", None)
         for _kind, name, d in remote.registry.all():
             out.append(
                 {
                     "name": name,
                     "kind": d.kind,
                     "node": hostname,
+                    "domain": domain,
                     "port": d.port,
                     "base_url": getattr(d, "base_url", None),
                     "subdomain": d.subdomain,