improvement(api): publish an RFC 9727 API catalog and stop padding tables in docs markdown

[waleedlatif1]

Summary

• Add /.well-known/api-catalog (RFC 9727): a Linkset (application/linkset+json with the RFC's profile) whose entry anchors the v2 REST API at the deployment's own origin and links its OpenAPI document (service-desc), reference docs (service-doc), and health endpoint (status) with the RFC 8631 relations. Link: rel="api-catalog" makes a HEAD request discoverable too (§2). The dedicated MCP host still serves only MCP paths
• Exempt the catalog from the empty-User-Agent block alongside the other protocol discovery paths (/api/*, including the status link, never reaches that filter)
• Docs markdown: stop padding tables at the source. remark-gfm's serializer pads every cell to its column's widest cell; configuring the preset's remark-gfm with tablePipeAlign: false drops that padding for every processed-markdown consumer (.md pages, llms-full.txt, Copy page) and replaces the post-processing compactTables string pass. Only serialization changes; rendered pages do not. The config throws if a fumadocs upgrade stops registering remark-gfm, so the setting cannot silently fall off

Type of Change

• Improvement

Testing

• test-mcp-host-e2e.ts against a local next dev configured like the CI cli group: 13/13 pass. New checks cover the catalog's GET (empty and tool User-Agents) and HEAD, content type, exact Link/anchor/status/service-desc URLs against the configured origin, the status link resolving, and the MCP host rejecting the path. Reverting the proxy exemption, or pointing the anchor at another origin, turns them red
• Docs, local next dev vs production: .md output for /integrations/plane, /integrations/file, /integrations/checkr, /cli/tables, /introduction is identical after normalizing table cells (same rows, cells, and alignment; all other lines byte-identical). /cli/reference (content differs from production) compared before/after the config change on the same build: equivalent, 524 KB → 294 KB. HTML pages render the same tables as production
• bun run lint, check:source-conventions, check:api-validation:strict, check:comment-hygiene, check:unused-exports

Checklist

• Code follows project style guidelines
• Self-reviewed my changes
• Tests added/updated and passing (new tests pass the test-audit authoring gate)
• No new warnings introduced
• I confirm that I have read and agree to the terms outlined in the Contributor License Agreement (CLA)

[vercel]

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

Project	Deployment	Actions	Updated
docs	Ready	Preview	Oct 15, 2026 6:56am UTC

[greptile-apps]

Confidence Score: 5/5

[Medium impact] The PR appears safe to merge; no new blocking issue was found.

Summary

The PR adds a public API catalog and moves compact table output into the docs markdown settings.

• API clients can find the v2 service details from one catalog.
• Docs Markdown tables use less padding in their output.

_{Reviews (2) · Last reviewed commit: "fix(docs): turn off table padding in the..." · Reviewed by Greptile}

[cubic-dev-ai]

2 issues found across 4 files

Confidence score: 4/5

• Clients sending HEAD to the API root won’t discover the catalog because apps/sim/app/.well-known/api-catalog/route.ts advertises it only after the catalog is requested. Add the rel="api-catalog" link to the API response context.
• Clients with an empty User-Agent can retrieve the catalog but get a 403 when following its status link. Exempt /api/health from the empty-User-Agent block in apps/sim/proxy.ts.

Prompt for AI agents (unresolved issues)

Check if these issues are valid — if so, understand the root cause of each and fix them. When an issue isn't valid or won't be fixed in this PR, reply in its thread with the reason and then resolve the thread. If appropriate, use sub-agents to investigate and fix each issue separately.


<file name="apps/sim/proxy.ts">

<violation number="1" location="apps/sim/proxy.ts:302">
P3: A client that retrieves this catalog with an empty User-Agent cannot follow its `status` link: `/api/health` still matches the empty-UA block and returns 403. Exempt the linked health endpoint as well so the advertised status relation works for these clients.</violation>
</file>

<file name="apps/sim/app/.well-known/api-catalog/route.ts">

<violation number="1" location="apps/sim/app/.well-known/api-catalog/route.ts:38">
P2: This advertises the catalog only after a client already requests `/.well-known/api-catalog`, so a `HEAD` to the API root cannot discover it through `rel="api-catalog"`. Add this link to the API response context (for example, `/api/v2`) so relation-based discovery works.</violation>
</file>

<sub>Reply with feedback, questions, or to request a fix.

Turn on auto-fix | Re-trigger cubic</sub>

[waleedlatif1]

@greptile

[waleedlatif1]

@cubic-dev-ai review this PR

[cubic-dev-ai]

@cubic-dev-ai review this PR

@waleedlatif1 I have started the AI code review. It will take a few minutes to complete.

[cubic-dev-ai]

No issues found across 5 files

Confidence score: 5/5

• Automated review surfaced no issues in the provided summaries.
• No files require special attention.

_{Turn on auto-fix | Re-trigger cubic}