docs: update documentation

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

Author: willkill07

.pre-commit-config.yaml

@@ -75,6 +75,8 @@ repos:
           - --accept
           - '200..=299,403,429'
           - --exclude
+          - '^https?://(localhost|127\.0\.0\.1|\[::1\])(:[0-9]+)?(/.*)?$'
+          - --exclude
           - '^https://www\.npmjs\.com/package/nemo-relay-(node|wasm)$'
           - --exclude
           - '^https://github\.com/NVIDIA/NeMo-Relay(?:/.*)?$'

docs/about/concepts/index.mdx

@@ -9,37 +9,65 @@ SPDX-License-Identifier: Apache-2.0 */}
 
 Use these pages to understand the NeMo Relay runtime model before applying it in a use-case workflow.
 
-<Cards>
-:gutter: 3
-
-<Card title="Scopes" href="/scopes">
+<CardGroup cols={3}>
+<Card
+  title="Scopes"
+  icon="regular object-group"
+  iconPosition="left"
+  href="/about-nemo-relay/concepts/scopes"
+>
 
 Ownership boundaries for agent runs, requests, workflows, tools, LLM calls, and nested runtime work.
 </Card>
 
-<Card title="Middleware" href="/middleware">
+<Card
+  title="Middleware"
+  icon="regular filters"
+  iconPosition="left"
+  href="/about-nemo-relay/concepts/middleware"
+>
 
 Guardrails and intercepts that sanitize, transform, block, or wrap tool and LLM execution.
 </Card>
 
-<Card title="Plugins" href="/plugins">
+<Card
+  title="Plugins"
+  icon="regular puzzle-piece"
+  iconPosition="left"
+  href="/about-nemo-relay/concepts/plugins"
+>
 
 Configuration-driven bundles that install reusable middleware, subscribers, and adaptive behavior.
 </Card>
 
-<Card title="Events" href="/events">
+<Card
+  title="Events"
+  icon="regular waveform-lines"
+  iconPosition="left"
+  href="/about-nemo-relay/concepts/events"
+>
 
 Canonical lifecycle records for scopes, tool calls, LLM calls, marks, subscribers, and exporters.
 </Card>
 
-<Card title="Subscribers" href="/subscribers">
+<Card
+  title="Subscribers"
+  icon="regular tower-broadcast"
+  iconPosition="left"
+  href="/about-nemo-relay/concepts/subscribers"
+>
 
 Consumers for lifecycle events, including logs, traces, trajectories, analytics, and diagnostics.
 </Card>
 
-<Card title="Framework Integrations" href="/framework-integrations">
+<Card
+  title="Framework Integrations"
+  icon="regular diagram-project"
+  iconPosition="left"
+  href="/about-nemo-relay/concepts/framework-integrations"
+>
 
 Integration patterns for frameworks that own invocation boundaries, scheduling, retries, or provider payloads.
 </Card>
 
-</Cards>
+</CardGroup>

docs/build-plugins/code-examples.mdx

@@ -14,11 +14,7 @@ This page collects concrete examples for the surrounding guide area.
 Use an LLM request intercept when a plugin needs to inject tenant or routing metadata into every provider request.
 
 <Tabs>
-:sync-group: language
-
-<Tab title="Python">
-:sync: python
-
+<Tab title="Python" language="python">
 ```python
 import nemo_relay
 
@@ -43,9 +39,7 @@ nemo_relay.plugin.register("header-plugin", HeaderPlugin())
 ```
 </Tab>
 
-<Tab title="Node.js">
-:sync: node
-
+<Tab title="Node.js" language="node">
 ```ts
 import * as plugin from 'nemo-relay-node/plugin';
 
@@ -92,11 +86,7 @@ This pattern is useful for:
 Use a subscriber-oriented plugin when the component should watch the full lifecycle rather than rewrite requests.
 
 <Tabs>
-:sync-group: language
-
-<Tab title="Python">
-:sync: python
-
+<Tab title="Python" language="python">
 ```python
 import nemo_relay
 
@@ -122,9 +112,7 @@ nemo_relay.plugin.register("openinference-export", OpenInferencePlugin())
 ```
 </Tab>
 
-<Tab title="Node.js">
-:sync: node
-
+<Tab title="Node.js" language="node">
 ```ts
 import * as plugin from 'nemo-relay-node/plugin';
 

docs/build-plugins/register-behavior.mdx

@@ -37,11 +37,7 @@ Use the plugin APIs in this order:
 6. Clear active config during teardown when needed.
 
 <Tabs>
-:sync-group: language
-
-<Tab title="Python">
-:sync: python
-
+<Tab title="Python" language="python">
 ```python
 import nemo_relay
 
@@ -61,9 +57,7 @@ nemo_relay.plugin.clear()
 
 </Tab>
 
-<Tab title="Node.js">
-:sync: node
-
+<Tab title="Node.js" language="node">
 ```ts
 import * as plugin from 'nemo-relay-node/plugin';
 
@@ -84,9 +78,7 @@ plugin.clear();
 
 </Tab>
 
-<Tab title="Rust">
-:sync: rust
-
+<Tab title="Rust" language="rust">
 ```rust
 use nemo_relay::plugin::{
     clear_plugin_configuration, initialize_plugins, list_plugin_kinds, validate_plugin_config,
@@ -114,11 +106,7 @@ clear_plugin_configuration()?;
 The same model applies in every binding: validate component-local config, then install middleware through the component-scoped registration context.
 
 <Tabs>
-:sync-group: language
-
-<Tab title="Python">
-:sync: python
-
+<Tab title="Python" language="python">
 ```python
 import nemo_relay
 
@@ -144,9 +132,7 @@ nemo_relay.plugin.register("header-plugin", HeaderPlugin())
 
 </Tab>
 
-<Tab title="Node.js">
-:sync: node
-
+<Tab title="Node.js" language="node">
 ```ts
 import * as plugin from 'nemo-relay-node/plugin';
 
@@ -180,9 +166,7 @@ plugin.register('header-plugin', headerPlugin);
 
 </Tab>
 
-<Tab title="Rust">
-:sync: rust
-
+<Tab title="Rust" language="rust">
 ```rust
 use nemo_relay::plugin::{
     register_plugin, ConfigDiagnostic, DiagnosticLevel, Plugin, PluginRegistrationContext,

docs/build-plugins/validate-configuration.mdx

@@ -26,11 +26,7 @@ Each component has:
 Disabled components are still validated. This lets operators detect config problems before enabling a component in a later rollout.
 
 <Tabs>
-:sync-group: language
-
-<Tab title="Python">
-:sync: python
-
+<Tab title="Python" language="python">
 ```python
 from nemo_relay.plugin import ComponentSpec, ConfigPolicy, PluginConfig
 
@@ -52,9 +48,7 @@ config = PluginConfig(
 ```
 </Tab>
 
-<Tab title="Node.js">
-:sync: node
-
+<Tab title="Node.js" language="node">
 ```ts
 import type { PluginConfig } from 'nemo-relay-node/plugin';
 
@@ -76,9 +70,7 @@ const config: PluginConfig = {
 ```
 </Tab>
 
-<Tab title="Rust">
-:sync: rust
-
+<Tab title="Rust" language="rust">
 ```rust
 use nemo_relay::plugin::{ConfigPolicy, PluginComponentSpec, PluginConfig};
 
@@ -135,11 +127,7 @@ Prefer stable diagnostic codes over prose-only messages. The message can improve
 Use the validation API before initialization and fail deployment if the report contains errors.
 
 <Tabs>
-:sync-group: language
-
-<Tab title="Python">
-:sync: python
-
+<Tab title="Python" language="python">
 ```python
 import nemo_relay
 
@@ -150,9 +138,7 @@ if has_errors:
 ```
 </Tab>
 
-<Tab title="Node.js">
-:sync: node
-
+<Tab title="Node.js" language="node">
 ```ts
 import * as plugin from 'nemo-relay-node/plugin';
 
@@ -164,9 +150,7 @@ if (hasErrors) {
 ```
 </Tab>
 
-<Tab title="Rust">
-:sync: rust
-
+<Tab title="Rust" language="rust">
 ```rust
 use nemo_relay::plugin::validate_plugin_config;
 

docs/getting-started/agent-runtime-primer.mdx

@@ -45,13 +45,16 @@ The core runtime model has five parts:
 
 The simplest mental model is:
 
-```text
-app or framework boundary
-  -> NeMo Relay scope
-  -> managed tool or LLM call
-  -> middleware
-  -> lifecycle event
-  -> subscriber or exporter
+```mermaid
+flowchart LR
+  boundary["App or framework boundary"]
+  scope["NeMo Relay scope"]
+  call["Managed tool or LLM call"]
+  middleware["Middleware"]
+  event["Lifecycle event"]
+  sink["Subscriber or exporter"]
+
+  boundary --> scope --> call --> middleware --> event --> sink
 ```
 
 ## What NeMo Relay Does Not Replace

docs/instrument-applications/adding-scopes-and-marks.mdx

@@ -47,11 +47,7 @@ Follow this sequence to keep framework work attached to the expected runtime con
 The examples below create one `agent-run` scope and emit two marks.
 
 <Tabs>
-:sync-group: language
-
-<Tab title="Python">
-:sync: python
-
+<Tab title="Python" language="python">
 ```python
 import nemo_relay
 
@@ -73,9 +69,7 @@ finally:
 ```
 </Tab>
 
-<Tab title="Node.js">
-:sync: node
-
+<Tab title="Node.js" language="node">
 ```js
 const {
   ScopeType,
@@ -116,9 +110,7 @@ main().catch((error) => {
 ```
 </Tab>
 
-<Tab title="Rust">
-:sync: rust
-
+<Tab title="Rust" language="rust">
 ```rust
 use nemo_relay::api::scope::{
     self, EmitMarkEventParams, PopScopeParams, PushScopeParams, ScopeAttributes, ScopeType,

docs/instrument-applications/advanced-guide.mdx

@@ -45,11 +45,7 @@ This example adds three behaviors around a `search` tool:
 - Measure execution duration.
 
 <Tabs>
-:sync-group: language
-
-<Tab title="Python">
-:sync: python
-
+<Tab title="Python" language="python">
 ```python
 import time
 
@@ -80,9 +76,7 @@ nemo_relay.intercepts.register_tool_execution("search.measure", 30, measure_tool
 ```
 </Tab>
 
-<Tab title="Node.js">
-:sync: node
-
+<Tab title="Node.js" language="node">
 ```js
 const {
   registerToolConditionalExecutionGuardrail,
@@ -112,9 +106,7 @@ registerToolExecutionIntercept("search.measure", 30, async (args, next) => {
 ```
 </Tab>
 
-<Tab title="Rust">
-:sync: rust
-
+<Tab title="Rust" language="rust">
 ```rust
 use nemo_relay::api::registry::{
     register_tool_conditional_execution_guardrail,