fix(openclaw): restore contract-driven tool registration - #281
Merged
Conversation
linfangw
marked this pull request as ready for review
July 30, 2026 04:44
Collaborator
|
@codex review |
Collaborator
|
@codex review |
vxwork
approved these changes
Jul 30, 2026
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.
Summary
qveris_discover,qveris_call, andqveris_inspectincontracts.tools@qverisai/qveris2026.7.30and update its changelog, troubleshooting guidance, and release notesRoot cause
OpenClaw
>=2026.6.11rejects agent-tool registrations unless the manifest declares ownership incontracts.tools. Version2026.7.15registered the three runtime names but omitted that manifest contract, so the plugin loaded withtoolNames: []and emittedplugin must declare contracts.tools before registering agent tools.The issue was reproduced against an isolated OpenClaw state directory before the fix. The same inspection now reports all three registered tools with no error diagnostics. A separate compiled-factory check verifies that all three concrete tool descriptors are produced when either supported credential path is configured, and that the factory returns
nullwhen credentials are absent.Deep-review corrections
plugins inspect --runtimeproves concrete factory instantiation;tools[].namesis registration metadata even when the factory returnsnullqveris_callexplicitlyreplaySafe: falseand now checks exact auth/config/replay metadataCompatibility matrix
2026.6.11minimum2026.6.33extended stable2026.7.1-2current stableRuntime checks use a synthetic key and do not call the QVeris API.
Validation
npm audit --omit=dev)Closes #272