For agents, on top of README.md, which they read first.

Notes for agents

Fix the note, not the check. When the deploy stops here, add a new entry at the top of RELEASES.md; never bypass the check to redeploy the same notes.

Storage is provisioned here, not by hand and not by wrangler at deploy time. resources.mjs reads the bindings from worker/wrangler.json, so a new D1 database or KV namespace needs only its binding there. Do not commit ids to make a deploy work, and do not rely on wrangler deploy's own provisioning: it creates a database too late to migrate it, and a KV title from a failed deploy is taken but bound to nothing. Its tests (resources.test.mjs) run on a fake wrangler; the command shapes and output fields it relies on were read from wrangler 4.132.0's source (d1 list --json rows name/uuid; kv namespace list rows title/id; --update-config=false skips the config prompt).