Fix stale Scanner backend maintenance guidance

[Talonsturgill]

What changed

• correct the Docket repository map to describe the deployed Scanner Worker, private D1 state, and FormSubmit fallback
• replace the daily routine's removed Supabase query with the current Cloudflare/D1 operational contract
• require the live Worker DAILY_CAP value and an explicit unknown result when private D1 or Worker settings are unavailable

Evidence

• Scanner main documents the Supabase-to-Cloudflare move on 2026-08-20 in CLAUDE.md
• Scanner workers/scan/wrangler.toml defines the texas-scan Worker, D1 binding, and DAILY_CAP
• Docket's site generator posts the JavaScript path to the same Worker and retains FormSubmit only as the network-failure fallback
• the live Worker currently enforces route methods, exact-origin CORS, request validation, and progress authentication

Verification

• python3 scripts/shared/ownership_check.py --actor human --files CLAUDE.md prompts/daily_routine.md — passed
• python3 scripts/shared/guards_local.py — 123 passed, 3 documented CI-only steps skipped
• python3 scripts/shared/guards_local.py --verdict — GREEN on base 1aeae5918ef8
• git diff --check — passed
• exact PR head: 35294ae97b240e02f0cb9fe95789e7b4c8bdf40b
• Actions run 33354828176 — completed successfully; browser-read, freshness, gates, browser-render, browser-layout, build, and aggregate guards all passed. The deployment-only release job was skipped on this PR as designed.

No generated docs/ output was hand-edited. No deployment, publication, feed update, or merge is included.