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

[JSONbored]

🤖 I have created a release beep boop

engine: 3.6.0

3.6.0 (2026-07-23)

Features

• gate: config-driven backtest-regression gate mode, default advisory (#8105) (#8162) (9c303a6)

mcp: 3.6.0

3.6.0 (2026-07-23)

Chores

• mcp: Synchronize engine-and-dependents versions

Dependencies

• The following workspace dependencies were updated
  • dependencies
    • @loopover/engine bumped from ^3.5.0 to ^3.6.0

miner: 3.6.0

3.6.0 (2026-07-23)

Chores

• miner: Synchronize engine-and-dependents versions

Dependencies

• The following workspace dependencies were updated
  • dependencies
    • @loopover/engine bumped from ^3.5.0 to ^3.6.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.06%. Comparing base (9c303a6) to head (2ca6609).
⚠️ Report is 6 commits behind head on main.
✅ All tests successful. No failed tests found.

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #8164   +/-   ##
=======================================
  Coverage   92.06%   92.06%           
=======================================
  Files         766      766           
  Lines       77772    77772           
  Branches    23495    23495           
=======================================
  Hits        71597    71597           
  Misses       5062     5062           
  Partials     1113     1113           

Flag	Coverage Δ
shard-1	57.10% <ø> (-0.01%)	⬇️
shard-2	52.73% <ø> (ø)
shard-3	53.62% <ø> (ø)

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 08:23:40 UTC}

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

⏸️ Suggested Action - Manual Review

Review summary
This is an automated Release Please PR that bumps engine/mcp/miner package versions from 3.5.0 to 3.6.0, syncing the manifest, package.json files, expected-engine.version, lockfile, and CHANGELOGs to reflect the already-merged gate config-driven backtest-regression feature (#8105/#8162). All version bumps are consistent across the manifest, package.json dependencies, expected-engine.version, and package-lock.json, and CI is fully green. This is standard release-automation bookkeeping with no functional code changes.

Nits — 2 non-blocking

• The external inventory note about missing SLSA/sigstore attestation and package-lock.json size is expected noise for a release-please PR and lockfile, not an actionable issue here.
• 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, 253 issue(s).
Contributor context	✅ Confirmed Gittensor contributor	JSONbored; Gittensor profile; 14 PR(s), 253 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, JavaScript, MDX, Shell, Solidity
• Official Gittensor activity: 14 PR(s), 253 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