Skip to content

docs: review OpenClaw integration OpenSpec draft - #7

Merged
loong10k merged 33 commits into
mainfrom
test/20261118
Nov 19, 2026
Merged

loong10k merged 33 commits into
mainfrom
test/20261118

Conversation

@loong10k

@loong10k loong10k commented Nov 17, 2026 •

Copy link
Copy Markdown
Collaborator

Scope

Promote the OpenClaw integration OpenSpec draft from test/20261118 for G0/G1 review. The draft contains six changes and 21 capability specs; it does not modify SDK Java source, build files, or active openspec/specs capabilities.

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

  • The original README/validation summary said all 97 tasks were unchecked and OpenSpec was unavailable. The later G0 commit had already checked five evidence tasks and recorded OpenSpec 1.8.0 validation. The corrected documents distinguish those historical steps from current verification.
  • A stray .mimosa session-state file was removed. The 61-file manifest matched the initial review snapshot. The evidence added since that snapshot is listed below.
  • Current OpenSpec 1.14.1 strict validation passes 6/6 changes with zero issues; git diff --check passed. 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

  • The recorded OpenClaw version 2026.7.1-2 is still available in the npm registry. Its official release tag resolves to commit 0790d9f593ad30c940ed93b5872a8cf6d6f3cf8c, matching the abbreviated commit in the G0 version record. The registry reports integrity sha512-ycF3yPcbjN6bUPeaUx6Mh6vze1hQWoD3CT/wWcmD7a8xaHHHRUaAlaq+lFxMHf1ssEgODVAwjlzYqp2twkYZ7g==.
  • On 2026-11-18 the latest stable release was 2026.11.5, tag commit e13cf15ece9bbd969b7362927c315362c90c97ff. npm also provides this version. It is a candidate for separate scope review.
  • 2026.7.1-2 remains the recorded baseline. 2026.11.5 has 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 to e13cf15ece9bbd969b7362927c315362c90c97ff. 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 includes protocol.schema.json, verified against npm's package integrity. The schema SHA-256 is fd29d1da7e6ebd0c1014617611ff442164495b3130bbdaea79ca87925324b8b6. 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 source

Existing change Scope proposed for this release
Compatibility governance Keep the three JDK lines and shared wire fixtures. Use the recorded source commit and published schema digest for candidate fixtures. The isolated candidate Gateway passed health, authenticated connect and permission denial checks.
Protocol contracts Revalidate Responses JSON/SSE continuation, incomplete/failed terminal events and cancellation. Check chat history delta, reset, and directional cursor paths and the Tools Invoke authorization matrix.
Managed Gateway client Revalidate hello decoding with additive fields such as server.buildId, server.bootId and auth metadata, along with reconnect and subscription reconciliation.
Agent, session and approval control Keep the proposed control surfaces. Verify method-level permission checks, exact run ownership and the distinction between one-shot approval decisions and persisted policy.
Gateway operations Keep the six existing capability areas. Enable methods according to the target Gateway's capabilities, installed plugins and granted scopes. New upstream methods outside these areas stay outside the current implementation scope.
Optional runtime adapters Keep terminal/voice, persistent MCP/ACP and typed CLI output optional. Select fixtures per documented command and verify tolerant JSON decoding and exit/status behavior.

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.list returned missing 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 client

The evidence is committed on the documentation feature branch at c9760eae36ab78047807cb880605a8c47f7e7871 and included in this PR at 37afb64b12d70e2ad43187f8dc02e0c0e98be1b5. Gateway test matrix and reproduction notes · JDK 17 GitHub CI

Follow-up evidence at fc9c74a

  • The shared compatibility fixture independently exercises both Gateway versions on the JDK 8, 17 and 21 lines. The G0 audit maps all eight governance scenarios to available evidence and outstanding acceptance checks. Shared fixture · G0 scenario audit
  • Across both Gateway versions and all three SDK lines, six sequential chat-stream checks passed and six concurrent checks failed at the final-text assertion. The test used a real loopback Gateway and a deterministic local model fixture. Concurrent run isolation and terminal semantics remain G1 acceptance items. Streaming evidence
  • OpenSpec 1.14.1 strict validation passed all six changes at this PR head. The JDK 17 GitHub check also passed. The proposed target is still awaiting maintainer approval. GitHub CI

2026.11.5 review evidence at 3456591

  • CHAT-01 live probes passed on JDK 8, 17 and 21 against both Gateway versions, with zero failures or skips. The 2026.11.5 Gateway sent one replace=true event with an empty deltaText between the regular deltas and the full final snapshot. The 2026.7.1-2 Gateway sent no replacement event. SDK acceptance still includes nonempty replacements, repeated terminal events and compatibility with existing callbacks. Live fixture and reproduction notes
  • The CHAT-02 strict runId patch 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 head

Responses review at 2554092

  • With a known response ID and a synthetic call ID, the 2026.11.5 Gateway 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.
  • A separate loopback 2026.11.5 configuration 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.
  • Both Gateway versions released the upstream model connection after the SSE client disconnected. The fixture recognizes TCP EOF and a connection reset. OpenSpec strict validation passed all six changes. Java SSE implementation, its acceptance checks and maintainer approval remain pending. Reproduction and evidence · CI

Java baseline at 7a007c2

The same loopback test executed on JDK 8, 17 and 21, one case per line with no failures or skips. Each line sent the stream=true request 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

loong10k and others added 4 commits September 20, 2026 22:22
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
loong10k and others added 2 commits November 18, 2026 06:28
@loong10k

Copy link
Copy Markdown
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
loong10k marked this pull request as ready for review November 19, 2026 05:19
@loong10k
loong10k merged commit 39e54d8 into main Nov 19, 2026
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant