Repository navigation
fix(fixtures): refresh eight official plugins to 2026.10.1 - #461
Conversation
Preserve the current Dependabot package locks and pair each fallback artifact with its published source provenance. Keep the frozen host, moving plugin tracks, Inspector source and compatibility policy unchanged. Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
|
ClawSweeper reviews are opt-in for maintainers. If a review is required, finish the work and validation first, then comment |
|
@clawsweeper re-review Please review exact head This incorporates eight current 2026.10.1 Dependabot snapshots with exact original lockfiles and corrected published source Exact-eight artifact qualification at carrier Coverage is deliberately limited: three metadata observations and three Voice Call tool-factory descriptor returns passed. Channel runtime, service lifecycle, CLI, configured provider calls and stored-config migration execution are not established. All eight declare plugin API >=2026.10.1, outside the frozen 2026.9.6 host range. The observed missing Twitch Qualification static/branch-cleanup and normal exact-head CI are still pending. This review request does not waive their terminal gates. No releases or original-PR closures are authorized by this comment. |
|
🦞👀 Re-review progress:
|
|
Codex review: needs maintainer review before merge. What this changesThis PR updates eight official plugin fallback packages to 2026.10.1 and aligns their source references with published provenance. Example: The moving npm tag cannot resolve for the voice-call fixture.
Review scores
ProductKind: Maintenance · Worth it: Yes · Fix scope: Complete Merge readiness✅ Ready for maintainer review Keep this PR open: the maintainer-authorized refresh is absent from main, and the pinned patch has no actionable findings. Required CI remains in progress. Priority: P3 Before mergeNone. FindingsNone. Tests
Agent review detailsHow this fits togetherCrabpot selects configured plugin artifacts, inspects their contracts against a pinned OpenClaw host, and produces compatibility reports with upstream source links. flowchart LR
A[Fixture manifest] --> C[Package selection]
B[Fallback shims and locks] --> C
C --> D[Published plugin artifacts]
D --> E[Contract inspection]
F[Frozen OpenClaw host] --> E
E --> G[Compatibility reports]
Technical reviewBest possible solution: Land the coherent fixture and provenance refresh after required gates finish, retaining the documented host limitations. Do we have a high-confidence way to reproduce the issue? This is fixture maintenance; source inspection establishes the changed fallback selection and attribution path without executing target code. Is this the best way to solve the issue? Updating each package pin together with both provenance references preserves the existing reporting contract and avoids changing host or Inspector policy. AGENTS.md: found and applied where relevant. Codex review notes: model internal, reasoning medium; reviewed against 2e68740ff8e4. Provenance checked
TestingProof path: in-process harness. SecurityNone. EvidenceWhat I checked:
Likely related people:
Root-cause clusterRelationship: Members:
Proposal only: this assessment does not dispatch repair, suppress jobs, mutate sibling items, close, or merge anything. LabelsLabel changes:
Label justifications:
Rating scale6/6 🦀 challenger crab · 5/6 🦞 diamond lobster · 4/6 🐚 platinum hermit · 3/6 🦐 gold shrimp · 2/6 🦪 silver shellfish · 1/6 🧂 unranked krab. Overall follows the weaker of proof and patch quality; ✨ marks media proof (a screenshot, video, or linked artifact) that directly shows the changed behavior. WorkflowClawSweeper edits this one comment on every review. Comment Reviewed October 14, 2026, 5:43 AM ET / 09:43 UTC. |
|
Post-merge closure proposal — 21 original PRs, no closures performed. The three canonical replacements are merged, preserve Dependabot credit, and passed their exact-head required checks and reviews:
Live post-merge checks found all 22 inspected originals still open, with no automatic Dependabot closures. Comparing each current package manifest and lockfile against the landed tree gives 20 byte-identical lockfiles and one semantic replacement (Tlon). The 20 package manifests select the same direct package/version; their remaining difference is the repaired source-provenance metadata. Shared fixture/provenance changes were reviewed together; stale generated-report drift was excluded.
Tlon is not byte-identical. Current 448 retains the same Excluded: 449 at This proposal does not include the six input-safety-held PRs or other unresolved dependency updates. The documented host/API limitations and inherited audit findings from the merged cohorts remain; these are fixture updates, not a claim that every plugin is compatible with the frozen host. No release, tag, package publication or deployment occurred. All 21 proposed manual closures remain pending one explicit bounded-scope approval. Recheck their heads/states immediately before any authorized closure and stop if the incorporated target changed. |
What Problem This Solves
Eight official plugin Dependabot PRs advanced to 2026.10.1 while the preceding cohort retained their older 2026.9.9 snapshots. This PR incorporates the current package locks and correct published-source references together.
User Impact
The eight fallback npm pins move to 2026.10.1. The promoted OpenClaw host remains
10bb24270d8dad0f85781980248c5ba9a1d5cd71(2026.9.6), and the normal moving-plugin tracks remain unchanged.Why This Change Was Made
The shared fixture manifest and provenance fields make one coherent update appropriate. All eight lockfiles match the frozen original PR heads; stale generated reports from the conflicted Twitch and Zalo PRs are excluded. Both source-reference fields point to the published build source
9cf7fc279c26cf3493b75e703aeadac6d0deb5ee. Inspector source remainsb56782860cbef840e8892f18f58c0c3a38c02dd6; the published CLI remains 0.3.26. Credit: @dependabot.All eight published artifacts declare OpenClaw/plugin API >=2026.10.1, outside the frozen host's declared range. Twitch uses
raceWithTimeout, Zalo usescreateChannelSecretContract, and Voice Call usesresolvePluginServiceSchedulerplus service API v2/ctx.scheduler; those contracts are absent from this frozen host. Capture results must not be read as real-host runtime compatibility. No host promotion, mock extension or policy relaxation is included.Tlon's original lock refresh includes AWS transitive changes, including token-providers 3.1138.0 to 3.1149.0. Voice Call removes its direct ws dependency. The published Zalouser session-state chunk remains on openKeyedStore; a different checkout-only V2 implementation is not attributed to this artifact.
Evidence
10bb24270d8dad0f85781980248c5ba9a1d5cd71with Inspector sourceb56782860cbef840e8892f18f58c0c3a38c02dd6. Executor and independent reviewer checked all 32 handoff hashes, 20 capture artifacts containing 23 registrations, and 20 synthetic artifacts: six passed probes, zero failures, 19 explicit blocks. Every profile step exited zero without error or timeout.Fixture Impact
Fixture Verification
npm testnode scripts/sync-fixtures.mjs --checknode scripts/run-contract-smoke.mjsNotes
Original PRs remain open until a merged replacement and fresh equivalence verification:
Existing prerequisite blocks and actual failures remain visible. No credentials, live-provider actions, release, package publication or deployment is requested.