Repository navigation
fix: stop false compat gaps for split OpenClaw registries - #78
Merged
Merged
Conversation
|
🦞👀 Pull request received. I will update this pull request when review starts. |
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.
What Problem This Solves
Fixes an issue where inspecting an OpenClaw checkout with a split compatibility registry reports existing records as missing. The released Inspector 0.3.25 reader scanned only the wrapper and reported zero records, producing four false P1 findings for Kitchen Sink 0.3.0.
This is an existing reader defect exposed by the current-main rerun, not a new OpenClaw runtime regression.
Why This Change Was Made
Follow the explicit value import of
PLUGIN_COMPAT_RECORDSfrom./registry-records.jsinto the fixed siblingregistry-records.ts. Report that selected source path and propagate missing delegated data as an error.Comments, quoted examples, and type-only imports do not select the sibling. Inline registries, including empty ones, remain authoritative without that value import. This does not recursively resolve imported record groups or claim exhaustive registry discovery.
User Impact
Existing compatibility records retain their statuses and no longer produce false missing-record findings. Genuine absent records still produce findings. Public report fields and codes, dependencies, and package versions are unchanged. This change is unreleased.
Evidence
npm run checkon Node 24.19.0: 502/502 tests and package-content checks pass.inspect --check --openclawagainst unchanged OpenClaw69213b315cb3d21d73e2759db5c2a50194110eaband Kitchen Sink904b69fd2af89042f4db7bb5ef0ca0e882193fcd: zero records/four false P1 compat gaps becomes 37 direct records/zero compat gaps. All four relevant statuses areactive.b61d2d9c8750010a0a561bd3e2165eb170689ec5passes for the single Kitchen fixture, using the candidate source CLI. This is an inventory smoke; the packed CLI runs above prove target compatibility.5018c62b94f7c230aeccdbcf999770ae2219d3a6: Node 22.23.2, 502/502 tests, zero skips, and package-content checks pass. https://github.com/openclaw/plugin-inspector/actions/runs/34776867536