pllan 2026.3.47 → 2026.3.49

package/docs/nb/gateway/remote.md

@@ -28,7 +28,7 @@ Run the Gateway on a persistent host and reach it via **Tailscale** or SSH.
 
 - **Best UX:** keep `gateway.bind: "loopback"` and use **Tailscale Serve** for the Control UI.
 - **Fallback:** keep loopback + SSH tunnel from any machine that needs access.
-- **Examples:** [exe.dev](/install/exe-dev) (easy VM) or [Hetzner](/install/hetzner) (production VPS).
+- **Examples:** [exe.dev](/nb/install/exe-dev) (easy VM) or [Hetzner](/nb/install/hetzner) (production VPS).
 
 This is ideal when your laptop sleeps often but you want the agent always-on.
 
@@ -39,7 +39,7 @@ The laptop does **not** run the agent. It connects remotely:
 - Use the macOS app’s **Remote over SSH** mode (Settings → General → “Pllan runs”).
 - The app opens and manages the tunnel, so WebChat + health checks “just work.”
 
-Runbook: [macOS remote access](/platforms/mac/remote).
+Runbook: [macOS remote access](/nb/platforms/mac/remote).
 
 ### 3) Laptop runs the Gateway, remote access from other machines
 
@@ -48,7 +48,7 @@ Keep the Gateway local but expose it safely:
 - SSH tunnel to the laptop from other machines, or
 - Tailscale Serve the Control UI and keep the Gateway loopback-only.
 
-Guide: [Tailscale](/gateway/tailscale) and [Web overview](/web).
+Guide: [Tailscale](/nb/gateway/tailscale) and [Web overview](/nb/web).
 
 ## Command flow (what runs where)
 
@@ -63,7 +63,7 @@ Flow example (Telegram → node):
 
 Notes:
 
-- **Nodes do not run the gateway service.** Only one gateway should run per host unless you intentionally run isolated profiles (see [Multiple gateways](/gateway/multiple-gateways)).
+- **Nodes do not run the gateway service.** Only one gateway should run per host unless you intentionally run isolated profiles (see [Multiple gateways](/nb/gateway/multiple-gateways)).
 - macOS app “node mode” is just a node client over the Gateway WebSocket.
 
 ## SSH tunnel (CLI + tools)
@@ -130,7 +130,7 @@ WebChat no longer uses a separate HTTP port. The SwiftUI chat UI connects direct
 
 The macOS menu bar app can drive the same setup end-to-end (remote status checks, WebChat, and Voice Wake forwarding).
 
-Runbook: [macOS remote access](/platforms/mac/remote).
+Runbook: [macOS remote access](/nb/platforms/mac/remote).
 
 ## Security rules (remote/VPN)
 
@@ -150,4 +150,4 @@ Short version: **keep the Gateway loopback-only** unless you’re sure you need
   trusted. Set it to `false` if you want tokens/passwords everywhere.
 - Treat browser control like operator access: tailnet-only + deliberate node pairing.
 
-Deep dive: [Security](/gateway/security).
+Deep dive: [Security](/nb/gateway/security).

package/docs/nb/gateway/sandbox-vs-tool-policy-vs-elevated.md

@@ -39,7 +39,7 @@ Sandboxing is controlled by `agents.defaults.sandbox.mode`:
 - `"non-main"`: only non-main sessions are sandboxed (common “surprise” for groups/channels).
 - `"all"`: everything is sandboxed.
 
-See [Sandboxing](/gateway/sandboxing) for the full matrix (scope, workspace mounts, images).
+See [Sandboxing](/nb/gateway/sandboxing) for the full matrix (scope, workspace mounts, images).
 
 ### Bind mounts (security quick check)
 
@@ -110,7 +110,7 @@ Gates:
 - Enablement: `tools.elevated.enabled` (and optionally `agents.list[].tools.elevated.enabled`)
 - Sender allowlists: `tools.elevated.allowFrom.<provider>` (and optionally `agents.list[].tools.elevated.allowFrom.<provider>`)
 
-See [Elevated Mode](/tools/elevated).
+See [Elevated Mode](/nb/tools/elevated).
 
 ## Common "sandbox jail" fixes
 
@@ -129,6 +129,6 @@ In `"non-main"` mode, group/channel keys are _not_ main. Use the main session ke
 
 ## See also
 
-- [Sandboxing](/gateway/sandboxing) -- full sandbox reference (modes, scopes, backends, images)
-- [Multi-Agent Sandbox & Tools](/tools/multi-agent-sandbox-tools) -- per-agent overrides and precedence
-- [Elevated Mode](/tools/elevated)
+- [Sandboxing](/nb/gateway/sandboxing) -- full sandbox reference (modes, scopes, backends, images)
+- [Multi-Agent Sandbox & Tools](/nb/tools/multi-agent-sandbox-tools) -- per-agent overrides and precedence
+- [Elevated Mode](/nb/tools/elevated)

package/docs/nb/gateway/sandboxing.md

@@ -34,7 +34,7 @@ Not sandboxed:
 - The Gateway process itself.
 - Any tool explicitly allowed to run on the host (e.g. `tools.elevated`).
   - **Elevated exec runs on the host and bypasses sandboxing.**
-  - If sandboxing is off, `tools.elevated` does not change execution (already on host). See [Elevated Mode](/tools/elevated).
+  - If sandboxing is off, `tools.elevated` does not change execution (already on host). See [Elevated Mode](/nb/tools/elevated).
 
 ## Modes
 
@@ -137,7 +137,7 @@ Important consequences:
 Use `backend: "openshell"` when you want Pllan to sandbox tools in an
 OpenShell-managed remote environment. For the full setup guide, configuration
 reference, and workspace mode comparison, see the dedicated
-[OpenShell page](/gateway/openshell).
+[OpenShell page](/nb/gateway/openshell).
 
 OpenShell reuses the same core SSH transport and remote filesystem bridge as the
 generic SSH backend, and adds OpenShell-specific lifecycle
@@ -320,7 +320,7 @@ Security notes:
 - Pllan blocks dangerous bind sources (for example: `docker.sock`, `/etc`, `/proc`, `/sys`, `/dev`, and parent mounts that would expose them).
 - Sensitive mounts (secrets, SSH keys, service credentials) should be `:ro` unless absolutely required.
 - Combine with `workspaceAccess: "ro"` if you only need read access to the workspace; bind modes stay independent.
-- See [Sandbox vs Tool Policy vs Elevated](/gateway/sandbox-vs-tool-policy-vs-elevated) for how binds interact with tool policy and elevated exec.
+- See [Sandbox vs Tool Policy vs Elevated](/nb/gateway/sandbox-vs-tool-policy-vs-elevated) for how binds interact with tool policy and elevated exec.
 
 ## Images + setup
 
@@ -397,12 +397,12 @@ Security defaults:
 - Break-glass override: `agents.defaults.sandbox.docker.dangerouslyAllowContainerNamespaceJoin: true`.
 
 Docker installs and the containerized gateway live here:
-[Docker](/install/docker)
+[Docker](/nb/install/docker)
 
 For Docker gateway deployments, `scripts/docker/setup.sh` can bootstrap sandbox config.
 Set `PLLAN_SANDBOX=1` (or `true`/`yes`/`on`) to enable that path. You can
 override socket location with `PLLAN_DOCKER_SOCKET`. Full setup and env
-reference: [Docker](/install/docker#enable-agent-sandbox-for-docker-gateway-opt-in).
+reference: [Docker](/nb/install/docker#enable-agent-sandbox-for-docker-gateway-opt-in).
 
 ## setupCommand (one-time container setup)
 
@@ -430,19 +430,19 @@ globally or per-agent, sandboxing doesn’t bring it back.
 
 `tools.elevated` is an explicit escape hatch that runs `exec` on the host.
 `/exec` directives only apply for authorized senders and persist per session; to hard-disable
-`exec`, use tool policy deny (see [Sandbox vs Tool Policy vs Elevated](/gateway/sandbox-vs-tool-policy-vs-elevated)).
+`exec`, use tool policy deny (see [Sandbox vs Tool Policy vs Elevated](/nb/gateway/sandbox-vs-tool-policy-vs-elevated)).
 
 Debugging:
 
 - Use `pllan sandbox explain` to inspect effective sandbox mode, tool policy, and fix-it config keys.
-- See [Sandbox vs Tool Policy vs Elevated](/gateway/sandbox-vs-tool-policy-vs-elevated) for the “why is this blocked?” mental model.
+- See [Sandbox vs Tool Policy vs Elevated](/nb/gateway/sandbox-vs-tool-policy-vs-elevated) for the “why is this blocked?” mental model.
   Keep it locked down.
 
 ## Multi-agent overrides
 
 Each agent can override sandbox + tools:
 `agents.list[].sandbox` and `agents.list[].tools` (plus `agents.list[].tools.sandbox.tools` for sandbox tool policy).
-See [Multi-Agent Sandbox & Tools](/tools/multi-agent-sandbox-tools) for precedence.
+See [Multi-Agent Sandbox & Tools](/nb/tools/multi-agent-sandbox-tools) for precedence.
 
 ## Minimal enable example
 
@@ -462,8 +462,8 @@ See [Multi-Agent Sandbox & Tools](/tools/multi-agent-sandbox-tools) for preceden
 
 ## Related docs
 
-- [OpenShell](/gateway/openshell) -- managed sandbox backend setup, workspace modes, and config reference
-- [Sandbox Configuration](/gateway/configuration-reference#agents-defaults-sandbox)
-- [Sandbox vs Tool Policy vs Elevated](/gateway/sandbox-vs-tool-policy-vs-elevated) -- debugging "why is this blocked?"
-- [Multi-Agent Sandbox & Tools](/tools/multi-agent-sandbox-tools) -- per-agent overrides and precedence
-- [Security](/gateway/security)
+- [OpenShell](/nb/gateway/openshell) -- managed sandbox backend setup, workspace modes, and config reference
+- [Sandbox Configuration](/nb/gateway/configuration-reference#agents-defaults-sandbox)
+- [Sandbox vs Tool Policy vs Elevated](/nb/gateway/sandbox-vs-tool-policy-vs-elevated) -- debugging "why is this blocked?"
+- [Multi-Agent Sandbox & Tools](/nb/tools/multi-agent-sandbox-tools) -- per-agent overrides and precedence
+- [Security](/nb/gateway/security)

package/docs/nb/gateway/secrets-plan-contract.md

@@ -44,7 +44,7 @@ If a target does not match these rules, apply fails before mutating configuratio
 
 Plan targets are accepted for supported credential paths in:
 
-- [SecretRef Credential Surface](/reference/secretref-credential-surface)
+- [SecretRef Credential Surface](/nb/reference/secretref-credential-surface)
 
 ## Target type behavior
 
@@ -110,7 +110,7 @@ If apply fails with an invalid target path message, regenerate the plan with `pl
 
 ## Related docs
 
-- [Secrets Management](/gateway/secrets)
-- [CLI `secrets`](/cli/secrets)
-- [SecretRef Credential Surface](/reference/secretref-credential-surface)
-- [Configuration Reference](/gateway/configuration-reference)
+- [Secrets Management](/nb/gateway/secrets)
+- [CLI `secrets`](/nb/cli/secrets)
+- [SecretRef Credential Surface](/nb/reference/secretref-credential-surface)
+- [Configuration Reference](/nb/gateway/configuration-reference)

package/docs/nb/gateway/secrets.md

@@ -321,7 +321,7 @@ Runtime behavior:
 
 Canonical supported and unsupported credentials are listed in:
 
-- [SecretRef Credential Surface](/reference/secretref-credential-surface)
+- [SecretRef Credential Surface](/nb/reference/secretref-credential-surface)
 
 Runtime-minted or rotating credentials and OAuth refresh material are intentionally excluded from read-only SecretRef resolution.
 
@@ -469,7 +469,7 @@ Exec note:
 
 For strict target/path contract details and exact rejection rules, see:
 
-- [Secrets Apply Plan Contract](/gateway/secrets-plan-contract)
+- [Secrets Apply Plan Contract](/nb/gateway/secrets-plan-contract)
 
 ## One-way safety policy
 
@@ -495,9 +495,9 @@ Some SecretInput unions are easier to configure in raw editor mode than in form
 
 ## Related docs
 
-- CLI commands: [secrets](/cli/secrets)
-- Plan contract details: [Secrets Apply Plan Contract](/gateway/secrets-plan-contract)
-- Credential surface: [SecretRef Credential Surface](/reference/secretref-credential-surface)
-- Auth setup: [Authentication](/gateway/authentication)
-- Security posture: [Security](/gateway/security)
-- Environment precedence: [Environment Variables](/help/environment)
+- CLI commands: [secrets](/nb/cli/secrets)
+- Plan contract details: [Secrets Apply Plan Contract](/nb/gateway/secrets-plan-contract)
+- Credential surface: [SecretRef Credential Surface](/nb/reference/secretref-credential-surface)
+- Auth setup: [Authentication](/nb/gateway/authentication)
+- Security posture: [Security](/nb/gateway/security)
+- Environment precedence: [Environment Variables](/nb/help/environment)

package/docs/nb/gateway/security/index.md

@@ -25,7 +25,7 @@ This page explains hardening **within that model**. It does not claim hostile mu
 
 ## Quick check: `pllan security audit`
 
-See also: [Formal Verification (Security Models)](/security/formal-verification)
+See also: [Formal Verification (Security Models)](/nb/security/formal-verification)
 
 Run this regularly (especially after changing config or exposing network surfaces):
 
@@ -356,7 +356,7 @@ proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
 
 - Pllan gateway is local/loopback first. If you terminate TLS at a reverse proxy, set HSTS on the proxy-facing HTTPS domain there.
 - If the gateway itself terminates HTTPS, you can set `gateway.http.securityHeaders.strictTransportSecurity` to emit the HSTS header from Pllan responses.
-- Detailed deployment guidance is in [Trusted Proxy Auth](/gateway/trusted-proxy-auth#tls-termination-and-hsts).
+- Detailed deployment guidance is in [Trusted Proxy Auth](/nb/gateway/trusted-proxy-auth#tls-termination-and-hsts).
 - For non-loopback Control UI deployments, `gateway.controlUi.allowedOrigins` is required by default.
 - `gateway.controlUi.allowedOrigins: ["*"]` is an explicit allow-all browser-origin policy, not a hardened default. Avoid it outside tightly controlled local testing.
 - `gateway.controlUi.dangerouslyAllowHostHeaderOriginFallback=true` enables Host-header origin fallback mode; treat it as a dangerous operator-selected policy.
@@ -416,8 +416,8 @@ Pllan’s stance:
 ## Command authorization model
 
 Slash commands and directives are only honored for **authorized senders**. Authorization is derived from
-channel allowlists/pairing plus `commands.useAccessGroups` (see [Configuration](/gateway/configuration)
-and [Slash commands](/tools/slash-commands)). If a channel allowlist is empty or includes `"*"`,
+channel allowlists/pairing plus `commands.useAccessGroups` (see [Configuration](/nb/gateway/configuration)
+and [Slash commands](/nb/tools/slash-commands)). If a channel allowlist is empty or includes `"*"`,
 commands are effectively open for that channel.
 
 `/exec` is a session-only convenience for authorized operators. It does **not** write config or
@@ -455,7 +455,7 @@ Plugins run **in-process** with the Gateway. Treat them as trusted code:
   - Pllan uses `npm pack` and then runs `npm install --omit=dev` in that directory (npm lifecycle scripts can execute code during install).
   - Prefer pinned, exact versions (`@scope/pkg@1.2.3`), and inspect the unpacked code on disk before enabling.
 
-Details: [Plugins](/tools/plugin)
+Details: [Plugins](/nb/tools/plugin)
 
 ## DM access model (pairing / allowlist / open / disabled)
 
@@ -473,7 +473,7 @@ pllan pairing list <channel>
 pllan pairing approve <channel> <code>
 ```
 
-Details + files on disk: [Pairing](/channels/pairing)
+Details + files on disk: [Pairing](/nb/channels/pairing)
 
 ## DM session isolation (multi-user mode)
 
@@ -497,7 +497,7 @@ Treat the snippet above as **secure DM mode**:
 - Local CLI onboarding default: writes `session.dmScope: "per-channel-peer"` when unset (keeps existing explicit values).
 - Secure DM mode: `session.dmScope: "per-channel-peer"` (each channel+sender pair gets an isolated DM context).
 
-If you run multiple accounts on the same channel, use `per-account-channel-peer` instead. If the same person contacts you on multiple channels, use `session.identityLinks` to collapse those DM sessions into one canonical identity. See [Session Management](/concepts/session) and [Configuration](/gateway/configuration).
+If you run multiple accounts on the same channel, use `per-account-channel-peer` instead. If the same person contacts you on multiple channels, use `session.identityLinks` to collapse those DM sessions into one canonical identity. See [Session Management](/nb/concepts/session) and [Configuration](/nb/gateway/configuration).
 
 ## Allowlists (DM + groups) - terminology
 
@@ -514,7 +514,7 @@ Pllan has two separate “who can trigger me?” layers:
   - Replying to a bot message (implicit mention) does **not** bypass sender allowlists like `groupAllowFrom`.
   - **Security note:** treat `dmPolicy="open"` and `groupPolicy="open"` as last-resort settings. They should be barely used; prefer pairing + allowlists unless you fully trust every member of the room.
 
-Details: [Configuration](/gateway/configuration) and [Groups](/channels/groups)
+Details: [Configuration](/nb/gateway/configuration) and [Groups](/nb/channels/groups)
 
 ## Prompt injection (what it is, why it matters)
 
@@ -780,7 +780,7 @@ Auth modes:
 
 - `gateway.auth.mode: "token"`: shared bearer token (recommended for most setups).
 - `gateway.auth.mode: "password"`: password auth (prefer setting via env: `PLLAN_GATEWAY_PASSWORD`).
-- `gateway.auth.mode: "trusted-proxy"`: trust an identity-aware reverse proxy to authenticate users and pass identity via headers (see [Trusted Proxy Auth](/gateway/trusted-proxy-auth)).
+- `gateway.auth.mode: "trusted-proxy"`: trust an identity-aware reverse proxy to authenticate users and pass identity via headers (see [Trusted Proxy Auth](/nb/gateway/trusted-proxy-auth)).
 
 Rotation checklist (token/password):
 
@@ -814,7 +814,7 @@ and require token/password auth.
 
 **Security rule:** do not forward these headers from your own reverse proxy. If
 you terminate TLS or proxy in front of the gateway, disable
-`gateway.auth.allowTailscale` and use token/password auth (or [Trusted Proxy Auth](/gateway/trusted-proxy-auth)) instead.
+`gateway.auth.allowTailscale` and use token/password auth (or [Trusted Proxy Auth](/nb/gateway/trusted-proxy-auth)) instead.
 
 Trusted proxies:
 
@@ -822,12 +822,12 @@ Trusted proxies:
 - Pllan will trust `x-forwarded-for` (or `x-real-ip`) from those IPs to determine the client IP for local pairing checks and HTTP auth/local checks.
 - Ensure your proxy **overwrites** `x-forwarded-for` and blocks direct access to the Gateway port.
 
-See [Tailscale](/gateway/tailscale) and [Web overview](/web).
+See [Tailscale](/nb/gateway/tailscale) and [Web overview](/nb/web).
 
 ### 0.6.1) Browser control via node host (recommended)
 
 If your Gateway is remote but the browser runs on another machine, run a **node host**
-on the browser machine and let the Gateway proxy browser actions (see [Browser tool](/tools/browser)).
+on the browser machine and let the Gateway proxy browser actions (see [Browser tool](/nb/tools/browser)).
 Treat node pairing like admin access.
 
 Recommended pattern:
@@ -873,7 +873,7 @@ Recommendations:
 - When sharing diagnostics, prefer `pllan status --all` (pasteable, secrets redacted) over raw logs.
 - Prune old session transcripts and log files if you don’t need long retention.
 
-Details: [Logging](/gateway/logging)
+Details: [Logging](/nb/gateway/logging)
 
 ### 1) DMs: pairing by default
 
@@ -956,12 +956,12 @@ Built-in baseline for chat-driven agent turns: non-owner senders cannot use the
 
 ## Sandboxing (recommended)
 
-Dedicated doc: [Sandboxing](/gateway/sandboxing)
+Dedicated doc: [Sandboxing](/nb/gateway/sandboxing)
 
 Two complementary approaches:
 
-- **Run the full Gateway in Docker** (container boundary): [Docker](/install/docker)
-- **Tool sandbox** (`agents.defaults.sandbox`, host gateway + Docker-isolated tools): [Sandboxing](/gateway/sandboxing)
+- **Run the full Gateway in Docker** (container boundary): [Docker](/nb/install/docker)
+- **Tool sandbox** (`agents.defaults.sandbox`, host gateway + Docker-isolated tools): [Sandboxing](/nb/gateway/sandboxing)
 
 Note: to prevent cross-agent access, keep `agents.defaults.sandbox.scope` at `"agent"` (default)
 or `"session"` for stricter per-session isolation. `scope: "shared"` uses a
@@ -973,7 +973,7 @@ Also consider agent workspace access inside the sandbox:
 - `agents.defaults.sandbox.workspaceAccess: "ro"` mounts the agent workspace read-only at `/agent` (disables `write`/`edit`/`apply_patch`)
 - `agents.defaults.sandbox.workspaceAccess: "rw"` mounts the agent workspace read/write at `/workspace`
 
-Important: `tools.elevated` is the global baseline escape hatch that runs exec on the host. Keep `tools.elevated.allowFrom` tight and don’t enable it for strangers. You can further restrict elevated per agent via `agents.list[].tools.elevated`. See [Elevated Mode](/tools/elevated).
+Important: `tools.elevated` is the global baseline escape hatch that runs exec on the host. Keep `tools.elevated.allowFrom` tight and don’t enable it for strangers. You can further restrict elevated per agent via `agents.list[].tools.elevated`. See [Elevated Mode](/nb/tools/elevated).
 
 ### Sub-agent delegation guardrail
 
@@ -1028,7 +1028,7 @@ Example strict policy:
 
 With multi-agent routing, each agent can have its own sandbox + tool policy:
 use this to give **full access**, **read-only**, or **no access** per agent.
-See [Multi-Agent Sandbox & Tools](/tools/multi-agent-sandbox-tools) for full details
+See [Multi-Agent Sandbox & Tools](/nb/tools/multi-agent-sandbox-tools) for full details
 and precedence rules.
 
 Common use cases:

package/docs/nb/gateway/troubleshooting.md

@@ -9,7 +9,7 @@ title: "Troubleshooting"
 # Gateway troubleshooting
 
 This page is the deep runbook.
-Start at [/help/troubleshooting](/help/troubleshooting) if you want the fast triage flow first.
+Start at [/help/troubleshooting](/nb/help/troubleshooting) if you want the fast triage flow first.
 
 ## Command ladder
 
@@ -54,9 +54,9 @@ Fix options:
 
 Related:
 
-- [/providers/anthropic](/providers/anthropic)
-- [/reference/token-use](/reference/token-use)
-- [/help/faq#why-am-i-seeing-http-429-ratelimiterror-from-anthropic](/help/faq#why-am-i-seeing-http-429-ratelimiterror-from-anthropic)
+- [/providers/anthropic](/nb/providers/anthropic)
+- [/reference/token-use](/nb/reference/token-use)
+- [/help/faq#why-am-i-seeing-http-429-ratelimiterror-from-anthropic](/nb/help/faq#why-am-i-seeing-http-429-ratelimiterror-from-anthropic)
 
 ## No replies
 
@@ -84,9 +84,9 @@ Common signatures:
 
 Related:
 
-- [/channels/troubleshooting](/channels/troubleshooting)
-- [/channels/pairing](/channels/pairing)
-- [/channels/groups](/channels/groups)
+- [/channels/troubleshooting](/nb/channels/troubleshooting)
+- [/channels/pairing](/nb/channels/pairing)
+- [/channels/groups](/nb/channels/groups)
 
 ## Dashboard control ui connectivity
 
@@ -124,8 +124,8 @@ Use `error.details.code` from the failed `connect` response to pick the next act
 | Detail code                  | Meaning                                                  | Recommended action                                                                                                                                                   |
 | ---------------------------- | -------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
 | `AUTH_TOKEN_MISSING`         | Client did not send a required shared token.             | Paste/set token in the client and retry. For dashboard paths: `pllan config get gateway.auth.token` then paste into Control UI settings.                          |
-| `AUTH_TOKEN_MISMATCH`        | Shared token did not match gateway auth token.           | If `canRetryWithDeviceToken=true`, allow one trusted retry. If still failing, run the [token drift recovery checklist](/cli/devices#token-drift-recovery-checklist). |
-| `AUTH_DEVICE_TOKEN_MISMATCH` | Cached per-device token is stale or revoked.             | Rotate/re-approve device token using [devices CLI](/cli/devices), then reconnect.                                                                                    |
+| `AUTH_TOKEN_MISMATCH`        | Shared token did not match gateway auth token.           | If `canRetryWithDeviceToken=true`, allow one trusted retry. If still failing, run the [token drift recovery checklist](/nb/cli/devices#token-drift-recovery-checklist). |
+| `AUTH_DEVICE_TOKEN_MISMATCH` | Cached per-device token is stale or revoked.             | Rotate/re-approve device token using [devices CLI](/nb/cli/devices), then reconnect.                                                                                    |
 | `PAIRING_REQUIRED`           | Device identity is known but not approved for this role. | Approve pending request: `pllan devices list` then `pllan devices approve <requestId>`.                                                                        |
 
 Device auth v2 migration check:
@@ -144,10 +144,10 @@ If logs show nonce/signature errors, update the connecting client and verify it:
 
 Related:
 
-- [/web/control-ui](/web/control-ui)
-- [/gateway/authentication](/gateway/authentication)
-- [/gateway/remote](/gateway/remote)
-- [/cli/devices](/cli/devices)
+- [/web/control-ui](/nb/web/control-ui)
+- [/gateway/authentication](/nb/gateway/authentication)
+- [/gateway/remote](/nb/gateway/remote)
+- [/cli/devices](/nb/cli/devices)
 
 ## Gateway service not running
 
@@ -175,9 +175,9 @@ Common signatures:
 
 Related:
 
-- [/gateway/background-process](/gateway/background-process)
-- [/gateway/configuration](/gateway/configuration)
-- [/gateway/doctor](/gateway/doctor)
+- [/gateway/background-process](/nb/gateway/background-process)
+- [/gateway/configuration](/nb/gateway/configuration)
+- [/gateway/doctor](/nb/gateway/doctor)
 
 ## Channel connected messages not flowing
 
@@ -205,10 +205,10 @@ Common signatures:
 
 Related:
 
-- [/channels/troubleshooting](/channels/troubleshooting)
-- [/channels/whatsapp](/channels/whatsapp)
-- [/channels/telegram](/channels/telegram)
-- [/channels/discord](/channels/discord)
+- [/channels/troubleshooting](/nb/channels/troubleshooting)
+- [/channels/whatsapp](/nb/channels/whatsapp)
+- [/channels/telegram](/nb/channels/telegram)
+- [/channels/discord](/nb/channels/discord)
 
 ## Cron and heartbeat delivery
 
@@ -238,9 +238,9 @@ Common signatures:
 
 Related:
 
-- [/automation/troubleshooting](/automation/troubleshooting)
-- [/automation/cron-jobs](/automation/cron-jobs)
-- [/gateway/heartbeat](/gateway/heartbeat)
+- [/automation/troubleshooting](/nb/automation/troubleshooting)
+- [/automation/cron-jobs](/nb/automation/cron-jobs)
+- [/gateway/heartbeat](/nb/gateway/heartbeat)
 
 ## Node paired tool fails
 
@@ -269,9 +269,9 @@ Common signatures:
 
 Related:
 
-- [/nodes/troubleshooting](/nodes/troubleshooting)
-- [/nodes/index](/nodes/index)
-- [/tools/exec-approvals](/tools/exec-approvals)
+- [/nodes/troubleshooting](/nb/nodes/troubleshooting)
+- [/nodes/index](/nb/nodes/index)
+- [/tools/exec-approvals](/nb/tools/exec-approvals)
 
 ## Browser tool fails
 
@@ -300,8 +300,8 @@ Common signatures:
 
 Related:
 
-- [/tools/browser-linux-troubleshooting](/tools/browser-linux-troubleshooting)
-- [/tools/browser](/tools/browser)
+- [/tools/browser-linux-troubleshooting](/nb/tools/browser-linux-troubleshooting)
+- [/tools/browser](/nb/tools/browser)
 
 ## If you upgraded and something suddenly broke
 
@@ -373,6 +373,6 @@ pllan gateway restart
 
 Related:
 
-- [/gateway/pairing](/gateway/pairing)
-- [/gateway/authentication](/gateway/authentication)
-- [/gateway/background-process](/gateway/background-process)
+- [/gateway/pairing](/nb/gateway/pairing)
+- [/gateway/authentication](/nb/gateway/authentication)
+- [/gateway/background-process](/nb/gateway/background-process)

package/docs/nb/gateway/trusted-proxy-auth.md

@@ -324,7 +324,7 @@ If you're moving from token auth to trusted-proxy:
 
 ## Related
 
-- [Security](/gateway/security) — full security guide
-- [Configuration](/gateway/configuration) — config reference
-- [Remote Access](/gateway/remote) — other remote access patterns
-- [Tailscale](/gateway/tailscale) — simpler alternative for tailnet-only access
+- [Security](/nb/gateway/security) — full security guide
+- [Configuration](/nb/gateway/configuration) — config reference
+- [Remote Access](/nb/gateway/remote) — other remote access patterns
+- [Tailscale](/nb/gateway/tailscale) — simpler alternative for tailnet-only access

package/docs/nb/help/environment.md

@@ -90,7 +90,7 @@ You can reference env vars directly in config string values using `${VAR_NAME}`
 }
 ```
 
-See [Configuration: Env var substitution](/gateway/configuration-reference#env-var-substitution) for full details.
+See [Configuration: Env var substitution](/nb/gateway/configuration-reference#env-var-substitution) for full details.
 
 ## Secret refs vs `${ENV}` strings
 
@@ -99,7 +99,7 @@ Pllan supports two env-driven patterns:
 - `${VAR}` string substitution in config values.
 - SecretRef objects (`{ source: "env", provider: "default", id: "VAR" }`) for fields that support secrets references.
 
-Both resolve from process env at activation time. SecretRef details are documented in [Secrets Management](/gateway/secrets).
+Both resolve from process env at activation time. SecretRef details are documented in [Secrets Management](/nb/gateway/secrets).
 
 ## Path-related env vars
 
@@ -135,6 +135,6 @@ When set, `PLLAN_HOME` replaces the system home directory (`$HOME` / `os.homedir
 
 ## Related
 
-- [Gateway configuration](/gateway/configuration)
-- [FAQ: env vars and .env loading](/help/faq#env-vars-and-env-loading)
-- [Models overview](/concepts/models)
+- [Gateway configuration](/nb/gateway/configuration)
+- [FAQ: env vars and .env loading](/nb/help/faq#env-vars-and-env-loading)
+- [Models overview](/nb/concepts/models)

package/docs/nb/help/faq.md

@@ -8,7 +8,7 @@ title: "FAQ"
 
 # FAQ
 
-Raske svar pluss dypere feilsoking for virkelige oppsett (lokal utvikling, VPS, fler-agent, OAuth/API-nokler, modell-failover). For kjoringsdiagnostikk, se [Feilsoking](/gateway/troubleshooting). For fullstendig konfigurasjonsreferanse, se [Konfigurasjon](/gateway/configuration).
+Raske svar pluss dypere feilsoking for virkelige oppsett (lokal utvikling, VPS, fler-agent, OAuth/API-nokler, modell-failover). For kjoringsdiagnostikk, se [Feilsoking](/nb/gateway/troubleshooting). For fullstendig konfigurasjonsreferanse, se [Konfigurasjon](/nb/gateway/configuration).
 
 ## Forste 60 sekunder hvis noe er odelatt
 
@@ -42,7 +42,7 @@ Raske svar pluss dypere feilsoking for virkelige oppsett (lokal utvikling, VPS,
    pllan status --deep
    ```
 
-   Kjorer gateway-helsesjekker + leverandorprober (krever en tilgjengelig gateway). Se [Helse](/gateway/health).
+   Kjorer gateway-helsesjekker + leverandorprober (krever en tilgjengelig gateway). Se [Helse](/nb/gateway/health).
 
 5. **Hale den nyeste loggen**
 
@@ -56,7 +56,7 @@ Raske svar pluss dypere feilsoking for virkelige oppsett (lokal utvikling, VPS,
    pllan doctor
    ```
 
-   Reparerer/migrerer konfigurasjon/tilstand + kjorer helsesjekker. Se [Doktor](/gateway/doctor).
+   Reparerer/migrerer konfigurasjon/tilstand + kjorer helsesjekker. Se [Doktor](/nb/gateway/doctor).
 
 7. **Gateway-overblikk**
 

package/docs/nb/help/index.md

@@ -10,19 +10,19 @@ title: "Hjelp"
 
 Hvis du vil ha en rask «kom deg videre»-flyt, start her:
 
-- **Feilsoking:** [Start her](/help/troubleshooting)
-- **Installasjonssjekk (Node/npm/PATH):** [Installer](/install/node#troubleshooting)
-- **Gateway-problemer:** [Gateway-feilsoking](/gateway/troubleshooting)
-- **Logger:** [Logging](/logging) og [Gateway-logging](/gateway/logging)
-- **Reparasjoner:** [Doktor](/gateway/doctor)
+- **Feilsoking:** [Start her](/nb/help/troubleshooting)
+- **Installasjonssjekk (Node/npm/PATH):** [Installer](/nb/install/node#troubleshooting)
+- **Gateway-problemer:** [Gateway-feilsoking](/nb/gateway/troubleshooting)
+- **Logger:** [Logging](/nb/logging) og [Gateway-logging](/nb/gateway/logging)
+- **Reparasjoner:** [Doktor](/nb/gateway/doctor)
 
 Hvis du leter etter konseptuelle sporsmal (ikke «noe gikk galt»):
 
-- [FAQ (konsepter)](/help/faq)
+- [FAQ (konsepter)](/nb/help/faq)
 
 ## Miljo og feilsoking
 
-- **Miljovaribler:** [Hvor Pllan laster miljovaribler og prioritet](/help/environment)
-- **Feilsoking:** [Overvakingsmodus, rastremmer og utviklerprofil](/help/debugging)
-- **Testing:** [Testserier, live-tester og Docker-kjoremiljoer](/help/testing)
-- **Skript:** [Depoets hjelpeskript](/help/scripts)
+- **Miljovaribler:** [Hvor Pllan laster miljovaribler og prioritet](/nb/help/environment)
+- **Feilsoking:** [Overvakingsmodus, rastremmer og utviklerprofil](/nb/help/debugging)
+- **Testing:** [Testserier, live-tester og Docker-kjoremiljoer](/nb/help/testing)
+- **Skript:** [Depoets hjelpeskript](/nb/help/scripts)

package/docs/nb/help/scripts.md

@@ -20,7 +20,7 @@ Use these when a task is clearly tied to a script; otherwise prefer the CLI.
 ## Auth monitoring scripts
 
 Auth monitoring scripts are documented here:
-[/automation/auth-monitoring](/automation/auth-monitoring)
+[/automation/auth-monitoring](/nb/automation/auth-monitoring)
 
 ## When adding scripts
 

package/docs/nb/help/testing.md

@@ -148,7 +148,7 @@ Use this decision table:
 - Optional target overrides:
   - `PLLAN_ANDROID_NODE_ID` or `PLLAN_ANDROID_NODE_NAME`.
   - `PLLAN_ANDROID_GATEWAY_URL` / `PLLAN_ANDROID_GATEWAY_TOKEN` / `PLLAN_ANDROID_GATEWAY_PASSWORD`.
-- Full Android setup details: [Android App](/platforms/android)
+- Full Android setup details: [Android App](/nb/platforms/android)
 
 ## Live: model smoke (profile keys)
 
@@ -449,7 +449,7 @@ We already have a few CI-safe tests that behave like “agent reliability evals
 - Mock tool-calling through the real gateway + agent loop (`src/gateway/gateway.test.ts`).
 - End-to-end wizard flows that validate session wiring and config effects (`src/gateway/gateway.test.ts`).
 
-What’s still missing for skills (see [Skills](/tools/skills)):
+What’s still missing for skills (see [Skills](/nb/tools/skills)):
 
 - **Decisioning:** when skills are listed in the prompt, does the agent pick the right skill (or avoid irrelevant ones)?
 - **Compliance:** does the agent read `SKILL.md` before use and follow required steps/args?