P0: Vercel deploy topology: the project is Git-linked to the wrong repo, so contextgraphprotocol.org can be silently overwritten

[macanderson]

Problem

contextgraphprotocol.org now serves this repo's site/ (a fumadocs / Next 16 app), deployed manually via vercel --prod from site/ on 2026-07-23. That manual deploy is fragile.

The Vercel project oxagen/context-graph-protocol (prj_s3lfCDvK9H9PwgvkpXiho1juiR63) has its Git integration connected to a different repository:

link.repo         = macanderson/cgp-website   (NOT macanderson/context-graph-protocol)
rootDirectory     = null                       (repo root)
productionBranch  = main

So every push to main in the separate cgp-website repo auto-deploys to this project and will overwrite the manual deploy, reverting contextgraphprotocol.org to the older cgp-website app (Next 15). The domain's current content depends on nobody pushing to cgp-website and on someone re-running vercel --prod from this repo after any change to site/.

Decision needed

Pick the intended topology and make production reproducible from Git:

• Option 1 — fold in (recommended if site/ is the canonical site): Repoint the project's Git connection to macanderson/context-graph-protocol, set Root Directory = site/, production branch main. Pushes to this repo then build and deploy the docs site. CI already has an advisory site job that builds site/, so the build is known-green.
• Option 2 — keep separate: Leave cgp-website as its own project on its own domain, and create/point a dedicated Vercel project at this repo's site/, then move contextgraphprotocol.org (+ the www. 308 redirect) to it.

Either way, also decide whether any content from the old cgp-website production app needs porting into site/ before it is retired.

Current state (corrected 2026-07-26 — the premise above has inverted)

The apex does not serve this repo's site/. The Problem section's opening line — "contextgraphprotocol.org now serves this repo's site/" — was true for a matter of minutes and is false now. The overwrite this issue predicts had already happened before the issue was filed.

• The last production deploy on the project carries githubCommitRepo: cgp-website, at 2026-07-23T21:51:53Z — eight minutes before this issue was created. The manual site/ deploy was reverted by it, not threatened by it.
• The live apex title appears nowhere in this repository, and contextgraphprotocol.org/paper 404s. Whatever is being served at the apex, it is not site/.
• So the vercel --prod stopgap does not hold the domain. It still runs; it just does not stay.

Still true from the initial deploy:

• site/ is linked to the project (site/.vercel/), so a manual vercel --prod from site/ works — until the next cgp-website push.
• contextgraphprotocol.org attached + verified (Vercel nameservers, DNS auto-configured).
• www.contextgraphprotocol.org → apex via a 308 redirect.

Consequence for the decision above: Option 1 is no longer "protect the manual deploy" — it is "migrate the domain back." Repointing the project's Git connection to this repo with Root Directory site/ is now a change to what the apex serves, not a hardening of the status quo, and should be planned as one — including deciding first what, if anything, ports out of the currently-live cgp-website app.

Cross-link: macanderson/cgp-website#12 defers to this issue by name as the authoritative place the topology gets decided, and freezes pushes to cgp-website@main until it is. cgp-website#1 (adopt contextgraphprotocol.org as canonical) and cgp-website#11 (SDK install commands) are both blocked behind it — and therefore behind this issue.

Acceptance criteria

• Vercel project Git integration and Root Directory reflect the chosen topology
• A push to main (of the chosen repo) auto-deploys the intended app to contextgraphprotocol.org with no manual CLI step
• Decision recorded on whether cgp-website content is ported into site/ or retired