pllan 2026.3.47 → 2026.3.49

package/docs/nb/tools/pdf.md

@@ -99,7 +99,7 @@ Fallback details:
 }
 ```
 
-See [Configuration Reference](/gateway/configuration-reference) for full field details.
+See [Configuration Reference](/nb/gateway/configuration-reference) for full field details.
 
 ## Output details
 

package/docs/nb/tools/perplexity-search.md

@@ -91,7 +91,7 @@ That field also accepts SecretRef objects.
 
 **Via environment:** set `PERPLEXITY_API_KEY` or `OPENROUTER_API_KEY`
 in the Gateway process environment. For a gateway install, put it in
-`~/.pllan/.env` (or your service environment). See [Env vars](/help/faq#how-does-pllan-load-environment-variables).
+`~/.pllan/.env` (or your service environment). See [Env vars](/nb/help/faq#how-does-pllan-load-environment-variables).
 
 If `provider: "perplexity"` is configured and the Perplexity key SecretRef is unresolved with no env fallback, startup/reload fails fast.
 
@@ -170,5 +170,5 @@ await web_search({
 - OpenRouter or explicit `plugins.entries.perplexity.config.webSearch.baseUrl` / `model` switches Perplexity back to Sonar chat completions for compatibility
 - Results are cached for 15 minutes by default (configurable via `cacheTtlMinutes`)
 
-See [Web tools](/tools/web) for the full web_search configuration.
+See [Web tools](/nb/tools/web) for the full web_search configuration.
 See [Perplexity Search API docs](https://docs.perplexity.ai/docs/search/quickstart) for more details.

package/docs/nb/tools/plugin.md

@@ -31,14 +31,14 @@ pllan plugins list
 pllan plugins install @pllan/voice-call
 ```
 
-Npm specs are registry-only. See [install rules](/cli/plugins#install) for
+Npm specs are registry-only. See [install rules](/nb/cli/plugins#install) for
 details on pinning, prerelease gating, and supported spec formats.
 
 3. Restart the Gateway, then configure under `plugins.entries.<id>.config`.
 
-See [Voice Call](/plugins/voice-call) for a concrete example plugin.
-Looking for third-party listings? See [Community plugins](/plugins/community).
-Need the bundle compatibility details? See [Plugin bundles](/plugins/bundles).
+See [Voice Call](/nb/plugins/voice-call) for a concrete example plugin.
+Looking for third-party listings? See [Community plugins](/nb/plugins/community).
+Need the bundle compatibility details? See [Plugin bundles](/nb/plugins/bundles).
 
 For compatible bundles, install from a local directory or archive:
 
@@ -67,12 +67,12 @@ These are published to npm and installed with `pllan plugins install`:
 
 | Plugin          | Package                | Docs                                 |
 | --------------- | ---------------------- | ------------------------------------ |
-| Matrix          | `@pllan/matrix`     | [Matrix](/channels/matrix)           |
-| Microsoft Teams | `@pllan/msteams`    | [Microsoft Teams](/channels/msteams) |
-| Nostr           | `@pllan/nostr`      | [Nostr](/channels/nostr)             |
-| Voice Call      | `@pllan/voice-call` | [Voice Call](/plugins/voice-call)    |
-| Zalo            | `@pllan/zalo`       | [Zalo](/channels/zalo)               |
-| Zalo Personal   | `@pllan/zalouser`   | [Zalo Personal](/plugins/zalouser)   |
+| Matrix          | `@pllan/matrix`     | [Matrix](/nb/channels/matrix)           |
+| Microsoft Teams | `@pllan/msteams`    | [Microsoft Teams](/nb/channels/msteams) |
+| Nostr           | `@pllan/nostr`      | [Nostr](/nb/channels/nostr)             |
+| Voice Call      | `@pllan/voice-call` | [Voice Call](/nb/plugins/voice-call)    |
+| Zalo            | `@pllan/zalo`       | [Zalo](/nb/channels/zalo)               |
+| Zalo Personal   | `@pllan/zalouser`   | [Zalo Personal](/nb/plugins/zalouser)   |
 
 Microsoft Teams is plugin-only as of 2026.1.15.
 
@@ -115,7 +115,7 @@ Pllan also recognizes compatible external bundle layouts:
 They are shown in the plugin list as `format=bundle`, with a subtype of
 `codex`, `claude`, or `cursor` in verbose/inspect output.
 
-See [Plugin bundles](/plugins/bundles) for the exact detection rules, mapping
+See [Plugin bundles](/nb/plugins/bundles) for the exact detection rules, mapping
 behavior, and current support matrix.
 
 ## Config
@@ -144,7 +144,7 @@ Fields:
 - `entries.<id>`: per-plugin toggles + config
 
 Config changes **require a gateway restart**. See
-[Configuration reference](/configuration) for the full config schema.
+[Configuration reference](/nb/configuration) for the full config schema.
 
 Validation rules (strict):
 
@@ -252,7 +252,7 @@ Supported exclusive slots:
 
 If multiple plugins declare `kind: "memory"` or `kind: "context-engine"`, only
 the selected plugin loads for that slot. Others are disabled with diagnostics.
-Declare `kind` in your [plugin manifest](/plugins/manifest).
+Declare `kind` in your [plugin manifest](/nb/plugins/manifest).
 
 ## Plugin IDs
 
@@ -293,7 +293,7 @@ pllan plugins disable <id>
 pllan plugins doctor
 ```
 
-See [`pllan plugins` CLI reference](/cli/plugins) for full details on each
+See [`pllan plugins` CLI reference](/nb/cli/plugins) for full details on each
 command (install rules, inspect output, marketplace installs, uninstall).
 
 Plugins may also register their own top-level commands (example:
@@ -322,16 +322,16 @@ Plugins export either:
 - `registerContextEngine`
 - `registerService`
 
-See [Plugin manifest](/plugins/manifest) for the manifest file format.
+See [Plugin manifest](/nb/plugins/manifest) for the manifest file format.
 
 ## Further reading
 
-- [Plugin architecture and internals](/plugins/architecture) -- capability model,
+- [Plugin architecture and internals](/nb/plugins/architecture) -- capability model,
   ownership model, contracts, load pipeline, runtime helpers, and developer API
   reference
-- [Building extensions](/plugins/building-extensions)
-- [Plugin bundles](/plugins/bundles)
-- [Plugin manifest](/plugins/manifest)
-- [Plugin agent tools](/plugins/agent-tools)
-- [Capability Cookbook](/tools/capability-cookbook)
-- [Community plugins](/plugins/community)
+- [Building extensions](/nb/plugins/building-extensions)
+- [Plugin bundles](/nb/plugins/bundles)
+- [Plugin manifest](/nb/plugins/manifest)
+- [Plugin agent tools](/nb/plugins/agent-tools)
+- [Capability Cookbook](/nb/tools/capability-cookbook)
+- [Community plugins](/nb/plugins/community)

package/docs/nb/tools/skills.md

@@ -44,14 +44,14 @@ Plugins can ship their own skills by listing `skills` directories in
 `pllan.plugin.json` (paths relative to the plugin root). Plugin skills load
 when the plugin is enabled and participate in the normal skill precedence rules.
 You can gate them via `metadata.pllan.requires.config` on the plugin’s config
-entry. See [Plugins](/tools/plugin) for discovery/config and [Tools](/tools) for the
+entry. See [Plugins](/nb/tools/plugin) for discovery/config and [Tools](/nb/tools) for the
 tool surface those skills teach.
 
 ## ClawHub (install + sync)
 
 ClawHub is the public skills registry for Pllan. Browse at
 [https://clawhub.com](https://clawhub.com). Use it to discover, install, update, and back up skills.
-Full guide: [ClawHub](/tools/clawhub).
+Full guide: [ClawHub](/nb/tools/clawhub).
 
 Common flows:
 
@@ -69,11 +69,11 @@ that up as `<workspace>/skills` on the next session.
 ## Security notes
 
 - Treat third-party skills as **untrusted code**. Read them before enabling.
-- Prefer sandboxed runs for untrusted inputs and risky tools. See [Sandboxing](/gateway/sandboxing).
+- Prefer sandboxed runs for untrusted inputs and risky tools. See [Sandboxing](/nb/gateway/sandboxing).
 - Workspace and extra-dir skill discovery only accepts skill roots and `SKILL.md` files whose resolved realpath stays inside the configured root.
 - `skills.entries.*.env` and `skills.entries.*.apiKey` inject secrets into the **host** process
   for that agent turn (not the sandbox). Keep secrets out of prompts and logs.
-- For a broader threat model and checklists, see [Security](/gateway/security).
+- For a broader threat model and checklists, see [Security](/nb/gateway/security).
 
 ## Format (AgentSkills + Pi-compatible)
 
@@ -297,7 +297,7 @@ copy). Workspace skills are user-owned and override both on name conflicts.
 
 ## Config reference
 
-See [Skills config](/tools/skills-config) for the full configuration schema.
+See [Skills config](/nb/tools/skills-config) for the full configuration schema.
 
 ## Looking for more skills?
 

package/docs/nb/tools/slash-commands.md

@@ -80,7 +80,7 @@ Text + native (when enabled):
 - `/allowlist` (list/add/remove allowlist entries)
 - `/approve <id> allow-once|allow-always|deny` (resolve exec approval prompts)
 - `/context [list|detail|json]` (explain “context”; `detail` shows per-file + per-tool + per-skill + system prompt size)
-- `/btw <question>` (ask an ephemeral side question about the current session without changing future session context; see [/tools/btw](/tools/btw))
+- `/btw <question>` (ask an ephemeral side question about the current session without changing future session context; see [/tools/btw](/nb/tools/btw))
 - `/export-session [path]` (alias: `/export`) (export current session to HTML with full system prompt)
 - `/whoami` (show your sender id; alias: `/id`)
 - `/session idle <duration|off>` (manage inactivity auto-unfocus for focused thread bindings)
@@ -98,7 +98,7 @@ Text + native (when enabled):
 - `/plugins list|show|get|enable|disable` (inspect discovered plugins and toggle enablement, owner-only for writes; requires `commands.plugins: true`)
 - `/debug show|set|unset|reset` (runtime overrides, owner-only; requires `commands.debug: true`)
 - `/usage off|tokens|full|cost` (per-response usage footer or local cost summary)
-- `/tts off|always|inbound|tagged|status|provider|limit|summary|audio` (control TTS; see [/tts](/tools/tts))
+- `/tts off|always|inbound|tagged|status|provider|limit|summary|audio` (control TTS; see [/tts](/nb/tools/tts))
   - Discord: native command is `/voice` (Discord reserves `/tts`); text `/tts` still works.
 - `/stop`
 - `/restart`
@@ -120,7 +120,7 @@ Text + native (when enabled):
 
 Text-only:
 
-- `/compact [instructions]` (see [/concepts/compaction](/concepts/compaction))
+- `/compact [instructions]` (see [/concepts/compaction](/nb/concepts/compaction))
 - `! <command>` (host-only; one at a time; use `!poll` + `!stop` for long-running jobs)
 - `!poll` (check output / status; accepts optional `sessionId`; `/bash poll` also works)
 - `!stop` (stop the running bash job; accepts optional `sessionId`; `/bash stop` also works)
@@ -136,7 +136,7 @@ Notes:
 - `/restart` is enabled by default; set `commands.restart: false` to disable it.
 - Discord-only native command: `/vc join|leave|status` controls voice channels (requires `channels.discord.voice` and native commands; not available as text).
 - Discord thread-binding commands (`/focus`, `/unfocus`, `/agents`, `/session idle`, `/session max-age`) require effective thread bindings to be enabled (`session.threadBindings.enabled` and/or `channels.discord.threadBindings.enabled`).
-- ACP command reference and runtime behavior: [ACP Agents](/tools/acp-agents).
+- ACP command reference and runtime behavior: [ACP Agents](/nb/tools/acp-agents).
 - `/verbose` is meant for debugging and extra visibility; keep it **off** in normal use.
 - `/fast on|off` persists a session override. Use the Sessions UI `inherit` option to clear it and fall back to config defaults.
 - Tool failure summaries are still shown when relevant, but detailed failure text is only included when `/verbose` is `on` or `full`.
@@ -151,7 +151,7 @@ Notes:
   - `/skill <name> [input]` runs a skill by name (useful when native command limits prevent per-skill commands).
   - By default, skill commands are forwarded to the model as a normal request.
   - Skills may optionally declare `command-dispatch: tool` to route the command directly to a tool (deterministic, no model).
-  - Example: `/prose` (OpenProse plugin) — see [OpenProse](/prose).
+  - Example: `/prose` (OpenProse plugin) — see [OpenProse](/nb/prose).
 - **Native command arguments:** Discord uses autocomplete for dynamic options (and button menus when you omit required args). Telegram and Slack show a button menu when a command supports choices and you omit the arg.
 
 ## Usage surfaces (what shows where)
@@ -290,5 +290,5 @@ Example:
 /btw what are we doing right now?
 ```
 
-See [BTW Side Questions](/tools/btw) for the full behavior and client UX
+See [BTW Side Questions](/nb/tools/btw) for the full behavior and client UX
 details.

package/docs/nb/tools/subagents.md

@@ -53,7 +53,7 @@ These commands work on channels that support persistent thread bindings. See **T
 - `--model` and `--thinking` override defaults for that specific run.
 - Use `info`/`log` to inspect details and output after completion.
 - `/subagents spawn` is one-shot mode (`mode: "run"`). For persistent thread-bound sessions, use `sessions_spawn` with `thread: true` and `mode: "session"`.
-- For ACP harness sessions (Codex, Claude Code, Gemini CLI), use `sessions_spawn` with `runtime: "acp"` and see [ACP Agents](/tools/acp-agents).
+- For ACP harness sessions (Codex, Claude Code, Gemini CLI), use `sessions_spawn` with `runtime: "acp"` and see [ACP Agents](/nb/tools/acp-agents).
 
 Primary goals:
 
@@ -121,7 +121,7 @@ Config switches:
 - Global default: `session.threadBindings.enabled`, `session.threadBindings.idleHours`, `session.threadBindings.maxAgeHours`
 - Channel override and spawn auto-bind keys are adapter-specific. See **Thread supporting channels** above.
 
-See [Configuration Reference](/gateway/configuration-reference) and [Slash commands](/tools/slash-commands) for current adapter details.
+See [Configuration Reference](/nb/gateway/configuration-reference) and [Slash commands](/nb/tools/slash-commands) for current adapter details.
 
 Allowlist:
 

package/docs/nb/tools/tavily.md

@@ -122,4 +122,4 @@ Tips:
 | Search with depth, topic, AI answers | `tavily_search`  |
 | Extract content from specific URLs   | `tavily_extract` |
 
-See [Web tools](/tools/web) for the full web tool setup and provider comparison.
+See [Web tools](/nb/tools/web) for the full web tool setup and provider comparison.

package/docs/nb/tools/thinking.md

@@ -79,7 +79,7 @@ title: "Thinking Levels"
 
 ## Related
 
-- Elevated mode docs live in [Elevated mode](/tools/elevated).
+- Elevated mode docs live in [Elevated mode](/nb/tools/elevated).
 
 ## Heartbeats
 

package/docs/nb/tools/tts.md

@@ -66,7 +66,7 @@ when no OpenAI or ElevenLabs API keys are available.
 ## Config
 
 TTS config lives under `messages.tts` in `pllan.json`.
-Full schema is in [Gateway configuration](/gateway/configuration).
+Full schema is in [Gateway configuration](/nb/gateway/configuration).
 
 ### Minimal config (enable + provider)
 
@@ -363,7 +363,7 @@ Reply -> TTS enabled?
 ## Slash command usage
 
 There is a single command: `/tts`.
-See [Slash commands](/tools/slash-commands) for enablement details.
+See [Slash commands](/nb/tools/slash-commands) for enablement details.
 
 Discord note: `/tts` is a built-in Discord command, so Pllan registers
 `/voice` as the native command there. Text `/tts ...` still works.

package/docs/nb/tools/web.md

@@ -15,7 +15,7 @@ Pllan ships two lightweight web tools:
 - `web_fetch` — HTTP fetch + readable extraction (HTML → markdown/text).
 
 These are **not** browser automation. For JS-heavy sites or logins, use the
-[Browser tool](/tools/browser).
+[Browser tool](/nb/tools/browser).
 
 ## How it works
 
@@ -27,7 +27,7 @@ These are **not** browser automation. For JS-heavy sites or logins, use the
 - The bundled Firecrawl plugin also adds `firecrawl_search` and `firecrawl_scrape` when enabled.
 - The bundled Tavily plugin also adds `tavily_search` and `tavily_extract` when enabled.
 
-See [Brave Search setup](/tools/brave-search), [Perplexity Search setup](/tools/perplexity-search), and [Tavily Search setup](/tools/tavily) for provider-specific details.
+See [Brave Search setup](/nb/tools/brave-search), [Perplexity Search setup](/nb/tools/perplexity-search), and [Tavily Search setup](/nb/tools/tavily) for provider-specific details.
 
 ## Choosing a search provider
 
@@ -114,7 +114,7 @@ All of these fields also support SecretRef objects.
 - Perplexity: `PERPLEXITY_API_KEY` or `OPENROUTER_API_KEY`
 - Tavily: `TAVILY_API_KEY`
 
-For a gateway install, put these in `~/.pllan/.env` (or your service environment). See [Env vars](/help/faq#how-does-pllan-load-environment-variables).
+For a gateway install, put these in `~/.pllan/.env` (or your service environment). See [Env vars](/nb/help/faq#how-does-pllan-load-environment-variables).
 
 ### Config examples
 
@@ -405,7 +405,7 @@ If you set `plugins.entries.perplexity.config.webSearch.baseUrl` / `model`, use
 
 Firecrawl `web_search` supports `query` and `count`. For Firecrawl-specific controls like `sources`, `categories`, result scraping, or scrape timeout, use `firecrawl_search` from the bundled Firecrawl plugin.
 
-Tavily `web_search` supports `query` and `count` (up to 20 results). For Tavily-specific controls like `search_depth`, `topic`, `include_answer`, or domain filters, use `tavily_search` from the bundled Tavily plugin. For URL content extraction, use `tavily_extract`. See [Tavily](/tools/tavily) for details.
+Tavily `web_search` supports `query` and `count` (up to 20 results). For Tavily-specific controls like `search_depth`, `topic`, `include_answer`, or domain filters, use `tavily_search` from the bundled Tavily plugin. For URL content extraction, use `tavily_extract`. See [Tavily](/nb/tools/tavily) for details.
 
 **Examples:**
 
@@ -510,7 +510,7 @@ Notes:
 - `maxChars` is clamped to `tools.web.fetch.maxCharsCap`.
 - `web_fetch` caps the downloaded response body size to `tools.web.fetch.maxResponseBytes` before parsing; oversized responses are truncated and include a warning.
 - `web_fetch` is best-effort extraction; some sites will need the browser tool.
-- See [Firecrawl](/tools/firecrawl) for key setup and service details.
+- See [Firecrawl](/nb/tools/firecrawl) for key setup and service details.
 - Responses are cached (default 15 minutes) to reduce repeated fetches.
 - If you use tool profiles/allowlists, add `web_search`/`web_fetch` or `group:web`.
 - If the API key is missing, `web_search` returns a short setup hint with a docs link.

package/docs/nb/tts.md

@@ -66,7 +66,7 @@ when no OpenAI or ElevenLabs API keys are available.
 ## Config
 
 TTS config lives under `messages.tts` in `pllan.json`.
-Full schema is in [Gateway configuration](/gateway/configuration).
+Full schema is in [Gateway configuration](/nb/gateway/configuration).
 
 ### Minimal config (enable + provider)
 
@@ -363,7 +363,7 @@ Reply -> TTS enabled?
 ## Slash command usage
 
 There is a single command: `/tts`.
-See [Slash commands](/tools/slash-commands) for enablement details.
+See [Slash commands](/nb/tools/slash-commands) for enablement details.
 
 Discord note: `/tts` is a built-in Discord command, so Pllan registers
 `/voice` as the native command there. Text `/tts ...` still works.

package/docs/nb/vps.md

@@ -17,16 +17,16 @@ tuning that applies everywhere.
 ## Pick a provider
 
 <CardGroup cols={2}>
-  <Card title="Railway" href="/install/railway">One-click, browser setup</Card>
-  <Card title="Northflank" href="/install/northflank">One-click, browser setup</Card>
-  <Card title="DigitalOcean" href="/install/digitalocean">Simple paid VPS</Card>
-  <Card title="Oracle Cloud" href="/install/oracle">Always Free ARM tier</Card>
-  <Card title="Fly.io" href="/install/fly">Fly Machines</Card>
-  <Card title="Hetzner" href="/install/hetzner">Docker on Hetzner VPS</Card>
-  <Card title="GCP" href="/install/gcp">Compute Engine</Card>
-  <Card title="Azure" href="/install/azure">Linux VM</Card>
-  <Card title="exe.dev" href="/install/exe-dev">VM with HTTPS proxy</Card>
-  <Card title="Raspberry Pi" href="/install/raspberry-pi">ARM self-hosted</Card>
+  <Card title="Railway" href="/nb/install/railway">One-click, browser setup</Card>
+  <Card title="Northflank" href="/nb/install/northflank">One-click, browser setup</Card>
+  <Card title="DigitalOcean" href="/nb/install/digitalocean">Simple paid VPS</Card>
+  <Card title="Oracle Cloud" href="/nb/install/oracle">Always Free ARM tier</Card>
+  <Card title="Fly.io" href="/nb/install/fly">Fly Machines</Card>
+  <Card title="Hetzner" href="/nb/install/hetzner">Docker on Hetzner VPS</Card>
+  <Card title="GCP" href="/nb/install/gcp">Compute Engine</Card>
+  <Card title="Azure" href="/nb/install/azure">Linux VM</Card>
+  <Card title="exe.dev" href="/nb/install/exe-dev">VM with HTTPS proxy</Card>
+  <Card title="Raspberry Pi" href="/nb/install/raspberry-pi">ARM self-hosted</Card>
 </CardGroup>
 
 **AWS (EC2 / Lightsail / free tier)** also works well.
@@ -42,7 +42,7 @@ A community video walkthrough is available at
 - Secure default: keep the Gateway on loopback and access it via SSH tunnel or Tailscale Serve.
   If you bind to `lan` or `tailnet`, require `gateway.auth.token` or `gateway.auth.password`.
 
-Related pages: [Gateway remote access](/gateway/remote), [Platforms hub](/platforms).
+Related pages: [Gateway remote access](/nb/gateway/remote), [Platforms hub](/nb/platforms).
 
 ## Shared company agent on a VPS
 
@@ -52,7 +52,7 @@ Running a single agent for a team is a valid setup when every user is in the sam
 - Do not sign that runtime into personal Apple/Google accounts or personal browser/password-manager profiles.
 - If users are adversarial to each other, split by gateway/host/OS user.
 
-Security model details: [Security](/gateway/security).
+Security model details: [Security](/nb/gateway/security).
 
 ## Using nodes with a VPS
 
@@ -60,7 +60,7 @@ You can keep the Gateway in the cloud and pair **nodes** on your local devices
 (Mac/iOS/Android/headless). Nodes provide local screen/camera/canvas and `system.run`
 capabilities while the Gateway stays in the cloud.
 
-Docs: [Nodes](/nodes), [Nodes CLI](/cli/nodes).
+Docs: [Nodes](/nb/nodes), [Nodes CLI](/nb/cli/nodes).
 
 ## Startup tuning for small VMs and ARM hosts
 
@@ -78,7 +78,7 @@ source ~/.bashrc
 - `NODE_COMPILE_CACHE` improves repeated command startup times.
 - `PLLAN_NO_RESPAWN=1` avoids extra startup overhead from a self-respawn path.
 - First command run warms the cache; subsequent runs are faster.
-- For Raspberry Pi specifics, see [Raspberry Pi](/install/raspberry-pi).
+- For Raspberry Pi specifics, see [Raspberry Pi](/nb/install/raspberry-pi).
 
 ### systemd tuning checklist (optional)
 

package/docs/nb/web/control-ui.md

@@ -124,4 +124,4 @@ pnpm ui:dev # autoinstallerer grensesnitt-avhengigheter ved forste kjoring
 
 Pek deretter grensesnittet mot din Gateway WS-URL (f.eks. `ws://127.0.0.1:18789`).
 
-Fjerntilgangsoppsett-detaljer: [Fjerntilgang](/gateway/remote).
+Fjerntilgangsoppsett-detaljer: [Fjerntilgang](/nb/gateway/remote).

package/docs/nb/web/dashboard.md

@@ -16,12 +16,12 @@ Hurtigapning (lokal gateway):
 
 Hovedreferanser:
 
-- [Kontrollpanel](/web/control-ui) for bruk og grensesnittfunksjoner.
-- [Tailscale](/gateway/tailscale) for Serve/Funnel-automatisering.
-- [Nettoverflater](/web) for bindingsmoduser og sikkerhetsnotater.
+- [Kontrollpanel](/nb/web/control-ui) for bruk og grensesnittfunksjoner.
+- [Tailscale](/nb/gateway/tailscale) for Serve/Funnel-automatisering.
+- [Nettoverflater](/nb/web) for bindingsmoduser og sikkerhetsnotater.
 
 Autentisering handheves ved WebSocket-handtrykket via `connect.params.auth`
-(token eller passord). Se `gateway.auth` i [Gateway-konfigurasjon](/gateway/configuration).
+(token eller passord). Se `gateway.auth` i [Gateway-konfigurasjon](/nb/gateway/configuration).
 
 Sikkerhetsnotat: kontrollpanelet er en **administrasjonsoverflate** (chat, konfigurasjon, exec-godkjenninger).
 Ikke eksponer det offentlig. Grensesnittet beholder dashbord-URL-tokens i sessionStorage
@@ -38,7 +38,7 @@ Foretrekk localhost, Tailscale Serve eller en SSH-tunnel.
 
 - **Localhost**: apne `http://127.0.0.1:18789/`.
 - **Tokenkilde**: `gateway.auth.token` (eller `PLLAN_GATEWAY_TOKEN`).
-- **Ikke localhost**: bruk Tailscale Serve, tailnet-binding med token, eller en SSH-tunnel. Se [Nettoverflater](/web).
+- **Ikke localhost**: bruk Tailscale Serve, tailnet-binding med token, eller en SSH-tunnel. Se [Nettoverflater](/nb/web).
 
 ## Hvis du ser «unauthorized» / 1008
 

package/docs/nb/web/index.md

@@ -13,13 +13,13 @@ Gatewayen serverer et lite **nettleser-kontrollpanel** (Vite + Lit) fra samme po
 - standard: `http://<vert>:18789/`
 - valgfritt prefiks: sett `gateway.controlUi.basePath` (f.eks. `/pllan`)
 
-Funksjoner beskrives i [Kontrollpanel](/web/control-ui).
+Funksjoner beskrives i [Kontrollpanel](/nb/web/control-ui).
 Denne siden fokuserer pa bindingsmoduser, sikkerhet og nettvendte overflater.
 
 ## Webhooks
 
 Nar `hooks.enabled=true`, eksponerer gatewayen ogsa et lite webhook-endepunkt pa samme HTTP-server.
-Se [Gateway-konfigurasjon](/gateway/configuration) -> `hooks` for autentisering + nyttelaster.
+Se [Gateway-konfigurasjon](/nb/gateway/configuration) -> `hooks` for autentisering + nyttelaster.
 
 ## Konfigurasjon (pa som standard)
 
@@ -107,7 +107,7 @@ Apne:
   nar `gateway.auth.allowTailscale` er `true` (ingen token/passord pakreves).
   HTTP API-endepunkter krever fortsatt token/passord. Sett
   `gateway.auth.allowTailscale: false` for a kreve eksplisitt legitimasjon. Se
-  [Tailscale](/gateway/tailscale) og [Sikkerhet](/gateway/security). Denne
+  [Tailscale](/nb/gateway/tailscale) og [Sikkerhet](/nb/gateway/security). Denne
   tokenlose flyten forutsetter at gateway-verten er betrodd.
 - `gateway.tailscale.mode: "funnel"` krever `gateway.auth.mode: "password"` (delt passord).
 

package/docs/nb/web/tui.md

@@ -95,7 +95,7 @@ Sesjonslivssyklus:
 - `/settings`
 - `/exit`
 
-Andre Gateway-skrastrekskommandoer (for eksempel `/context`) videresendes til gatewayen og vises som systemutdata. Se [Skrastrekskommandoer](/tools/slash-commands).
+Andre Gateway-skrastrekskommandoer (for eksempel `/context`) videresendes til gatewayen og vises som systemutdata. Se [Skrastrekskommandoer](/nb/tools/slash-commands).
 
 ## Lokale skallkommandoer
 

package/docs/nb/web/webchat.md

@@ -37,7 +37,7 @@ Status: macOS/iOS SwiftUI chat-grensesnittet snakker direkte til Gateway WebSock
 
 ## Konfigurasjonsreferanse (WebChat)
 
-Fullstendig konfigurasjon: [Konfigurasjon](/gateway/configuration)
+Fullstendig konfigurasjon: [Konfigurasjon](/nb/gateway/configuration)
 
 Kanalalternativer:
 

package/docs/sv/automation/cron-jobs.md

@@ -9,7 +9,7 @@ title: "Cron Jobs"
 
 # Cron jobs (Gateway scheduler)
 
-> **Cron vs Heartbeat?** See [Cron vs Heartbeat](/automation/cron-vs-heartbeat) for guidance on when to use each.
+> **Cron vs Heartbeat?** See [Cron vs Heartbeat](/sv/automation/cron-vs-heartbeat) for guidance on when to use each.
 
 Cron is the Gateway’s built-in scheduler. It persists jobs, wakes the agent at
 the right time, and can optionally deliver output back to a chat.
@@ -17,7 +17,7 @@ the right time, and can optionally deliver output back to a chat.
 If you want _“run this every morning”_ or _“poke the agent in 20 minutes”_,
 cron is the mechanism.
 
-Troubleshooting: [/automation/troubleshooting](/automation/troubleshooting)
+Troubleshooting: [/automation/troubleshooting](/sv/automation/troubleshooting)
 
 ## TL;DR
 
@@ -67,7 +67,7 @@ pllan cron add \
 
 ## Tool-call equivalents (Gateway cron tool)
 
-For the canonical JSON shapes and examples, see [JSON schema for tool calls](/automation/cron-jobs#json-schema-for-tool-calls).
+For the canonical JSON shapes and examples, see [JSON schema for tool calls](/sv/automation/cron-jobs#json-schema-for-tool-calls).
 
 ## Where cron jobs are stored
 
@@ -153,7 +153,7 @@ They must use `payload.kind = "systemEvent"`.
 - `wakeMode: "next-heartbeat"`: event waits for the next scheduled heartbeat.
 
 This is the best fit when you want the normal heartbeat prompt + main-session context.
-See [Heartbeat](/gateway/heartbeat).
+See [Heartbeat](/sv/gateway/heartbeat).
 
 #### Isolated jobs (dedicated cron sessions)
 
@@ -437,7 +437,7 @@ When a job fails, Pllan classifies errors as **transient** (retryable) or **perm
 - On any error: apply exponential backoff (30s → 1m → 5m → 15m → 60m) before the next scheduled run.
 - Job stays enabled; backoff resets after the next successful run.
 
-Configure `cron.retry` to override these defaults (see [Configuration](/automation/cron-jobs#configuration)).
+Configure `cron.retry` to override these defaults (see [Configuration](/sv/automation/cron-jobs#configuration)).
 
 ## Configuration
 
@@ -696,7 +696,7 @@ pllan system event --mode now --text "Next heartbeat: check battery."
 
 - `cron.list`, `cron.status`, `cron.add`, `cron.update`, `cron.remove`
 - `cron.run` (force or due), `cron.runs`
-  For immediate system events without a job, use [`pllan system event`](/cli/system).
+  For immediate system events without a job, use [`pllan system event`](/sv/cli/system).
 
 ## Troubleshooting
 
@@ -711,7 +711,7 @@ pllan system event --mode now --text "Next heartbeat: check battery."
 - Pllan applies exponential retry backoff for recurring jobs after consecutive errors:
   30s, 1m, 5m, 15m, then 60m between retries.
 - Backoff resets automatically after the next successful run.
-- One-shot (`at`) jobs retry transient errors (rate limit, overloaded, network, server_error) up to 3 times with backoff; permanent errors disable immediately. See [Retry policy](/automation/cron-jobs#retry-policy).
+- One-shot (`at`) jobs retry transient errors (rate limit, overloaded, network, server_error) up to 3 times with backoff; permanent errors disable immediately. See [Retry policy](/sv/automation/cron-jobs#retry-policy).
 
 ### Telegram delivers to the wrong place
 

package/docs/sv/automation/cron-vs-heartbeat.md

@@ -70,7 +70,7 @@ The agent reads this on each heartbeat and handles all items in one turn.
 }
 ```
 
-See [Heartbeat](/gateway/heartbeat) for full configuration.
+See [Heartbeat](/sv/gateway/heartbeat) for full configuration.
 
 ## Cron: Precise Scheduling
 
@@ -128,7 +128,7 @@ pllan cron add \
   --delete-after-run
 ```
 
-See [Cron jobs](/automation/cron-jobs) for full CLI reference.
+See [Cron jobs](/sv/automation/cron-jobs) for full CLI reference.
 
 ## Decision Flowchart
 
@@ -213,7 +213,7 @@ For ad-hoc workflows, call pllan directly.
 - The tool is an **optional plugin**; enable it additively via `tools.alsoAllow: ["pllan"]` (recommended).
 - pllan expects the `pllan` CLI to be available on `PATH`.
 
-See [pllan](/tools/pllan) for full usage and examples.
+See [pllan](/sv/tools/pllan) for full usage and examples.
 
 ## Main Session vs Isolated Session
 
@@ -281,6 +281,6 @@ pllan cron add \
 
 ## Related
 
-- [Heartbeat](/gateway/heartbeat) - full heartbeat configuration
-- [Cron jobs](/automation/cron-jobs) - full cron CLI and API reference
-- [System](/cli/system) - system events + heartbeat controls
+- [Heartbeat](/sv/gateway/heartbeat) - full heartbeat configuration
+- [Cron jobs](/sv/automation/cron-jobs) - full cron CLI and API reference
+- [System](/sv/cli/system) - system events + heartbeat controls

package/docs/sv/automation/gmail-pubsub.md

@@ -14,7 +14,7 @@ Goal: Gmail watch -> Pub/Sub push -> `gog gmail watch serve` -> Pllan webhook.
 
 - `gcloud` installed and logged in ([install guide](https://docs.cloud.google.com/sdk/docs/install-sdk)).
 - `gog` (gogcli) installed and authorized for the Gmail account ([gogcli.sh](https://gogcli.sh/)).
-- Pllan hooks enabled (see [Webhooks](/automation/webhook)).
+- Pllan hooks enabled (see [Webhooks](/sv/automation/webhook)).
 - `tailscale` logged in ([tailscale.com](https://tailscale.com/)). Supported setup uses Tailscale Funnel for the public HTTPS endpoint.
   Other tunnel services can work, but are DIY/unsupported and require manual wiring.
   Right now, Tailscale is what we support.
@@ -88,7 +88,7 @@ Notes:
   To disable (dangerous), set `hooks.gmail.allowUnsafeExternalContent: true`.
 
 To customize payload handling further, add `hooks.mappings` or a JS/TS transform module
-under `~/.pllan/hooks/transforms` (see [Webhooks](/automation/webhook)).
+under `~/.pllan/hooks/transforms` (see [Webhooks](/sv/automation/webhook)).
 
 ## Wizard (recommended)
 

package/docs/sv/automation/hooks.md

@@ -15,9 +15,9 @@ Hooks provide an extensible event-driven system for automating actions in respon
 Hooks are small scripts that run when something happens. There are two kinds:
 
 - **Hooks** (this page): run inside the Gateway when agent events fire, like `/new`, `/reset`, `/stop`, or lifecycle events.
-- **Webhooks**: external HTTP webhooks that let other systems trigger work in Pllan. See [Webhook Hooks](/automation/webhook) or use `pllan webhooks` for Gmail helper commands.
+- **Webhooks**: external HTTP webhooks that let other systems trigger work in Pllan. See [Webhook Hooks](/sv/automation/webhook) or use `pllan webhooks` for Gmail helper commands.
 
-Hooks can also be bundled inside plugins; see [Plugin hooks](/plugins/architecture#provider-runtime-hooks).
+Hooks can also be bundled inside plugins; see [Plugin hooks](/sv/plugins/architecture#provider-runtime-hooks).
 
 Common uses:
 
@@ -362,7 +362,7 @@ export default handler;
 
 These hooks are not event-stream listeners; they let plugins synchronously adjust tool results before Pllan persists them.
 
-- **`tool_result_persist`**: transform tool results before they are written to the session transcript. Must be synchronous; return the updated tool result payload or `undefined` to keep it as-is. See [Agent Loop](/concepts/agent-loop).
+- **`tool_result_persist`**: transform tool results before they are written to the session transcript. Must be synchronous; return the updated tool result payload or `undefined` to keep it as-is. See [Agent Loop](/sv/concepts/agent-loop).
 
 ### Plugin Hook Events
 
@@ -1043,7 +1043,7 @@ node -e "import('./path/to/handler.ts').then(console.log)"
 
 ## See Also
 
-- [CLI Reference: hooks](/cli/hooks)
+- [CLI Reference: hooks](/sv/cli/hooks)
 - [Bundled Hooks README](https://github.com/pllan/pllan/tree/main/src/hooks/bundled)
-- [Webhook Hooks](/automation/webhook)
-- [Configuration](/gateway/configuration-reference#hooks)
+- [Webhook Hooks](/sv/automation/webhook)
+- [Configuration](/sv/gateway/configuration-reference#hooks)