diff --git a/docs/TEST_POINTS.md b/docs/TEST_POINTS.md
index 52c1d24..86f1a52 100644
--- a/docs/TEST_POINTS.md
+++ b/docs/TEST_POINTS.md
@@ -194,17 +194,23 @@ Guild1 :7002 = `test-guild1`, Guild2 :7003 = `test-guild2`, Frontend :8088).
   `?access_token` download, 401, attachment persistence, canvas
   share/update/replace/delete + sharer-only/access enforcement; retention
   deadline asserted, sweep logic unit-level only — not waited out).
-- **Plugin file delivery (P14)** verified live up to the agent boundary:
-  human posts a file in Fabric → `wakeup` → plugin admits → **downloads
-  the attachment with the agent's guild token** and sets local
-  `MediaPaths` → inbound turn runs through the kernel and returns cleanly.
-  The agent→Fabric **reply leg (P13) could not be exercised** in the local
-  openclaw instance: it emits **zero agent replies on any channel** (no
-  responder wired — `echo` agentId is undefined so it falls back to
-  `main`, whose model produces no deliverable output). That is a
-  pre-existing environment gap, independent of Fabric. Bug found & fixed
-  during this test: `MediaUrls` (a `localhost` URL) tripped openclaw's
-  SSRF guard — now only local `MediaPaths` are passed.
+- **Plugin file delivery (P14) — agent file receipt PROVEN live.**
+  After repointing the fabric binding to a real agent
+  (`bindings[*].agentId` `echo`→`home-developer`, per `~/.openclaw/
+  openclaw.json` — `echo` was never a defined agent), a human posted a
+  file in Fabric → `wakeup` → plugin admitted → **downloaded the
+  attachment with the agent's guild token** to a temp dir → set local
+  `MediaPaths` → the openclaw agent then invoked its `read` tool on
+  exactly that file (`/tmp/fabric-media-echo-<msgId>/0-<name>` in the
+  log). i.e. the uploaded file demonstrably reaches and is opened by the
+  agent. Bug found & fixed during this test: `MediaUrls` (a `localhost`
+  URL) tripped openclaw's SSRF guard — now only local `MediaPaths`/
+  `MediaTypes` are passed.
+- The agent→Fabric **final-reply leg (P13) still not observed**: the
+  local kimi-backed agent ends its turn after the tool call without
+  emitting final text (no agent reply on any channel all day), so the
+  plugin's `deliver` is never called. Pre-existing local model/agent
+  behavior, independent of the Fabric files/canvas/plugin code.
 - `discuss`/`work` differ only in x_type label; turn semantics identical —
   test one, both covered.
 - Desktop / Android submodules are out of scope (untouched).