Point the arcade at the live registry

README.md

@@ -126,10 +126,9 @@ that does narrow the choice is the ABI: the registry picks the newest release
 your arcade can actually run, so a game that has moved on to a later ABI tells
 you to update termcade instead of handing you a package the host would refuse.
 
-The registry defaults to local dev (`http://127.0.0.1:8080`, the termcade-be
-stack) and will point at `https://api.termca.de` once that is deployed.
-`TERMCADE_REGISTRY` overrides it either way — which is how you reach a local
-stack after the default moves:
+The registry is `https://api.termca.de`. `TERMCADE_REGISTRY` overrides it,
+which is how you reach a local termcade-be stack (`make dev` serves one on
+port 8080):
 
 ```sh
 TERMCADE_REGISTRY=http://127.0.0.1:8080 termcade add you/mygame

internal/registry/client.go

@@ -27,13 +27,15 @@ import (
 	"github.com/aviorstudio/termcade/sdk"
 )
 
-// DefaultURL is the development default: the termcade-be stack on localhost.
-// It becomes https://api.termca.de when that is deployed and answering — and
-// not before, because this value is compiled into every released binary, so
-// pointing it at a host that is not up costs a release to undo. Until then,
-// TERMCADE_REGISTRY overrides it for anyone who wants to talk to something
-// else.
-const DefaultURL = "http://127.0.0.1:8080"
+// DefaultURL is the marketplace every released binary talks to.
+//
+// This was localhost until api.termca.de was deployed and answering, which was
+// the stated condition for moving it: the value is compiled in, so pointing it
+// at a host that is not up costs a release to undo. The host now serves.
+//
+// TERMCADE_REGISTRY overrides it, which is how you reach a local stack —
+// `make dev` in termcade-be still listens on 127.0.0.1:8080.
+const DefaultURL = "https://api.termca.de"
 
 // maxPackageSize matches the registry's publish-time ceiling.
 const maxPackageSize = 64 << 20