重构主控编排与运行时预热链路，统一工作区提示词/专家调度协议并补齐 wiki 记忆注入与写回闭环。

同时收敛启动与运维脚本默认行为（含 wiki worker）、更新 Admin 可观测性与相关测试，降低首轮时延并提高运行稳定性。

Made-with: Cursor

openclaw/docs/providers/opencode-go.md

@@ -0,0 +1,110 @@
+---
+summary: "Use the OpenCode Go catalog with the shared OpenCode setup"
+read_when:
+  - You want the OpenCode Go catalog
+  - You need the runtime model refs for Go-hosted models
+title: "OpenCode Go"
+---
+
+# OpenCode Go
+
+OpenCode Go is the Go catalog within [OpenCode](/providers/opencode).
+It uses the same `OPENCODE_API_KEY` as the Zen catalog, but keeps the runtime
+provider id `opencode-go` so upstream per-model routing stays correct.
+
+| Property         | Value                           |
+| ---------------- | ------------------------------- |
+| Runtime provider | `opencode-go`                   |
+| Auth             | `OPENCODE_API_KEY`              |
+| Parent setup     | [OpenCode](/providers/opencode) |
+
+## Supported models
+
+| Model ref                  | Name         |
+| -------------------------- | ------------ |
+| `opencode-go/kimi-k2.5`    | Kimi K2.5    |
+| `opencode-go/glm-5`        | GLM 5        |
+| `opencode-go/minimax-m2.5` | MiniMax M2.5 |
+
+## Getting started
+
+<Tabs>
+  <Tab title="Interactive">
+    <Steps>
+      <Step title="Run onboarding">
+        ```bash
+        openclaw onboard --auth-choice opencode-go
+        ```
+      </Step>
+      <Step title="Set a Go model as default">
+        ```bash
+        openclaw config set agents.defaults.model.primary "opencode-go/kimi-k2.5"
+        ```
+      </Step>
+      <Step title="Verify models are available">
+        ```bash
+        openclaw models list --provider opencode-go
+        ```
+      </Step>
+    </Steps>
+  </Tab>
+
+  <Tab title="Non-interactive">
+    <Steps>
+      <Step title="Pass the key directly">
+        ```bash
+        openclaw onboard --opencode-go-api-key "$OPENCODE_API_KEY"
+        ```
+      </Step>
+      <Step title="Verify models are available">
+        ```bash
+        openclaw models list --provider opencode-go
+        ```
+      </Step>
+    </Steps>
+  </Tab>
+</Tabs>
+
+## Config example
+
+```json5
+{
+  env: { OPENCODE_API_KEY: "YOUR_API_KEY_HERE" }, // pragma: allowlist secret
+  agents: { defaults: { model: { primary: "opencode-go/kimi-k2.5" } } },
+}
+```
+
+## Advanced notes
+
+<AccordionGroup>
+  <Accordion title="Routing behavior">
+    OpenClaw handles per-model routing automatically when the model ref uses
+    `opencode-go/...`. No additional provider config is required.
+  </Accordion>
+
+  <Accordion title="Runtime ref convention">
+    Runtime refs stay explicit: `opencode/...` for Zen, `opencode-go/...` for Go.
+    This keeps upstream per-model routing correct across both catalogs.
+  </Accordion>
+
+  <Accordion title="Shared credentials">
+    The same `OPENCODE_API_KEY` is used by both the Zen and Go catalogs. Entering
+    the key during setup stores credentials for both runtime providers.
+  </Accordion>
+</AccordionGroup>
+
+<Tip>
+See [OpenCode](/providers/opencode) for the shared onboarding overview and the full
+Zen + Go catalog reference.
+</Tip>
+
+## Related
+
+<CardGroup cols={2}>
+  <Card title="OpenCode (parent)" href="/providers/opencode" icon="server">
+    Shared onboarding, catalog overview, and advanced notes.
+  </Card>
+  <Card title="Model selection" href="/concepts/model-providers" icon="layers">
+    Choosing providers, model refs, and failover behavior.
+  </Card>
+</CardGroup>