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

[JSONbored]

🤖 I have created a release beep boop

engine: 3.11.0

3.11.0 (2026-07-23)

Features

• calibration: claimed-confidence reliability curves with derived threshold suggestion (#8252) (2defb4a)
• calibration: pure counterfactual fixture assembler per the replay contract (#8220) (#8247) (7a8b9b6)

mcp: 3.11.0

3.11.0 (2026-07-23)

Chores

• mcp: Synchronize engine-and-dependents versions

Dependencies

• The following workspace dependencies were updated
  • dependencies
    • @loopover/engine bumped from ^3.10.0 to ^3.11.0

miner: 3.11.0

3.11.0 (2026-07-23)

Features

• miner: wire AMS's hosted entry point to the #8202 tenant-secret bootstrap (#8246) (#8263) (904ec7d)

Dependencies

• The following workspace dependencies were updated
  • dependencies
    • @loopover/engine bumped from ^3.10.0 to ^3.11.0

---

This PR was generated with Release Please. See documentation.

[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.15%. Comparing base (904ec7d) to head (7ce3c31).
⚠️ Report is 1 commits behind head on main.
✅ All tests successful. No failed tests found.

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #8249   +/-   ##
=======================================
  Coverage   92.15%   92.15%           
=======================================
  Files         786      786           
  Lines       78814    78814           
  Branches    23790    23790           
=======================================
  Hits        72630    72630           
  Misses       5062     5062           
  Partials     1122     1122           

Flag	Coverage Δ
shard-1	53.86% <ø> (ø)
shard-2	50.26% <ø> (+<0.01%)	⬆️
shard-3	57.30% <ø> (-0.01%)	⬇️

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

[loopover-orb]

Warning

⏸️ LoopOver review result - manual review recommended

_{Review updated: 2026-07-23 16:54:38 UTC}

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

⏸️ Suggested Action - Manual Review

Review summary
This is a standard Release Please automation PR bumping engine/mcp/miner from 3.10.0 to 3.11.0, synchronizing the manifest, package.json versions, expected-engine.version, CHANGELOG entries, and package-lock.json accordingly. All version bumps and dependency pins are internally consistent across every touched file. This is a mechanical, bot-generated chore PR with no hand-written logic changes.

Nits — 3 non-blocking

• The external review brief's provenance/attestation and long-file flags on package-lock.json are expected noise for a lockfile-touching release PR and not real defects.
• None needed — verify CI passes before merge as usual for release PRs.
• 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	✅ No active overlap found	No same-issue or scoped active PR overlap found.
Change scope	✅ 20/20	Low review scope from cached public metadata (no linked issue context).
Validation posture	⚠️ 20/25	Preflight is ready, but the PR body does not name the validation run.
Contributor workload	✅ 10/10	Author activity: 14 registered-repo PR(s), 14 merged, 255 issue(s).
Contributor context	✅ Confirmed Gittensor contributor	JSONbored; Gittensor profile; 14 PR(s), 255 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: 14 PR(s), 255 issue(s).
• PR-specific overlap: none found.

Contributor next steps

• Start here: Treat this as maintainer-lane context rather than normal contributor-lane activity.
• Then work through the remaining 1 step 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.

_{🟩 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