The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
worldmonitor	Ready	Preview, Comment	Apr 23, 2026 2:32pm

Greptile Summary

This PR implements RFC 9727 API catalog discovery by serving public/.well-known/api-catalog (a RFC 9264 linkset pointing to the OpenAPI spec, docs, health endpoint, and MCP server card) and by natively serving worldmonitor.openapi.yaml from Vercel with a clean Content-Type: application/yaml; charset=utf-8 — bypassing the Mintlify proxy that was doubling the content-type header. The vercel.json, .gitignore, prebuild hook, and SPA catch-all regex are all updated consistently, and the existing deploy-config guardrail test is kept in sync.

Confidence Score: 5/5

Safe to merge — all remaining findings are P2 style/DX suggestions that do not affect production behaviour.

No P0 or P1 issues found. The two P2 comments cover: (1) the prebuild hook not firing for non-default build scripts (production Vercel uses npm run build, so no deployment impact), and (2) a more precise MIME type hint in the linkset JSON. Both are minor and non-blocking.

No files require special attention for merging.

Important Files Changed

Sequence Diagram

sequenceDiagram
    participant Scanner as Agent Scanner
    participant Vercel as Vercel Edge
    participant Public as public/ static files
    participant DocsAPI as docs/api/ source

    Note over DocsAPI,Public: npm run build (prebuild hook)
    DocsAPI->>Public: "cp worldmonitor.openapi.yaml to public/openapi.yaml"

    Scanner->>Vercel: "GET /.well-known/api-catalog"
    Vercel->>Public: "serve api-catalog (extensionless JSON)"
    Vercel-->>Scanner: "200 Content-Type: application/linkset+json"

    Scanner->>Vercel: "GET /openapi.yaml (service-desc href)"
    Vercel->>Public: "serve openapi.yaml (build artifact)"
    Vercel-->>Scanner: "200 Content-Type: application/yaml"

    Scanner->>Vercel: "GET /docs/documentation (service-doc href)"
    Vercel-->>Scanner: "302 to Mintlify proxy"

_{Reviews (1): Last reviewed commit: "test(deploy-config): update SPA catch-al..." | Re-trigger Greptile}

Round-2 review feedback addressed in e94af87 (plus one item from the previous commit):

P1 — status href was pointing at the SPA, not the health endpoint
https://api.worldmonitor.app/health 200s on text/html (the SPA bundle), while the real JSON endpoint is at /api/health (served by api/health.js, returns {"status":"HEALTHY",...}). Corrected status[0].href in public/.well-known/api-catalog to /api/health. Verified both paths with curl -I against prod.

P2 — prebuild only fires for the default build script
Already addressed in fa27eca8a (previous commit on this branch): extracted the copy into a named build:openapi script and prefixed every web-variant build (build:full / build:tech / build:finance / build:happy / build:commodity). prebuild kept as a thin delegator for the default npm run build path. build:desktop and build:pro are intentionally excluded — Tauri sidecar and the standalone pro-test workspace don't ship the spec.

P2 — guardrail test coverage
Added a new agent readiness: api-catalog + openapi build suite in tests/deploy-config.test.mjs that asserts:

• Linkset structure: api anchor first, points at https://api.worldmonitor.app/, status href ends with /api/health and lives on the api host, service-desc ends with /openapi.yaml with application/vnd.oai.openapi type, second MCP anchor with service-desc pointing at /.well-known/mcp/server-card.json.
• Build chain: build:openapi exists and references both docs/api/worldmonitor.openapi.yaml and public/openapi.yaml; every web-variant build chains npm run build:openapi; prebuild hook still present; openapi source exists on disk.

Confirmed the P1 assertion would have caught the regression: temporarily reverted the fix locally → red (AssertionError: status href must end with /api/health...) → re-applied → green. Full suite: 30/30 pass.