From e14f63b510a9262671d5891984c2227cba0ef5de Mon Sep 17 00:00:00 2001
From: "Alice (OpenClaw)" <alice@cowbay.org>
Date: Thu, 14 May 2026 09:36:11 +0800
Subject: [PATCH] =?UTF-8?q?docs:=20point=20consumers=20to=20adapter=20seam?=
 =?UTF-8?q?=20/=20=E6=96=87=E4=BB=B6=E6=98=8E=E7=A2=BA=E5=B0=8E=E5=90=91?=
 =?UTF-8?q?=20adapter=20seam?=
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

---
 HANDOFF.md     | 11 +++++++++++
 INSTALL.md     |  7 +++++++
 INTEGRATION.md |  9 +++++++++
 3 files changed, 27 insertions(+)

diff --git a/HANDOFF.md b/HANDOFF.md
index 8942340..ba518cc 100644
--- a/HANDOFF.md
+++ b/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:
diff --git a/INSTALL.md b/INSTALL.md
index bf8f303..3f137ec 100644
--- a/INSTALL.md
+++ b/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
diff --git a/INTEGRATION.md b/INTEGRATION.md
index 08b59fa..34be190 100644
--- a/INTEGRATION.md
+++ b/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.