Document non-existent relations to prevent common LLM mistakes

Add guidance about `next` and `latest_sts` relations that don't exist
in the schema. LLMs were guessing these relations during testing. The
graph is designed for backward navigation from the present using
`latest*` entry points and `prev`/`prev-security` traversal.

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude Opus 4.5 <[email protected]>

Author: richlander

release-notes/skills/SKILL.md

@@ -52,3 +52,21 @@ Each `_embedded.latest_patches[]` entry has `_links` for 2-fetch navigation:
 - `release-major` → version index (breaking changes, TFMs, OS support)
 - `latest-sdk` → SDK index (feature bands, downloads)
 - `latest-security` → last security patch for that version
+
+## Key Relations
+
+From `llms.json._links`:
+
+| Relation | Purpose |
+|----------|---------|
+| `latest` | Newest supported release (LTS or STS) |
+| `latest-lts` | Newest LTS release |
+| `latest-security-month` | Current security month index |
+| `releases-index` | Full version list including EOL |
+
+**Relations that do NOT exist** (common mistakes):
+
+| Relation | Why It Doesn't Exist |
+|----------|---------------------|
+| `next` | Navigate backwards from present — start at `latest*`, walk back with `prev` |
+| `latest_sts` | Not useful — use `latest` if STS is acceptable |

release-notes/skills/navigation.md

@@ -111,6 +111,15 @@ From version index:
   target-frameworks-json ──► TFMs
 ```
 
+## Non-Existent Relations (Common LLM Mistakes)
+
+These relations do **not exist** — do not attempt to use them:
+
+| Relation | Why It Doesn't Exist |
+|----------|---------------------|
+| `next` | The graph is designed for backward navigation from the present. Use `latest`, `latest-lts`, or `latest-security-month` to start at the most recent asset, then walk backwards with `prev` or `prev-security`. This is more efficient since most queries care about recent data. |
+| `latest_sts` | Not useful — we always have an LTS release in support, but not always an STS. If STS is acceptable, use `latest` which returns the newest release regardless of type. |
+
 ## Fetch Count Summary
 
 | Pattern | Fetches | Notes |