chore(release): cut mcp v3.1.1

[JSONbored]

🤖 I have created a release beep boop

3.1.1 (2026-07-17)

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	de0e807	Jul 17 2026, 08:06 PM

[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 20:30:47 UTC}

3 files · 1 AI reviewer · 1 blocker · CI failing · dirty

🛑 Suggested Action - Manual Review

Review summary
This is an automated release-please version bump for @​loopover/mcp from 3.1.0 to 3.1.1, syncing package.json, CHANGELOG.md, and the package-lock.json workspace version entry, driven purely by an upstream @​loopover/engine dependency bump (^3.0.0 to ^3.2.1). The package.json and CHANGELOG changes are mechanical and correct, but the package-lock.json hunk only updates the workspace's top-level "version" field — the surrounding (unchanged) context still shows the dependencies block pinned at "@​loopover/engine": "^3.2.0", not the new ^3.2.1 range, meaning the lockfile's resolved dependency entry wasn't regenerated to match the manifest bump.

Blockers

• package-lock.json's loopover-mcp workspace entry updates only the "version" field to 3.1.1 but leaves the dependencies block referencing @​loopover/engine ^3.2.0 instead of the new ^3.2.1 range from package.json, which per the repo's own sync-release-lockfile-versions.mjs comment is exactly the class of drift that breaks `npm ci` with "Missing: @​loopover/engine@​X from lock file".

Nits — 4 non-blocking

• No provenance/attestation is published for the bumped @​loopover/engine 3.2.1 or the mcp 3.1.1 release artifact, though this is standard for this release-please flow and not specific to this PR.
• Regenerate package-lock.json via `npm install` (or run scripts/sync-release-lockfile-versions.mjs against the full dependency tree, not just the version field) so the @​loopover/engine range in the lockfile matches package.json's ^3.2.1 before merging.
• Confirm the failing validate-tests/validate-code/Build UI checks aren't caused by this lockfile mismatch before merging the release.
• Readiness score is below the configured threshold — Use the readiness panel as advisory maintainer context; the score does not block this PR.

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 (1)
• validate-tests (4)
• validate-tests (3)
• validate-tests (2)
• validate-tests (5)
• validate-tests (6)
• 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	⚠️ 12/25	Preflight needs author follow-up before maintainer review.
Contributor workload	✅ 10/10	Author activity: 33 registered-repo PR(s), 26 merged, 336 issue(s).
Contributor context	✅ Confirmed Gittensor contributor	JSONbored; Gittensor profile; 33 PR(s), 336 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: 33 PR(s), 336 issue(s).
• Related work: Titles/paths share 7 meaningful terms. (PR #7058)
• Related work: Titles/paths share 7 meaningful terms. (PR #7057)
• Related work: Titles/paths share 9 meaningful terms. (PR #7058, PR #7057)

Contributor next steps

• Start here: Treat this as maintainer-lane context rather than normal contributor-lane activity.
• Then work through the remaining 4 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: mcp v3.1.1 was already cut manually in #7064 (mcp-v3.1.0/mcp-v3.1.1's own release-please cycle was stuck on tag-protection + a since-fixed publish validation gate — see #7054/#7060/#7064 for the full story). Main is already at packages/loopover-mcp v3.1.1, so this proposal's base is stale. Closing; release-please will recompute a fresh proposal from here on its next run.