Skip to content

fix(fixtures): refresh eight official plugins to 2026.10.1 - #461

Merged
vincentkoc merged 1 commit into
mainfrom
fix/crabpot-official-2026-10-1-cohort-20261014
Oct 14, 2026
Merged

vincentkoc merged 1 commit into
mainfrom
fix/crabpot-official-2026-10-1-cohort-20261014

Conversation

@vincentkoc

@vincentkoc vincentkoc commented Oct 14, 2026 •

Copy link
Copy Markdown
Member

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 remains b56782860cbef840e8892f18f58c0c3a38c02dd6; 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 uses createChannelSecretContract, and Voice Call uses resolvePluginServiceScheduler plus 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

  • 47 focused manifest and provenance tests passed.
  • Astra/high P1 source review found no actionable findings; this is source review, not runtime qualification.
  • Exact eight-artifact qualification ran all eight published 2026.10.1 artifacts against frozen host 10bb24270d8dad0f85781980248c5ba9a1d5cd71 with Inspector source b56782860cbef840e8892f18f58c0c3a38c02dd6. 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.
  • The six successful probes are three metadata observations and three Voice Call tool-factory descriptor returns. Channel runtime, service lifecycle, CLI, configured provider calls and stored-config migration execution remain unqualified. The three frozen-host API gaps above remain real limitations even though mock capture succeeds.
  • Six dependency audit artifacts report zero findings; Brave and diagnostics have no external dependency tree and emit no audit artifact. This does not claim that every dependency in the repository is audit-clean.
  • The qualification static lane passed (792 tests: 776 passed, zero failed, 16 skipped), and the exact temporary branch was deleted successfully with its absence verified. Fresh normal CI passed on the exact production head, including all four static platforms, eight isolated fixtures and the real fixture-lock audit. Windows completed 792 tests (764 passed, zero failed, 28 skipped). The full current-head review has no findings, pre-merge requests or remaining rank-up moves. The optional Windows HEAD canary remains pending; it is separate from the required frozen-host checks.

Fixture Impact

  • Adds or updates fixture manifest entries
  • Updates submodule pins
  • Changes contract or smoke logic
  • Docs 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

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.

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

clawsweeper Bot commented Oct 14, 2026

Copy link
Copy Markdown
Contributor

ClawSweeper reviews are opt-in for maintainers. If a review is required, finish the work and validation first, then comment @clawsweeper review. Please avoid repeated requests while a review is queued or running; agents should not request reviews automatically.

@vincentkoc

Copy link
Copy Markdown
Member Author

@clawsweeper re-review

Please review exact head 311eb97da1c5027f7c6788d0289fe529619168b5.

This incorporates eight current 2026.10.1 Dependabot snapshots with exact original lockfiles and corrected published source 9cf7fc279c26cf3493b75e703aeadac6d0deb5ee. Independent source review and Astra/high P1 review found no actionable findings; 47 focused manifest/provenance tests passed.

Exact-eight artifact qualification at carrier d2d45e1377452b5ad1c4015261a1cb392edea490 used those eight versions, frozen host 10bb24270d8dad0f85781980248c5ba9a1d5cd71, and unchanged Inspector b56782860cbef840e8892f18f58c0c3a38c02dd6. Executor and independent reviewer checked all 32 handoff hashes and raw outputs: 20 captures, 23 registrations, 20 synthetic artifacts, six passed probes, zero failures and 19 explicit blocks. Six actual dependency audits reported zero findings; Brave and diagnostics have no external dependency tree/audit artifact.

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 raceWithTimeout, Zalo createChannelSecretContract, and Voice Call scheduler/service-v2 contracts remain explicit real-host limitations. No host promotion, mock expansion or policy waiver is requested.

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.

@clawsweeper

clawsweeper Bot commented Oct 14, 2026 •

Copy link
Copy Markdown
Contributor

🦞👀
Exact review queued.

Re-review progress:

@clawsweeper clawsweeper Bot added P3 Low-risk cleanup, docs, polish, ergonomics, or speculative feature. merge-risk: 🚨 compatibility 🚨 Merging this PR could break existing users, config, migrations, defaults, or upgrades. rating: 🦐 gold shrimp Decent PR readiness signal, but merge confidence is limited. status: 👀 ready for maintainer look ClawSweeper has no concrete contributor-facing blocker left for this PR. labels Oct 14, 2026
@clawsweeper

clawsweeper Bot commented Oct 14, 2026

Copy link
Copy Markdown
Contributor

Codex review: needs maintainer review before merge.

What this changes

This 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.

  • Before: Crabpot falls back to @openclaw/voice-call 2026.9.9.
  • After: Crabpot falls back to 2026.10.1 and attributes it to source commit 9cf7fc279c26cf3493b75e703aeadac6d0deb5ee.

Review scores

Measure Result What it means
Overall readiness 🦐 gold shrimp (3/6) The focused patch is coherent and source-verified; available validation is deliberately limited to fixture inspection and synthetic qualification.
Proof confidence 🦐 gold shrimp (3/6) This maintainer-authored fixture refresh is outside the ordinary contributor proof gate; the exact-artifact qualification exercises Inspector capture and synthetic probes, not real-host runtime compatibility, and raw artifact downloads were blocked by reviewer infrastructure.
Patch quality 🐚 platinum hermit (4/6) No actionable review findings were identified.

Product

Kind: Maintenance · Worth it: Yes · Fix scope: Complete
User problem: Fallback fixture versions lag the selected published plugins, and advancing versions alone would leave misleading upstream source links.
Reason: The maintainer authorizes this coherent refresh and explicitly records the narrower inspection purpose and accepted host mismatch.

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
Reviewed head: 311eb97da1c5027f7c6788d0289fe529619168b5

Before merge

None.

Findings

None.

Tests

  • Missing end-to-end proof: The supplied qualification does not establish channel runtime, service lifecycle, configured provider calls, or stored-config migration on a supported real host.
Agent review details

How this fits together

Crabpot 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]
Loading

Technical review

Best 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

  • Fallback versions and paired source references changes intended behavior with a stated reason (2e68740: The preceding merged cohort deliberately preserved 2026.9.9 snapshots and left newer 2026.10.1 proposals for separate review.)
  • Version-qualified report attribution keeps the original intent (3840012: Prevent moving npm artifacts from borrowing source references belonging to different fallback versions.)
  • Fixture dependency locks and security overrides keeps the original intent (61be4f5: Keep fixture locks aligned with selected packages while retaining compatible security overrides.)

Testing

Proof path: in-process harness.

Security

None.

Evidence

What I checked:

Likely related people:

  • Peter Steinberger: Raw commit 61be4f5 adds plugins/voice-call/package.json:18 relative to its recorded parents. This identifies author metadata, not feature responsibility or a PR merger. (role: source-line author; confidence: high; commits: 61be4f5165d2; files: plugins/voice-call/package.json)

Root-cause cluster

Relationship: canonical
Canonical: #461
Summary: This PR consolidates the eight existing update proposals and repairs their paired source attribution; original proposals remain open pending a merged replacement.

Members:

Proposal only: this assessment does not dispatch repair, suppress jobs, mutate sibling items, close, or merge anything.

Labels

Label changes:

  • add P3: This is bounded fixture maintenance without an established urgent user-facing regression.
  • add merge-risk: 🚨 compatibility: The fallback artifacts require a newer host API than the frozen host provides; the maintainer explicitly accepts retaining that limitation for compatibility inspection.
  • add rating: 🦐 gold shrimp: Overall readiness is 🦐 gold shrimp; proof is 🦐 gold shrimp and patch quality is 🐚 platinum hermit.
  • add status: 👀 ready for maintainer look: ClawSweeper has no concrete contributor-facing blocker left for this PR.

Label justifications:

  • P3: This is bounded fixture maintenance without an established urgent user-facing regression.
  • merge-risk: 🚨 compatibility: The fallback artifacts require a newer host API than the frozen host provides; the maintainer explicitly accepts retaining that limitation for compatibility inspection.
  • rating: 🦐 gold shrimp: Overall readiness is 🦐 gold shrimp; proof is 🦐 gold shrimp and patch quality is 🐚 platinum hermit.
  • status: 👀 ready for maintainer look: ClawSweeper has no concrete contributor-facing blocker left for this PR.

Rating scale

6/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.

Workflow

ClawSweeper edits this one comment on every review. Comment @clawsweeper re-review for a fresh review only. Repair and merge execution lanes are retired.

Reviewed October 14, 2026, 5:43 AM ET / 09:43 UTC.

@vincentkoc
vincentkoc merged commit f0a68ce into main Oct 14, 2026
34 checks passed
@vincentkoc
vincentkoc deleted the fix/crabpot-official-2026-10-1-cohort-20261014 branch October 14, 2026 09:53
@vincentkoc

Copy link
Copy Markdown
Member Author

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.

Original Fixture Inspected current head Landed replacement Evidence
375 diagnostics-otel 64e59e2bec01 401 Exact
389 mattermost 04a76c17401f 401 Exact
396 whatsapp de4318c01322 401 Exact
457 lobster bb212ea88d7c 460 Exact
455 matrix 00331e024edc 460 Exact
453 google-meet dc5ad534adf0 460 Exact
444 nextcloud-talk 7f15ba0b1fbf 460 Exact
442 memory-lancedb 1f4ef19e7a77 460 Exact
440 codex 60bc1ec13512 460 Exact
428 nostr e8ae4d54e86a 460 Exact
426 diffs 779b5b5c56b6 460 Exact
420 synology-chat 8824e6a814f1 460 Exact
408 discord 339f1f8677ad 460 Exact
456 msteams 23e2dffae3a5 461 Exact
452 diagnostics-prometheus 31a34e5ea1e8 461 Exact
451 brave-plugin 202cce8f108f 461 Exact
450 twitch bd4fc177778c 461 Exact
448 tlon bc9a9b7dd6c7 461 Semantic
447 zalouser 9f8243b47d4b 461 Exact
446 zalo 6fc81e5f4e3b 461 Exact
445 voice-call 31ea39af80b5 461 Exact

Tlon is not byte-identical. Current 448 retains the same @openclaw/tlon@2026.10.1 artifact and root lock entry, but has 15 older transitive resolutions (14 AWS packages and Smithy core) than the qualified landed lock. Examples: core 3.978.1 versus landed 3.978.2, token-providers 3.1138.0 versus 3.1149.0, Smithy core 3.35.1 versus 3.35.2. There are no added/removed packages or changed top-level lock fields. Its source reference is stale; the landed reference is the verified 9cf7fc build. Its README and 16 generated-report changes are not new package work. The selected target is incorporated with the qualified newer resolutions; this supports semantic supersession, not a claim of identical locks.

Excluded: 449 at 193350ea4a579309b9c91193535d12b915f38074. It advanced after the freeze to Feishu 2026.10.1 while the landed snapshot is 2026.9.9. Its actual package/lock changes include the new artifact and fs-safe 0.21.1 to 0.24.2 with platform packages. This newer target has not received the exact-artifact qualification required here; keep it open. The earlier 9.9 qualification does not cover it.

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.

This was referenced Oct 14, 2026
This was referenced Oct 14, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

merge-risk: 🚨 compatibility 🚨 Merging this PR could break existing users, config, migrations, defaults, or upgrades. P3 Low-risk cleanup, docs, polish, ergonomics, or speculative feature. rating: 🦐 gold shrimp Decent PR readiness signal, but merge confidence is limited. 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.

1 participant