chore(release): cut mcp v3.1.0

[JSONbored]

🤖 I have created a release beep boop

3.1.0 (2026-07-17)

Features

• api: add a REST route + CLI mirror for loopover_check_test_evidence (#6810) (d45d8fd), closes #6749
• api: add a REST route + CLI mirror for loopover_evaluate_escalation (#6805) (f8d1628), closes #6754
• api: add a REST route + CLI mirror for loopover_get_pr_ai_review_findings (#6676) (885336a), closes #6619
• api: add a REST route + CLI mirror for loopover_simulate_open_pr_pressure (#6915) (68b8694), closes #6751
• api: add a REST route + CLI mirror for loopover_suggest_boundary_tests (80869bd)
• api: add a REST route + CLI mirror for loopover_suggest_boundary_tests (4d5212e), closes #6750
• api: add GET /v1/repos/:owner/:repo/automation-state + CLI mirror (#6742) (#6964) (c566906)
• api: add POST /v1/repos/:owner/:repo/repo-docs/refresh + CLI mirror (#6973) (f1e9632)
• api: mirror loopover_propose_action to REST and the CLI (#6744) (#7030) (a752b8f)
• api: REST + CLI mirror for contributor notifications (#6745) (#7018) (447ee82)
• api: REST + CLI mirror for loopover_build_results_payload (#6904) (7f7ea50), closes #6752
• api: REST + CLI mirror for loopover_check_improvement_potential (#6955) (27c7c59)
• api: REST + CLI mirror for loopover_explain_review_risk (#6980) (#7026) (15715dc)
• api: REST + CLI mirror for loopover_intake_idea (#6916) (f1fb812), closes #6755
• api: REST + CLI mirror for loopover_pr_outcome (#6747) (748acee)
• api: REST + CLI mirror for loopover_pr_outcome (#6747) (efbe09c)
• api: REST + stdio mirror for loopover_build_progress_snapshot (#6943) (d6cf892)
• api: REST + stdio mirror for loopover_plan_idea_claims (#6952) (8fa47d1), closes #6756
• mcp: add a contributor-profile CLI command (#6961) (484c9c8)
• mcp: add a loopover_get_bounty_advisory CLI mirror (#6954) (7733371)
• mcp: add a loopover_get_maintainer_lane CLI mirror (#6942) (71bc183)
• mcp: add a maintain audit-feed CLI mirror for loopover_get_agent_audit_feed (#6733) (#6933) (5347291)
• mcp: add a maintain outcome-calibration CLI mirror (#6960) (a4310f1)
• mcp: add a typed PostHog wrapper module for packages/loopover-mcp (7152db6)
• mcp: add maintain onboarding-pack CLI mirror (#6913) (96ee9c4)
• mcp: CLI mirror for loopover_draft_pr_body (#6974) (13bd48b)
• mcp: CLI mirror for loopover_explain_gate_disposition (#6966) (4966070)
• mcp: CLI stdio mirror for loopover_get_repo_outcome_patterns (#6962) (244988b)
• mcp: mirror contributor-issue-draft generation to an MCP tool + maintain CLI (#7019) (bd4c172), closes #6757
• mcp: mirror loopover_monitor_open_prs to the stdio wrapper and CLI (#6789) (544cb31)
• mcp: record local stdio tool calls at the dispatch chokepoint (#6432) (45fe399), closes #6238
• mcp: register loopover_close_pr write-tool in both MCP surfaces (#6615) (#6715) (3f6591d)
• mcp: register plan-DAG tools + local scorer in packages/loopover-mcp (1aa6603)
• mcp: register plan-DAG tools + local scorer in packages/loopover-mcp (f096969), closes #6150
• mcp: register the 8 miner write-tools on the local stdio server (#6390) (9197680), closes #6149
• mcp: register the maintain REST surface as local stdio tools (#6382) (aa83a48), closes #6152
• mcp: REST route + CLI mirror for loopover_get_eligibility_plan (#6692) (bb028ec), closes #6621
• mcp: REST routes + CLI resource mirrors for finding-taxonomy and enrichment-analyzers (#6709) (b0677cd), closes #6620
• mcp: validate .loopover.yml offline by extracting buildFocusManifestValidation into @loopover/engine (#6425) (22faecf), closes #6269

Fixes

• apps: update remaining gittensory references across loopover-miner-ui, loopover-ui, and loopover-miner-extension (af6b16c)
• apps: update remaining gittensory references across loopover-miner-ui, loopover-ui, and loopover-miner-extension (3287ab3)
• auth: give device-flow polling its own rate-limit budget (0244058)
• auth: give device-flow polling its own rate-limit budget (1c566a0), closes #6792
• ci: derive version-copy floor from single source of truth (e449499)
• ci: derive version-copy floor from single source of truth (ab11e8b), closes #6292
• config: scrub remaining pre-rename gittensory references (23152da)
• config: scrub remaining pre-rename gittensory references (e4b0f8c)
• mcp: honor --help on the contributor-profile CLI command (4ac395a)
• mcp: honor --help on the contributor-profile CLI command (dee57ea), closes #6992
• mcp: list maintain and contributor-profile in --help (#7036) (b153047)
• mcp: redact a parenthesis/bracket/colon-prefixed local path in redactLocalPath (97e3e6b)
• mcp: rename enrichment-analyzers resource URI to loopover:// (feec18c)
• mcp: rename enrichment-analyzers resource URI to loopover:// (4d9d6c4)
• mcp: sanitize every terminal path that prints API-controlled text (436c6c1)
• mcp: sanitize every terminal path that prints API-controlled text (7506cda), closes #6261
• test: update grafana dashboard assertions for the historical-continuity query rewrite (8cd0b24)

---

This PR was generated with Release Please. See documentation.

[superagent-security]

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

[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	Preview URL	Updated (UTC)
✅ Deployment successful! View logs	loopover-ui	b6d19c5	Commit Preview URL Branch Preview URL	Jul 17 2026, 07:30 PM

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 93.74%. Comparing base (7a7f90a) to head (b6d19c5).
⚠️ Report is 27 commits behind head on main.
✅ All tests successful. No failed tests found.

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #7004      +/-   ##
==========================================
- Coverage   93.75%   93.74%   -0.01%     
==========================================
  Files         692      692              
  Lines       68760    68706      -54     
  Branches    18769    18760       -9     
==========================================
- Hits        64463    64409      -54     
  Misses       3302     3302              
  Partials      995      995              

Flag	Coverage Δ
shard-1	43.79% <ø> (+<0.01%)	⬆️
shard-2	36.85% <ø> (ø)
shard-3	33.27% <ø> (ø)
shard-4	33.90% <ø> (ø)
shard-5	32.24% <ø> (ø)
shard-6	45.75% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.
see 1 file with indirect coverage changes

[loopover-orb]

Caution

🛑 LoopOver review result - fixes required

_{Review updated: 2026-07-17 19:24:30 UTC}

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

🛑 Suggested Action - Manual Review

Review summary
This is an automated release-please PR that bumps @​loopover/mcp from 3.0.0 to 4.0.0, updates the @​loopover/engine dependency range to ^3.2.0, and regenerates CHANGELOG.md and package-lock.json accordingly. The version bumps are internally consistent across package.json, .release-please-manifest.json, and package-lock.json, and the CHANGELOG content matches the PR description's release notes.

Nits — 6 non-blocking

• package.json bumps @​loopover/engine to ^3.2.0 but package-lock.json's shown hunk still lists 3.0.0 as the resolved dependency version for loopover-mcp — worth confirming the lockfile was fully regenerated (npm install) rather than hand-edited for just the top-level version field.
• The CI failures listed (validate-tests, validate-code, Workers Builds, etc.) are not explained by anything in this diff, which only touches version metadata and changelog — worth confirming these failures are pre-existing/unrelated before merging a release PR.
• Verify the full package-lock.json regeneration is complete and consistent for the @​loopover/engine range bump, not just the top-level package version.
• Given the CI failures, hold this release PR until the failing validate-tests/validate-code/Workers Builds checks are understood, since merging a broken build under a new version tag would be worse than delaying it.
• Diff looks like trivial or whitespace-only churn — Reduce whitespace-only or formatting-only churn and keep the diff focused on substantive changes.
• 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 (5)
• validate-tests (2)
• validate-tests (3)
• validate-tests (1)
• validate-tests (6)
• validate-tests (4)
• 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	⚠️ 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	⚠️ 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: 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: not available
• Official Gittensor activity: 33 PR(s), 336 issue(s).
• Related work: Titles/paths share 9 meaningful terms. (PR #7003)

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

[codecov]

Bundle Report

Bundle size has no change ✅

[JSONbored]

🤖 Created releases:

• mcp-v3.1.0

🌻