chore(release): cut miner v3.1.0

[JSONbored]

🤖 I have created a release beep boop

3.1.0 (2026-07-17)

Features

• miner-ui: add discover and attempt HTTP action routes (#6574) (5c34c3a), closes #6522
• miner: add config-gated chat action-dispatch scaffolding (#6542) (c9984c1), closes #6519
• miner: add the ContributionProfile local cache store + doctor/migrate integration (#6797) (#7001) (9171769)
• miner: consult selfLoopAutonomy in decideNextAction's pass-to-handoff step (#6581) (7a275c7), closes #6560
• miner: consume ORB live gate thresholds in self-review-context (1cb09e4)
• miner: design the ContributionProfile schema + caching shape (#6795) (#6970) (ad8536e)
• miner: exclude discover candidates assigned to the repo owner (7a7f90a)
• miner: exclude discover candidates assigned to the repo owner (995686f)
• miner: implement generic ContributionProfile extraction (#6796) (#6979) (018e261)
• miner: probe ORB live-gate-thresholds in self-review-context (087a0e3)
• miner: register governor pause/resume chat actions (#6521) (#6587) (ad4486f)
• miner: wire chat action-dispatch to the existing discover/attempt routes (#6837) (#6855) (a4c76a6)
• miner: wire chat action-dispatch to the existing portfolio release/requeue routes (#6838) (#6850) (61202e3)
• miner: wire ContributionProfile eligibility filtering into discover (08e56fb)
• miner: wire ContributionProfile eligibility filtering into discover (#6798) (324490b)
• purge: add purgeByRepo method to portfolio queue and run state stores (#6694) (11a6dac)

Fixes

• config: scrub remaining pre-rename gittensory references (23152da)
• config: scrub remaining pre-rename gittensory references (e4b0f8c)
• miner: add the tenant_id column to governor-ledger and plan-store (#6707) (28f7f05), closes #6597
• miner: cover four omitted stores in doctor and migrate (#6928) (e1df4aa)
• miner: enforce maxConcurrentClaims atomically across sibling processes (#6912) (b1a2bbd), closes #6758
• miner: expire claims orphaned by a dead process at claim time (#6441) (4d326e4), closes #6156
• miner: fail fast instead of hanging when init --interactive has no TTY (#6907) (fa52680), closes #6846
• miner: flag real LOOPOVER_MINER_* env vars missing from DEPLOYMENT.md (#6601) (2e12f63)
• miner: flag real LOOPOVER_MINER_* env vars missing from DEPLOYMENT.md (#6601) (b586810)
• miner: forward HOME and the real coding-agent credential to CLI subprocesses (4a852de)
• miner: open doctor's laptop-state check read-only (camelCase readOnly) (#6866) (81a3a03)
• miner: open the worktree allocator through local-store's openLocalStoreDb (#6600) (#6704) (4e9aa2d)
• miner: reject blank acceptance hints as an objective success signal (#6766) (25792fd)
• miner: reject blank acceptance hints as an objective success signal (#6766) (fd730f1)
• miner: release the primed portfolio claim when --max-cycles is exhausted (d2244e9)
• miner: release the primed portfolio claim when --max-cycles is exhausted (c976ca3)
• miner: report the real post-failure schema version for a partially-applied migration (#6860) (4b786b1)
• miner: require a closing keyword in self-review's linked-PR extractor (#6769) (6f5520d)
• miner: require a closing keyword in self-review's linked-PR extractor (#6769) (5192411)
• miner: retain a crashed attempt's worktree for post-mortem (#6867) (8ef43a4)
• miner: retry GitHub rate-limit responses in http-retry instead of aborting the poll (#6761) (#6878) (58cd901)
• miner: route the governor/prediction/plan local stores through openLocalStoreDb (#6667) (0591ffc)
• miner: scope the managed-PR queue row to the polled forge host (de1c473)
• miner: scope the managed-PR queue row to the polled forge host (492aef3)
• miner: serialize per-repo base clone to prevent concurrent git races (#6917) (2e2f588), closes #6762
• miner: stamp prediction-ledger schema version and add tenant_id column (#6702) (46b1aca), closes #6596
• miner: wire DEPLOYMENT.md audit into real CI execution (1019fb2)
• miner: wire DEPLOYMENT.md audit into real CI execution (cdf3321), closes #6158
• registry: scope self-host repo registration to gittensor opt-ins (67af510)
• selfhost: templatize the docker-prune systemd unit for multi-host use (a740bce)
• selfhost: templatize the docker-prune systemd unit for multi-host use (1842bd3), closes #4894
• 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	8c81187	Commit Preview URL Branch Preview URL	Jul 17 2026, 07:31 PM

[codecov]

Codecov Report

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

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #7003      +/-   ##
==========================================
- Coverage   93.74%   93.74%   -0.01%     
==========================================
  Files         692      692              
  Lines       68748    68706      -42     
  Branches    18769    18760       -9     
==========================================
- Hits        64451    64409      -42     
  Misses       3302     3302              
  Partials      995      995              

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

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

4 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/miner from 3.0.0 to 4.0.0 (major, due to the earlier breaking loopover.ai cutover), bumping the @​loopover/engine dependency range to ^3.2.0 and regenerating the CHANGELOG.md and package-lock.json/manifest accordingly. The mechanical version/lockfile edits are internally consistent (package.json, manifest, and lockfile all agree on 4.0.0), and the changelog content matches the referenced commits. The only functional edit outside pure version bumps is a whitespace fix to the 'miner' keyword indentation in package.json.

Nits — 7 non-blocking

• package.json:19 fixes stray indentation on the 'miner' keyword — unrelated to the release but harmless drift cleanup, worth a one-line mention in the PR description.
• Confirm the @​loopover/engine range bump to ^3.2.0 is intentional and that 3.2.0 is actually published/compatible, since release-please infers this from workspace deps rather than a manual review.
• Multiple CI jobs (validate-code, validate-tests, Workers Builds) are failing on this commit; while CI status itself isn't a code defect, a release PR should not be merged while its own validation is red.
• Verify the failing validate-tests/validate-code/Workers Builds checks aren't caused by something in this diff (e.g., a lockfile/version mismatch elsewhere) before tagging the release.
• Since package-lock.json is a generated artifact, no manual review of its diff is needed beyond confirming the version bump line matches.
• 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 (6)
• validate-tests (2)
• validate-tests (3)
• validate-tests (4)
• validate-tests (5)
• validate-tests (1)
• 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 #7004)

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:

• miner-v3.1.0

🌻