From 31bb30755bfa9413fb5d1c901173d800db7af45c Mon Sep 17 00:00:00 2001 From: Claude Date: Thu, 6 Aug 2026 15:03:02 +0000 Subject: [PATCH] =?UTF-8?q?docs(client-sdk):=20=E5=90=88=E8=A7=84=E7=9F=A9?= =?UTF-8?q?=E9=98=B5=E9=93=BE=E6=8E=A5=E5=A6=82=E5=AE=9E=E6=A0=87=E6=B3=A8?= =?UTF-8?q?=E4=B8=BA=E5=B7=B2=E9=80=80=E5=BD=B9,=E5=B9=B6=E6=8C=87?= =?UTF-8?q?=E5=90=91=E7=9C=9F=E6=AD=A3=E7=9A=84=E4=BA=8B=E5=AE=9E=E6=BA=90?= =?UTF-8?q?=20(#5878)?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit content/docs/api/client-sdk.mdx 的 "Protocol Compliance Documentation" 一节 把 packages/client/CLIENT_SPEC_COMPLIANCE.md 宣传成「逐方法验证 13 个 namespace」的活矩阵,而该文件今天第一行就是 (RETIRED):它 2026-07-27 已被 #3563 路由审计退役,并自述当年的 "FULLY COMPLIANT" 结论是拿运行时无人消费的 DEFAULT_DISPATCHER_ROUTES 量出来的 —— 按服务端真实路由面重测,审计当天就有 27 条路由没有 SDK 表达。 被链接方已自我否定,链接方仍按它退役前的口径宣传 —— 点进去之前,读者(尤其是 照 backlog 找「协议覆盖在哪看」的 agent)得到的是「有一份逐方法验证的活矩阵」 这个错误印象。 按立单者倾向的方向 1 处置:保留链接(不断入链)但如实描述其已退役身份,并把 「今天覆盖在哪断言」指向 packages/runtime/src/route-ledger.ts 与两侧 conformance 测试 —— 二者均已对 origin/main 核实存在。 不动 packages/client/CLIENT_SPEC_COMPLIANCE.md:它是有意保留的墓碑, 自述 "Hand-maintained compliance tables drift; this one is not coming back"。 不重建任何合规矩阵 —— 那正是被退役的做法。 Co-Authored-By: Claude Fable 5 Claude-Session: https://claude.ai/code/session_01BDmDsu2575gDxeMCxXhDE3 --- content/docs/api/client-sdk.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/docs/api/client-sdk.mdx b/content/docs/api/client-sdk.mdx index 154b02cfe7..4116b19622 100644 --- a/content/docs/api/client-sdk.mdx +++ b/content/docs/api/client-sdk.mdx @@ -696,7 +696,7 @@ Integration tests verify end-to-end communication with a live ObjectStack server For detailed information about the client's protocol implementation: -- **[Protocol Compliance Matrix](https://github.com/objectstack-ai/objectstack/blob/main/packages/client/CLIENT_SPEC_COMPLIANCE.md)** — Method-by-method verification of all API methods across 13 namespaces +- **[Protocol Compliance Matrix (retired)](https://github.com/objectstack-ai/objectstack/blob/main/packages/client/CLIENT_SPEC_COMPLIANCE.md)** — Historical only: retired 2026-07-27 by the #3563 route audit, which disproved its "fully compliant" verdict (27 routes had no SDK expression on the day it still claimed one). Kept so inbound links don't break; coverage today is asserted in CI by [`packages/runtime/src/route-ledger.ts`](https://github.com/objectstack-ai/objectstack/blob/main/packages/runtime/src/route-ledger.ts) and the conformance tests on both sides - **[Integration Tests](https://github.com/objectstack-ai/objectstack/blob/main/packages/client/tests/integration/README.md)** — What client-server integration coverage exists today, and the backlog of namespaces still unwritten - **[Package README](https://github.com/objectstack-ai/objectstack/blob/main/packages/client/README.md)** — Developer navigation and API reference