chore(deps): bump plugins/hyperspell from 056dcd9 to f994920

[dependabot]

Bumps plugins/hyperspell from 056dcd9 to f994920.

Commits

• f994920 chore: release 0.21.0
• bb97447 feat(coverage): zero-result coverage log, local JSONL, opt-in — Sounding (#102)
• f6fc7bf feat(audit): mood-retrieval skew audit instrument — Tinted Lens (#95)
• e978eb6 feat(auto-context): adaptive highlight budget — Spotlight (#93)
• bdd708e feat(ranking): opt-in elbow cutoff at natural score cliffs — Waterline (#91)
• 5277093 feat(ranking): near-duplicate diversity check in selection — Chorus (#89)
• bd8f33b feat(ranking): per-source weighting on base relevance — Counterweight (#88)
• f2dc78b feat(ranking): bounded recency decay in the composite score — Hourglass (#86)
• 88b9a6d chore: release 0.20.0
• 17d866d fix(logging): operator diagnostics via info-level log.diag — visible in gatew...
• Additional commits viewable in compare view

You can trigger a rebase of this PR by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

Note
Automatic rebases have been disabled on this pull request as it has been open for over 30 days.

[clawsweeper]

Codex review: needs maintainer review before merge. Reviewed August 27, 2026, 10:50 PM ET / August 28, 2026, 02:50 UTC.

ClawSweeper review

What this changes

This PR advances the Hyperspell fixture submodule to release 0.21.0 and refreshes Crabpot’s generated compatibility reports.

Merge readiness

⚠️ Ready for maintainer review - 3 items remain

Keep this PR open for a maintainer decision: current main still uses the older Hyperspell fixture ref, while this branch is conflict-dirty and its July compatibility snapshot is no longer current. A repository participant requested that Dependabot close it, but the supplied association does not establish authority for an automatic close.

Priority: P3
Reviewed head: 849551afef76329bb5696914b871b10944c1cb8a
Owner decision: Required. See Decision needed.

Review scores

Measure	Result	What it means
Overall readiness	🦐 gold shrimp (3/6)	The fixture update is coherent, but the dirty branch and stale dynamic-track evidence leave it short of merge-ready confidence.
Proof confidence	🌊 off-meta tidepool	Not applicable: Not applicable: this Dependabot PR is exempt from the external-contributor proof gate; its historical generated reports still need replacement before a re-created branch can be accepted.
Patch quality	🦐 gold shrimp (3/6)	No actionable review findings were identified.

Verification

Check	Result	Evidence
Real behavior	Not applicable	Not applicable: Not applicable: this Dependabot PR is exempt from the external-contributor proof gate; its historical generated reports still need replacement before a re-created branch can be accepted.
Evidence reviewed	7 items	Requested ref is not on current main: Current main still records the prior Hyperspell submodule revision 056dcd9, so the central dependency update has not already landed. PR-introduced fixture update: The reviewed head changes the fixture gitlink from 056dcd9 to f994920. Historical report target: The refreshed report identifies OpenClaw 2026.7.1 at 2d2ddc43 and was generated on 2026-07-14, so it is not current compatibility evidence for a re-created branch.
Findings	None	None.
Security	None	None.

How this fits together

Crabpot pins external plugin fixtures and scans them against selected OpenClaw tracks. The inspector produces committed reports that feed the repository dashboard and compatibility review.

flowchart LR
  A[Plugin fixture source] --> B[Fixture pin]
  B --> C[Plugin inspector]
  D[OpenClaw Default Track] --> C
  C --> E[Generated compatibility reports]
  E --> F[Dashboard and CI review]

Loading

Decision needed

Question	Recommendation
Should this stale, conflict-dirty Dependabot branch be closed as requested in discussion, or should its Hyperspell update be recreated against current main?	Close and await a fresh update: Honor the existing close request and let Dependabot propose a current Hyperspell revision from current main.

Why: Current main has not adopted the requested fixture ref, while the branch no longer supplies current compatibility evidence; choosing whether to retain the update is repository policy rather than a mechanical repair.

Before merge

• Resolve merge risk (P1) - The branch is dirty against main; resolving its generated-report conflicts without re-running the dynamic Default Track would publish stale compatibility evidence.
• Complete next step (P2) - A maintainer must decide whether to honor the existing close request or retain the update by recreating it from current main; no safe automated repair should choose that policy.

Agent review details

Security

None.

Review metrics

Metric	Value	Why it matters
Changed surface	19 files; +1,022 / -1,127 lines	One fixture gitlink and mostly generated reports make a current rerun more meaningful than hand-resolving the stale branch.

Merge-risk options

Maintainer options:

1. Decide the mitigation before merge
   Keep a fresh Hyperspell fixture ref with reports regenerated against the current Default Track and validate it through the required source-mode and package-mode smoke checks.
2. Pause or close
   Do not merge this PR until maintainers decide whether the risk is worth taking.

Technical review

Best possible solution:

Keep a fresh Hyperspell fixture ref with reports regenerated against the current Default Track and validate it through the required source-mode and package-mode smoke checks.

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

Not applicable: this is a fixture dependency and generated-report update, not a reported product failure.

Is this the best way to solve the issue?

No: the exact branch is not landing-ready because it is conflict-dirty and carries a historical dynamic-track snapshot; it should be closed or recreated from current main.

AGENTS.md: found and applied where relevant.

Codex review notes: model internal, reasoning high; reviewed against b03503877def.

Labels

Label changes:

• add status: 👀 ready for maintainer look: ClawSweeper has no concrete contributor-facing blocker left for this PR. Not applicable: Not applicable: this Dependabot PR is exempt from the external-contributor proof gate; its historical generated reports still need replacement before a re-created branch can be accepted.
• remove status: ⏳ waiting on author: Current PR status label is status: 👀 ready for maintainer look.
• remove merge-risk: 🚨 compatibility: Current PR review selected no merge-risk labels.
• remove proof: sufficient: Current real behavior proof status is not_applicable, not sufficient.

Label justifications:

• P3: This is a routine fixture dependency update awaiting a maintainer choice, not a user-facing regression.
• rating: 🦐 gold shrimp: Overall readiness is 🦐 gold shrimp; proof is 🌊 off-meta tidepool and patch quality is 🦐 gold shrimp.
• status: 👀 ready for maintainer look: ClawSweeper has no concrete contributor-facing blocker left for this PR. Not applicable: Not applicable: this Dependabot PR is exempt from the external-contributor proof gate; its historical generated reports still need replacement before a re-created branch can be accepted.

Evidence

What I checked:

• Requested ref is not on current main: Current main still records the prior Hyperspell submodule revision 056dcd9, so the central dependency update has not already landed. (plugins/hyperspell:1, b03503877def)
• PR-introduced fixture update: The reviewed head changes the fixture gitlink from 056dcd9 to f994920. (plugins/hyperspell:1, 849551afef76)
• Historical report target: The refreshed report identifies OpenClaw 2026.7.1 at 2d2ddc43 and was generated on 2026-07-14, so it is not current compatibility evidence for a re-created branch. (reports/crabpot-dashboard-data.json:3, 849551afef76)
• Track behavior: The default branch resolves the latest OpenClaw npm dist-tag dynamically; a report refresh must therefore run against the then-current resolved target. (scripts/resolve-openclaw-track.mjs:94, 849551afef76)
• Repository policy: Repository guidance requires package-version changes to update the source ref and generated expectations, with source-mode and package-mode smoke checks after publish. (AGENTS.md:13, 849551afef76)
• Track-maintenance provenance: Recent main history includes a dedicated Default Track promotion, showing this CI/report surface has continued to evolve after the branch snapshot. (.github/workflows/check.yml:1, 4f1be46609f0)

Likely related people:

• Vincent Koc: Recent commits maintain the verified OpenClaw default pin and isolate Default Track cache behavior. (role: recent track and CI contributor; confidence: high; commits: 4f1be46609f0, 08b3d31ba732; files: .github/workflows/check.yml, scripts/resolve-openclaw-track.mjs)
• Peter Steinberger: History records a direct plugin-fixture refresh and several adjacent dashboard/CI changes. (role: recent fixture updater; confidence: medium; commits: b7a09d7dd2ba, 3c7ddf3e3b56; files: plugins/hyperspell, README.md)

Rank-up moves

Optional improvements that raise the rating; they are not merge blockers.

• Either close the outdated Dependabot branch or recreate it from current main and regenerate the compatibility reports.
• Run the repository-required source-mode and package-mode smoke checks for the refreshed fixture.

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 (64 earlier review cycles; latest 8 shown)

• reviewed 2026-08-09T15:53:53.431Z sha 849551a :: found issues before merge. :: [P1] Regenerate reports against the pinned Default Track
• reviewed 2026-08-09T17:34:27.664Z sha 849551a :: found issues before merge. :: [P1] Regenerate reports against the pinned Default Track
• reviewed 2026-08-09T19:32:20.979Z sha 849551a :: found issues before merge. :: [P1] Regenerate reports against the current Default Track
• reviewed 2026-08-09T21:01:58.754Z sha 849551a :: found issues before merge. :: [P1] Regenerate reports against the current Default Track
• reviewed 2026-08-09T22:13:31.800Z sha 849551a :: found issues before merge. :: [P1] Regenerate reports against the current Default Track
• reviewed 2026-08-11T05:15:51.688Z sha 849551a :: found issues before merge. :: [P1] Regenerate reports against the current Default Track
• reviewed 2026-08-11T11:10:13.200Z sha 849551a :: found issues before merge. :: [P1] Regenerate reports against the current Default Track
• reviewed 2026-08-21T13:51:18.710Z sha 849551a :: found issues before merge. :: [P1] Regenerate reports against the current Default Track

[dependabot]

A newer version of plugins/hyperspell exists, but since this PR has been edited by someone other than Dependabot I haven't updated it. You'll get a PR for the updated version as normal once this PR is merged.

[steipete]

@dependabot close