chore(main): release engine-and-dependents libraries

[JSONbored]

🤖 I have created a release beep boop

contract: 3.21.1

3.21.1 (2026-07-31)

Chores

• contract: Synchronize engine-and-dependents versions

engine: 3.21.1

3.21.1 (2026-07-31)

Fixes

• orb: gate the ai_review_inconclusive hold on aiReviewGateMode (#10239) (00e3ee9)

mcp: 3.21.1

3.21.1 (2026-07-31)

Chores

• mcp: Synchronize engine-and-dependents versions

Dependencies

• The following workspace dependencies were updated
  • dependencies
    • @loopover/contract bumped from ^3.21.0 to ^3.21.1
    • @loopover/engine bumped from ^3.21.0 to ^3.21.1

miner: 3.21.1

3.21.1 (2026-07-31)

Fixes

• miner: cap check-runs page follows so poll cannot spin forever (#10007) (#10258) (470d417)
• miner: keep discover --dry-run off the contribution-profile cache (#10255) (e8c5200)
• miner: prime runLoop's ledger cursor with an indexed MAX(seq) lookup (#10259) (efc2c7e)
• miner: scope the policy-verdict-cache purge to its real host-scoped repo key (#10250) (5b24374)
• miner: stop doctor's ams-backtest-proposals check from creating and pruning the event ledger (#10264) (6f3ac84)
• miner: stop pickScript selecting watch/fix validation scripts (#10261) (c7e8e80)

Dependencies

• The following workspace dependencies were updated
  • dependencies
    • @loopover/contract bumped from ^3.21.0 to ^3.21.1
    • @loopover/engine bumped from ^3.21.0 to ^3.21.1

---

This PR was generated with Release Please. See documentation.

[cloudflare-workers-and-pages]

Deploying with    Cloudflare Workers

The latest updates on your project. Learn more about integrating Git with Workers.

Status	Name	Latest Commit	Updated (UTC)
❌ Deployment failed View logs	loopover-ui	51693f8	Jul 31 2026, 03:09 PM

[loopover-orb]

Warning

⏸️ LoopOver review result - manual review recommended

_{Review updated: 2026-07-31 15:48:41 UTC}

12 files · 1 AI reviewer · 1 blocker · CI green · clean

⏸️ Suggested Action - Manual Review

Review summary
This is an automated release-please chore PR bumping engine-and-dependents packages (contract, engine, mcp, miner) from 3.21.0 to 3.21.1, synchronizing version fields, changelogs, the manifest, package-lock, and server.json. The version bumps are internally consistent across all files (package.json, .release-please-manifest.json, expected-engine.version, package-lock.json, server.json all agree at 3.21.1), and the changelogs correctly attribute the miner/engine fixes driving the bump. This is generated, mechanical content with no hand-written logic to review.

Nits — 4 non-blocking

• The CI failures (codecov-notify, validate-code, validate-tests, changes, Workers Builds) are undetailed and this branch is 1 commit behind default — worth confirming they aren't caused by this PR itself before merging, though a release-please chore PR is unlikely to be the cause.
• The dependency inventory notes no SLSA/sigstore attestation for the newly bumped packages — standard for this repo's current publish pipeline, but worth tracking as a supply-chain hardening item separately from this PR.
• Verify the undetailed CI failures resolve after rebasing onto the current default branch tip, per the 1-commit-behind base branch status.
• Diff looks like trivial or whitespace-only churn — Reduce whitespace-only or formatting-only churn and keep the diff focused on substantive changes.

Concerns raised — review before merging

• No linked issue detected: No closing reference or linked issue number was found in the PR metadata/body. — If this PR is intended to solve an issue, link it explicitly in the PR body.

📋 Copy for AI agents — paste into your coding agent

Fix the following blocker(s) from this PR review:

1. No linked issue detected: No closing reference or linked issue number was found in the PR metadata/body. — If this PR is intended to solve an issue, link it explicitly in the PR body.

Decision drivers

• ❌ Code review — 1 blocker (1 reviewer)
• ❌ Gate result — Blocking (Repo-configured hard blocker found.)

Context & advisory signals — never blocks the verdict

Signal	Result	Evidence
Linked issue	✅ No-issue rationale	PR body explains why no issue is linked.
Related work	⚠️ 1 scoped overlap	Top overlaps are listed below; lower-confidence bulk is hidden.
Change scope	❌ 8/20	High review scope from cached public metadata (no linked issue context).
Validation posture	✅ 25/25	PR body includes validation/test evidence.
Contributor workload	✅ 10/10	Author activity: 9 registered-repo PR(s), 8 merged, 299 issue(s).
Contributor context	✅ Confirmed Gittensor contributor	JSONbored; Gittensor profile; 9 PR(s), 299 issue(s).
Improvement	ℹ️ Insufficient signal	risk: low · value: insufficient-signal

Review context

• Author: JSONbored
• Role context: owner (maintainer lane)
• Public audience mode: oss maintainer
• Lane context: Repository is configured for direct PR review.
• Public profile languages: Python, TypeScript, Ruby, Go, MDX, Shell, Solidity, JavaScript
• Official Gittensor activity: 9 PR(s), 299 issue(s).
• Related work: Titles/paths share 6 meaningful terms. (PR #10196)

Contributor next steps

• Start here: Treat this as maintainer-lane context rather than normal contributor-lane activity.
• Then work through the remaining 3 steps in the Signals table above.

Signal definitions

• Related work = same linked issue, overlapping active PRs, or title/path similarity.
• Change scope = cached public metadata such as size labels, draft state, and review-burden hints.
• Validation posture = whether the PR provides enough public validation/test evidence for maintainer review.
• Contributor workload = public contributor activity and cleanup pressure, not a repo-wide quality failure.
• Contributor context = public GitHub/Gittensor identity context; non-Gittensor status is not a blocker.

🧪 Chat with LoopOver

Ask LoopOver a question about this PR directly in a comment — grounded only in the same cached, public-safe facts shown above, never a new claim.

• @loopover ask <question> answers contribution-quality Q&A with source citations and freshness.
• @loopover chat <question> answers in natural prose from cached decision-pack facts via local inference (maintainer/collaborator; read-only).
• A plain-language @loopover mention with a real question is routed to the closest matching read-only command automatically — no exact syntax required.

Full command reference: https://loopover.ai/docs/loopover-commands

🧪 Experimental — new and may change.

Decision record

• action: hold · clause: missing_linked_issue
• config: 5c3867fbee43dd791de367b4a96323e0a86d4742b9e47837c292208da2e65fdd · pack: oss-anti-slop · ci: passed
• record: 2a99a45fca9de545d7bbc0a59dcbdff1f28e8a19bf9b796d42ece287e30c52d4 (schema v6, head 4813cc9)

_{🟩 Safe / merged · 🟦 Advisory · 🟨 Held for review · 🟥 Blocked / closed}

---

💰 Earn for open-source contributions like this. Gittensor lets GitHub contributors earn for the work they already do — register to start earning →.

Checked by LoopOver, a quiet PR intelligence layer for OSS maintainers.

• Re-run LoopOver review

[superagent-security]

Superagent didn't find any vulnerabilities or security issues in this PR.

[codecov]

Bundle Report

Bundle size has no change ✅

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 92.28%. Comparing base (6f3ac84) to head (4813cc9).
⚠️ Report is 1 commits behind head on main.
✅ All tests successful. No failed tests found.

Additional details and impacted files

@@           Coverage Diff           @@
##             main   #10242   +/-   ##
=======================================
  Coverage   92.28%   92.28%           
=======================================
  Files         939      939           
  Lines      114765   114765           
  Branches    27713    27713           
=======================================
  Hits       105908   105908           
  Misses       7555     7555           
  Partials     1302     1302           

Flag	Coverage Δ
backend	95.70% <ø> (ø)
engine	74.11% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.