RS-DOC: require a code, test, or fixture anchor for evidence: verified (REQ-DOC-014)

[jeremi]

REQ-DOC-014 currently accepts "published site pages" as evidence supporting evidence: verified. That legitimizes a doc-cites-doc loop: RS-SEC-G's Evidence section cited only other docs pages while carrying verified, and the 2026-07-07 review found one of its requirements contradicted by code (REQ-SEC-G-006, fixed separately).

Tighten REQ-DOC-014 so verified requires at least one code, test, fixture, or generated-artifact anchor per load-bearing claim; docs pages may corroborate but cannot be the sole evidence. Land the rule change together with evidence-section upgrades on the pages that would otherwise regress to partial.

[jeremi]

Triage decision for 1.0: required documentation-contract honesty.

A formal specification marked evidence: verified must not prove itself by citing another narrative page. Tighten REQ-DOC-014 to require an inspectable code, test, fixture, generated artifact, or released machine contract for each load-bearing claim, then downgrade any page that cannot meet that bar.

Keep this review-based and small. Do not create a new evidence database or require one anchor per sentence. The invariant is that verified cannot be a doc-cites-doc loop.