fix(llms): point llms.txt docs links at the current release

[Marian Koreniuk (themoriarti)]

What this PR does

Fixes the documentation links in llms.txt. One of them is broken and two lead agents to the obsolete v0 docs:

Entry	Before	Where it actually went	After
Quickstart	/docs/get-started/	meta-refresh to /docs/v0/getting-started/ (v0 alias)	/docs/v1.6/getting-started/
Components	/docs/components/	meta-refresh to /docs/v0/applications/ (v0 alias)	/docs/v1.6/guides/platform-stack/
Architecture	/docs/architecture/	404	/docs/v1.6/guides/concepts/

The short /docs/v1/... path is not an option here: only layouts/404.html redirects it, in JavaScript, after an HTTP 404. So llms.txt needs full version paths.

To keep those paths current, static/llms.txt becomes the template layouts/home.llms.txt. It builds the three links from params.latest_version_id, the value layouts/404.html and layouts/docs/docs-landing.html already read. register_version.sh updates that value in hugo.yaml at release time, and the release workflows already commit hugo.yaml, so no release step is needed. Each link is resolved with site.GetPage, and the build fails with errorf if the page is missing from the latest version.

The llms output format (text/plain, baseName: llms) is defined in hugo.yaml and enabled only for the English home page (languages.en.outputs), so no /de/llms.txt, /ru/llms.txt and so on are emitted.

AFDocs, which CLOMonitor uses for its agent-readiness checks, reported the broken link (llms-txt-links-resolve: 5/6 same-origin links resolve). The two v0 redirects passed that check while still sending readers to the wrong docs.

Verification, with Hugo 0.164.0 extended (the version in netlify.toml):

• hack/check-i18n.sh passes; no translated page goes stale, since no content file changes.
• Production build: same file list as main, and no file differs except /llms.txt, which is byte-identical to the static file it replaces.
• HUGOxPARAMSxLATEST_VERSION_ID=v1.5: the links become /docs/v1.5/....
• HUGOxPARAMSxLATEST_VERSION_ID=v9.9: the build fails with llms.txt: /docs/v9.9/getting-started does not exist; update the link in layouts/home.llms.txt, one error per link.
• Deploy-preview build (HUGO_ENV=preview, -b <preview URL>): the links still point at https://cozystack.io/docs/v1.6/..., and no per-language copies appear.
• All three new URLs return 200 on cozystack.io, and all three pages exist under content/en/docs/next/, so the next release keeps them.

[netlify]

✅ Deploy Preview for cozystack ready!

Name	Link
🔨 Latest commit	244c228
🔍 Latest deploy log	https://app.netlify.com/projects/cozystack/deploys/6aca5e32847b8c0009169951
😎 Deploy Preview	https://deploy-preview-737--cozystack.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify project configuration.

[coderabbitai]

Important

• 🔍 Trigger review

This repository does not receive automatic reviews because it has fewer than 10 stars.

⚙️ Run configuration

• Configuration used: defaults
• Review profile: CHILL
• Plan: Advanced
• Run ID: e677c440-81cf-49ec-90bb-96acc83e6b6e

---

• Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

---

_{Comment @coderabbitai help to get the list of available commands.}

[Aleksei Sviridkin (lexfrei)]

Marian Koreniuk (@themoriarti) NOT LGTM: the new release step rewrites static/llms.txt, but the release automation never commits that file, so the links will still go stale at the next minor.

The link fix itself checks out. /docs/architecture/ is a 404, the other two old paths land on the v0 pages, and the three new v1.6 URLs return 200.

The drift guard is what doesn't work. make release-next is run by two workflows in cozystack/cozystack, promote-rc.yaml and tags.yaml. Both stage the result with git add content hugo.yaml data/versions and then commit only what is staged. Step 6 edits static/llms.txt in the runner checkout, and the change is dropped. I see two ways to fix it:

1. Add static/llms.txt to the git add line in both workflows (a small companion PR in cozystack/cozystack).
2. Drop step 6 and render llms.txt from a Hugo template that reads .Site.Params.latest_version_id, the same value layouts/404.html and layouts/docs/docs-landing.html already use. Then nothing has to be rewritten at release time.

I'd prefer the second, since it keeps the version in one place, but either one is fine with me.

Small one: the commit body says the old links led to docs "two major versions old". v0 is one major version behind v1.6.

[Marian Koreniuk (themoriarti)]

Aleksei Sviridkin (@lexfrei) Thanks, you're right: both workflows stage only content hugo.yaml data/versions, so step 6 never reached a commit. I went with option 2:

• static/llms.txt is now layouts/home.llms.txt, rendered through a plain-text llms output format on the English home page only. The three docs links come from site.Params.latest_version_id, so once register_version.sh updates hugo.yaml, the next build serves the new version, with nothing to stage beyond what the workflows already add.
• Step 6 is gone from release_next.sh. Its header now says that llms.txt follows latest_version_id.
• Each link goes through site.GetPage, and the build fails if the page is missing from the latest version, so a renamed page shows up at build time instead of as a 404.
• Commit body fixed: "one major version behind".

I also rebased on main. With Hugo 0.164.0 the production build matches main except /llms.txt, which is byte-identical to the previous revision of this PR.

[Aleksei Sviridkin (lexfrei)]

Marian Koreniuk (@themoriarti) LGTM, everything from my last review is fixed.

Rendering llms.txt from latest_version_id takes care of the release workflows, since nothing new has to be staged. The branch is on top of current main, and I built it locally. /llms.txt has the three v1.6 links, no per-language copy is emitted, and the deploy preview serves it as text/plain. When I point one link at a page that doesn't exist, the build fails with your errorf message.

Not blocking: the Verification section compares /llms.txt with "the previous static revision of this PR". Nobody reading the merge commit will have that revision, so I'd drop it.