docs: fix broken documentation links

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

Author: willkill07

CONTRIBUTING.md

@@ -325,9 +325,9 @@ The pre-commit hooks do not currently enforce SPDX headers automatically, but re
 Before making significant changes, read through the documentation in
 [`docs/`](docs/), especially:
 
-- [Architecture Overview](docs/about/architecture.mdx) -- runtime model and data flow
-- [Scopes](docs/about/concepts/scopes.mdx) -- scopes, handles, events, and runtime ownership
-- [Middleware](docs/about/concepts/middleware.mdx) -- execution ordering and middleware behavior
+- [Architecture Overview](docs/about-nemo-relay/architecture.mdx) -- runtime model and data flow
+- [Scopes](docs/about-nemo-relay/concepts/scopes.mdx) -- scopes, handles, events, and runtime ownership
+- [Middleware](docs/about-nemo-relay/concepts/middleware.mdx) -- execution ordering and middleware behavior
 - [API Reference](docs/reference/api/index.mdx) -- public surfaces across Rust, Python, and Node.js
 
 The codebase follows a layered architecture: **Core (Rust)** provides the runtime, with bindings through **FFI (C, used by Go through CGo)**, **PyO3 (Python)**, **NAPI (Node.js)**, and **wasm-bindgen (WebAssembly)**. Each binding mirrors the full API surface.

docs/about/architecture.mdx docs/about-nemo-relay/architecture.mdxdocs/about/architecture.mdx renamed to docs/about-nemo-relay/architecture.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-frameworks/about).
+  deeper integration patterns in [Integrate into Frameworks](/integrate-into-frameworks/about).

docs/about/concepts/events.mdx docs/about-nemo-relay/concepts/events.mdxdocs/about/concepts/events.mdx renamed to docs/about-nemo-relay/concepts/events.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](/plugins/adaptive/configuration),
-[Adaptive Cache Governor (ACG)](/plugins/adaptive/acg), and
-[Adaptive Hints](/plugins/adaptive/adaptive-hints).
+[Adaptive Configuration](/adaptive-plugin/configuration),
+[Adaptive Cache Governor (ACG)](/adaptive-plugin/acg), and
+[Adaptive Hints](/adaptive-plugin/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](/plugins/observability/configuration).
+[Observability Configuration](/observability-plugin/configuration).
 
 For the CLI gateway's `plugins.toml` discovery, precedence, merge, and editing
 rules, see [Plugin Configuration Files](/build-plugins/plugin-configuration-files).

…bout/concepts/framework-integrations.mdx …elay/concepts/framework-integrations.mdxdocs/about/concepts/framework-integrations.mdx renamed to docs/about-nemo-relay/concepts/framework-integrations.mdx docs/about/concepts/framework-integrations.mdx renamed to docs/about-nemo-relay/concepts/framework-integrations.mdx

@@ -134,13 +134,13 @@ of the canonical event stream.
 
 ### Agent Trajectory Interchange Format (ATIF) Exporter
 
-The [Agent Trajectory Interchange Format (ATIF) exporter](/plugins/observability/atif)
+The [Agent Trajectory Interchange Format (ATIF) exporter](/observability-plugin/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](/plugins/observability/atof)
+The [Agent Trajectory Observability Format (ATOF) JSONL exporter](/observability-plugin/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](/plugins/observability/about).
+[Observability](/observability-plugin/about).
 For configuration-driven setup, use the built-in
-[`observability` plugin](/plugins/observability/configuration)
+[`observability` plugin](/observability-plugin/configuration)
 to install ATOF, ATIF, OpenTelemetry, and OpenInference subscribers from one
 plugin component.
 

docs/about/concepts/index.mdx docs/about-nemo-relay/concepts/index.mdxdocs/about/concepts/index.mdx renamed to docs/about-nemo-relay/concepts/index.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-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)
+- [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)
 - [Plugin Model](/build-plugins/basic-guide)