docs: fix Fern link validation issues

Signed-off-by: Will Killian <wkillian@nvidia.com>

Author: willkill07

.github/ISSUE_TEMPLATE/03-documentation.yml

@@ -40,7 +40,7 @@ body:
       description: Link to pages or list file paths. Enter N/A if you are not sure.
       placeholder: |
         - https://...
-        - fern/...
+        - fern/... or docs/...
     validations: {required: true}
   - type: textarea
     id: proposed_change

.github/workflows/fern-docs.yml

@@ -390,6 +390,10 @@ jobs:
           git config user.name "github-actions[bot]"
           git config user.email "github-actions[bot]@users.noreply.github.com"
           git add -A
+          if git diff --cached --quiet; then
+            echo "No docs snapshot changes to commit."
+            exit 0
+          fi
           git commit -m "docs(fern): release version v${{ steps.version.outputs.tag }}
 
           Automated documentation snapshot.

.pre-commit-config.yaml

@@ -67,7 +67,7 @@ repos:
           - --no-progress
           - --include-fragments
           - --root-dir
-          - /
+          - .
           - --scheme
           - http
           - --scheme

AGENTS.md

@@ -154,7 +154,7 @@ Minimum guidance:
 - Node.js binding or wrapper changes: `just test-node`.
 - Go binding or raw FFI changes: `just test-go` and the relevant Rust/FFI checks.
 - WebAssembly binding changes: `just test-wasm`.
-- Documentation site changes, including link or navigation changes: `just docs`. The recipe regenerates the ignored Fern API reference pages before validation.
+- Documentation site changes: `just docs`. Run docs link validation with `just docs-linkcheck` when links change. The recipes regenerate the ignored Fern API reference pages before validation.
 - Cross-language API changes: run the touched binding tests and update docs, package READMEs, and generated surfaces where applicable.
 
 Before review, prefer `uv run pre-commit run --all-files` when the change crosses languages or tooling. The hooks enforce SPDX headers, file hygiene, Ruff, `ty`, Markdown link checks, Cargo formatting/lints/audits, Go formatting/vet, Node formatting, and public docstring checks.

CONTRIBUTING.md

@@ -201,7 +201,7 @@ Before opening a PR, check the following:
 2. The relevant reference docs are updated for any public API change.
 3. The relevant crate or package README is updated when that surface changed.
 4. Embedded documentation snippets, patch docs, and binding-support notes are updated if examples or supported bindings changed.
-5. For docs site changes, run `./scripts/build-docs.sh`; it regenerates ignored Fern API reference pages before validation.
+5. For docs site changes, run `just docs` (or `./scripts/build-docs.sh html` as a compatibility wrapper) — it regenerates ignored Fern API reference pages before validation.
 
 For documentation-heavy changes, prefer small targeted commits so the history
 shows entry-point changes, reference changes, examples, and maintenance updates

docs/about/concepts/framework-integrations.mdx

@@ -151,4 +151,4 @@ Use these practices when applying the concept in application or integration code
 - Use mark events to fill visibility gaps rather than to model full execution
   spans.
 - Keep binding-level API details in the [API Reference](/reference/api) and
-  deeper integration patterns in [Integrate into Frameworks](/integrate-into-frameworks/about).
+  deeper integration patterns in [Integrate into Frameworks](/integrate-frameworks/about).

docs/about/concepts/plugins.mdx

@@ -150,9 +150,9 @@ through the same component lifecycle as other plugins:
 - Inspect the activation result if needed
 
 Detailed adaptive configuration belongs in
-[Adaptive Configuration](/adaptive-plugin/configuration),
-[Adaptive Cache Governor (ACG)](/adaptive-plugin/acg), and
-[Adaptive Hints](/adaptive-plugin/adaptive-hints).
+[Adaptive Configuration](/plugins/adaptive/configuration),
+[Adaptive Cache Governor (ACG)](/plugins/adaptive/acg), and
+[Adaptive Hints](/plugins/adaptive/adaptive-hints).
 
 ### Observability
 
@@ -163,7 +163,7 @@ disabled unless its section sets `enabled: true`, and subscriber names are
 inferred from the plugin namespace instead of exposed in public config.
 
 Detailed observability plugin configuration belongs in
-[Observability Configuration](/observability-plugin/configuration).
+[Observability Configuration](/plugins/observability/configuration).
 
 For the CLI gateway's `plugins.toml` discovery, precedence, merge, and editing
 rules, see [Plugin Configuration Files](/build-plugins/plugin-configuration-files).

docs/about/concepts/subscribers.mdx

@@ -134,13 +134,13 @@ of the canonical event stream.
 
 ### Agent Trajectory Interchange Format (ATIF) Exporter
 
-The [Agent Trajectory Interchange Format (ATIF) exporter](/observability-plugin/atif)
+The [Agent Trajectory Interchange Format (ATIF) exporter](/plugins/observability/atif)
 collects lifecycle events and emits trajectory artifacts for offline analysis,
 replay, or debugging.
 
 ### Agent Trajectory Observability Format (ATOF) JSONL Exporter
 
-The [Agent Trajectory Observability Format (ATOF) JSONL exporter](/observability-plugin/atof)
+The [Agent Trajectory Observability Format (ATOF) JSONL exporter](/plugins/observability/atof)
 writes the canonical event stream to a native filesystem path as one raw ATOF
 event per line.
 
@@ -155,9 +155,9 @@ The OpenInference subscriber maps runtime events into OTLP traces using
 OpenInference semantics for model-centric observability.
 
 Detailed setup, configuration, and API shape for these subscribers belongs in
-[Observability](/observability-plugin/about).
+[Observability](/plugins/observability/about).
 For configuration-driven setup, use the built-in
-[`observability` plugin](/observability-plugin/configuration)
+[`observability` plugin](/plugins/observability/configuration)
 to install ATOF, ATIF, OpenTelemetry, and OpenInference subscribers from one
 plugin component.
 

docs/about/ecosystem.mdx

@@ -111,8 +111,8 @@ Use these links to continue into adjacent concepts and workflows.
 - [NVIDIA NeMo documentation](https://docs.nvidia.com/nemo/index.html)
 - [NVIDIA NeMo Agent Toolkit documentation](https://docs.nvidia.com/nemo/agent-toolkit/latest/)
 - [NVIDIA NeMo Guardrails documentation](https://docs.nvidia.com/nemo-guardrails/index.html)
-- [Integrate into Frameworks](/integrate-into-frameworks/about)
-- [Adding Framework Scopes](/integrate-into-frameworks/adding-scopes)
-- [Wrapping Tool Calls](/integrate-into-frameworks/wrap-tool-calls)
-- [Wrapping LLM Calls](/integrate-into-frameworks/wrap-llm-calls)
+- [Integrate into Frameworks](/integrate-frameworks/about)
+- [Adding Framework Scopes](/integrate-frameworks/adding-scopes)
+- [Wrapping Tool Calls](/integrate-frameworks/wrap-tool-calls)
+- [Wrapping LLM Calls](/integrate-frameworks/wrap-llm-calls)
 - [Plugin Model](/build-plugins/basic-guide)

docs/about/overview.mdx

@@ -67,13 +67,13 @@ Use the reading path that matches your task:
 | Develop from source | [Development Setup](/contribute/development-setup) |
 | Understand the runtime model | [Concepts](/about-nemo-relay/concepts) |
 | Instrument an application | [Instrument Applications](/instrument-applications/about) |
-| Use a maintained integration | [Supported Integrations](/supported-integrations/about) |
-| Integrate a framework | [Integrate into Frameworks](/integrate-into-frameworks/about) |
+| Use a maintained integration | [Supported Integrations](/integrations/about) |
+| Integrate a framework | [Integrate into Frameworks](/integrate-frameworks/about) |
 | Observe a local coding-agent CLI | [NeMo Relay CLI](/nemo-relay-cli/about) |
 | Package reusable behavior | [Build Plugins](/build-plugins/about) |
-| Export traces or trajectories | [Observability](/observability-plugin/about) |
+| Export traces or trajectories | [Observability](/plugins/observability/about) |
 | Debug trace incidents | [Trace Incident Runbook](/resources/troubleshooting/trace-incident-runbook) |
-| Tune performance with adaptive behavior | [Adaptive](/adaptive-plugin/about) |
+| Tune performance with adaptive behavior | [Adaptive](/plugins/adaptive/about) |
 | Look up symbols | [APIs](/reference/api) |
 
 ## Conceptual Diagram