docs: drop closed queue gap from README's Deno Deploy paragraph

[davidwkeith]

Summary

• Follow-up to docs: document Fastly/Deno/AWS/GCP host feasibility in README #419 (root README's "Running it" host-feasibility documentation), per the review thread on that PR: feat(deno-host): KV-backed durable at-least-once queue emulation #418 landed after docs: document Fastly/Deno/AWS/GCP host feasibility in README #419 merged, implementing the KV-backed queue emulation (feat(deno-host): durable at-least-once queue emulation on Deno KV #399) for @dwk/deno-host.
• Updates the "Deno Deploy (exploratory — not yet a supported host)" paragraph in root README.md so it no longer claims the queue gap is open — it now correctly states that only the object-storage (R2Bucket-equivalent) adapter (feat(deno-host): R2Bucket-shaped object storage adapter over an S3-compatible store #400) remains gated, matching the current state of spec/packages/deno-host.md.

Packages affected

None (root README.md only — no publishable package touched).

Checklist

• Read the relevant spec(s) under spec/packages/ and updated them if behaviour changed — not applicable, no behaviour changed; this reconciles the README with spec/packages/deno-host.md's already-current state
• Added/updated colocated tests (src/*.test.ts) — not applicable, no code changed
• Ran the local CI gate: pnpm lint && pnpm format:check && pnpm typecheck && pnpm build && pnpm test — full gate passes (228 test files, 2759 tests)
• Added a changeset (pnpm changeset) if this touches a publishable package — not applicable, no publishable package touched
• Updated catalog.json / conformance/status.json if this adds a new mountable worker or changes conformance status — not applicable, no new worker or conformance change

[davidwkeith]

Reviewed against CONTRIBUTING.md.

Content: accurate and well-scoped. The updated paragraph matches spec/packages/deno-host.md's current status verbatim — the SQL shim (#397), single-writer actor/alarm lease (#398), and KV-backed queue (#399) are implemented, and only the R2Bucket-equivalent object-storage adapter (#400) remains gated. Good follow-up to #419/#418.

Conventions: commit message and PR title use Conventional Commits (docs: ...); omitting a (scope) is reasonable here since this touches only the root README.md, not a package. PR body keeps the template's Summary / Packages affected / Checklist headings verbatim and gives one-line reasons for the inapplicable checklist items, per the contributing guide.

One minor nit: the "Ran the local CI gate" checklist item is checked [x], but its note says only npx prettier --check README.md was run, not the full pnpm lint && pnpm format:check && pnpm typecheck && pnpm build && pnpm test sequence. For a markdown-only change that's a reasonable shortcut, but CONTRIBUTING.md asks for inapplicable/partial items to be left unchecked with the one-line reason rather than checked — consider flipping that box to [ ] (or just running the full gate, which is cheap here). Not blocking; CI's own build-test/release-gate jobs will catch any real regression either way.

No other issues found.

---

Generated by Claude Code

[davidwkeith]

Fixed the nit — ran the full local CI gate (pnpm lint && pnpm format:check && pnpm typecheck && pnpm build && pnpm test; 228 test files, 2759 tests, all passing) and updated the checklist item to reflect that instead of the partial prettier --check note. The github-advanced-security check failure is the same unrelated platform issue seen on #418/#419.

---

Generated by Claude Code