pllan 2026.3.47 → 2026.3.49

package/docs/sv/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="/sv/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="/sv/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="/sv/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](/sv/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](/sv/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](/sv/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](/sv/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](/sv/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](/sv/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](/sv/channels/pairing)
+- [Channel routing](/sv/channels/channel-routing)
+- [Multi-agent routing](/sv/concepts/multi-agent)
+- [Troubleshooting](/sv/channels/troubleshooting)

package/docs/sv/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](/sv/tools/plugin)
 
 ## Setup
 
@@ -249,7 +249,7 @@ Common failures:
 
 ## Configuration reference
 
-Full configuration: [Configuration](/gateway/configuration)
+Full configuration: [Configuration](/sv/gateway/configuration)
 
 Provider options:
 

package/docs/sv/channels/troubleshooting.md

@@ -38,7 +38,7 @@ Healthy baseline:
 | Group messages ignored          | Check `requireMention` + mention patterns in config | Mention the bot or relax mention policy for that group. |
 | Random disconnect/relogin loops | `pllan channels status --probe` + logs           | Re-login and verify credentials directory is healthy.   |
 
-Full troubleshooting: [/channels/whatsapp#troubleshooting](/channels/whatsapp#troubleshooting)
+Full troubleshooting: [/channels/whatsapp#troubleshooting](/sv/channels/whatsapp#troubleshooting)
 
 ## Telegram
 
@@ -52,7 +52,7 @@ Full troubleshooting: [/channels/whatsapp#troubleshooting](/channels/whatsapp#tr
 | `setMyCommands` rejected at startup | Inspect logs for `BOT_COMMANDS_TOO_MUCH`        | Reduce plugin/skill/custom Telegram commands or disable native menus.       |
 | Upgraded and allowlist blocks you   | `pllan security audit` and config allowlists | Run `pllan doctor --fix` or replace `@username` with numeric sender IDs. |
 
-Full troubleshooting: [/channels/telegram#troubleshooting](/channels/telegram#troubleshooting)
+Full troubleshooting: [/channels/telegram#troubleshooting](/sv/channels/telegram#troubleshooting)
 
 ## Discord
 
@@ -64,7 +64,7 @@ Full troubleshooting: [/channels/telegram#troubleshooting](/channels/telegram#tr
 | Group messages ignored          | Check logs for mention gating drops | Mention bot or set guild/channel `requireMention: false`. |
 | DM replies missing              | `pllan pairing list discord`     | Approve DM pairing or adjust DM policy.                   |
 
-Full troubleshooting: [/channels/discord#troubleshooting](/channels/discord#troubleshooting)
+Full troubleshooting: [/channels/discord#troubleshooting](/sv/channels/discord#troubleshooting)
 
 ## Slack
 
@@ -76,7 +76,7 @@ Full troubleshooting: [/channels/discord#troubleshooting](/channels/discord#trou
 | DMs blocked                            | `pllan pairing list slack`             | Approve pairing or relax DM policy.               |
 | Channel message ignored                | Check `groupPolicy` and channel allowlist | Allow the channel or switch policy to `open`.     |
 
-Full troubleshooting: [/channels/slack#troubleshooting](/channels/slack#troubleshooting)
+Full troubleshooting: [/channels/slack#troubleshooting](/sv/channels/slack#troubleshooting)
 
 ## iMessage and BlueBubbles
 
@@ -90,8 +90,8 @@ Full troubleshooting: [/channels/slack#troubleshooting](/channels/slack#troubles
 
 Full troubleshooting:
 
-- [/channels/imessage#troubleshooting](/channels/imessage#troubleshooting)
-- [/channels/bluebubbles#troubleshooting](/channels/bluebubbles#troubleshooting)
+- [/channels/imessage#troubleshooting](/sv/channels/imessage#troubleshooting)
+- [/channels/bluebubbles#troubleshooting](/sv/channels/bluebubbles#troubleshooting)
 
 ## Signal
 
@@ -103,7 +103,7 @@ Full troubleshooting:
 | DM blocked                      | `pllan pairing list signal`             | Approve sender or adjust DM policy.                      |
 | Group replies do not trigger    | Check group allowlist and mention patterns | Add sender/group or loosen gating.                       |
 
-Full troubleshooting: [/channels/signal#troubleshooting](/channels/signal#troubleshooting)
+Full troubleshooting: [/channels/signal#troubleshooting](/sv/channels/signal#troubleshooting)
 
 ## Matrix
 
@@ -115,4 +115,4 @@ Full troubleshooting: [/channels/signal#troubleshooting](/channels/signal#troubl
 | DMs do not process                  | `pllan pairing list matrix`               | Approve sender or adjust DM policy.             |
 | Encrypted rooms fail                | Verify crypto module and encryption settings | Enable encryption support and rejoin/sync room. |
 
-Full troubleshooting: [/channels/matrix#troubleshooting](/channels/matrix#troubleshooting)
+Full troubleshooting: [/channels/matrix#troubleshooting](/sv/channels/matrix#troubleshooting)

package/docs/sv/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](/sv/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`](/sv/gateway/configuration) for the shared pattern.
 
 Example (one bot account in two channels):
 

package/docs/sv/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="/sv/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="/sv/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="/sv/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](/sv/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](/sv/channels/pairing)
+- [Channel routing](/sv/channels/channel-routing)
+- [Multi-agent routing](/sv/concepts/multi-agent)
+- [Troubleshooting](/sv/channels/troubleshooting)

package/docs/sv/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](/sv/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](/sv/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](/sv/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/sv/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](/sv/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](/sv/tools/reactions)
 - For inbound messages that include event metadata, Pllan sends delivered + seen acknowledgements (best-effort).
 
 ## Troubleshooting

package/docs/sv/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](/sv/concepts/session).
 
 ## Options
 

package/docs/sv/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](/sv/tools/agent-send)
 
 ## Examples
 

package/docs/sv/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](/sv/concepts/multi-agent)
+- Agent workspace: [Agent workspace](/sv/concepts/agent-workspace)
 
 ## Examples
 

package/docs/sv/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](/sv/tools/exec-approvals)
+- Nodes: [Nodes](/sv/nodes)
 
 ## Common commands
 

package/docs/sv/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](/sv/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](/sv/tools/browser), [Remote access](/sv/gateway/remote), [Tailscale](/sv/gateway/tailscale), [Security](/sv/gateway/security)

package/docs/sv/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](/sv/channels/index)
+- Gateway configuration: [Configuration](/sv/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](/sv/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/sv/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`](/sv/cli/qr))
 
 ## Migration
 

package/docs/sv/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](/sv/gateway/configuration)
+- Config CLI: [Config](/sv/cli/config)
 
 Notes:
 

package/docs/sv/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](/sv/automation/cron-jobs)
 
 Tip: run `pllan cron --help` for the full command surface.
 

package/docs/sv/cli/daemon.md

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

package/docs/sv/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](/sv/web/dashboard#if-you-see-unauthorized-1008)
+- [Gateway troubleshooting](/sv/gateway/troubleshooting#dashboard-control-ui-connectivity)

package/docs/sv/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](/sv/gateway/discovery)
+- Wide-area discovery config: [Configuration](/sv/gateway/configuration)
 
 ## Setup
 

package/docs/sv/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](/sv/gateway/troubleshooting)
+- Security audit: [Security](/sv/gateway/security)
 
 ## Examples
 

package/docs/sv/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](/sv/gateway/bonjour)
+- [/gateway/discovery](/sv/gateway/discovery)
+- [/gateway/configuration](/sv/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](/sv/gateway/bonjour)
 
 Only gateways with Bonjour discovery enabled (default) advertise the beacon.
 

package/docs/sv/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](/sv/automation/hooks)
+- Plugin hooks: [Plugin hooks](/sv/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](/sv/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](/sv/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](/sv/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](/sv/automation/hooks#boot-md)

package/docs/sv/cli/index.md

@@ -12,52 +12,52 @@ Denna sida beskriver det nuvarande CLI-beteendet. Om kommandon ändras, uppdater
 
 ## Kommandosidor
 
-- [`setup`](/cli/setup)
-- [`onboard`](/cli/onboard)
-- [`configure`](/cli/configure)
-- [`config`](/cli/config)
-- [`completion`](/cli/completion)
-- [`doctor`](/cli/doctor)
-- [`dashboard`](/cli/dashboard)
-- [`backup`](/cli/backup)
-- [`reset`](/cli/reset)
-- [`uninstall`](/cli/uninstall)
-- [`update`](/cli/update)
-- [`message`](/cli/message)
-- [`agent`](/cli/agent)
-- [`agents`](/cli/agents)
-- [`acp`](/cli/acp)
-- [`status`](/cli/status)
-- [`health`](/cli/health)
-- [`sessions`](/cli/sessions)
-- [`gateway`](/cli/gateway)
-- [`logs`](/cli/logs)
-- [`system`](/cli/system)
-- [`models`](/cli/models)
-- [`memory`](/cli/memory)
-- [`directory`](/cli/directory)
-- [`nodes`](/cli/nodes)
-- [`devices`](/cli/devices)
-- [`node`](/cli/node)
-- [`approvals`](/cli/approvals)
-- [`sandbox`](/cli/sandbox)
-- [`tui`](/cli/tui)
-- [`browser`](/cli/browser)
-- [`cron`](/cli/cron)
-- [`dns`](/cli/dns)
-- [`docs`](/cli/docs)
-- [`hooks`](/cli/hooks)
-- [`webhooks`](/cli/webhooks)
-- [`pairing`](/cli/pairing)
-- [`qr`](/cli/qr)
-- [`plugins`](/cli/plugins) (plugin-kommandon)
-- [`channels`](/cli/channels)
-- [`security`](/cli/security)
-- [`secrets`](/cli/secrets)
-- [`skills`](/cli/skills)
-- [`daemon`](/cli/daemon) (äldre alias för gateway-tjänstkommandon)
-- [`clawbot`](/cli/clawbot) (äldre aliasnamnrymd)
-- [`voicecall`](/cli/voicecall) (plugin; om installerat)
+- [`setup`](/sv/cli/setup)
+- [`onboard`](/sv/cli/onboard)
+- [`configure`](/sv/cli/configure)
+- [`config`](/sv/cli/config)
+- [`completion`](/sv/cli/completion)
+- [`doctor`](/sv/cli/doctor)
+- [`dashboard`](/sv/cli/dashboard)
+- [`backup`](/sv/cli/backup)
+- [`reset`](/sv/cli/reset)
+- [`uninstall`](/sv/cli/uninstall)
+- [`update`](/sv/cli/update)
+- [`message`](/sv/cli/message)
+- [`agent`](/sv/cli/agent)
+- [`agents`](/sv/cli/agents)
+- [`acp`](/sv/cli/acp)
+- [`status`](/sv/cli/status)
+- [`health`](/sv/cli/health)
+- [`sessions`](/sv/cli/sessions)
+- [`gateway`](/sv/cli/gateway)
+- [`logs`](/sv/cli/logs)
+- [`system`](/sv/cli/system)
+- [`models`](/sv/cli/models)
+- [`memory`](/sv/cli/memory)
+- [`directory`](/sv/cli/directory)
+- [`nodes`](/sv/cli/nodes)
+- [`devices`](/sv/cli/devices)
+- [`node`](/sv/cli/node)
+- [`approvals`](/sv/cli/approvals)
+- [`sandbox`](/sv/cli/sandbox)
+- [`tui`](/sv/cli/tui)
+- [`browser`](/sv/cli/browser)
+- [`cron`](/sv/cli/cron)
+- [`dns`](/sv/cli/dns)
+- [`docs`](/sv/cli/docs)
+- [`hooks`](/sv/cli/hooks)
+- [`webhooks`](/sv/cli/webhooks)
+- [`pairing`](/sv/cli/pairing)
+- [`qr`](/sv/cli/qr)
+- [`plugins`](/sv/cli/plugins) (plugin-kommandon)
+- [`channels`](/sv/cli/channels)
+- [`security`](/sv/cli/security)
+- [`secrets`](/sv/cli/secrets)
+- [`skills`](/sv/cli/skills)
+- [`daemon`](/sv/cli/daemon) (äldre alias för gateway-tjänstkommandon)
+- [`clawbot`](/sv/cli/clawbot) (äldre aliasnamnrymd)
+- [`voicecall`](/sv/cli/voicecall) (plugin; om installerat)
 
 ## Globala flaggor
 

package/docs/sv/cli/logs.md

@@ -12,7 +12,7 @@ Tail Gateway file logs over RPC (works in remote mode).
 
 Related:
 
-- Logging overview: [Logging](/logging)
+- Logging overview: [Logging](/sv/logging)
 
 ## Examples
 

package/docs/sv/cli/memory.md

@@ -13,8 +13,8 @@ Provided by the active memory plugin (default: `memory-core`; set `plugins.slots
 
 Related:
 
-- Memory concept: [Memory](/concepts/memory)
-- Plugins: [Plugins](/tools/plugin)
+- Memory concept: [Memory](/sv/concepts/memory)
+- Plugins: [Plugins](/sv/tools/plugin)
 
 ## Examples
 

package/docs/sv/cli/message.md

@@ -210,7 +210,7 @@ pllan message send --channel discord \
   --components '{"text":"Choose a path","blocks":[{"type":"actions","buttons":[{"label":"Approve","style":"success"},{"label":"Decline","style":"danger"}]}]}'
 ```
 
-See [Discord components](/channels/discord#interactive-components) for the full schema.
+See [Discord components](/sv/channels/discord#interactive-components) for the full schema.
 
 Create a Discord poll:
 

package/docs/sv/cli/models.md

@@ -12,8 +12,8 @@ Model discovery, scanning, and configuration (default model, fallbacks, auth pro
 
 Related:
 
-- Providers + models: [Models](/providers/models)
-- Provider auth setup: [Getting started](/start/getting-started)
+- Providers + models: [Models](/sv/providers/models)
+- Provider auth setup: [Getting started](/sv/start/getting-started)
 
 ## Common commands
 

package/docs/sv/cli/node.md

@@ -123,5 +123,5 @@ The node host stores its node id, token, display name, and gateway connection in
 `system.run` is gated by local exec approvals:
 
 - `~/.pllan/exec-approvals.json`
-- [Exec approvals](/tools/exec-approvals)
+- [Exec approvals](/sv/tools/exec-approvals)
 - `pllan approvals --node <id|name|ip>` (edit from the Gateway)