Docs: fix internal links

docs/concepts/agent-workspace.md

@@ -215,6 +215,6 @@ Suggested `.gitignore` starter:
 ## Advanced notes
 
 - Multi-agent routing can use different workspaces per agent. See
-  `docs/provider-routing.md` for routing configuration.
+  [Provider routing](/concepts/provider-routing) for routing configuration.
 - If `agents.defaults.sandbox` is enabled, non-main sessions can use per-session sandbox
   workspaces under `agents.defaults.sandbox.workspaceRoot`.

docs/concepts/agent.md

@@ -13,11 +13,11 @@ Clawdbot uses a single agent workspace directory (`agents.defaults.workspace`) a
 
 Recommended: use `clawdbot setup` to create `~/.clawdbot/clawdbot.json` if missing and initialize the workspace files.
 
-Full workspace layout + backup guide: [`docs/agent-workspace.md`](/concepts/agent-workspace)
+Full workspace layout + backup guide: [Agent workspace](/concepts/agent-workspace)
 
 If `agents.defaults.sandbox` is enabled, non-main sessions can override this with
 per-session workspaces under `agents.defaults.sandbox.workspaceRoot` (see
-[`docs/configuration.md`](/gateway/configuration)).
+[Gateway configuration](/gateway/configuration)).
 
 ## Bootstrap files (injected)
 
@@ -54,7 +54,7 @@ Clawdbot loads skills from three locations (workspace wins on name conflict):
 - Managed/local: `~/.clawdbot/skills`
 - Workspace: `<workspace>/skills`
 
-Skills can be gated by config/env (see `skills` in [`docs/configuration.md`](/gateway/configuration)).
+Skills can be gated by config/env (see `skills` in [Gateway configuration](/gateway/configuration)).
 
 ## p-mono integration
 
@@ -81,7 +81,7 @@ message is injected before the next assistant response.
 
 When queue mode is `followup` or `collect`, inbound messages are held until the
 current turn ends, then a new agent turn starts with the queued payloads. See
-[`docs/queue.md`](/concepts/queue) for mode + debounce/cap behavior.
+[Queue](/concepts/queue) for mode + debounce/cap behavior.
 
 Block streaming sends completed assistant blocks as soon as they finish; it is
 **off by default** (`agents.defaults.blockStreamingDefault: "off"`).

docs/concepts/groups.md

@@ -215,4 +215,4 @@ The agent system prompt includes a group intro on the first turn of a new group
 - Group replies always go back to the same `chat_id`.
 
 ## WhatsApp specifics
-See [`docs/group-messages.md`](/concepts/group-messages) for WhatsApp-only behavior (history injection, mention handling details).
+See [Group messages](/concepts/group-messages) for WhatsApp-only behavior (history injection, mention handling details).

docs/concepts/model-failover.md

@@ -113,11 +113,11 @@ When a run starts with a model override (hooks or CLI), fallbacks still end at
 
 ## Related config
 
-See [`docs/configuration.md`](/gateway/configuration) for:
+See [Gateway configuration](/gateway/configuration) for:
 - `auth.profiles` / `auth.order`
 - `auth.cooldowns.billingBackoffHours` / `auth.cooldowns.billingBackoffHoursByProvider`
 - `auth.cooldowns.billingMaxHours` / `auth.cooldowns.failureWindowHours`
 - `agents.defaults.model.primary` / `agents.defaults.model.fallbacks`
 - `agents.defaults.imageModel` routing
 
-See [`docs/models.md`](/concepts/models) for the broader model selection and fallback overview.
+See [Models](/concepts/models) for the broader model selection and fallback overview.

docs/concepts/sessions.md

@@ -5,4 +5,4 @@ read_when:
 ---
 # Sessions
 
-Canonical session management docs live in [`docs/session.md`](/concepts/session).
+Canonical session management docs live in [Session management](/concepts/session).