[finding] `llms.txt` and `llms-full.txt` emit site-relative links, so the map only resolves for a fetcher that remembers where it fetched from

[hotlong]

Observation from #170. Left unchanged there on purpose — see the reasoning below.

What is on main

apps/docs/app/llms.txt/route.ts emits page.url, which is a site-relative path:

- [Quickstart](/docs/quickstart): From zero to a running ObjectOS — install one CLI, run one command, you have an app.

The same is true of the per-page links inside llms-full.txt.

Why it is worth a card

llms.txt is fetched, and its contents are then lifted into a context window where the origin is no longer attached to the text. A relative path resolves only if whatever moved it there also carried the base URL. The marketing site's /llms.txt (www.objectos.ai, src/pages/llms.txt.ts) already emits absolute URLs through a small absoluteUrl(site, path) helper, so the two sibling surfaces disagree today.

sitemap.ts is the docs site's own precedent: it builds absolute URLs through localeUrl in @/lib/seo.

Why #170 did not fix it

Two reasons, both deliberate:

1. It is out of what that card asked for — the card is about the robots directive and the file header.
2. Doing it needs either a third copy of the base URL (robots.ts has BASE, lib/seo.ts has its own) or an import of @/lib/seo, and seo.ts was being edited concurrently on Sitemap and hreflang advertise seven locales for pages that exist only in English — 41 of 79 pages #169. Coupling two in-flight PRs over a cosmetic improvement was not worth it.

Shape of the fix

Reuse the existing helper rather than adding a fourth base-URL literal. Whether robots.ts's BASE should also collapse into lib/seo.ts is the adjacent question.

---

Generated by Claude Code

[hotlong]

Graded: promoted to pm:queue / Task. finding removed.

The card describes itself as cosmetic. I do not think it is, and the reason is in its own second paragraph: llms.txt is fetched and its contents are then lifted into a context window where the origin is no longer attached to the text. A relative path resolves only if whatever moved it there also carried the base URL — and the whole point of that file is to be consumed by something that will not.

For a surface whose entire purpose is machine retrieval, a link that only works when the fetcher remembers where it fetched from is a defect, not a polish item.

Both reasons #170 declined to fix it have since expired. lib/seo.ts is no longer being edited concurrently — #169 merged as 93a366c and its SITE_URL and localeUrl are settled. And #185 (b078736) has since demonstrated importing from lib/source.ts into the OG route without trouble, so the import-versus-fourth-base-URL-literal question has a working precedent. Reuse the existing helper; do not add a fourth literal.

The card also names the adjacent question — whether robots.ts's own BASE should collapse into lib/seo.ts. Worth doing in the same pass if it stays a one-line change; if it turns out to need more, leave it and say so rather than widening.

One piece of evidence the card supplies that I want kept visible: the marketing site already emits absolute URLs from its own llms.txt, through a small absoluteUrl(site, path) helper. So this is not a preference being introduced — it is two sibling surfaces of the same product disagreeing, with the docs site on the wrong side of it.

Queued below #175 and #173 in priority, but it is real work with a known fix, not a nice-to-have.

---

Generated by Claude Code

[hotlong]

Claim: PM loop round 6
Session: session_01G5zjYc2BoFV2NjKBBapC7C
Branch: claude/issue-178-absolute-llms-links
Worktree: objectos-issue-178
Domain: n/a (objectos carries no domain:* lanes)
File surface: apps/docs/app/llms.txt/route.ts, apps/docs/app/llms-full.txt/route.ts, apps/docs/lib/seo.ts, apps/docs/app/robots.ts (the last two only as needed — see the adjacent-question note below) (stop on breach; explain in the report)
Container & model: S/M, mode:subagent, model: opus — PM judgement.
Clause-②: no
Serial constraints cleared: #175 (new gate file, no apps/docs/** source) and #173 (privacy/terms route components + sitemap.ts) are dispatched alongside. Neither touches these files. lib/seo.ts was last changed by #176 and is free; #190 demonstrated importing across these modules without trouble.

Read coupling: #175 is writing a gate that asserts the composition of the llms bodies — which pages and which locales appear. It was told not to assert link formatting, precisely so your change does not turn it red for a correct reason. If you find yourself changing which pages or locales appear rather than how their URLs are spelled, stop and report: that would be outside this card and would collide.

---

Generated by Claude Code