pllan 2026.3.47 → 2026.3.49

package/docs/sv/diagnostics/flags.md

@@ -82,10 +82,10 @@ Or tail while reproducing:
 tail -f /tmp/pllan/pllan-$(date +%F).log | rg "telegram http error"
 ```
 
-For remote gateways, you can also use `pllan logs --follow` (see [/cli/logs](/cli/logs)).
+For remote gateways, you can also use `pllan logs --follow` (see [/cli/logs](/sv/cli/logs)).
 
 ## Notes
 
 - If `logging.level` is set higher than `warn`, these logs may be suppressed. Default `info` is fine.
 - Flags are safe to leave enabled; they only affect log volume for the specific subsystem.
-- Use [/logging](/logging) to change log destinations, levels, and redaction.
+- Use [/logging](/sv/logging) to change log destinations, levels, and redaction.

package/docs/sv/gateway/authentication.md

@@ -12,11 +12,11 @@ Pllan supports OAuth and API keys for model providers. For always-on gateway
 hosts, API keys are usually the most predictable option. Subscription/OAuth
 flows are also supported when they match your provider account model.
 
-See [/concepts/oauth](/concepts/oauth) for the full OAuth flow and storage
+See [/concepts/oauth](/sv/concepts/oauth) for the full OAuth flow and storage
 layout.
-For SecretRef-based auth (`env`/`file`/`exec` providers), see [Secrets Management](/gateway/secrets).
+For SecretRef-based auth (`env`/`file`/`exec` providers), see [Secrets Management](/sv/gateway/secrets).
 For credential eligibility/reason-code rules used by `models status --probe`, see
-[Auth Credential Semantics](/auth-credential-semantics).
+[Auth Credential Semantics](/sv/auth-credential-semantics).
 
 ## Recommended setup (API key, any provider)
 
@@ -52,7 +52,7 @@ pllan doctor
 If you’d rather not manage env vars yourself, onboarding can store
 API keys for daemon use: `pllan onboard`.
 
-See [Help](/help) for details on env inheritance (`env.shellEnv`,
+See [Help](/sv/help) for details on env inheritance (`env.shellEnv`,
 `~/.pllan/.env`, systemd/launchd).
 
 ## Anthropic: setup-token (subscription auth)
@@ -109,7 +109,7 @@ pllan models status --check
 ```
 
 Optional ops scripts (systemd/Termux) are documented here:
-[/automation/auth-monitoring](/automation/auth-monitoring)
+[/automation/auth-monitoring](/sv/automation/auth-monitoring)
 
 > `claude setup-token` requires an interactive TTY.
 

package/docs/sv/gateway/bonjour.md

@@ -173,5 +173,5 @@ sequences (e.g. spaces become `\032`).
 
 ## Related docs
 
-- Discovery policy and transport selection: [Discovery](/gateway/discovery)
-- Node pairing + approvals: [Gateway pairing](/gateway/pairing)
+- Discovery policy and transport selection: [Discovery](/sv/gateway/discovery)
+- Node pairing + approvals: [Gateway pairing](/sv/gateway/pairing)

package/docs/sv/gateway/bridge-protocol.md

@@ -13,7 +13,7 @@ The Bridge protocol is a **legacy** node transport (TCP JSONL). New node clients
 should use the unified Gateway WebSocket protocol instead.
 
 If you are building an operator or node client, use the
-[Gateway protocol](/gateway/protocol).
+[Gateway protocol](/sv/gateway/protocol).
 
 **Note:** Current Pllan builds no longer ship the TCP bridge listener; this document is kept for historical reference.
 Legacy `bridge.*` config keys are no longer part of the config schema.

package/docs/sv/gateway/configuration-examples.md

@@ -9,7 +9,7 @@ title: "Configuration Examples"
 
 # Configuration Examples
 
-Examples below are aligned with the current config schema. For the exhaustive reference and per-field notes, see [Configuration](/gateway/configuration).
+Examples below are aligned with the current config schema. For the exhaustive reference and per-field notes, see [Configuration](/sv/gateway/configuration).
 
 ## Quick start
 
@@ -634,4 +634,4 @@ terms before depending on subscription auth.
 - If you set `dmPolicy: "open"`, the matching `allowFrom` list must include `"*"`.
 - Provider IDs differ (phone numbers, user IDs, channel IDs). Use the provider docs to confirm the format.
 - Optional sections to add later: `web`, `browser`, `ui`, `discovery`, `canvasHost`, `talk`, `signal`, `imessage`.
-- See [Providers](/providers) and [Troubleshooting](/gateway/troubleshooting) for deeper setup notes.
+- See [Providers](/sv/providers) and [Troubleshooting](/sv/gateway/troubleshooting) for deeper setup notes.

package/docs/sv/gateway/configuration-reference.md

@@ -8,7 +8,7 @@ read_when:
 
 # Configuration Reference
 
-Every field available in `~/.pllan/pllan.json`. For a task-oriented overview, see [Configuration](/gateway/configuration).
+Every field available in `~/.pllan/pllan.json`. For a task-oriented overview, see [Configuration](/sv/gateway/configuration).
 
 Config format is **JSON5** (comments + trailing commas allowed). All fields are optional — Pllan uses safe defaults when omitted.
 
@@ -206,9 +206,9 @@ WhatsApp runs through the gateway's web channel (Baileys Web). It starts automat
 - Optional `channels.telegram.defaultAccount` overrides default account selection when it matches a configured account id.
 - In multi-account setups (2+ account ids), set an explicit default (`channels.telegram.defaultAccount` or `channels.telegram.accounts.default`) to avoid fallback routing; `pllan doctor` warns when this is missing or invalid.
 - `configWrites: false` blocks Telegram-initiated config writes (supergroup ID migrations, `/config set|unset`).
-- Top-level `bindings[]` entries with `type: "acp"` configure persistent ACP bindings for forum topics (use canonical `chatId:topic:topicId` in `match.peer.id`). Field semantics are shared in [ACP Agents](/tools/acp-agents#channel-specific-settings).
+- Top-level `bindings[]` entries with `type: "acp"` configure persistent ACP bindings for forum topics (use canonical `chatId:topic:topicId` in `match.peer.id`). Field semantics are shared in [ACP Agents](/sv/tools/acp-agents#channel-specific-settings).
 - Telegram stream previews use `sendMessage` + `editMessageText` (works in direct and group chats).
-- Retry policy: see [Retry policy](/concepts/retry).
+- Retry policy: see [Retry policy](/sv/concepts/retry).
 
 ### Discord
 
@@ -315,7 +315,7 @@ WhatsApp runs through the gateway's web channel (Baileys Web). It starts automat
   - `idleHours`: Discord override for inactivity auto-unfocus in hours (`0` disables)
   - `maxAgeHours`: Discord override for hard max age in hours (`0` disables)
   - `spawnSubagentSessions`: opt-in switch for `sessions_spawn({ thread: true })` auto thread creation/binding
-- Top-level `bindings[]` entries with `type: "acp"` configure persistent ACP bindings for channels and threads (use channel/thread id in `match.peer.id`). Field semantics are shared in [ACP Agents](/tools/acp-agents#channel-specific-settings).
+- Top-level `bindings[]` entries with `type: "acp"` configure persistent ACP bindings for channels and threads (use channel/thread id in `match.peer.id`). Field semantics are shared in [ACP Agents](/sv/tools/acp-agents#channel-specific-settings).
 - `channels.discord.ui.components.accentColor` sets the accent color for Discord components v2 containers.
 - `channels.discord.voice` enables Discord voice channel conversations and optional auto-join + TTS overrides.
 - `channels.discord.voice.daveEncryption` and `channels.discord.voice.decryptionFailureTolerance` pass through to `@discordjs/voice` DAVE options (`true` and `24` by default).
@@ -523,7 +523,7 @@ BlueBubbles is the recommended iMessage path (plugin-backed, configured under `c
 
 - Core key paths covered here: `channels.bluebubbles`, `channels.bluebubbles.dmPolicy`.
 - Optional `channels.bluebubbles.defaultAccount` overrides default account selection when it matches a configured account id.
-- Full BlueBubbles channel configuration is documented in [BlueBubbles](/channels/bluebubbles).
+- Full BlueBubbles channel configuration is documented in [BlueBubbles](/sv/channels/bluebubbles).
 
 ### iMessage
 
@@ -587,7 +587,7 @@ Microsoft Teams is extension-backed and configured under `channels.msteams`.
 ```
 
 - Core key paths covered here: `channels.msteams`, `channels.msteams.configWrites`.
-- Full Teams config (credentials, webhook, DM/group policy, per-team/per-channel overrides) is documented in [Microsoft Teams](/channels/msteams).
+- Full Teams config (credentials, webhook, DM/group policy, per-team/per-channel overrides) is documented in [Microsoft Teams](/sv/channels/msteams).
 
 ### IRC
 
@@ -614,7 +614,7 @@ IRC is extension-backed and configured under `channels.irc`.
 
 - Core key paths covered here: `channels.irc`, `channels.irc.dmPolicy`, `channels.irc.configWrites`, `channels.irc.nickserv.*`.
 - Optional `channels.irc.defaultAccount` overrides default account selection when it matches a configured account id.
-- Full IRC channel configuration (host/port/TLS/channels/allowlists/mention gating) is documented in [IRC](/channels/irc).
+- Full IRC channel configuration (host/port/TLS/channels/allowlists/mention gating) is documented in [IRC](/sv/channels/irc).
 
 ### Multi-account (all channels)
 
@@ -650,7 +650,7 @@ Run multiple accounts per channel (each with its own `accountId`):
 ### Other extension channels
 
 Many extension channels are configured as `channels.<id>` and documented in their dedicated channel pages (for example Feishu, Matrix, LINE, Nostr, Zalo, Nextcloud Talk, Synology Chat, and Twitch).
-See the full channel index: [Channels](/channels).
+See the full channel index: [Channels](/sv/channels).
 
 ### Group chat mention gating
 
@@ -1031,7 +1031,7 @@ Periodic heartbeat runs.
 }
 ```
 
-- `mode`: `default` or `safeguard` (chunked summarization for long histories). See [Compaction](/concepts/compaction).
+- `mode`: `default` or `safeguard` (chunked summarization for long histories). See [Compaction](/sv/concepts/compaction).
 - `timeoutSeconds`: maximum seconds allowed for a single compaction operation before Pllan aborts it. Default: `900`.
 - `identifierPolicy`: `strict` (default), `off`, or `custom`. `strict` prepends built-in opaque identifier retention guidance during compaction summarization.
 - `identifierInstructions`: optional custom identifier-preservation text used when `identifierPolicy=custom`.
@@ -1081,7 +1081,7 @@ Notes:
 
 </Accordion>
 
-See [Session Pruning](/concepts/session-pruning) for behavior details.
+See [Session Pruning](/sv/concepts/session-pruning) for behavior details.
 
 ### Block streaming
 
@@ -1103,7 +1103,7 @@ See [Session Pruning](/concepts/session-pruning) for behavior details.
 - Channel overrides: `channels.<channel>.blockStreamingCoalesce` (and per-account variants). Signal/Slack/Discord/Google Chat default `minChars: 1500`.
 - `humanDelay`: randomized pause between block replies. `natural` = 800–2500ms. Per-agent override: `agents.list[].humanDelay`.
 
-See [Streaming](/concepts/streaming) for behavior + chunking details.
+See [Streaming](/sv/concepts/streaming) for behavior + chunking details.
 
 ### Typing indicators
 
@@ -1121,11 +1121,11 @@ See [Streaming](/concepts/streaming) for behavior + chunking details.
 - Defaults: `instant` for direct chats/mentions, `message` for unmentioned group chats.
 - Per-session overrides: `session.typingMode`, `session.typingIntervalSeconds`.
 
-See [Typing Indicators](/concepts/typing-indicators).
+See [Typing Indicators](/sv/concepts/typing-indicators).
 
 ### `agents.defaults.sandbox`
 
-Optional sandboxing for the embedded agent. See [Sandboxing](/gateway/sandboxing) for the full guide.
+Optional sandboxing for the embedded agent. See [Sandboxing](/sv/gateway/sandboxing) for the full guide.
 
 ```json5
 {
@@ -1417,7 +1417,7 @@ scripts/sandbox-browser-setup.sh   # optional browser image
 
 ## Multi-agent routing
 
-Run multiple isolated agents inside one Gateway. See [Multi-Agent](/concepts/multi-agent).
+Run multiple isolated agents inside one Gateway. See [Multi-Agent](/sv/concepts/multi-agent).
 
 ```json5
 {
@@ -1551,7 +1551,7 @@ For `type: "acp"` entries, Pllan resolves by exact conversation identity (`match
 
 </Accordion>
 
-See [Multi-Agent Sandbox & Tools](/tools/multi-agent-sandbox-tools) for precedence details.
+See [Multi-Agent Sandbox & Tools](/sv/tools/multi-agent-sandbox-tools) for precedence details.
 
 ---
 
@@ -2354,7 +2354,7 @@ Set `MINIMAX_API_KEY`. Shortcut: `pllan onboard --auth-choice minimax-api`.
 
 <Accordion title="Local models (LM Studio)">
 
-See [Local Models](/gateway/local-models). TL;DR: run MiniMax M2.5 via LM Studio Responses API on serious hardware; keep hosted models merged for fallback.
+See [Local Models](/sv/gateway/local-models). TL;DR: run MiniMax M2.5 via LM Studio Responses API on serious hardware; keep hosted models merged for fallback.
 
 </Accordion>
 
@@ -2432,7 +2432,7 @@ See [Local Models](/gateway/local-models). TL;DR: run MiniMax M2.5 via LM Studio
   - Includes `source`, `spec`, `sourcePath`, `installPath`, `version`, `resolvedName`, `resolvedVersion`, `resolvedSpec`, `integrity`, `shasum`, `resolvedAt`, `installedAt`.
   - Treat `plugins.installs.*` as managed state; prefer CLI commands over manual edits.
 
-See [Plugins](/tools/plugin).
+See [Plugins](/sv/tools/plugin).
 
 ---
 
@@ -2579,7 +2579,7 @@ See [Plugins](/tools/plugin).
 - **Auth**: required by default. Non-loopback binds require a shared token/password. Onboarding wizard generates a token by default.
 - If both `gateway.auth.token` and `gateway.auth.password` are configured (including SecretRefs), set `gateway.auth.mode` explicitly to `token` or `password`. Startup and service install/repair flows fail when both are configured and mode is unset.
 - `gateway.auth.mode: "none"`: explicit no-auth mode. Use only for trusted local loopback setups; this is intentionally not offered by onboarding prompts.
-- `gateway.auth.mode: "trusted-proxy"`: delegate auth to an identity-aware reverse proxy and trust identity headers from `gateway.trustedProxies` (see [Trusted Proxy Auth](/gateway/trusted-proxy-auth)).
+- `gateway.auth.mode: "trusted-proxy"`: delegate auth to an identity-aware reverse proxy and trust identity headers from `gateway.trustedProxies` (see [Trusted Proxy Auth](/sv/gateway/trusted-proxy-auth)).
 - `gateway.auth.allowTailscale`: when `true`, Tailscale Serve identity headers can satisfy Control UI/WebSocket auth (verified via `tailscale whois`); HTTP API endpoints still require token/password auth. This tokenless flow assumes the gateway host is trusted. Defaults to `true` when `tailscale.mode = "serve"`.
 - `gateway.auth.rateLimit`: optional failed-auth limiter. Applies per client IP and per auth scope (shared-secret and device-token are tracked independently). Blocked attempts return `429` + `Retry-After`.
   - `gateway.auth.rateLimit.exemptLoopback` defaults to `true`; set `false` when you intentionally want localhost traffic rate-limited too (for test setups or strict proxy deployments).
@@ -2620,7 +2620,7 @@ See [Plugins](/tools/plugin).
     Empty allowlists are treated as unset; use `gateway.http.endpoints.responses.files.allowUrl=false`
     and/or `gateway.http.endpoints.responses.images.allowUrl=false` to disable URL fetching.
 - Optional response hardening header:
-  - `gateway.http.securityHeaders.strictTransportSecurity` (set only for HTTPS origins you control; see [Trusted Proxy Auth](/gateway/trusted-proxy-auth#tls-termination-and-hsts))
+  - `gateway.http.securityHeaders.strictTransportSecurity` (set only for HTTPS origins you control; see [Trusted Proxy Auth](/sv/gateway/trusted-proxy-auth#tls-termination-and-hsts))
 
 ### Multi-instance isolation
 
@@ -2634,7 +2634,7 @@ pllan gateway --port 19001
 
 Convenience flags: `--dev` (uses `~/.pllan-dev` + port `19001`), `--profile <name>` (uses `~/.pllan-<name>`).
 
-See [Multiple Gateways](/gateway/multiple-gateways).
+See [Multiple Gateways](/sv/gateway/multiple-gateways).
 
 ---
 
@@ -2808,7 +2808,7 @@ Setup: `pllan dns setup --apply`.
 - Inline env vars are only applied if the process env is missing the key.
 - `.env` files: CWD `.env` + `~/.pllan/.env` (neither overrides existing vars).
 - `shellEnv`: imports missing expected keys from your login shell profile.
-- See [Environment](/help/environment) for full precedence.
+- See [Environment](/sv/help/environment) for full precedence.
 
 ### Env var substitution
 
@@ -2851,7 +2851,7 @@ Validation:
 
 ### Supported credential surface
 
-- Canonical matrix: [SecretRef Credential Surface](/reference/secretref-credential-surface)
+- Canonical matrix: [SecretRef Credential Surface](/sv/reference/secretref-credential-surface)
 - `secrets apply` targets supported `pllan.json` credential paths.
 - `auth-profiles.json` refs are included in runtime resolution and audit coverage.
 
@@ -2915,8 +2915,8 @@ Notes:
 - `auth-profiles.json` supports value-level refs (`keyRef` for `api_key`, `tokenRef` for `token`).
 - Static runtime credentials come from in-memory resolved snapshots; legacy static `auth.json` entries are scrubbed when discovered.
 - Legacy OAuth imports from `~/.pllan/credentials/oauth.json`.
-- See [OAuth](/concepts/oauth).
-- Secrets runtime behavior and `audit/configure/apply` tooling: [Secrets Management](/gateway/secrets).
+- See [OAuth](/sv/concepts/oauth).
+- Secrets runtime behavior and `audit/configure/apply` tooling: [Secrets Management](/sv/gateway/secrets).
 
 ---
 
@@ -3055,7 +3055,7 @@ Current builds no longer include the TCP bridge. Nodes connect over the Gateway
 - `webhookToken`: bearer token used for cron webhook POST delivery (`delivery.mode = "webhook"`), if omitted no auth header is sent.
 - `webhook`: deprecated legacy fallback webhook URL (http/https) used only for stored jobs that still have `notify: true`.
 
-See [Cron Jobs](/automation/cron-jobs).
+See [Cron Jobs](/sv/automation/cron-jobs).
 
 ---
 
@@ -3114,4 +3114,4 @@ Split config into multiple files:
 
 ---
 
-_Related: [Configuration](/gateway/configuration) · [Configuration Examples](/gateway/configuration-examples) · [Doctor](/gateway/doctor)_
+_Related: [Configuration](/sv/gateway/configuration) · [Configuration Examples](/sv/gateway/configuration-examples) · [Doctor](/sv/gateway/doctor)_

package/docs/sv/gateway/configuration.md

@@ -17,10 +17,10 @@ If the file is missing, Pllan uses safe defaults. Common reasons to add a config
 - Set models, tools, sandboxing, or automation (cron, hooks)
 - Tune sessions, media, networking, or UI
 
-See the [full reference](/gateway/configuration-reference) for every available field.
+See the [full reference](/sv/gateway/configuration-reference) for every available field.
 
 <Tip>
-**New to configuration?** Start with `pllan onboard` for interactive setup, or check out the [Configuration Examples](/gateway/configuration-examples) guide for complete copy-paste configs.
+**New to configuration?** Start with `pllan onboard` for interactive setup, or check out the [Configuration Examples](/sv/gateway/configuration-examples) guide for complete copy-paste configs.
 </Tip>
 
 ## Minimal config
@@ -77,15 +77,15 @@ When validation fails:
   <Accordion title="Set up a channel (WhatsApp, Telegram, Discord, etc.)">
     Each channel has its own config section under `channels.<provider>`. See the dedicated channel page for setup steps:
 
-    - [WhatsApp](/channels/whatsapp) — `channels.whatsapp`
-    - [Telegram](/channels/telegram) — `channels.telegram`
-    - [Discord](/channels/discord) — `channels.discord`
-    - [Slack](/channels/slack) — `channels.slack`
-    - [Signal](/channels/signal) — `channels.signal`
-    - [iMessage](/channels/imessage) — `channels.imessage`
-    - [Google Chat](/channels/googlechat) — `channels.googlechat`
-    - [Mattermost](/channels/mattermost) — `channels.mattermost`
-    - [Microsoft Teams](/channels/msteams) — `channels.msteams`
+    - [WhatsApp](/sv/channels/whatsapp) — `channels.whatsapp`
+    - [Telegram](/sv/channels/telegram) — `channels.telegram`
+    - [Discord](/sv/channels/discord) — `channels.discord`
+    - [Slack](/sv/channels/slack) — `channels.slack`
+    - [Signal](/sv/channels/signal) — `channels.signal`
+    - [iMessage](/sv/channels/imessage) — `channels.imessage`
+    - [Google Chat](/sv/channels/googlechat) — `channels.googlechat`
+    - [Mattermost](/sv/channels/mattermost) — `channels.mattermost`
+    - [Microsoft Teams](/sv/channels/msteams) — `channels.msteams`
 
     All channels share the same DM policy pattern:
 
@@ -127,8 +127,8 @@ When validation fails:
     - `agents.defaults.models` defines the model catalog and acts as the allowlist for `/model`.
     - Model refs use `provider/model` format (e.g. `anthropic/claude-opus-4-6`).
     - `agents.defaults.imageMaxDimensionPx` controls transcript/tool image downscaling (default `1200`); lower values usually reduce vision-token usage on screenshot-heavy runs.
-    - See [Models CLI](/concepts/models) for switching models in chat and [Model Failover](/concepts/model-failover) for auth rotation and fallback behavior.
-    - For custom/self-hosted providers, see [Custom providers](/gateway/configuration-reference#custom-providers-and-base-urls) in the reference.
+    - See [Models CLI](/sv/concepts/models) for switching models in chat and [Model Failover](/sv/concepts/model-failover) for auth rotation and fallback behavior.
+    - For custom/self-hosted providers, see [Custom providers](/sv/gateway/configuration-reference#custom-providers-and-base-urls) in the reference.
 
   </Accordion>
 
@@ -142,7 +142,7 @@ When validation fails:
 
     For groups, use `groupPolicy` + `groupAllowFrom` or channel-specific allowlists.
 
-    See the [full reference](/gateway/configuration-reference#dm-and-group-access) for per-channel details.
+    See the [full reference](/sv/gateway/configuration-reference#dm-and-group-access) for per-channel details.
 
   </Accordion>
 
@@ -171,7 +171,7 @@ When validation fails:
 
     - **Metadata mentions**: native @-mentions (WhatsApp tap-to-mention, Telegram @bot, etc.)
     - **Text patterns**: safe regex patterns in `mentionPatterns`
-    - See [full reference](/gateway/configuration-reference#group-chat-mention-gating) for per-channel overrides and self-chat mode.
+    - See [full reference](/sv/gateway/configuration-reference#group-chat-mention-gating) for per-channel overrides and self-chat mode.
 
   </Accordion>
 
@@ -201,7 +201,7 @@ When validation fails:
     - Set `gateway.channelHealthCheckMinutes: 0` to disable health-monitor restarts globally.
     - `channelStaleEventThresholdMinutes` should be greater than or equal to the check interval.
     - Use `channels.<provider>.healthMonitor.enabled` or `channels.<provider>.accounts.<id>.healthMonitor.enabled` to disable auto-restarts for one channel or account without disabling the global monitor.
-    - See [Health Checks](/gateway/health) for operational debugging and the [full reference](/gateway/configuration-reference#gateway) for all fields.
+    - See [Health Checks](/sv/gateway/health) for operational debugging and the [full reference](/sv/gateway/configuration-reference#gateway) for all fields.
 
   </Accordion>
 
@@ -228,8 +228,8 @@ When validation fails:
 
     - `dmScope`: `main` (shared) | `per-peer` | `per-channel-peer` | `per-account-channel-peer`
     - `threadBindings`: global defaults for thread-bound session routing (Discord supports `/focus`, `/unfocus`, `/agents`, `/session idle`, and `/session max-age`).
-    - See [Session Management](/concepts/session) for scoping, identity links, and send policy.
-    - See [full reference](/gateway/configuration-reference#session) for all fields.
+    - See [Session Management](/sv/concepts/session) for scoping, identity links, and send policy.
+    - See [full reference](/sv/gateway/configuration-reference#session) for all fields.
 
   </Accordion>
 
@@ -251,7 +251,7 @@ When validation fails:
 
     Build the image first: `scripts/sandbox-setup.sh`
 
-    See [Sandboxing](/gateway/sandboxing) for the full guide and [full reference](/gateway/configuration-reference#agents-defaults-sandbox) for all options.
+    See [Sandboxing](/sv/gateway/sandboxing) for the full guide and [full reference](/sv/gateway/configuration-reference#agents-defaults-sandbox) for all options.
 
   </Accordion>
 
@@ -308,7 +308,7 @@ When validation fails:
     - `PLLAN_APNS_RELAY_BASE_URL` and `PLLAN_APNS_RELAY_TIMEOUT_MS` still work as temporary env overrides.
     - `PLLAN_APNS_RELAY_ALLOW_HTTP=true` remains a loopback-only development escape hatch; do not persist HTTP relay URLs in config.
 
-    See [iOS App](/platforms/ios#relay-backed-push-for-official-builds) for the end-to-end flow and [Authentication and trust flow](/platforms/ios#authentication-and-trust-flow) for the relay security model.
+    See [iOS App](/sv/platforms/ios#relay-backed-push-for-official-builds) for the end-to-end flow and [Authentication and trust flow](/sv/platforms/ios#authentication-and-trust-flow) for the relay security model.
 
   </Accordion>
 
@@ -329,7 +329,7 @@ When validation fails:
     - `every`: duration string (`30m`, `2h`). Set `0m` to disable.
     - `target`: `last` | `whatsapp` | `telegram` | `discord` | `none`
     - `directPolicy`: `allow` (default) or `block` for DM-style heartbeat targets
-    - See [Heartbeat](/gateway/heartbeat) for the full guide.
+    - See [Heartbeat](/sv/gateway/heartbeat) for the full guide.
 
   </Accordion>
 
@@ -350,7 +350,7 @@ When validation fails:
 
     - `sessionRetention`: prune completed isolated run sessions from `sessions.json` (default `24h`; set `false` to disable).
     - `runLog`: prune `cron/runs/<jobId>.jsonl` by size and retained lines.
-    - See [Cron jobs](/automation/cron-jobs) for feature overview and CLI examples.
+    - See [Cron jobs](/sv/automation/cron-jobs) for feature overview and CLI examples.
 
   </Accordion>
 
@@ -383,7 +383,7 @@ When validation fails:
     - Keep unsafe-content bypass flags disabled (`hooks.gmail.allowUnsafeExternalContent`, `hooks.mappings[].allowUnsafeExternalContent`) unless doing tightly scoped debugging.
     - For hook-driven agents, prefer strong modern model tiers and strict tool policy (for example messaging-only plus sandboxing where possible).
 
-    See [full reference](/gateway/configuration-reference#hooks) for all mapping options and Gmail integration.
+    See [full reference](/sv/gateway/configuration-reference#hooks) for all mapping options and Gmail integration.
 
   </Accordion>
 
@@ -405,7 +405,7 @@ When validation fails:
     }
     ```
 
-    See [Multi-Agent](/concepts/multi-agent) and [full reference](/gateway/configuration-reference#multi-agent-routing) for binding rules and per-agent access profiles.
+    See [Multi-Agent](/sv/concepts/multi-agent) and [full reference](/sv/gateway/configuration-reference#multi-agent-routing) for binding rules and per-agent access profiles.
 
   </Accordion>
 
@@ -618,16 +618,16 @@ Rules:
 }
 ```
 
-SecretRef details (including `secrets.providers` for `env`/`file`/`exec`) are in [Secrets Management](/gateway/secrets).
-Supported credential paths are listed in [SecretRef Credential Surface](/reference/secretref-credential-surface).
+SecretRef details (including `secrets.providers` for `env`/`file`/`exec`) are in [Secrets Management](/sv/gateway/secrets).
+Supported credential paths are listed in [SecretRef Credential Surface](/sv/reference/secretref-credential-surface).
 </Accordion>
 
-See [Environment](/help/environment) for full precedence and sources.
+See [Environment](/sv/help/environment) for full precedence and sources.
 
 ## Full reference
 
-For the complete field-by-field reference, see **[Configuration Reference](/gateway/configuration-reference)**.
+For the complete field-by-field reference, see **[Configuration Reference](/sv/gateway/configuration-reference)**.
 
 ---
 
-_Related: [Configuration Examples](/gateway/configuration-examples) · [Configuration Reference](/gateway/configuration-reference) · [Doctor](/gateway/doctor)_
+_Related: [Configuration Examples](/sv/gateway/configuration-examples) · [Configuration Reference](/sv/gateway/configuration-reference) · [Doctor](/sv/gateway/doctor)_

package/docs/sv/gateway/discovery.md

@@ -22,12 +22,12 @@ The design goal is to keep all network discovery/advertising in the **Node Gatew
 - **Gateway WS (control plane)**: the WebSocket endpoint on `127.0.0.1:18789` by default; can be bound to LAN/tailnet via `gateway.bind`.
 - **Direct WS transport**: a LAN/tailnet-facing Gateway WS endpoint (no SSH).
 - **SSH transport (fallback)**: remote control by forwarding `127.0.0.1:18789` over SSH.
-- **Legacy TCP bridge (deprecated/removed)**: older node transport (see [Bridge protocol](/gateway/bridge-protocol)); no longer advertised for discovery.
+- **Legacy TCP bridge (deprecated/removed)**: older node transport (see [Bridge protocol](/sv/gateway/bridge-protocol)); no longer advertised for discovery.
 
 Protocol details:
 
-- [Gateway protocol](/gateway/protocol)
-- [Bridge protocol (legacy)](/gateway/bridge-protocol)
+- [Gateway protocol](/sv/gateway/protocol)
+- [Bridge protocol (legacy)](/sv/gateway/bridge-protocol)
 
 ## Why we keep both "direct" and SSH
 
@@ -51,7 +51,7 @@ Target direction:
 - The **gateway** advertises its WS endpoint via Bonjour.
 - Clients browse and show a “pick a gateway” list, then store the chosen endpoint.
 
-Troubleshooting and beacon details: [Bonjour](/gateway/bonjour).
+Troubleshooting and beacon details: [Bonjour](/sv/gateway/bonjour).
 
 #### Service beacon details
 
@@ -95,7 +95,7 @@ If the gateway can detect it is running under Tailscale, it publishes `tailnetDn
 
 When there is no direct route (or direct is disabled), clients can always connect via SSH by forwarding the loopback gateway port.
 
-See [Remote access](/gateway/remote).
+See [Remote access](/sv/gateway/remote).
 
 ## Transport selection (client policy)
 
@@ -110,7 +110,7 @@ Recommended client behavior:
 
 The gateway is the source of truth for node/client admission.
 
-- Pairing requests are created/approved/rejected in the gateway (see [Gateway pairing](/gateway/pairing)).
+- Pairing requests are created/approved/rejected in the gateway (see [Gateway pairing](/sv/gateway/pairing)).
 - The gateway enforces:
   - auth (token / keypair)
   - scopes/ACLs (the gateway is not a raw proxy to every method)

package/docs/sv/gateway/doctor.md

@@ -358,5 +358,5 @@ doctor run.
 Doctor suggests a workspace memory system when missing and prints a backup tip
 if the workspace is not already under git.
 
-See [/concepts/agent-workspace](/concepts/agent-workspace) for a full guide to
+See [/concepts/agent-workspace](/sv/concepts/agent-workspace) for a full guide to
 workspace structure and git backup (recommended private GitHub or GitLab).

package/docs/sv/gateway/heartbeat.md

@@ -8,12 +8,12 @@ title: "Heartbeat"
 
 # Heartbeat (Gateway)
 
-> **Heartbeat vs Cron?** See [Cron vs Heartbeat](/automation/cron-vs-heartbeat) for guidance on when to use each.
+> **Heartbeat vs Cron?** See [Cron vs Heartbeat](/sv/automation/cron-vs-heartbeat) for guidance on when to use each.
 
 Heartbeat runs **periodic agent turns** in the main session so the model can
 surface anything that needs attention without spamming you.
 
-Troubleshooting: [/automation/troubleshooting](/automation/troubleshooting)
+Troubleshooting: [/automation/troubleshooting](/sv/automation/troubleshooting)
 
 ## Quick start (beginner)
 
@@ -63,7 +63,7 @@ The default prompt is intentionally broad:
   follow-ups (inbox, calendar, reminders, queued work) and surface anything urgent.
 - **Human check-in**: “Checkup sometimes on your human during day time” nudges an
   occasional lightweight “anything you need?” message, but avoids night-time spam
-  by using your configured local timezone (see [/concepts/timezone](/concepts/timezone)).
+  by using your configured local timezone (see [/concepts/timezone](/sv/concepts/timezone)).
 
 If you want a heartbeat to do something very specific (e.g. “check Gmail PubSub
 stats” or “verify gateway health”), set `agents.defaults.heartbeat.prompt` (or
@@ -218,8 +218,8 @@ Use `accountId` to target a specific account on multi-account channels like Tele
 - `isolatedSession`: when true, each heartbeat runs in a fresh session with no prior conversation history. Uses the same isolation pattern as cron `sessionTarget: "isolated"`. Dramatically reduces per-heartbeat token cost. Combine with `lightContext: true` for maximum savings. Delivery routing still uses the main session context.
 - `session`: optional session key for heartbeat runs.
   - `main` (default): agent main session.
-  - Explicit session key (copy from `pllan sessions --json` or the [sessions CLI](/cli/sessions)).
-  - Session key formats: see [Sessions](/concepts/session) and [Groups](/channels/groups).
+  - Explicit session key (copy from `pllan sessions --json` or the [sessions CLI](/sv/cli/sessions)).
+  - Session key formats: see [Sessions](/sv/concepts/session) and [Groups](/sv/channels/groups).
 - `target`:
   - `last`: deliver to the last used external channel.
   - explicit channel: `whatsapp` / `telegram` / `discord` / `googlechat` / `slack` / `msteams` / `signal` / `imessage`.

package/docs/sv/gateway/index.md

@@ -10,16 +10,16 @@ title: "Gateway-runbook"
 Använd denna sida för dag-1-uppstart och dag-2-drift av Gateway-tjänsten.
 
 <CardGroup cols={2}>
-  <Card title="Djupfelsökning" icon="siren" href="/gateway/troubleshooting">
+  <Card title="Djupfelsökning" icon="siren" href="/sv/gateway/troubleshooting">
     Symptomförst-diagnostik med exakta kommandostegar och loggsignaturer.
   </Card>
-  <Card title="Konfiguration" icon="sliders" href="/gateway/configuration">
+  <Card title="Konfiguration" icon="sliders" href="/sv/gateway/configuration">
     Uppgiftsorienterad installationsguide + fullständig konfigurationsreferens.
   </Card>
-  <Card title="Hemlighetshantering" icon="key-round" href="/gateway/secrets">
+  <Card title="Hemlighetshantering" icon="key-round" href="/sv/gateway/secrets">
     SecretRef-kontrakt, runtime-ögonblicksbildsbeteende och migrera/ladda om-operationer.
   </Card>
-  <Card title="Hemlighetsplankontrakt" icon="shield-check" href="/gateway/secrets-plan-contract">
+  <Card title="Hemlighetsplankontrakt" icon="shield-check" href="/sv/gateway/secrets-plan-contract">
     Exakta `secrets apply` mål/sökvägsregler och ref-only autentiseringsprofilbeteende.
   </Card>
 </CardGroup>
@@ -120,7 +120,7 @@ Anslut sedan klienter till `ws://127.0.0.1:18789` lokalt.
 Om gateway-autentisering är konfigurerad måste klienter fortfarande skicka autentisering (`token`/`password`) även över SSH-tunnlar.
 </Warning>
 
-Se: [Fjärr-Gateway](/gateway/remote), [Autentisering](/gateway/authentication), [Tailscale](/gateway/tailscale).
+Se: [Fjärr-Gateway](/sv/gateway/remote), [Autentisering](/sv/gateway/authentication), [Tailscale](/sv/gateway/tailscale).
 
 ## Supervision och tjänstelivscykel
 
@@ -187,7 +187,7 @@ PLLAN_CONFIG_PATH=~/.pllan/a.json PLLAN_STATE_DIR=~/.pllan-a pllan gateway --por
 PLLAN_CONFIG_PATH=~/.pllan/b.json PLLAN_STATE_DIR=~/.pllan-b pllan gateway --port 19002
 ```
 
-Se: [Flera gateways](/gateway/multiple-gateways).
+Se: [Flera gateways](/sv/gateway/multiple-gateways).
 
 ### Dev-profil snabbväg
 
@@ -211,7 +211,7 @@ Agentkörningar är tvåstegs:
 1. Omedelbar accepterad bekräftelse (`status:"accepted"`)
 2. Slutgiltigt svar (`status:"ok"|"error"`), med strömade `agent`-händelser emellan.
 
-Se fullständig protokolldokumentation: [Gateway-protokoll](/gateway/protocol).
+Se fullständig protokolldokumentation: [Gateway-protokoll](/sv/gateway/protocol).
 
 ## Driftskontroller
 
@@ -241,7 +241,7 @@ Händelser spelas inte om. Vid sekvensluckor, uppdatera tillstånd (`health`, `s
 | `Gateway start blocked: set gateway.mode=local`                | Konfiguration satt till fjärrläge        |
 | `unauthorized` under connect                                   | Autentiseringskrockar mellan klient och gateway |
 
-För fullständiga diagnosstegar, använd [Gateway-felsökning](/gateway/troubleshooting).
+För fullständiga diagnosstegar, använd [Gateway-felsökning](/sv/gateway/troubleshooting).
 
 ## Säkerhetsgarantier
 
@@ -253,9 +253,9 @@ För fullständiga diagnosstegar, använd [Gateway-felsökning](/gateway/trouble
 
 Relaterat:
 
-- [Felsökning](/gateway/troubleshooting)
-- [Bakgrundsprocess](/gateway/background-process)
-- [Konfiguration](/gateway/configuration)
-- [Hälsa](/gateway/health)
-- [Doctor](/gateway/doctor)
-- [Autentisering](/gateway/authentication)
+- [Felsökning](/sv/gateway/troubleshooting)
+- [Bakgrundsprocess](/sv/gateway/background-process)
+- [Konfiguration](/sv/gateway/configuration)
+- [Hälsa](/sv/gateway/health)
+- [Doctor](/sv/gateway/doctor)
+- [Autentisering](/sv/gateway/authentication)

package/docs/sv/gateway/local-models.md

@@ -9,9 +9,9 @@ title: "Local Models"
 
 # Local models
 
-Local is doable, but Pllan expects large context + strong defenses against prompt injection. Small cards truncate context and leak safety. Aim high: **≥2 maxed-out Mac Studios or equivalent GPU rig (~$30k+)**. A single **24 GB** GPU works only for lighter prompts with higher latency. Use the **largest / full-size model variant you can run**; aggressively quantized or “small” checkpoints raise prompt-injection risk (see [Security](/gateway/security)).
+Local is doable, but Pllan expects large context + strong defenses against prompt injection. Small cards truncate context and leak safety. Aim high: **≥2 maxed-out Mac Studios or equivalent GPU rig (~$30k+)**. A single **24 GB** GPU works only for lighter prompts with higher latency. Use the **largest / full-size model variant you can run**; aggressively quantized or “small” checkpoints raise prompt-injection risk (see [Security](/sv/gateway/security)).
 
-If you want the lowest-friction local setup, start with [Ollama](/providers/ollama) and `pllan onboard`. This page is the opinionated guide for higher-end local stacks and custom OpenAI-compatible local servers.
+If you want the lowest-friction local setup, start with [Ollama](/sv/providers/ollama) and `pllan onboard`. This page is the opinionated guide for higher-end local stacks and custom OpenAI-compatible local servers.
 
 ## Recommended: LM Studio + MiniMax M2.5 (Responses API, full-size)
 

package/docs/sv/gateway/logging.md

@@ -8,7 +8,7 @@ title: "Logging"
 
 # Logging
 
-For a user-facing overview (CLI + Control UI + config), see [/logging](/logging).
+For a user-facing overview (CLI + Control UI + config), see [/logging](/sv/logging).
 
 Pllan has two log “surfaces”: