Phase 0 — Footings

**Status: in progress.** The Worker/Hono/D1/Drizzle skeleton is in place (`c54d0bd`), with Ed25519 verification and the four-command surface defined. Nothing has been cut over.

Retires the biggest risks first: the unverified Google auth pattern, and the one-way Discord cutover. Sub-issues are **strictly in order** — the cutover can't happen until the Worker is deployed and verifying, and the Hermuz ids must be captured before that repo is archived.

Exit criterion: a posted message whose button click round-trips to D1 and rewrites that message as its interaction response, in the real guild, on the repurposed Hermuz application.

## In order
1. #10 — Copy Hermuz's SQLite as the id lookup, note the ids, archive the repo
1. #11 — Prove the service-account calendar pattern by hand
1. #12 — Deploy the Worker with working Ed25519 verification
1. #13 — Cutover — save the Interactions Endpoint URL and retire Hermuz
1. #14 — Smoke test — a button click round-trips to D1 and rewrites its message
1. #15 — Privacy policy and delete-my-data path (ship now, not later)