docs: add llm.txt with repository context

[miqui]

Add an llm.txt file at the repository root with a short description of the project to support LLM-oriented tooling and discovery.

[miqui]

reference: https://llmstxt.org/

[lornajane]

I'd like us to progress with our AI policy statements before implementing any tooling support.

[miqui]

@lornajane > I'd like us to progress with our AI policy statements before implementing any tooling support.

Ok, then this AI topic should be a high priority imho. Where is this work being done? Is there a thread? Thanks.

[lornajane]

The discussion is on the main spec repo: OAI/OpenAPI-Specification#5209

[lornajane]

Jumping back in here as we're making progress on the overall AI policy topics.

How does this content stay up to date? Would it make more sense to have a generator script that builds this page at the same time as the website?

[miqui]

hi @lornajane - good point. Other repos (I assume maintain it manually - I don't think this file changes often). However, I am looking into your suggestion.

[miqui]

@lornajane Updated: llm.txt is now llms.txt (llmstxt.org convention) and is generated at build time from page front matter via a Liquid template. No plugin needed, and it can't drift from the site. Verified with a Docker Jekyll build. Since the AI policy question is resolved, this should be ready for another look.

[miqui]

@lornajane , @baywet , @ralfhandl

In practice:

• If someone adds specification/foo.md with a title and a parent, it
  appears in llms.txt on the next build. Nobody touches llms.txt.
• If someone renames or reorders a page, the file follows.
• The intro paragraph and the "Related resources" links at the bottom are
  still static text in the template. Everything else is generated.