Skip to content

chore: adopt plugin-inspector 0.3.27 - #407

Closed
vincentkoc wants to merge 2 commits into
mainfrom
chore/plugin-inspector-0.3.27
Closed

vincentkoc wants to merge 2 commits into
mainfrom
chore/plugin-inspector-0.3.27

Conversation

@vincentkoc

@vincentkoc vincentkoc commented Oct 1, 2026 •

Copy link
Copy Markdown
Member

What Problem This Solves

Crabpot's source and package Inspector pins did not include the released 0.3.27 fixes.

User Impact

Crabpot now validates the same landed Plugin Inspector release in source and published-package modes.

Why This Change Was Made

Pins source mode to the exact landed release commit, adopts the published 0.3.27 package, updates both guards and operator documentation, and records the release in the changelog.

Related release: https://github.com/openclaw/plugin-inspector/releases/tag/v0.3.27

Evidence

  • Landed source: b8321a836f69f44e42d51945dedd252ec4114f35.
  • Published package: @openclaw/plugin-inspector@0.3.27.
  • Source-mode smoke: 59 fixtures, zero breakages, 59 logs.
  • Published-package smoke with a fresh npm cache: 59 fixtures, zero breakages, 59 logs.
  • Both smoke modes produced report SHA-256 1d26ec007cac2de00bc8b04dd83148b770eea826627fe3d3336f6d176b30fd8e.
  • Source/package pin guards: 8 tests passed.
  • Plugin Inspector published follow-through check passed the source ref, package pin, and public-API migration checks.
  • git diff --check passed.

Fixture Impact

  • Adds or updates fixture manifest entries
  • Updates submodule pins
  • Changes contract or smoke logic
  • Docs only

Source/package dependency pins, matching guard assertions, and release documentation only.

Fixture Verification

  • npm test
  • node scripts/sync-fixtures.mjs --check
  • node scripts/run-contract-smoke.mjs
  • Strict fixture smoke, if submodules were materialized

Notes

The 0.3.27 release was published through the protected GitHub OIDC workflow. No local publish or authentication changes were used.

@vincentkoc vincentkoc self-assigned this Oct 1, 2026
@clawsweeper

clawsweeper Bot commented Oct 1, 2026 •

Copy link
Copy Markdown
Contributor

🦞👀
ClawSweeper picked this up.

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

ClawSweeper review complete

ClawSweeper finished reviewing this revision. The review result is being finalized.

View the workflow run.

@clawsweeper clawsweeper Bot added P3 Low-risk cleanup, docs, polish, ergonomics, or speculative feature. rating: 🐚 platinum hermit Good normal PR readiness with ordinary maintainer review expected. status: 👀 ready for maintainer look ClawSweeper has no concrete contributor-facing blocker left for this PR. labels Oct 1, 2026
@clawsweeper

clawsweeper Bot commented Oct 1, 2026 •

Copy link
Copy Markdown
Contributor

Codex review: needs maintainer review before merge. Reviewed October 1, 2026, 4:50 AM ET / 08:50 UTC (Revision 2).

ClawSweeper review

What this changes

Updates Crabpot’s Plugin Inspector source and published-package pins to 0.3.27, with matching guard assertions and release documentation.

Merge readiness

✅ Ready for maintainer review

The publication follow-through resolves the earlier blocker, and no introduced defect was found. This adoption is still absent from main and remains useful.

Priority: P3
Reviewed head: c751235c8d9c9acc5fa7333d3a2c8f95f00af3b5

Review scores

Measure Result What it means
Overall readiness 🐚 platinum hermit (4/6) A focused release adoption with verified publication identity and recorded matching production smoke outcomes.
Proof confidence 🐚 platinum hermit (4/6) Sufficient (live_output): The captured maintainer follow-up ties the changed Inspector pins to exact-head source and fresh-cache package inspection of 59 fixtures, with zero breakages and identical report hashes. These runs address the prior release-adoption proof request; no stored-data contract changes are introduced.
Patch quality 🐚 platinum hermit (4/6) No actionable review findings were identified.

Verification

Check Result Evidence
Real behavior Verified Sufficient (live_output): The captured maintainer follow-up ties the changed Inspector pins to exact-head source and fresh-cache package inspection of 59 fixtures, with zero breakages and identical report hashes. These runs address the prior release-adoption proof request; no stored-data contract changes are introduced.
Evidence reviewed 7 items Introduced changes: The pinned introduction diff changes only two dependency constants, their corresponding test assertions, and three documentation files. The verified test merge has the exact main and head parents and produces the same five-file change.
Still necessary on main: Fetched main retains source e2f36f1cdf943826c37303e3632866e12eaf15ce and published package 0.3.26; it does not contain this release adoption.
Applicable policy and dependency boundary: The full root AGENTS.md requires coordinated source/package pins, expectations, and both smoke modes. No nested ancestor policy or matching maintainer notes were found. The source resolver directly imports Plugin Inspector and executes its CLI, establishing the dependency contract.
Findings None None.
Security None None.

How this fits together

Crabpot feeds configured community-plugin fixtures into Plugin Inspector to check compatibility with OpenClaw. Inspector results become reports and CI findings.

flowchart TD
 A[Fixture configuration] --> B[Crabpot inspection]
 C[Inspector release pins] --> D[Source or published package]
 D --> B
 B --> E[Compatibility checks]
 E --> F[Reports and CI findings]
Loading

Before merge

None.

Agent review details

Security

None.

Review metrics

Metric Value Why it matters
Release smoke coverage 2 modes × 59 fixtures; 0 breakages The maintainer records matching report hashes for source and freshly fetched published-package inspection.

Technical review

Best possible solution:

Keep source and published-package inspection aligned on the verified 0.3.27 release with matching fixture outcomes.

Do we have a high-confidence way to reproduce the issue?

Not applicable: this is release adoption rather than a bug report; the captured follow-up records both production inspection modes against the fixture inventory.

Is this the best way to solve the issue?

Yes: updating the existing shared pins and their guards is the narrowest supported adoption path, and the package metadata matches the tagged source.

AGENTS.md: found and applied where relevant.

Codex review notes: model internal, reasoning medium; reviewed against 4ff73eb1397d.

Labels

Label changes:

  • add proof: sufficient: Contributor real behavior proof is sufficient. The captured maintainer follow-up ties the changed Inspector pins to exact-head source and fresh-cache package inspection of 59 fixtures, with zero breakages and identical report hashes. These runs address the prior release-adoption proof request; no stored-data contract changes are introduced.

Label justifications:

  • P3: This is bounded dependency-release maintenance with matching smoke outcomes and no demonstrated urgent user regression.
  • rating: 🐚 platinum hermit: Overall readiness is 🐚 platinum hermit; proof is 🐚 platinum hermit and patch quality is 🐚 platinum hermit.
  • status: 👀 ready for maintainer look: ClawSweeper has no concrete contributor-facing blocker left for this PR. Sufficient (live_output): The captured maintainer follow-up ties the changed Inspector pins to exact-head source and fresh-cache package inspection of 59 fixtures, with zero breakages and identical report hashes. These runs address the prior release-adoption proof request; no stored-data contract changes are introduced.
  • proof: sufficient: Contributor real behavior proof is sufficient. The captured maintainer follow-up ties the changed Inspector pins to exact-head source and fresh-cache package inspection of 59 fixtures, with zero breakages and identical report hashes. These runs address the prior release-adoption proof request; no stored-data contract changes are introduced.

Evidence

What I checked:

  • Introduced changes: The pinned introduction diff changes only two dependency constants, their corresponding test assertions, and three documentation files. The verified test merge has the exact main and head parents and produces the same five-file change. (scripts/plugin-inspector-source.mjs:7, c751235c8d9c)
  • Still necessary on main: Fetched main retains source e2f36f1cdf943826c37303e3632866e12eaf15ce and published package 0.3.26; it does not contain this release adoption. (scripts/plugin-inspector-source.mjs:7, 4ff73eb1397d)
  • Applicable policy and dependency boundary: The full root AGENTS.md requires coordinated source/package pins, expectations, and both smoke modes. No nested ancestor policy or matching maintainer notes were found. The source resolver directly imports Plugin Inspector and executes its CLI, establishing the dependency contract. (scripts/plugin-inspector-source.mjs:14, c751235c8d9c)
  • Released source identity: GitHub’s annotated v0.3.27 tag resolves to b8321a836f69f44e42d51945dedd252ec4114f35, exactly matching the new source pin. The release was published at 2026-10-01T08:44:43Z. (b8321a836f69)
  • Published package and supply-chain metadata: The npm registry exposes @openclaw/plugin-inspector 0.3.27 with gitHead matching the pinned release commit, the expected repository, integrity metadata, and a provenance-attestation URL. Package scripts contain no install lifecycle hook; signatures and attestations were not independently cryptographically verified. (package.json, b8321a836f69)
  • Earlier blocker resolved: The captured MEMBER-authored follow-up at chore: adopt plugin-inspector 0.3.27 #407 (comment) records exact-head source and fresh-cache published-package smoke runs: each inspected 59 fixtures with zero breakages and 59 logs, producing identical report SHA-256 1d26ec007cac2de00bc8b04dd83148b770eea826627fe3d3336f6d176b30fd8e. It also records eight passing pin guards and successful published follow-through checks. This addresses the retained prior rank-up request. (c751235c8d9c)

Likely related people:

  • vincentkoc: Suggested for follow-up; no historical authorship or introduction is verified. (role: unverified routing candidate; confidence: low)
  • RomneyDa: Suggested for follow-up; no historical authorship or introduction is verified. (role: unverified routing candidate; confidence: low)

Rating scale

Score Internal tier Crab rank Meaning
6/6 S 🦀 challenger crab Exceptional readiness
5/6 A 🦞 diamond lobster Very strong readiness
4/6 B 🐚 platinum hermit Good normal PR; ordinary maintainer review
3/6 C 🦐 gold shrimp Useful, but confidence is limited
2/6 D 🦪 silver shellfish Proof or implementation needs work
1/6 F 🧂 unranked krab Not merge-ready
N/A NA 🌊 off-meta tidepool Rating does not apply

Overall follows the weaker of proof and patch quality.
Shiny media proof means a screenshot, video, or linked artifact directly shows the changed behavior. Runtime, network, CSP, and security claims still need visible diagnostics.

Workflow

  • ClawSweeper keeps one durable marker-backed review comment per issue or PR.
  • Re-runs edit this comment so the latest verdict, findings, and automation markers stay together instead of adding duplicate bot comments.
  • A fresh review can be triggered by eligible @clawsweeper re-review comments, exact-item GitHub events, scheduled/background review runs, or manual workflow dispatch.
  • PR/issue authors and users with repository write access can comment @clawsweeper re-review or @clawsweeper re-run on an open PR or issue to request a fresh review only.
  • Maintainers can also comment @clawsweeper review to request a fresh review only.
  • Fresh-review commands do not start repair, autofix, rebase, CI repair, or automerge.
  • Maintainer-only repair and merge flows require explicit commands such as @clawsweeper autofix, @clawsweeper automerge, @clawsweeper fix ci, or @clawsweeper address review.
  • Maintainers can comment @clawsweeper explain to ask for more context, or @clawsweeper stop to stop active automation.

History

Review history (1 earlier review cycle)
  • reviewed 2026-10-01T08:42:12.902Z sha c2c4620 :: blocked before merge. :: none

@vincentkoc vincentkoc changed the title chore: stage plugin-inspector 0.3.27 candidate chore: adopt plugin-inspector 0.3.27 Oct 1, 2026
@vincentkoc

Copy link
Copy Markdown
Member Author

@clawsweeper re-review

The publication follow-through is complete on exact head c751235c8d9c9acc5fa7333d3a2c8f95f00af3b5:

  • landed Plugin Inspector source: b8321a836f69f44e42d51945dedd252ec4114f35
  • published package: @openclaw/plugin-inspector@0.3.27
  • source smoke: 59 fixtures, zero breakages, 59 logs
  • fresh-cache package smoke: 59 fixtures, zero breakages, 59 logs
  • identical report SHA-256: 1d26ec007cac2de00bc8b04dd83148b770eea826627fe3d3336f6d176b30fd8e
  • 8 pin-guard tests passed
  • published follow-through checker passed source ref, package pin, and public API migration

@clawsweeper

clawsweeper Bot commented Oct 1, 2026 •

Copy link
Copy Markdown
Contributor

🦞👀
Exact review queued.

Re-review progress:

@clawsweeper clawsweeper Bot added the proof: sufficient Contributor real behavior proof is sufficient. label Oct 1, 2026
@steipete

Copy link
Copy Markdown
Contributor

Main now adopts the published Plugin Inspector 0.4.0 package and matching source at 943148854bf51b1e6cfa5d8b12047cfec8642297 via #478 (c41d256), with source, packed, and published-package smoke coverage. This older pin update is superseded. Thank you for preparing it.

@steipete steipete closed this Oct 15, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

P3 Low-risk cleanup, docs, polish, ergonomics, or speculative feature. proof: sufficient Contributor real behavior proof is sufficient. rating: 🐚 platinum hermit Good normal PR readiness with ordinary maintainer review expected. status: 👀 ready for maintainer look ClawSweeper has no concrete contributor-facing blocker left for this PR.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants