feat: generate per-doc markdown files via docusaurus-plugin-llms

[RicardoStoklosa]

Summary

• Bump docusaurus-plugin-llms from ^0.3.0 to ^0.4.0.
• Enable generateMarkdownFiles: true so every doc page is emitted as a sibling .md file in the build output (e.g. /tagodeploy/new-project.md).
• Preserve title and description front matter on the generated files via keepFrontMatter.

The plugin defaults to addMdExtension: true, so llms.txt now links to the .md versions instead of HTML pages. TagoDeploy (and other consumers) can fetch those URLs directly to render the docs as markdown.

Why

TagoDeploy needs the raw markdown of each doc to render help content inside the product. The 0.4.0 release of docusaurus-plugin-llms adds first-class support for emitting per-doc .md files alongside the existing llms.txt / llms-full.txt artifacts.

Risk (CIA)

• Confidentiality: none. Same content already published as HTML.
• Integrity: none. Build artifacts only, no source docs touched.
• Availability: none. Additive output files.

Test plan

• npm install succeeds with minimal lockfile delta
• npm run build succeeds
• 330 .md files generated under build/ matching the docs tree
• build/llms.txt and build/llms-full.txt still generated
• Sample build/tagodeploy/new-project.md contains preserved title / description front matter
• Beta deploy verified: https://docs.beta.tago.io/<path>.md resolves