docs: point consumers to adapter seam / 文件明確導向 adapter seam

HANDOFF.md

@@ -33,6 +33,17 @@ In `openclawtest`, the Telegram + OpenClaw PoC has already proven:
 
 This is not yet a clean cross-agent installable package. It is a successful PoC being pushed toward a cleaner reusable path.
 
+## Preferred integration seam now
+
+When extending the project, prefer the repo-side OpenClaw adapter path over directly expanding runtime patch logic.
+
+Current preferred seam:
+
+- `src/adapters/openclaw-plugin-skeleton.ts`
+- `src/adapters/openclaw-interactive-handler.ts`
+- `src/adapters/openclaw-message-tool.ts`
+- `src/adapters/openclaw-state-file.ts`
+
 ## Where to start reading
 
 Read these files first:

INSTALL.md

@@ -36,6 +36,13 @@ This does two things:
 
 ## Manual paths
 
+If you are extending the feature rather than merely applying the PoC, prefer starting from these repo-side integration seams before editing runtime files directly:
+
+- `src/adapters/openclaw-plugin-skeleton.ts`
+- `src/adapters/openclaw-interactive-handler.ts`
+- `src/adapters/openclaw-message-tool.ts`
+- `src/adapters/openclaw-state-file.ts`
+
 ### Apply patch only
 
 ```bash

INTEGRATION.md

@@ -53,11 +53,20 @@ At minimum, verify these behaviors in Telegram:
 
 - `src/adapters/openclaw.ts`
 - `src/adapters/openclaw-state-file.ts`
+- `src/adapters/openclaw-message-tool.ts`
+- `src/adapters/openclaw-interactive-handler.ts`
+- `src/adapters/openclaw-plugin-skeleton.ts`
 - `src/runtime/openclaw-telegram-bridge.ts`
 - `src/runtime/openclaw-telegram-poc.ts`
 
 These do not yet replace the runtime patch end-to-end, but they are the current repo-side ownership points for the logic.
 
+Current preferred future seam:
+
+- `src/adapters/openclaw-plugin-skeleton.ts`
+
+This is the clearest current approximation of where a cleaner formal plugin-facing integration path should grow.
+
 ## Known limitation
 
 The current integration path is reproducible, but not yet clean enough to call a final plugin package.