docs: dedupe latest Fern release pages

Author: andreatgretel

fern/AGENTS.md

@@ -23,7 +23,7 @@ Use hybrid versioning. A version YAML may reuse older page files for unchanged c
 
 Example: a `v0.5.9` nav entry can point to `./v0.5.8/pages/concepts/columns.mdx`. Users still see the page under the active `v0.5.9` URL because Fern routes by version slug and nav title, not by source file path.
 
-Before editing a file under an older shared tree such as `fern/versions/v0.5.8/pages/...`, check every `fern/versions/*.yml` file that points at it. If the content describes a newer release, copy it into `latest/pages/...` and the target `vX.Y.Z/pages/...` tree, then retarget only those nav entries.
+Before editing a file under an older shared tree such as `fern/versions/v0.5.8/pages/...`, check every `fern/versions/*.yml` file that points at it. If the content describes a newer release, copy it into the target `vX.Y.Z/pages/...` tree and retarget that release. Point `latest.yml` at the released copy unless latest has already diverged after that release.
 
 Dev Notes are versioned. Do not add a new release-specific post to an older frozen nav or page tree. If a post says "As of Data Designer vX.Y.Z", it belongs in `latest.yml` and `vX.Y.Z.yml`, not in older version navs.
 

fern/README.md

@@ -76,7 +76,7 @@ Current Fern versions:
 ```
 fern/versions/
 ├── latest.yml          ← rolling nav file
-├── latest/pages/...    ← latest-only page overrides
+├── latest/pages/...    ← optional latest-only page overrides after release divergence
 ├── v0.6.0.yml          ← release nav file
 ├── v0.6.0/pages/...    ← v0.6.0-only page overrides
 ├── v0.5.9.yml          ← release nav file
@@ -87,11 +87,11 @@ fern/versions/
 └── older/pages/...     ← links to the MkDocs archive
 ```
 
-`docs.yml` registers `slug: latest`, `slug: v0.6.0`, `slug: v0.5.9`, `slug: v0.5.8`, and `slug: older-versions`. The `latest`, `v0.6.0`, and `v0.5.9` nav files intentionally reuse the migrated `v0.5.8/pages/` tree for unchanged content so Fern-native versions do not duplicate every page. Add version-specific page copies only when content diverges.
+`docs.yml` registers `slug: latest`, `slug: v0.6.0`, `slug: v0.5.9`, `slug: v0.5.8`, and `slug: older-versions`. The `latest`, `v0.6.0`, and `v0.5.9` nav files intentionally reuse older version page trees for unchanged content so Fern-native versions do not duplicate every page. Add version-specific page copies only when content diverges.
 
 Fern version URLs are based on the active version entry, not the source file path. A `v0.5.9` page can point at `./v0.5.8/pages/...` and still render under `/nemo/datadesigner/v0.5.9/...`; users do not see the reused source path.
 
-Before editing a file under an older shared tree such as `fern/versions/v0.5.8/pages/...`, check every `fern/versions/*.yml` file that points at it. If the content describes a newer release, copy it into `latest/pages/...` and the target `vX.Y.Z/pages/...` tree, then retarget only those nav entries.
+Before editing a file under an older shared tree such as `fern/versions/v0.5.8/pages/...`, check every `fern/versions/*.yml` file that points at it. If the content describes a newer release, copy it into the target `vX.Y.Z/pages/...` tree and retarget that release. Point `latest.yml` at the released copy unless latest has already diverged after that release.
 
 Dev Notes are versioned: `latest.yml` can include posts from `main` that are not in old release navs yet. Frozen release navs (`v0.6.0.yml`, `v0.5.9.yml`, `v0.5.8.yml`) should include only posts available at that release point. If a Dev Note says "As of Data Designer vX.Y.Z", do not add it to an older frozen nav or an older shared page tree.
 
@@ -104,7 +104,7 @@ When cutting future Fern-native versions, use a hybrid model:
 3. Reuse older page paths for unchanged content.
 4. Copy changed/new pages into `versions/vX.Y.Z/pages/...`.
 5. Point only changed nav entries at the copied `vX.Y.Z` pages.
-6. Update `latest.yml` if the rolling docs should diverge after release prep.
+6. Point `latest.yml` at the new release copy. Use `latest/pages/...` only for post-release divergence.
 7. Run `make check-fern-docs`.
 
 Do not add a new version entry without deciding which pages are release-specific. A version YAML that points at shared pages can drift when those shared files change later.

fern/versions/latest.yml

@@ -132,11 +132,11 @@ navigation:
   - section: Plugins
     contents:
       - page: Overview
-        path: ./latest/pages/plugins/overview.mdx
+        path: ./v0.6.0/pages/plugins/overview.mdx
       - page: Example Plugin
-        path: ./latest/pages/plugins/example.mdx
+        path: ./v0.6.0/pages/plugins/example.mdx
       - page: FileSystemSeedReader Plugins
-        path: ./latest/pages/plugins/filesystem_seed_reader.mdx
+        path: ./v0.6.0/pages/plugins/filesystem_seed_reader.mdx
       - page: Discover
         path: ./v0.5.8/pages/plugins/discover.mdx
   - section: Code Reference
@@ -168,11 +168,11 @@ navigation:
   - section: Dev Notes
     contents:
       - page: Overview
-        path: ./latest/pages/devnotes/index.mdx
+        path: ./v0.6.0/pages/devnotes/index.mdx
       - page: Have It Your Way
-        path: ./latest/pages/devnotes/posts/have-it-your-way.mdx
+        path: ./v0.6.0/pages/devnotes/posts/have-it-your-way.mdx
       - page: VLM Long Document Understanding
-        path: ./latest/pages/devnotes/posts/vlm-long-document-understanding.mdx
+        path: ./v0.6.0/pages/devnotes/posts/vlm-long-document-understanding.mdx
       - page: Push Datasets to Hugging Face Hub
         path: ./v0.5.8/pages/devnotes/posts/push-datasets-to-hugging-face-hub.mdx
       - page: Text-to-SQL for Nemotron Super