web-driftlisted

# Web drift ## Scope and triggers Also fires on "audit our websites", "are our sites still readable by an agent". Enumerates every site the consumer declared in `WEB_DRIFT_SITES`, probes each over read-only HTTP with `lib/webcheck` (groundwork, page, and API tiers), verdicts each check with evidence, and files the fixes as board rows in the repo that owns the site's source, plus a report. Page-speed/Lighthouse/Core Web Vitals is a different tool and a different question. No answer-engine-citation probe ships here. This repo holds no website source: the loop files rows, it never edits a site. ## Overview Audit every declared public website against the agent-readiness contract and file the fixes. This is the live-site instance of `docs/patterns/audit-loop.md`: enumerate, verdict with evidence, apply, gate through the operator. `kit:ci-drift` already reaches the network, so reaching outward is not the novelty. What is new is the surface: no in-kit loop audits a public HTTP surface, and the fix lands in whichever repo builds that site, never here. The contract this measures: an agent that runs no JavaScript should be able to find the site, fetch a page, read its content, tell a dead URL from a live one, and call its API if it has one. A deploy can break any of those silently, and nothing in a repo notices. ## The four slots (per the audit-loop pattern) | Slot | This instance | |---|---| | Item set | one `(site, check)` pair. The site axis is `WEB_DRIFT_SITES`, enumerated