chore(release): cut mcp v3.1.2

[JSONbored]

🤖 I have created a release beep boop

3.1.2 (2026-07-17)

Fixes

• api: blunt slop-risk / issue-slop REST + CLI to match the MCP tools (#6990) (#7052) (9971476)
• release: scope MCP publish validation to its own package (86ee117)

Dependencies

• The following workspace dependencies were updated
  • dependencies
    • @loopover/engine bumped from ^3.0.0 to ^3.2.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	6d272b7	Jul 17 2026, 09:35 PM

[superagent-security]

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

[superagent-security]

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

[codecov]

⚠️ JUnit XML file not found

The CLI was unable to find any JUnit XML files to upload.
For more help, visit our troubleshooting guide.

[loopover-orb]

Caution

🛑 LoopOver review result - fixes required

_{Review updated: 2026-07-17 21:46:10 UTC}

4 files · 1 AI reviewer · 1 blocker · CI failing · blocked

🛑 Suggested Action - Manual Review

Review summary
Automated release-please version bump for @​loopover/mcp 3.1.1 → 3.1.2, bumping its @​loopover/engine dependency from ^3.0.0 to ^3.2.1 and syncing the manifest/changelog/lockfile in lockstep. All four changed files are consistent with each other and with the stated release intent, and no source logic is touched.

Nits — 2 non-blocking

• The engine dependency jump from ^3.0.0 to ^3.2.1 pulls in two minor versions of changes sight-unseen; worth confirming the engine's own changelog has no breaking behavior for MCP callers even though semver says it should be safe.
• Since the failing CI jobs (validate-code, validate-tests, Build UI preview artifact) are broad and not obviously related to this version-bump-only diff, worth a quick check that they aren't failing due to the new @​loopover/engine range before merging.

Why this is blocked

• No linked issue detected — 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 — If this PR is intended to solve an issue, link it explicitly in the PR body.

CI checks failing

• validate
• validate-tests (4)
• validate-tests (6)
• validate-tests (1)
• validate-tests (2)
• validate-tests (3)
• validate-tests (5)
• validate-code
• Workers Builds: loopover-ui — Workers Builds: loopover-ui
• Build UI preview artifact

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	⚠️ 3 scoped overlaps	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: 32 registered-repo PR(s), 25 merged, 368 issue(s).
Contributor context	✅ Confirmed Gittensor contributor	JSONbored; Gittensor profile; 32 PR(s), 368 issue(s).
Improvement	ℹ️ Insufficient signal	risk: clean · 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: 32 PR(s), 368 issue(s).
• Related work: Titles/paths share 5 meaningful terms. (PR #7109)
• Related work: Titles/paths share 5 meaningful terms. (PR #7107)
• Related work: Titles/paths share 5 meaningful terms. (PR #7109, PR #7107)

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.

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

[JSONbored]

Superseded -- #7114 fixed release-please-config.json so engine's release and its dependents (mcp, miner) now land as one combined PR/commit, structurally eliminating the ordering race that made this PR's own branch stale. Closing to let release-please regenerate correctly under the new config.