P1: Point the schema $id at a resolvable host (Cargo.toml homepage fixed in #45)

[macanderson]

Problem

The live site is now https://contextgraphprotocol.org, but two in-repo references point at hosts that do not resolve there:

• Cargo.toml (workspace.package): homepage = "https://contextgraphprotocol.io" — wrong TLD (.io, not .org).
• schema/contextgraph-envelope.schema.json $id: https://context-graph-protocol.org/schema/contextgraph-envelope.schema.json — wrong host. It is hyphenated (context-graph-protocol.org), which is not a registered domain — curl returns 000 (DNS failure). The live domain is contextgraphprotocol.org (no hyphens).

The $id matters most because it is the schema's public identity that third parties resolve and quote; it currently points at a domain that does not exist. This resolves the open sub-question in #21 ("confirm that domain is actually registered/intended, or repoint the $id") — the registered, live domain is contextgraphprotocol.org.

Note: even after fixing the host, https://contextgraphprotocol.org/schema/contextgraph-envelope.schema.json currently 404s — the fumadocs site does not serve the schema file. So this needs a decision: either serve the schema at that path from site/, or point $id at a URL that actually resolves (e.g. the GitHub raw/Pages URL). Pick one so the $id is dereferenceable.

Fix

• Cargo.toml homepage → https://contextgraphprotocol.org
• schema/contextgraph-envelope.schema.json $id → a resolvable URL on contextgraphprotocol.org (and make that path actually serve the schema), or point $id at the GitHub raw/Pages URL that serves it — decide once
• Sweep for other stale hosts and fix: rg -n 'contextgraphprotocol\.io|context-graph-protocol\.org' -g '!target' -g '!node_modules'
• Confirm nothing else (README, docs, SDK package metadata) hardcodes the wrong host

Refs #21.

[macanderson]

Re-verified 2026-07-26 against origin/main @ 1ee9b1c.

What landed: the Cargo.toml half. homepage was changed in PR #45, so that claim in the body is stale and its checkbox can be ticked.

What survives: the schema $id — and it is worse than the body describes. context-graph-protocol.org fails DNS entirely, so a third party dereferencing $id today does not get a 404, they get no host at all. And the same path on the live domain also 404s, so simply swapping the hostname does not fix it either. Both halves of the obvious fix are currently broken.

Recommended scope: narrow to the $id alone. Note the entanglement with #57: pointing $id at contextgraphprotocol.org only works if this repo's site/ actually owns and serves that domain, which today it does not. A GitHub raw URL resolves today regardless of how #57 is decided and is worth considering as the interim target. #21 has explicitly handed this bullet here.