feat(deploy): drop the IaC layer, and make both apps runnable as containers

Moving the issuer's state into Postgres removed the last thing that tied
either app to one hosting provider. What was left was a deployment tool
describing resources that no longer existed — so this replaces it with
`wrangler`, which is what actually deploys a Worker, and adds a second way
to run each app that involves no provider at all.

Each app now has a `wrangler.jsonc` with an environment per stage, and a
`Dockerfile` beside it. The handler is the same one in both cases; what
differs is only where its settings come from. Two of them gained a second
spelling so that nothing has to branch on the runtime: Postgres arrives as
a pooled binding or as `DATABASE_URL`, and the route to the issuer is a
service binding or `AUTH_INTERNAL_URL`.

That last one is new, and it is a split the binding was already making
without saying so. `AUTH_ISSUER_URL` has to be the issuer's public name,
because it is compared literally against every token's `iss` claim — but
the public name is often not routable from inside a deployment. So the
name and the route are two settings now rather than one that cannot be
both.

DNS moves out of code and into `docs/dns.md`, which lists every hostname
and what it is for. Six records that change roughly never did not need a
tool, and the table outlives whatever is answering the names — which is
the point, since some of them will stop being Workers. The sandbox
hostnames are hyphenated rather than nested for the same reason: a
certificate covering `*.nestri.io` covers one label and not two, so
`api-sandbox.nestri.io` can become an ordinary origin later without a
certificate having to be ordered for it first.

Also drops `EMAIL_DEV_LOG` from committed configuration into `.dev.vars`,
which `wrangler deploy` cannot upload. Printing a live sign-in code to a
log should not be one forgotten override away from production.

CLAUDE.md

@@ -13,7 +13,7 @@ apps/       what runs        api, auth (TS) · nescope, neswire, nescapture, nes
                             nesdoctor (Rust, runs on the user's own machine)
 crates/     shared Rust      nesprotocol
 packages/   shared TS        core, auth
-docs/       long-form        alchemy.md
+docs/       long-form        deploy.md · dns.md
 ```
 
 Both toolchains live at the root: `package.json` is the Bun workspace,
@@ -22,7 +22,7 @@ Both toolchains live at the root: `package.json` is the Bun workspace,
 | | |
 |---|---|
 | `bun install` | dependencies |
-| `bun dev` | local Cloudflare dev via Alchemy |
+| `bun dev` | both control-plane apps locally, under the Workers runtime |
 | `cargo build --workspace` · `cargo test --workspace` | the Rust half |
 | `bun run deploy:sandbox` | deploy a stage |
 
@@ -96,8 +96,11 @@ them there rather than duplicating them here.
   actor model, the error type, auth flow.
 - [`apps/api/CLAUDE.md`](apps/api/CLAUDE.md) — route modules, registration,
   `.meta()` vs `.openapi()`, error flow.
-- [`docs/alchemy.md`](docs/alchemy.md) — infrastructure: stages, bindings,
-  secrets, service bindings, the CLI.
+- [`docs/deploy.md`](docs/deploy.md) — the two ways each control-plane app
+  runs (Workers via `wrangler`, and a container), the settings each needs, and
+  what is shared between them.
+- [`docs/dns.md`](docs/dns.md) — every hostname, what it is for, and the one
+  rule about their shape.
 
 ## Things worth knowing before you start