Skip to content

fix: stop false compat gaps for split OpenClaw registries - #78

Merged
vincentkoc merged 1 commit into
mainfrom
fix/inspector-split-compat-registry
Sep 13, 2026
Merged

vincentkoc merged 1 commit into
mainfrom
fix/inspector-split-compat-registry

Conversation

@vincentkoc

@vincentkoc vincentkoc commented Sep 13, 2026 •

Copy link
Copy Markdown
Member

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_RECORDS from ./registry-records.js into the fixed sibling registry-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

  • Original production fails the new split-registry/path and missing-delegated-file regressions; focused reader/report tests pass after the fix: 48/48.
  • npm run check on Node 24.19.0: 502/502 tests and package-content checks pass.
  • Packed CLI before/after, using inspect --check --openclaw against unchanged OpenClaw 69213b315cb3d21d73e2759db5c2a50194110eab and Kitchen Sink 904b69fd2af89042f4db7bb5ef0ca0e882193fcd: zero records/four false P1 compat gaps becomes 37 direct records/zero compat gaps. All four relevant statuses are active.
  • Four separate Inspector coverage-gap findings remain; they are not silently suppressed by this repair.
  • Maintained Crabpot source-mode smoke at b61d2d9c8750010a0a561bd3e2165eb170689ec5 passes for the single Kitchen fixture, using the candidate source CLI. This is an inventory smoke; the packed CLI runs above prove target compatibility.
  • Fresh independent P2 autoreview: scoped-clean, no findings.
  • Exact-head CI for 5018c62b94f7c230aeccdbcf999770ae2219d3a6: Node 22.23.2, 502/502 tests, zero skips, and package-content checks pass. https://github.com/openclaw/plugin-inspector/actions/runs/34776867536

@clawsweeper

clawsweeper Bot commented Sep 13, 2026

Copy link
Copy Markdown

🦞👀
ClawSweeper picked this up.

Pull request received. I will update this pull request when review starts.

@vincentkoc
vincentkoc marked this pull request as ready for review September 13, 2026 19:12
@vincentkoc
vincentkoc requested a review from a team as a code owner September 13, 2026 19:12
@vincentkoc
vincentkoc merged commit f837579 into main Sep 13, 2026
8 checks passed
@vincentkoc
vincentkoc deleted the fix/inspector-split-compat-registry branch September 13, 2026 19:12
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