Repository navigation
docs: review OpenClaw integration OpenSpec draft - #7
Merged
Merged
Conversation
Add six draft changes, 21 capability specifications, 64 requirements, 128 scenarios, and 97 unchecked implementation tasks. Include source baselines, roadmap, acceptance plan, traceability and losslessly packaged document-validation evidence. Preserve existing SDK sources, tests, build files, and root READMEs. Documentation only: no implementation approval, official OpenSpec CLI validation, SDK builds, or live Gateway tests are claimed.
…校验 6/6 - 任务 1.2/1.3/2.1/3.3/3.4 完成并附证据工件(evidence/) - 1.1/2.2/2.3/2.4/3.1/3.2/3.5 标注人审或环境阻塞原因,G1 编码保持阻断
…nclaw-doc-evidence docs: verify OpenClaw draft evidence on feature branch
…nclaw-doc-evidence docs: align OpenClaw roadmap with verified G0 status
Collaborator
Author
|
Verification update for exact test branch head c059f0c: JDK 17 Build & Verify CI run 44190567891 succeeded. The follow-up roadmap correction entered test via PR #8. Local OpenSpec 1.14.1 strict validation passed 6/6 changes; 61/61 manifest hashes match. This is document validation only. G0/G1 maintainer review and live Gateway acceptance remain open, so this PR stays draft. |
loong10k
marked this pull request as ready for review
November 19, 2026 05:19
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Scope
Promote the OpenClaw integration OpenSpec draft from
test/20261118for G0/G1 review. The draft contains six changes and 21 capability specs; it does not modify SDK Java source, build files, or activeopenspec/specscapabilities.This supersedes the original documentation PR #2 with the same draft plus corrected status evidence. The feature → test integration is PR #6, merged at
fe0c14f344e97407731f802064aa36c19e9b339a.Review findings and corrections
.mimosasession-state file was removed. The 61-file manifest matched the initial review snapshot. The evidence added since that snapshot is listed below.git diff --checkpassed. This validates document structure, not product behavior.Gate
Remain draft until the G0/G1 scope and exact target OpenClaw version are reviewed by the maintainer. Across the six changes, 7 of 97 tasks are checked and 90 remain. The isolated live Gateway checks satisfy G0 task 3.1. Full Gateway acceptance, SDK implementation, and spec sync and archive remain pending.
Reproducible upstream version evidence
2026.7.1-2is still available in the npm registry. Its official release tag resolves to commit0790d9f593ad30c940ed93b5872a8cf6d6f3cf8c, matching the abbreviated commit in the G0 version record. The registry reports integritysha512-ycF3yPcbjN6bUPeaUx6Mh6vze1hQWoD3CT/wWcmD7a8xaHHHRUaAlaq+lFxMHf1ssEgODVAwjlzYqp2twkYZ7g==.2026.11.5, tag commite13cf15ece9bbd969b7362927c315362c90c97ff. npm also provides this version. It is a candidate for separate scope review.2026.7.1-2remains the recorded baseline.2026.11.5has completed the same isolated handshake, authentication and authorization checks as a candidate for the baseline.2026.11.5 scope review
The maintainer requested a scope review for
2026.11.5. The release tag resolves toe13cf15ece9bbd969b7362927c315362c90c97ff. The npm runtime requires Node>=24.16.0 <25 || >=26.1.0. Gateway protocol and minimum operator client protocol remain 4 across the two tags. The published protocol package includesprotocol.schema.json, verified against npm's package integrity. The schema SHA-256 isfd29d1da7e6ebd0c1014617611ff442164495b3130bbdaea79ca87925324b8b6. It exposes 559 method records and 1,149 definitions. Runtime capability checks still use the target Gateway's advertised methods and event set. Release · Protocol package · Protocol version sourceserver.buildId,server.bootIdand auth metadata, along with reconnect and subscription reconciliation.Responses HTTP · Tools Invoke · Handshake schema · Session control · Approvals · MCP CLI JSON
The review uses published artifacts, tagged upstream source, and isolated runtime evidence. Maintainer approval of the target version and G0/G1 scope remains pending.
On both Gateway versions, all three SDK release lines negotiated protocol 4 with valid tokens, received Gateway rejections for invalid tokens and successfully listed sessions with
operator.read. With an empty scope list,sessions.listreturnedmissing scope: operator.read. Together with the two default-branch probes, 26 test cases ran without failures or skips. The default-branch client was rejected at connect metadata validation (client.id) on both versions, before its declared protocol 1 could be negotiated. Track this gap under G1. The live checks did not invoke a model or exercise the proposed G1 features. JDK 8 head · JDK 17 head · JDK 21 head · Default-branch clientThe evidence is committed on the documentation feature branch at
c9760eae36ab78047807cb880605a8c47f7e7871and included in this PR at37afb64b12d70e2ad43187f8dc02e0c0e98be1b5. Gateway test matrix and reproduction notes · JDK 17 GitHub CIFollow-up evidence at
fc9c74a2026.11.5 review evidence at
34565912026.11.5Gateway sent onereplace=trueevent with an emptydeltaTextbetween the regular deltas and the full final snapshot. The2026.7.1-2Gateway sent no replacement event. SDK acceptance still includes nonempty replacements, repeated terminal events and compatibility with existing callbacks. Live fixture and reproduction notesrunIdpatch passed the isolated concurrent Gateway fixture on both versions across the three Java lines. The candidate patch is attached for review. Approval of the target release and implementation scope is still pending. Concurrent verification and candidate patch · JDK 17 CI at this headResponses review at
25540922026.11.5Gateway accepted an empty tool result in both JSON and SSE and called the local model once per request. The locked version returned HTTP 400 before model invocation.2026.11.5configuration allowed only the synthetic tool, disabled tool discovery and declared a larger model context. With that configuration, the Gateway generated a function call and accepted an empty result using the returned call ID and the original response ID. A mixed SSE probe preserved both output indexes, text, call ID, arguments and usage. The synthetic model fixture still fails to produce tool calls under the default configuration.Java baseline at
7a007c2The same loopback test executed on JDK 8, 17 and 21, one case per line with no failures or skips. Each line sent the
stream=truerequest through the existing JSON entry and attempted JSON parsing after receiving SSE. This reproduces the RSP-01-S2 gap on all three current feature heads. The fixture was recorded alongside the review evidence. Fixture and exact feature commits