Launchpad 0.52.0 alpha — build 260923001

This testing release combines the native macOS app with Launchpad server 0.52.0. The built-in server includes its Bun runtime; no separate Bun or Node.js installation is needed. Docker is required to run local apps.

Apps that answer at more than one name
- A Launchfile can now declare the names an app answers at (`at:` on a `provides` entry, Launchfile D-68). Launchpad routes every declared name or refuses the launch before anything is created, naming the entry and the value it cannot route.
- You can launch such an app on the apex of a domain you own, for example cogzero.com. Launchpad allocates exactly the declared names (dash.cogzero.com, auth.cogzero.com, ...) and leaves the apex untouched.
- The launch sheet shows the names the app declares. They come from the app, so there is nothing to toggle.
- A name two or more levels below your zone is routed, but Cloudflare's Universal SSL does not cover it. Launchpad says so in the routing step rather than failing.
- Refreshing an app follows its Launchfile: names added or dropped since the last launch are published or withdrawn.
- This is a feature of a Launchpad that owns its routing domain, which the built-in server does. A shared multi-tenant Launchpad refuses these apps.
- On your own domain, the names `api`, `www`, `admin`, `mail` and `auth` are yours: an app may be named one or declare one. Only `launchpad` and `localhost` stay reserved. A shared multi-tenant Launchpad keeps all of them.

Also in this release
- Setup commands that print a link resolve it against the app's published address.
- The built-in server's shared service pool is released when the last app is removed, and recreated on the next launch from the same data.
- When the built-in server reports a different identity than expected, the message says which one did not match and names a stale server.
- Server settings say when a saved Cloudflare token is not in use because routing is Local only.
- A release build checks its notarization profile before building anything.

Own domain, name choices and declared names need a server that supports them. The built-in server in this release does. A server you connect to by address shows the declared names only once it runs Launchpad 0.51.0 or later.

Alpha limitations
- Once an installation has begun, it cannot be undone. Launchpad cannot prove that the installer has exited, so it will not restart the previous server behind it. If an install is cancelled or interrupted, finish it by downloading this release and replacing Launchpad yourself, then reopening it.
- Installing an update requires the built-in server to be running and reachable. Servers you connect to by address are updated separately by their owners.
- Signing and notarization verify the package, not successful Cloudflare configuration or Gate acceptance on your machine. Those remain alpha testing targets.
- Names two levels below the app's host (`*.*`) are refused: no hostname front door can route them.

Closing or quitting Launchpad leaves its registered built-in server running. Use the app's server controls to stop it. Running app containers are separate from the control-plane UI.