pllan 2026.3.47 → 2026.3.49

package/docs/nb/channels/pairing.md

@@ -15,13 +15,13 @@ Det brukes to steder:
 1. **DM-sammenkobling** (hvem som far lov til a snakke med boten)
 2. **Nodesammenkobling** (hvilke enheter/noder som far bli med i gateway-nettverket)
 
-Sikkerhetskontekst: [Sikkerhet](/gateway/security)
+Sikkerhetskontekst: [Sikkerhet](/nb/gateway/security)
 
 ## 1) DM-sammenkobling (innkommende chat-tilgang)
 
 Nar en kanal er konfigurert med DM-retningslinje `pairing`, far ukjente avsendere en kort kode, og meldingen deres blir **ikke behandlet** for du godkjenner.
 
-Standard DM-retningslinjer er dokumentert i: [Sikkerhet](/gateway/security)
+Standard DM-retningslinjer er dokumentert i: [Sikkerhet](/nb/gateway/security)
 
 Sammenkoblingskoder:
 
@@ -102,13 +102,13 @@ Lagret under `~/.pllan/devices/`:
 
 ## Relatert dokumentasjon
 
-- Sikkerhetsmodell + prompt-injeksjon: [Sikkerhet](/gateway/security)
-- Oppdater trygt (kjor doktor): [Oppdatering](/install/updating)
+- Sikkerhetsmodell + prompt-injeksjon: [Sikkerhet](/nb/gateway/security)
+- Oppdater trygt (kjor doktor): [Oppdatering](/nb/install/updating)
 - Kanalkonfigurasjoner:
-  - Telegram: [Telegram](/channels/telegram)
-  - WhatsApp: [WhatsApp](/channels/whatsapp)
-  - Signal: [Signal](/channels/signal)
-  - BlueBubbles (iMessage): [BlueBubbles](/channels/bluebubbles)
-  - iMessage (eldre): [iMessage](/channels/imessage)
-  - Discord: [Discord](/channels/discord)
-  - Slack: [Slack](/channels/slack)
+  - Telegram: [Telegram](/nb/channels/telegram)
+  - WhatsApp: [WhatsApp](/nb/channels/whatsapp)
+  - Signal: [Signal](/nb/channels/signal)
+  - BlueBubbles (iMessage): [BlueBubbles](/nb/channels/bluebubbles)
+  - iMessage (eldre): [iMessage](/nb/channels/imessage)
+  - Discord: [Discord](/nb/channels/discord)
+  - Slack: [Slack](/nb/channels/slack)

package/docs/nb/channels/signal.md

@@ -99,7 +99,7 @@ Example:
 }
 ```
 
-Multi-account support: use `channels.signal.accounts` with per-account config and optional `name`. See [`gateway/configuration`](/gateway/configuration-reference#multi-account-all-channels) for the shared pattern.
+Multi-account support: use `channels.signal.accounts` with per-account config and optional `name`. See [`gateway/configuration`](/nb/gateway/configuration-reference#multi-account-all-channels) for the shared pattern.
 
 ## Setup path B: register dedicated bot number (SMS, Linux)
 
@@ -188,7 +188,7 @@ DMs:
 - Approve via:
   - `pllan pairing list signal`
   - `pllan pairing approve signal <CODE>`
-- Pairing is the default token exchange for Signal DMs. Details: [Pairing](/channels/pairing)
+- Pairing is the default token exchange for Signal DMs. Details: [Pairing](/nb/channels/pairing)
 - UUID-only senders (from `sourceUuid`) are stored as `uuid:<id>` in `channels.signal.allowFrom`.
 
 Groups:
@@ -284,7 +284,7 @@ pgrep -af signal-cli
 grep -i "signal" "/tmp/pllan/pllan-$(date +%Y-%m-%d).log" | tail -20
 ```
 
-For triage flow: [/channels/troubleshooting](/channels/troubleshooting).
+For triage flow: [/channels/troubleshooting](/nb/channels/troubleshooting).
 
 ## Security notes
 
@@ -295,7 +295,7 @@ For triage flow: [/channels/troubleshooting](/channels/troubleshooting).
 
 ## Configuration reference (Signal)
 
-Full configuration: [Configuration](/gateway/configuration)
+Full configuration: [Configuration](/nb/gateway/configuration)
 
 Provider options:
 

package/docs/nb/channels/slack.md

@@ -10,13 +10,13 @@ title: "Slack"
 Status: production-ready for DMs + channels via Slack app integrations. Default mode is Socket Mode; HTTP Events API mode is also supported.
 
 <CardGroup cols={3}>
-  <Card title="Pairing" icon="link" href="/channels/pairing">
+  <Card title="Pairing" icon="link" href="/nb/channels/pairing">
     Slack DMs default to pairing mode.
   </Card>
-  <Card title="Slash commands" icon="terminal" href="/tools/slash-commands">
+  <Card title="Slash commands" icon="terminal" href="/nb/tools/slash-commands">
     Native command behavior and command catalog.
   </Card>
-  <Card title="Channel troubleshooting" icon="wrench" href="/channels/troubleshooting">
+  <Card title="Channel troubleshooting" icon="wrench" href="/nb/channels/troubleshooting">
     Cross-channel diagnostics and repair playbooks.
   </Card>
 </CardGroup>
@@ -583,7 +583,7 @@ Legacy keys:
 
 Primary reference:
 
-- [Configuration reference - Slack](/gateway/configuration-reference#slack)
+- [Configuration reference - Slack](/nb/gateway/configuration-reference#slack)
 
   High-signal Slack fields:
   - mode/auth: `mode`, `botToken`, `appToken`, `signingSecret`, `webhookPath`, `accounts.*`
@@ -596,8 +596,8 @@ Primary reference:
 
 ## Related
 
-- [Pairing](/channels/pairing)
-- [Channel routing](/channels/channel-routing)
-- [Troubleshooting](/channels/troubleshooting)
-- [Configuration](/gateway/configuration)
-- [Slash commands](/tools/slash-commands)
+- [Pairing](/nb/channels/pairing)
+- [Channel routing](/nb/channels/channel-routing)
+- [Troubleshooting](/nb/channels/troubleshooting)
+- [Configuration](/nb/gateway/configuration)
+- [Slash commands](/nb/tools/slash-commands)

package/docs/nb/channels/synology-chat.md

@@ -22,7 +22,7 @@ Install from a local checkout:
 pllan plugins install ./extensions/synology-chat
 ```
 
-Details: [Plugins](/tools/plugin)
+Details: [Plugins](/nb/tools/plugin)
 
 ## Quick setup
 

package/docs/nb/channels/telegram.md

@@ -10,13 +10,13 @@ title: "Telegram"
 Status: production-ready for bot DMs + groups via grammY. Long polling is the default mode; webhook mode is optional.
 
 <CardGroup cols={3}>
-  <Card title="Pairing" icon="link" href="/channels/pairing">
+  <Card title="Pairing" icon="link" href="/nb/channels/pairing">
     Default DM policy for Telegram is pairing.
   </Card>
-  <Card title="Channel troubleshooting" icon="wrench" href="/channels/troubleshooting">
+  <Card title="Channel troubleshooting" icon="wrench" href="/nb/channels/troubleshooting">
     Cross-channel diagnostics and repair playbooks.
   </Card>
-  <Card title="Gateway configuration" icon="settings" href="/gateway/configuration">
+  <Card title="Gateway configuration" icon="settings" href="/nb/gateway/configuration">
     Full channel config patterns and examples.
   </Card>
 </CardGroup>
@@ -354,7 +354,7 @@ curl "https://api.telegram.org/bot<bot_token>/getUpdates"
 
     If a device retries with changed auth details (for example role/scopes/public key), the previous pending request is superseded and the new request uses a different `requestId`. Re-run `/pair pending` before approving.
 
-    More details: [Pairing](/channels/pairing#pair-via-telegram-recommended-for-ios).
+    More details: [Pairing](/nb/channels/pairing#pair-via-telegram-recommended-for-ios).
 
   </Accordion>
 
@@ -445,7 +445,7 @@ curl "https://api.telegram.org/bot<bot_token>/getUpdates"
     Note: `edit` and `topic-create` are currently enabled by default and do not have separate `channels.telegram.actions.*` toggles.
     Runtime sends use the active config/secrets snapshot (startup/reload), so action paths do not perform ad-hoc SecretRef re-resolution per send.
 
-    Reaction removal semantics: [/tools/reactions](/tools/reactions)
+    Reaction removal semantics: [/tools/reactions](/nb/tools/reactions)
 
   </Accordion>
 
@@ -824,7 +824,7 @@ pllan message poll --channel telegram --target -1001234567890:topic:42 \
 
     Inline approval buttons also depend on `channels.telegram.capabilities.inlineButtons` allowing the target surface (`dm`, `group`, or `all`).
 
-    Related docs: [Exec approvals](/tools/exec-approvals)
+    Related docs: [Exec approvals](/nb/tools/exec-approvals)
 
   </Accordion>
 </AccordionGroup>
@@ -897,7 +897,7 @@ dig +short api.telegram.org AAAA
   </Accordion>
 </AccordionGroup>
 
-More help: [Channel troubleshooting](/channels/troubleshooting).
+More help: [Channel troubleshooting](/nb/channels/troubleshooting).
 
 ## Telegram config reference pointers
 
@@ -929,7 +929,7 @@ Primary reference:
   - `channels.telegram.groups.<id>.topics.<threadId>.agentId`: route this topic to a specific agent (overrides group-level and binding routing).
 - `channels.telegram.groups.<id>.topics.<threadId>.groupPolicy`: per-topic override for groupPolicy (`open | allowlist | disabled`).
 - `channels.telegram.groups.<id>.topics.<threadId>.requireMention`: per-topic mention gating override.
-- top-level `bindings[]` with `type: "acp"` and canonical topic id `chatId:topic:topicId` in `match.peer.id`: persistent ACP topic binding fields (see [ACP Agents](/tools/acp-agents#channel-specific-settings)).
+- top-level `bindings[]` with `type: "acp"` and canonical topic id `chatId:topic:topicId` in `match.peer.id`: persistent ACP topic binding fields (see [ACP Agents](/nb/tools/acp-agents#channel-specific-settings)).
 - `channels.telegram.direct.<id>.topics.<threadId>.agentId`: route DM topics to a specific agent (same behavior as forum topics).
 - `channels.telegram.execApprovals.enabled`: enable Telegram as a chat-based exec approval client for this account.
 - `channels.telegram.execApprovals.approvers`: Telegram user IDs allowed to approve or deny exec requests. Required when exec approvals are enabled.
@@ -962,7 +962,7 @@ Primary reference:
 - `channels.telegram.reactionNotifications`: `off | own | all` — control which reactions trigger system events (default: `own` when not set).
 - `channels.telegram.reactionLevel`: `off | ack | minimal | extensive` — control agent's reaction capability (default: `minimal` when not set).
 
-- [Configuration reference - Telegram](/gateway/configuration-reference#telegram)
+- [Configuration reference - Telegram](/nb/gateway/configuration-reference#telegram)
 
 Telegram-specific high-signal fields:
 
@@ -981,7 +981,7 @@ Telegram-specific high-signal fields:
 
 ## Related
 
-- [Pairing](/channels/pairing)
-- [Channel routing](/channels/channel-routing)
-- [Multi-agent routing](/concepts/multi-agent)
-- [Troubleshooting](/channels/troubleshooting)
+- [Pairing](/nb/channels/pairing)
+- [Channel routing](/nb/channels/channel-routing)
+- [Multi-agent routing](/nb/concepts/multi-agent)
+- [Troubleshooting](/nb/channels/troubleshooting)

package/docs/nb/channels/tlon.md

@@ -30,7 +30,7 @@ Local checkout (when running from a git repo):
 pllan plugins install ./extensions/tlon
 ```
 
-Details: [Plugins](/tools/plugin)
+Details: [Plugins](/nb/tools/plugin)
 
 ## Setup
 
@@ -249,7 +249,7 @@ Common failures:
 
 ## Configuration reference
 
-Full configuration: [Configuration](/gateway/configuration)
+Full configuration: [Configuration](/nb/gateway/configuration)
 
 Provider options:
 

package/docs/nb/channels/troubleshooting.md

@@ -38,7 +38,7 @@ Sunn grunnlinje:
 | Gruppemeldinger ignoreres       | Sjekk `requireMention` + nevnelsesmontre i konfig   | Nevn boten eller slapp opp nevnelsesretningslinje for gruppen. |
 | Tilfeldige frakoblinger/innloggingslooper | `pllan channels status --probe` + logger     | Logg inn pa nytt og bekreft at legitimasjonskatalogen er sunn. |
 
-Fullstendig feilsoking: [/channels/whatsapp#troubleshooting](/channels/whatsapp#troubleshooting)
+Fullstendig feilsoking: [/channels/whatsapp#troubleshooting](/nb/channels/whatsapp#troubleshooting)
 
 ## Telegram
 
@@ -52,7 +52,7 @@ Fullstendig feilsoking: [/channels/whatsapp#troubleshooting](/channels/whatsapp#
 | `setMyCommands` avvist ved oppstart    | Inspiser logger for `BOT_COMMANDS_TOO_MUCH`      | Reduser tilleggs-/ferdighets-/egendefinerte Telegram-kommandoer eller deaktiver native menyer. |
 | Oppgradert og tilgangsliste blokkerer deg | `pllan security audit` og konfigurasjonstilgangslister | Kjor `pllan doctor --fix` eller erstatt `@brukernavn` med numeriske avsender-IDer. |
 
-Fullstendig feilsoking: [/channels/telegram#troubleshooting](/channels/telegram#troubleshooting)
+Fullstendig feilsoking: [/channels/telegram#troubleshooting](/nb/channels/telegram#troubleshooting)
 
 ## Discord
 
@@ -64,7 +64,7 @@ Fullstendig feilsoking: [/channels/telegram#troubleshooting](/channels/telegram#
 | Gruppemeldinger ignoreres        | Sjekk logger for nevnelsessperringsforkastelser | Nevn bot eller sett guild/kanal `requireMention: false`. |
 | DM-svar mangler                  | `pllan pairing list discord`     | Godkjenn DM-sammenkobling eller juster DM-retningslinje.  |
 
-Fullstendig feilsoking: [/channels/discord#troubleshooting](/channels/discord#troubleshooting)
+Fullstendig feilsoking: [/channels/discord#troubleshooting](/nb/channels/discord#troubleshooting)
 
 ## Slack
 
@@ -76,7 +76,7 @@ Fullstendig feilsoking: [/channels/discord#troubleshooting](/channels/discord#tr
 | DM-er blokkert                           | `pllan pairing list slack`             | Godkjenn sammenkobling eller slapp opp DM-retningslinje. |
 | Kanalmelding ignorert                    | Sjekk `groupPolicy` og kanaltilgangsliste | Tillat kanalen eller bytt retningslinje til `open`. |
 
-Fullstendig feilsoking: [/channels/slack#troubleshooting](/channels/slack#troubleshooting)
+Fullstendig feilsoking: [/channels/slack#troubleshooting](/nb/channels/slack#troubleshooting)
 
 ## iMessage og BlueBubbles
 
@@ -90,8 +90,8 @@ Fullstendig feilsoking: [/channels/slack#troubleshooting](/channels/slack#troubl
 
 Fullstendig feilsoking:
 
-- [/channels/imessage#troubleshooting](/channels/imessage#troubleshooting)
-- [/channels/bluebubbles#troubleshooting](/channels/bluebubbles#troubleshooting)
+- [/channels/imessage#troubleshooting](/nb/channels/imessage#troubleshooting)
+- [/channels/bluebubbles#troubleshooting](/nb/channels/bluebubbles#troubleshooting)
 
 ## Signal
 
@@ -103,7 +103,7 @@ Fullstendig feilsoking:
 | DM blokkert                      | `pllan pairing list signal`             | Godkjenn avsender eller juster DM-retningslinje.         |
 | Gruppesvar utloses ikke          | Sjekk gruppetilgangsliste og nevnelsesmontre | Legg til avsender/gruppe eller slapp opp sperring.      |
 
-Fullstendig feilsoking: [/channels/signal#troubleshooting](/channels/signal#troubleshooting)
+Fullstendig feilsoking: [/channels/signal#troubleshooting](/nb/channels/signal#troubleshooting)
 
 ## Matrix
 
@@ -115,4 +115,4 @@ Fullstendig feilsoking: [/channels/signal#troubleshooting](/channels/signal#trou
 | DM-er behandles ikke                 | `pllan pairing list matrix`               | Godkjenn avsender eller juster DM-retningslinje. |
 | Krypterte rom feiler                 | Bekreft kryptomodul og krypteringsinnstillinger | Aktiver krypteringsstotte og koble til/synkroniser rommet pa nytt. |
 
-Fullstendig feilsoking: [/channels/matrix#troubleshooting](/channels/matrix#troubleshooting)
+Fullstendig feilsoking: [/channels/matrix#troubleshooting](/nb/channels/matrix#troubleshooting)

package/docs/nb/channels/twitch.md

@@ -25,7 +25,7 @@ Local checkout (when running from a git repo):
 pllan plugins install ./extensions/twitch
 ```
 
-Details: [Plugins](/tools/plugin)
+Details: [Plugins](/nb/tools/plugin)
 
 ## Quick setup (beginner)
 
@@ -146,7 +146,7 @@ The bot automatically refreshes tokens before expiration and logs refresh events
 
 ## Multi-account support
 
-Use `channels.twitch.accounts` with per-account tokens. See [`gateway/configuration`](/gateway/configuration) for the shared pattern.
+Use `channels.twitch.accounts` with per-account tokens. See [`gateway/configuration`](/nb/gateway/configuration) for the shared pattern.
 
 Example (one bot account in two channels):
 

package/docs/nb/channels/whatsapp.md

@@ -25,13 +25,13 @@ pllan plugins install @pllan/whatsapp
 ```
 
 <CardGroup cols={3}>
-  <Card title="Pairing" icon="link" href="/channels/pairing">
+  <Card title="Pairing" icon="link" href="/nb/channels/pairing">
     Default DM policy is pairing for unknown senders.
   </Card>
-  <Card title="Channel troubleshooting" icon="wrench" href="/channels/troubleshooting">
+  <Card title="Channel troubleshooting" icon="wrench" href="/nb/channels/troubleshooting">
     Cross-channel diagnostics and repair playbooks.
   </Card>
-  <Card title="Gateway configuration" icon="settings" href="/gateway/configuration">
+  <Card title="Gateway configuration" icon="settings" href="/nb/gateway/configuration">
     Full channel config patterns and examples.
   </Card>
 </CardGroup>
@@ -442,7 +442,7 @@ Behavior notes:
 
 Primary reference:
 
-- [Configuration reference - WhatsApp](/gateway/configuration-reference#whatsapp)
+- [Configuration reference - WhatsApp](/nb/gateway/configuration-reference#whatsapp)
 
 High-signal WhatsApp fields:
 
@@ -454,7 +454,7 @@ High-signal WhatsApp fields:
 
 ## Related
 
-- [Pairing](/channels/pairing)
-- [Channel routing](/channels/channel-routing)
-- [Multi-agent routing](/concepts/multi-agent)
-- [Troubleshooting](/channels/troubleshooting)
+- [Pairing](/nb/channels/pairing)
+- [Channel routing](/nb/channels/channel-routing)
+- [Multi-agent routing](/nb/concepts/multi-agent)
+- [Troubleshooting](/nb/channels/troubleshooting)

package/docs/nb/channels/zalo.md

@@ -15,7 +15,7 @@ Zalo ships as a plugin and is not bundled with the core install.
 
 - Install via CLI: `pllan plugins install @pllan/zalo`
 - Or select **Zalo** during setup and confirm the install prompt
-- Details: [Plugins](/tools/plugin)
+- Details: [Plugins](/nb/tools/plugin)
 
 ## Quick setup (beginner)
 
@@ -117,7 +117,7 @@ Multi-account support: use `channels.zalo.accounts` with per-account tokens and
 - Approve via:
   - `pllan pairing list zalo`
   - `pllan pairing approve zalo <CODE>`
-- Pairing is the default token exchange. Details: [Pairing](/channels/pairing)
+- Pairing is the default token exchange. Details: [Pairing](/nb/channels/pairing)
 - `channels.zalo.allowFrom` accepts numeric user IDs (no username lookup available).
 
 ## Access control (Groups)
@@ -208,7 +208,7 @@ This table summarizes current **Zalo Bot Creator / Marketplace bot** behavior in
 
 ## Configuration reference (Zalo)
 
-Full configuration: [Configuration](/gateway/configuration)
+Full configuration: [Configuration](/nb/gateway/configuration)
 
 The flat top-level keys (`channels.zalo.botToken`, `channels.zalo.dmPolicy`, and similar) are a legacy single-account shorthand. Prefer `channels.zalo.accounts.<id>.*` for new configs. Both forms are still documented here because they exist in the schema.
 

package/docs/nb/channels/zalouser.md

@@ -18,7 +18,7 @@ Zalo Personal ships as a plugin and is not bundled with the core install.
 
 - Install via CLI: `pllan plugins install @pllan/zalouser`
 - Or from a source checkout: `pllan plugins install ./extensions/zalouser`
-- Details: [Plugins](/tools/plugin)
+- Details: [Plugins](/nb/tools/plugin)
 
 No external `zca`/`openzca` CLI binary is required.
 
@@ -161,7 +161,7 @@ Accounts map to `zalouser` profiles in Pllan state. Example:
 - Pllan sends a typing event before dispatching a reply (best-effort).
 - Message reaction action `react` is supported for `zalouser` in channel actions.
   - Use `remove: true` to remove a specific reaction emoji from a message.
-  - Reaction semantics: [Reactions](/tools/reactions)
+  - Reaction semantics: [Reactions](/nb/tools/reactions)
 - For inbound messages that include event metadata, Pllan sends delivered + seen acknowledgements (best-effort).
 
 ## Troubleshooting

package/docs/nb/cli/acp.md

@@ -252,7 +252,7 @@ If your ACP client supports metadata, you can override per session:
 }
 ```
 
-Learn more about session keys at [/concepts/session](/concepts/session).
+Learn more about session keys at [/concepts/session](/nb/concepts/session).
 
 ## Options
 

package/docs/nb/cli/agent.md

@@ -12,7 +12,7 @@ Use `--agent <id>` to target a configured agent directly.
 
 Related:
 
-- Agent send tool: [Agent send](/tools/agent-send)
+- Agent send tool: [Agent send](/nb/tools/agent-send)
 
 ## Examples
 

package/docs/nb/cli/agents.md

@@ -11,8 +11,8 @@ Manage isolated agents (workspaces + auth + routing).
 
 Related:
 
-- Multi-agent routing: [Multi-Agent Routing](/concepts/multi-agent)
-- Agent workspace: [Agent workspace](/concepts/agent-workspace)
+- Multi-agent routing: [Multi-Agent Routing](/nb/concepts/multi-agent)
+- Agent workspace: [Agent workspace](/nb/concepts/agent-workspace)
 
 ## Examples
 

package/docs/nb/cli/approvals.md

@@ -13,8 +13,8 @@ By default, commands target the local approvals file on disk. Use `--gateway` to
 
 Related:
 
-- Exec approvals: [Exec approvals](/tools/exec-approvals)
-- Nodes: [Nodes](/nodes)
+- Exec approvals: [Exec approvals](/nb/tools/exec-approvals)
+- Nodes: [Nodes](/nb/nodes)
 
 ## Common commands
 

package/docs/nb/cli/browser.md

@@ -13,7 +13,7 @@ Manage Pllan’s browser control server and run browser actions (tabs, snapshots
 
 Related:
 
-- Browser tool + API: [Browser tool](/tools/browser)
+- Browser tool + API: [Browser tool](/nb/tools/browser)
 
 ## Common flags
 
@@ -103,4 +103,4 @@ If the Gateway runs on a different machine than the browser, run a **node host**
 
 Use `gateway.nodes.browser.mode` to control auto-routing and `gateway.nodes.browser.node` to pin a specific node if multiple are connected.
 
-Security + remote setup: [Browser tool](/tools/browser), [Remote access](/gateway/remote), [Tailscale](/gateway/tailscale), [Security](/gateway/security)
+Security + remote setup: [Browser tool](/nb/tools/browser), [Remote access](/nb/gateway/remote), [Tailscale](/nb/gateway/tailscale), [Security](/nb/gateway/security)

package/docs/nb/cli/channels.md

@@ -12,8 +12,8 @@ Manage chat channel accounts and their runtime status on the Gateway.
 
 Related docs:
 
-- Channel guides: [Channels](/channels/index)
-- Gateway configuration: [Configuration](/gateway/configuration)
+- Channel guides: [Channels](/nb/channels/index)
+- Gateway configuration: [Configuration](/nb/gateway/configuration)
 
 ## Common commands
 
@@ -44,7 +44,7 @@ When you run `pllan channels add` without flags, the interactive wizard can prom
 
 If you confirm bind now, the wizard asks which agent should own each configured channel account and writes account-scoped routing bindings.
 
-You can also manage the same routing rules later with `pllan agents bindings`, `pllan agents bind`, and `pllan agents unbind` (see [agents](/cli/agents)).
+You can also manage the same routing rules later with `pllan agents bindings`, `pllan agents bind`, and `pllan agents unbind` (see [agents](/nb/cli/agents)).
 
 When you add a non-default account to a channel that is still using single-account top-level settings (no `channels.<channel>.accounts` entries yet), Pllan moves account-scoped single-account top-level values into `channels.<channel>.accounts.default`, then writes the new account. This preserves the original account behavior while moving to the multi-account shape.
 

package/docs/nb/cli/clawbot.md

@@ -12,7 +12,7 @@ Legacy alias namespace kept for backwards compatibility.
 
 Current supported alias:
 
-- `pllan clawbot qr` (same behavior as [`pllan qr`](/cli/qr))
+- `pllan clawbot qr` (same behavior as [`pllan qr`](/nb/cli/qr))
 
 ## Migration
 

package/docs/nb/cli/configure.md

@@ -17,8 +17,8 @@ Tip: `pllan config` without a subcommand opens the same wizard. Use
 
 Related:
 
-- Gateway configuration reference: [Configuration](/gateway/configuration)
-- Config CLI: [Config](/cli/config)
+- Gateway configuration reference: [Configuration](/nb/gateway/configuration)
+- Config CLI: [Config](/nb/cli/config)
 
 Notes:
 

package/docs/nb/cli/cron.md

@@ -12,7 +12,7 @@ Manage cron jobs for the Gateway scheduler.
 
 Related:
 
-- Cron jobs: [Cron jobs](/automation/cron-jobs)
+- Cron jobs: [Cron jobs](/nb/automation/cron-jobs)
 
 Tip: run `pllan cron --help` for the full command surface.
 

package/docs/nb/cli/daemon.md

@@ -50,4 +50,4 @@ Notes:
 
 ## Prefer
 
-Use [`pllan gateway`](/cli/gateway) for current docs and examples.
+Use [`pllan gateway`](/nb/cli/gateway) for current docs and examples.

package/docs/nb/cli/devices.md

@@ -135,5 +135,5 @@ pllan devices approve <requestId>
 
 Related:
 
-- [Dashboard auth troubleshooting](/web/dashboard#if-you-see-unauthorized-1008)
-- [Gateway troubleshooting](/gateway/troubleshooting#dashboard-control-ui-connectivity)
+- [Dashboard auth troubleshooting](/nb/web/dashboard#if-you-see-unauthorized-1008)
+- [Gateway troubleshooting](/nb/gateway/troubleshooting#dashboard-control-ui-connectivity)

package/docs/nb/cli/dns.md

@@ -12,8 +12,8 @@ DNS helpers for wide-area discovery (Tailscale + CoreDNS). Currently focused on
 
 Related:
 
-- Gateway discovery: [Discovery](/gateway/discovery)
-- Wide-area discovery config: [Configuration](/gateway/configuration)
+- Gateway discovery: [Discovery](/nb/gateway/discovery)
+- Wide-area discovery config: [Configuration](/nb/gateway/configuration)
 
 ## Setup
 

package/docs/nb/cli/doctor.md

@@ -12,8 +12,8 @@ Health checks + quick fixes for the gateway and channels.
 
 Related:
 
-- Troubleshooting: [Troubleshooting](/gateway/troubleshooting)
-- Security audit: [Security](/gateway/security)
+- Troubleshooting: [Troubleshooting](/nb/gateway/troubleshooting)
+- Security audit: [Security](/nb/gateway/security)
 
 ## Examples
 

package/docs/nb/cli/gateway.md

@@ -15,9 +15,9 @@ Subcommands in this page live under `pllan gateway …`.
 
 Related docs:
 
-- [/gateway/bonjour](/gateway/bonjour)
-- [/gateway/discovery](/gateway/discovery)
-- [/gateway/configuration](/gateway/configuration)
+- [/gateway/bonjour](/nb/gateway/bonjour)
+- [/gateway/discovery](/nb/gateway/discovery)
+- [/gateway/configuration](/nb/gateway/configuration)
 
 ## Run the Gateway
 
@@ -202,7 +202,7 @@ Notes:
 `gateway discover` scans for Gateway beacons (`_pllan-gw._tcp`).
 
 - Multicast DNS-SD: `local.`
-- Unicast DNS-SD (Wide-Area Bonjour): choose a domain (example: `pllan.internal.`) and set up split DNS + a DNS server; see [/gateway/bonjour](/gateway/bonjour)
+- Unicast DNS-SD (Wide-Area Bonjour): choose a domain (example: `pllan.internal.`) and set up split DNS + a DNS server; see [/gateway/bonjour](/nb/gateway/bonjour)
 
 Only gateways with Bonjour discovery enabled (default) advertise the beacon.
 

package/docs/nb/cli/hooks.md

@@ -12,8 +12,8 @@ Manage agent hooks (event-driven automations for commands like `/new`, `/reset`,
 
 Related:
 
-- Hooks: [Hooks](/automation/hooks)
-- Plugin hooks: [Plugin hooks](/plugins/architecture#provider-runtime-hooks)
+- Hooks: [Hooks](/nb/automation/hooks)
+- Plugin hooks: [Plugin hooks](/nb/plugins/architecture#provider-runtime-hooks)
 
 ## List All Hooks
 
@@ -262,7 +262,7 @@ pllan hooks enable session-memory
 
 **Output:** `~/.pllan/workspace/memory/YYYY-MM-DD-slug.md`
 
-**See:** [session-memory documentation](/automation/hooks#session-memory)
+**See:** [session-memory documentation](/nb/automation/hooks#session-memory)
 
 ### bootstrap-extra-files
 
@@ -274,7 +274,7 @@ Injects additional bootstrap files (for example monorepo-local `AGENTS.md` / `TO
 pllan hooks enable bootstrap-extra-files
 ```
 
-**See:** [bootstrap-extra-files documentation](/automation/hooks#bootstrap-extra-files)
+**See:** [bootstrap-extra-files documentation](/nb/automation/hooks#bootstrap-extra-files)
 
 ### command-logger
 
@@ -301,7 +301,7 @@ cat ~/.pllan/logs/commands.log | jq .
 grep '"action":"new"' ~/.pllan/logs/commands.log | jq .
 ```
 
-**See:** [command-logger documentation](/automation/hooks#command-logger)
+**See:** [command-logger documentation](/nb/automation/hooks#command-logger)
 
 ### boot-md
 
@@ -315,4 +315,4 @@ Runs `BOOT.md` when the gateway starts (after channels start).
 pllan hooks enable boot-md
 ```
 
-**See:** [boot-md documentation](/automation/hooks#boot-md)
+**See:** [boot-md documentation](/nb/automation/hooks#boot-md)