Deploy the Worker with working Ed25519 verification

Discord validates the Interactions Endpoint URL on save — including a request with a deliberately bad signature it expects a **401** for — so the Worker must be deployed and verifying before the cutover issue can begin.

- [ ] `wrangler d1 create orrey`; put the `database_id` into `wrangler.jsonc` (currently `REPLACE_ME_AFTER_wrangler_d1_create_orrey`).
- [ ] Apply the phase-0 migrations remotely (`users`, `settings`, `jobs`).
- [ ] Create the `orrey-outbox` and `orrey-outbox-dlq` queues.
- [ ] Set the Discord public key, application id, bot token and client secret as Worker secrets — via `op run`, never on stdout.
- [ ] Deploy. Confirm `POST /interactions` returns 401 on a bad signature and answers `PING` with `PONG` on a good one.
- [ ] Confirm the four cron triggers and the two Durable Object classes are live.

Start by reading wrangler.jsonc and the phase-0 migrations, then review the listed Worker deployment steps for the D1 database, queues, secrets, cron triggers, and Durable Objects. Done means deployment succeeds, secrets are provided through op run, POST /interactions returns 401 for a bad signature and PONG for a good PING, and all listed triggers and classes are live.

索引モデルが issue の本文から書いたものです。