docs: complete reference test vector index

[garvitkaushik-123]

Summary

• add every missing versioned compliance vector set to the reference index
• add the missing unversioned discovery, format-classification, and media-buy vector sets
• generalize the versioning and README guidance so it remains accurate as the catalog grows
• retain existing unversioned vector files for backward-compatible public URLs

Verification

• npm run test:docs-nav
• npm run test:compliance-snippets
• completeness check confirms every top-level set in static/compliance/source/test-vectors/ and static/test-vectors/ is indexed
• git diff --check upstream/main...HEAD

[bokelley]

Reviewed the complete vector catalog, live CDN targets, versioning guidance, changeset, and updated Scope language against current main. Local docs navigation, compliance snippet/build checks, changeset checks, catalog completeness, and full precommit all pass.

The merge-base changed after approval.

[bokelley]

Reviewed clean head e554089: two-file reference-vector catalog update with corrected Scope language. Verified every logical top-level set, 14 live CDN targets, docs navigation, compliance snippets/build, changeset scope/status, and full precommit.

[aao-secretariat]

Ladon verdict: Approve

Approve — docs-only PR completing the reference test-vector index.

Checked:

• docs/reference/test-vectors/index.mdx (+20/-7): every added set resolves to a real path under static/compliance/source/test-vectors/ or static/test-vectors/; media-buy direct-file links and sampled vector descriptions match on-disk contents. Prose corrections (README softening, compliance/latest snapshot semantics) are accurate.
• No schema files touched (static/schemas/source/** untouched) — no schema↔docs coherence or oneOf-discriminator concerns.
• No released-artifact (dist/**) files modified.
• .changeset/complete-test-vector-index.md present and correctly typed (patch) for a docs-scope change.

Decision-table walk: no critical/high findings (row 1 no). gated_paths is false (row 2 no). high_risk is true but the only sensitive-path match is a (modified) docs file with zero medium-or-higher findings — not a deletion (rows 3/5 no), no medium data-loss/schema/infra finding (row 4 no). No prior decision (row 6 no). No no-auto-approve team match (row 7 no). Zero medium findings (row 8 no). Falls through to row 9 → approve.

Note: high_risk matches only via the docs/reference/** glob on a modified file with a clean review; per the high-risk-flag guidance this is not escalation-worthy on the flag alone.