fix(docs): publish full LLM text as a static asset

[waleedlatif1]

Summary

• Generate the full documentation text as a public static asset before the docs build, avoiding the hosting limit on prerendered route responses.
• Preserve processed documentation sections, stream page generation sequentially, and atomically publish the completed file.
• Apply an explicit one-day CDN cache policy; fail generation on errors, empty output, or the asset size budget.
• Replace the full-text runtime route with the generated asset and include it in Turborepo build-cache outputs.
• Keep development text fresh with a debounced filesystem watcher and managed dev processes.

Type of Change

• Bug fix

Testing

Docs production build, build-cache restoration, production-mode HTTP verification, and live dev edit/restore verification; documentation-section parity; injected generation failure preserves the previous asset and removes temporary files; docs tests and root test suite; lint, type-check, all audits, block registry check, and docs manifest check.

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 7, 2026 11:24pm UTC

[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 6 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}

[cubic-dev-ai]

All reported issues were addressed across 6 files

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

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

[greptile-apps]

Confidence Score: 5/5

[Medium risk] Moves LLM text generation from dynamic route to build-time static asset.

The PR appears safe to merge; no new actionable issues were found.

What we checked:

• Rebuilds stay separate: The watcher waits for each child to finish. Edits during that wait set pending, so another generation runs afterward.

Summary

Publishes /llms-full.txt as a generated static asset instead of a prerendered route.

• Generates pages sequentially and publishes the finished file with an atomic rename.
• Adds a size limit, empty-output checks, CDN caching, and build-cache coverage.
• Adds a development watcher that rebuilds after documentation edits. This addresses the previous stale-development-text finding.

Diagram

%%{init: {'theme': 'neutral'}}%%
flowchart LR
  A[Documentation inputs] --> B[fumadocs-mdx]
  B --> C[Generate text sequentially]
  C --> D[Temporary file]
  D --> E[Atomic rename]
  E --> F[public/llms-full.txt]
  F --> G[Next.js static response]
  A --> H[Development watcher]
  H --> B

Loading

_{Reviews (2) · Last reviewed commit: "fix(docs): regenerate full text during d..." · Reviewed by Greptile}

[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 7 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}