Add LOOP-22 website growth and simplification overhaul

[dbarrante]

What changed

• Added LOOP-22, a runnable branch-mutating website growth and simplification overhaul covering crawl/render/index health, technical SEO, entity and claim truth, content usefulness, generative retrieval, information architecture, accessibility, performance, reliability, and conversion journeys.
• Added an explicit simplification ledger, evidence hierarchy, anti-hype rails, reversible mutation teeth, quantitative exit criteria, approval gates, and post-deployment measurement contract.
• Updated the README catalog and cadence to include LOOP-22.
• Updated LOOP-20 so plain-language website SEO/GEO overhaul goals can route to LOOP-22.

Why

The catalog did not have a single end-to-end loop for simplifying and improving a public website as a growth system. The supplied source material used the already-occupied LOOP-04 identifier and included several fast-moving GEO assumptions as universal rules. This PR assigns the next free identifier and keeps useful coverage while requiring current primary evidence and reproducible measurement.

In particular, llms.txt is optional and consumer-specific, structured data must match visible facts, research findings are not treated as ranking APIs, and traffic/ranking/citation improvements cannot be claimed before a real post-deployment observation window.

Impact

Operators can now run one bounded loop for a website overhaul while preserving the existing specialized frontend, UX, testing, CI, and adversarial-review guarantees. LOOP-20 can discover and dispatch the new capability from a plain-language goal.

Validation

• Confirmed 22 loop files and 22 unique loop-id values.
• Confirmed LOOP-22 includes every required PROTOCOL template section.
• Confirmed balanced fenced blocks and valid internal catalog file targets.
• Ran git diff --check with no errors.
• No runtime test suite applies; this repository is Markdown-only.

[AetherAI3]

Unblocked and reviewed. #5 landed after this branch was cut, so the README catalog area conflicted and the validator did not exist here yet. Merged master in and resolved it — MERGEABLE/CLEAN, Loop contract green.

LOOP-22 itself needed no changes. It conforms to the section 14 contract, carries no project-specific paths or infrastructure assumptions, and its approval gates are stricter than the protocol default rather than looser — content deletion, entity claims, analytics and consent changes, and framework migrations all require explicit operator sign-off on top of §10, and the loop never self-merges or deploys.

Conflicts resolved in this branch's favour where it was right: "Loops That Run the Catalog" beats master's "Loops That Run the Other 15" now that the catalog is 22 and no longer 15-plus-meta, and the same for LOOP-20's "the applicable catalog loops" over a hard-coded 19. Master's meta-loop index table is kept.

The merge exposed three stale claims, now fixed: the catalog note still said "the 15 base loops" with LOOP-22 sitting in the table; the table-of-contents link pointed at the old heading anchor; and the loop-cards graphic was titled for "the base loops", which is now 16 rather than the 15 it actually draws.

Two validator additions came out of that, both proven by breaking them first:

• Same-page anchors are now checked against the file's own headings. Renaming a heading silently breaks every TOC entry pointing at it, and the link and the heading sit far enough apart that no diff looks wrong. This is exactly what happened here and nothing caught it.
• coordinates-with, which this PR introduces, is documented in PROTOCOL.md §14 and CONTRIBUTING.md beside composed-of, and its references are resolved the same way. Worth keeping distinct: one loop runs another, the other hands findings to it.

Merging.