Three commits moved the AICV nonprofit site to the ceiling of what's achievable on a free-plan static site — no phantom 200s, no missing discovery headers, schema cleaned up.
The April scan left the .org at Cloudflare Discoverability 2/3 — the /.well-known/api-catalog file existed and served correctly, but nothing in the HTTP response advertised it. A one-line addition to _headers fixed it: Link: </.well-known/api-catalog>; rel="api-catalog" on all responses. RFC 9727 registers api-catalog as the correct relation type for a linkset — not service-doc, which is for human-readable documentation. Verified live on the custom domain within minutes of deploy.
Cloudflare Pages has a default behavior most static sites don't notice: without a 404.html in the repo, it falls back to serving index.html with HTTP 200 for any unmatched path. That meant /.well-known/openid-configuration, /.well-known/oauth-authorization-server, and similar paths all returned text/html at 200 — which agent scanners read as "found HTML, not JSON" rather than "correctly absent." Adding 404.html resolved the whole class at once. The page matches the site's existing chrome — same design tokens, nav, and footer as events.html — and contains a static link back to the homepage. No JS redirect, no meta-refresh; those would reintroduce the soft-404 problem the file is meant to fix.
Two JSON-LD improvements landed together. An operationalStatus PropertyValue was added to the Organization node — a machine-readable partial-active summary noting that the Intelligence Network is live, AI Builder Workshops are paused, and the AI Talent Job Board is in development. The Service node @id was renamed from #service-intelligence-layer to #service-intelligence-network, aligning the schema anchor with the confirmed naming convention used across all surfaces.