docs(website): add system prompt section and rename openclaw page

Document how CLI, Gen, and server share the same base system prompt
in architecture.md. Rename openclaw-migration to openclaw-compatibility
to reflect that the projects have diverged as fundamentally different
tools, and remove the cleanup section.

Author: yiwang

website/docs/architecture.md

@@ -177,6 +177,30 @@ Primary user-facing binary with commands:
 - Procedural environmental audio (FunDSP)
 - glTF/GLB scene export
 
+## System Prompt
+
+All binaries share the same base system prompt, built by `build_system_prompt()` in `localgpt-core`. This function assembles identity, safety guidelines, tool descriptions, workspace info, and runtime metadata. On each new session, the agent loads workspace context (SOUL.md, MEMORY.md, daily logs, HEARTBEAT.md) and appends it to the system prompt.
+
+### What's shared
+
+Every binary — CLI, Gen, server, mobile, bridge daemons — gets the same core prompt through `Agent::new_session()`. This includes:
+
+- Identity and safety guidelines
+- Tool documentation (generated from the registered tool set)
+- Workspace directory and current time
+- Memory file conventions
+- Runtime info (model, hostname, OS)
+
+### What differs
+
+| | CLI | Gen | Server / Mobile |
+|---|---|---|---|
+| **Agent creation** | `Agent::new()` — async, connects MCP servers | `Agent::new_with_tools()` — sync, tools provided upfront | `Agent::new()` — safe tools only |
+| **Tools** | Safe tools + CLI tools (bash, file ops) + spawn_agent | Safe tools + gen3d tools (spawn_entity, etc.); interactive mode also adds CLI tools | Safe tools only (no file system access) |
+| **Extra prompts** | None | `GEN_MEMORY_PROMPT` (creative memory guidance) added as a user message; `HEADLESS_EXPERIMENT_PROMPT` for headless mode | None |
+
+Gen's additional prompts live in `crates/gen/src/gen3d/system_prompt.rs` and are injected as **user messages** in the chat history, not modifications to the system prompt itself. This keeps the core prompt identical while giving Gen domain-specific guidance for creative world-building and memory usage.
+
 ## Mobile
 
 ### `localgpt-mobile-ffi`

website/docs/openclaw-migration.md website/docs/openclaw-compatibility.mdwebsite/docs/openclaw-migration.md renamed to website/docs/openclaw-compatibility.md

@@ -1,8 +1,6 @@
-# Migrating from OpenClaw
+# OpenClaw Compatibility
 
-LocalGPT is a spiritual successor to OpenClaw, built from scratch in Rust. It uses the same workspace file formats and conventions, so migrating your data is straightforward.
-
-LocalGPT does **not** auto-migrate your OpenClaw data. Follow the steps below to bring your existing workspace, config, and sessions into LocalGPT.
+LocalGPT started as a spiritual successor to OpenClaw, built from scratch in Rust. While the two projects have since diverged into fundamentally different tools, LocalGPT uses the same workspace file formats and conventions, so existing OpenClaw data can be reused.
 
 ## Config
 
@@ -80,13 +78,3 @@ LocalGPT takes a different approach from OpenClaw in several areas:
 - **No subagent spawning** — single "main" agent
 
 Everything else — memory, heartbeat, skills, session management — works the same way.
-
-## Cleanup
-
-Once you have verified that LocalGPT is working correctly with your migrated data, you can optionally remove the OpenClaw directory:
-
-```bash
-rm -rf ~/.openclaw
-```
-
-This will suppress the startup notice about detected OpenClaw data.

website/sidebars.ts

@@ -6,7 +6,7 @@ const sidebars: SidebarsConfig = {
     {
       type: 'category',
       label: 'Getting Started',
-      items: ['installation', 'quick-start', 'openclaw-migration', 'upgrade-v0.2'],
+      items: ['installation', 'quick-start', 'openclaw-compatibility', 'upgrade-v0.2'],
     },
     {
       type: 'category',