Context
`src/lib/v2/projection/registry.ts` (around line 261 — `synthesizeFormatIdFromGlob`) bakes `https://creative.adcontextprotocol.org/\` directly into a fabricated `agent_url` for the registry's reverse-lookup path. Out of scope for the 7.10 mirror-host collapse (PR #1896 / adcp#4866) which centralized the same host in `src/lib/v2/format-schema/sandbox-refs.ts` via `DEFAULT_MIRROR_HOSTS`.
The 7.10 review (post-merge follow-ups) flagged this as a hygiene item: when the AAO mirror moves again in the future, the fix should land in one place. Two sites carrying the same literal will drift.
Ask
- Centralize the literal: `registry.ts` reads `DEFAULT_MIRROR_HOSTS[0]` (or a re-exported alias) instead of an inline string.
- If a re-export is cleaner than a cross-module dependency, consider adding a `AAO_DEFAULT_AGENT_URL` constant to a shared module (`src/lib/v2/projection/cache-versions.ts` or a new `anchors.ts`).
- Adjust the JSDoc on the registry's synthesized `agent_url` to call out that it's non-normative per the spec's "registry synthesis is implementation-defined" rule — this isn't a wire-truth value, it's a best-effort fallback.
Scope
One-file change. Not blocking 7.10 publish — the current literal still resolves to the right host (`creative.adcontextprotocol.org` is the single AAO trust anchor post-adcp#4866). The motivation is preventing drift on the next mirror move.
Forward references
Context
`src/lib/v2/projection/registry.ts` (around line 261 — `synthesizeFormatIdFromGlob`) bakes `https://creative.adcontextprotocol.org/\` directly into a fabricated `agent_url` for the registry's reverse-lookup path. Out of scope for the 7.10 mirror-host collapse (PR #1896 / adcp#4866) which centralized the same host in `src/lib/v2/format-schema/sandbox-refs.ts` via `DEFAULT_MIRROR_HOSTS`.
The 7.10 review (post-merge follow-ups) flagged this as a hygiene item: when the AAO mirror moves again in the future, the fix should land in one place. Two sites carrying the same literal will drift.
Ask
Scope
One-file change. Not blocking 7.10 publish — the current literal still resolves to the right host (`creative.adcontextprotocol.org` is the single AAO trust anchor post-adcp#4866). The motivation is preventing drift on the next mirror move.
Forward references