docs: fix internal doc links

docs/concepts/agent.md

@@ -13,11 +13,11 @@ CLAWDBOT uses a single agent workspace directory (`agent.workspace`) as the agen
 
 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`](/agent-workspace)
+Full workspace layout + backup guide: [`docs/agent-workspace.md`](/concepts/agent-workspace)
 
 If `agent.sandbox` is enabled, non-main sessions can override this with
 per-session workspaces under `agent.sandbox.workspaceRoot` (see
-[`docs/configuration.md`](/configuration)).
+[`docs/configuration.md`](/gateway/configuration)).
 
 ## Bootstrap files (injected)
 
@@ -52,7 +52,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`](/configuration)).
+Skills can be gated by config/env (see `skills` in [`docs/configuration.md`](/gateway/configuration)).
 
 ## p-mono integration
 
@@ -91,7 +91,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`](/queue) for mode + debounce/cap behavior.
+[`docs/queue.md`](/concepts/queue) for mode + debounce/cap behavior.
 
 Block streaming sends completed assistant blocks as soon as they finish; disable
 via `agent.blockStreamingDefault: "off"` if you only want the final response.
@@ -109,4 +109,4 @@ At minimum, set:
 
 ---
 
-*Next: [Group Chats](/group-messages)* 🦞
+*Next: [Group Chats](/concepts/group-messages)* 🦞

docs/concepts/architecture.md

@@ -46,7 +46,7 @@ Last updated: 2026-01-05
 - **Clients (mac app / CLI / web admin)**  
   - One WS connection per client.  
   - Send requests (`health`, `status`, `send`, `agent`, `system-presence`, toggles) and subscribe to events (`tick`, `agent`, `presence`, `shutdown`).
-  - On macOS, the app can also be invoked via deep links (`clawdbot://agent?...`) which translate into the same Gateway `agent` request path (see [`docs/macos.md`](/macos)).
+  - On macOS, the app can also be invoked via deep links (`clawdbot://agent?...`) which translate into the same Gateway `agent` request path (see [`docs/macos.md`](/platforms/macos)).
 - **Agent process (Pi)**  
   - Spawned by the Gateway on demand for `agent` calls; streams events back over the same WS connection.
 - **WebChat**  

docs/concepts/groups.md

@@ -127,4 +127,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`](/group-messages) for WhatsApp-only behavior (history injection, mention handling details).
+See [`docs/group-messages.md`](/concepts/group-messages) for WhatsApp-only behavior (history injection, mention handling details).

docs/concepts/model-failover.md

@@ -85,9 +85,9 @@ timeouts that exhausted profile rotation.
 
 ## Related config
 
-See [`docs/configuration.md`](/configuration) for:
+See [`docs/configuration.md`](/gateway/configuration) for:
 - `auth.profiles` / `auth.order`
 - `agent.model.primary` / `agent.model.fallbacks`
 - `agent.imageModel` routing
 
-See [`docs/models.md`](/models) for the broader model selection and fallback overview.
+See [`docs/models.md`](/concepts/models) for the broader model selection and fallback overview.

docs/concepts/models.md

@@ -7,7 +7,7 @@ read_when:
 ---
 # Models CLI plan
 
-See [`docs/model-failover.md`](/model-failover) for how auth profiles rotate (OAuth vs API keys), cooldowns, and how that interacts with model fallbacks.
+See [`docs/model-failover.md`](/concepts/model-failover) for how auth profiles rotate (OAuth vs API keys), cooldowns, and how that interacts with model fallbacks.
 
 Goal: give clear model visibility + control (configured vs available), plus scan tooling
 that prefers tool-call + image-capable models and maintains ordered fallbacks.
@@ -83,7 +83,7 @@ Output
 - Image routing uses `agent.imageModel` **only when configured** and the primary
   model lacks image input.
 - Persist last successful provider/model to session entry; auth profile success is global.
-- See [`docs/model-failover.md`](/model-failover) for auth profile rotation, cooldowns, and timeout handling.
+- See [`docs/model-failover.md`](/concepts/model-failover) for auth profile rotation, cooldowns, and timeout handling.
 
 ## Tests
 
@@ -93,5 +93,5 @@ Output
 
 ## Docs
 
-- Update [`docs/configuration.md`](/configuration) with `agent.models` + `agent.model` + `agent.imageModel`.
+- Update [`docs/configuration.md`](/gateway/configuration) with `agent.models` + `agent.model` + `agent.imageModel`.
 - Keep this doc current when CLI surface or scan logic changes.

docs/concepts/sessions.md

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