docs(conformance): catalog creative vector sets

[bokelley]

Summary

• catalog the two versioned creative vector sets added by feat(creative): add creative revision identity #6781
• document their existing source and immutable-version CDN paths
• refresh the catalog date
• add an empty changeset because the catalog is classified as protocol release surface, while intentionally declaring no package bump

This is a documentation-only repair for the deterministic main-branch conformance freshness failure. It does not change schemas, vectors, protocol behavior, or conformance rules.

Verification

• npm run test:doc-compliance-drift (20 freshness/compliance tests and release instrumentation passed)
• npx changeset status --since=origin/main
• git diff --check

[aao-secretariat]

MUST FIX: No .changeset/*.md in this PR. docs/reference/** is protocol-scoped — check-changeset-protocol-scope.cjs matches /^docs\/reference\//, so the Changeset Check job runs changesets status and will not skip. Precedent: the two prior edits to this exact file each carried a changeset — #6807 (patch) and #4559 (empty notes-only). Add one (empty ---\n--- notes changeset matches #4559 for a catalog-freshness sync). Omitting it ships a docs/reference/ change untracked against the versioning surface: high.

[aao-secretariat]

Ladon verdict: Request changes

Request changes — 1 blocking finding.

Blocking findings

• docs/reference/test-vectors/index.mdx:38 — docs/reference/ (protocol-scoped) change ships with no changeset. Per the repo's mandatory changeset-scope rule, a PR touching the published protocol surface (including normative reference docs under docs/reference/**) without a .changeset/*.md is high — it ships an untracked wire/spec change. Add an appropriate changeset (node scripts/check-changeset-protocol-scope.cjs origin/main is the gate; an empty changeset to satisfy CI is not the fix).

The rest of the PR checks out: both source vector files exist, row descriptions match their contents, and CDN paths follow the /compliance/latest/ column convention. The high-risk flag is only a (modified) docs match, not an escalation trigger. Row 1 of the decision table fires on the single high finding.

Blocking findings

• docs/reference/test-vectors/index.mdx:38 — docs/reference/ (protocol-scoped) change ships with no changeset

[aao-secretariat]

Ladon verdict: Approve

Approve — documentation-only catalog repair with no blocking findings.

What I checked:

• Diff touches only .changeset/catalog-creative-vector-sets.md and docs/reference/test-vectors/index.mdx (7 additions, 1 deletion).
• The change catalogs two creative vector sets (creative-representation-resolution, macro-processing) already published under #6781 and refreshes the freshness date to 2026-08-25. Catalog descriptions and source paths are coherent with on-disk vector files.
• Empty no-bump changeset correctly satisfies the protocol-scope gate for a docs/reference change that ships no new wire surface.
• high_risk is true only because docs/reference/index.mdx is a (modified) match — no medium-or-higher finding on that file, so the modification is presumed safe. Row 5 does not fire (no medium finding).
• gated_paths is false, so row 2 does not apply despite review_decision: REVIEW_REQUIRED.
• No no-auto-approve team match; no prior decision.

No findings from the reviewer. Rows 1–8 do not fire → row 9 approve.

[bokelley]

Superseded by #6874, which incorporated this exact reviewed catalog repair to unblock the Addie PR after the base-branch static failure. The repair is now merged to main in 772256f.