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

[JSONbored]

🤖 I have created a release beep boop

engine: 3.14.1

3.14.1 (2026-07-25)

Chores

• engine: Synchronize engine-and-dependents versions

mcp: 3.14.1

3.14.1 (2026-07-25)

Fixes

• build: migrate loopover-miner/loopover-mcp to out-of-place dist/ emit (#8590) (c896797)

Dependencies

• The following workspace dependencies were updated
  • dependencies
    • @loopover/engine bumped from ^3.14.0 to ^3.14.1

miner: 3.14.1

3.14.1 (2026-07-25)

Fixes

• build: migrate loopover-miner/loopover-mcp to out-of-place dist/ emit (#8590) (c896797)

Dependencies

• The following workspace dependencies were updated
  • dependencies
    • @loopover/engine bumped from ^3.14.0 to ^3.14.1

---

This PR was generated with Release Please. See documentation.

[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]

Bundle Report

Bundle size has no change ✅

[loopover-orb]

Warning

⏸️ LoopOver review result - manual review recommended

_{Review updated: 2026-07-25 00:51:57 UTC}

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

⏸️ Suggested Action - Manual Review

Review summary
This is an automated release-please version bump PR synchronizing engine/mcp/miner packages from 3.14.0 to 3.14.1 across package.json, package-lock.json, CHANGELOG.md, .release-please-manifest.json, and expected-engine.version. All version bumps are consistent across files (manifest, individual package.json, dependency ranges, lockfile, and the miner's expected-engine.version pin), and the CHANGELOG entries correctly attribute the fix to #8590 (out-of-place dist/ emit). This is standard release-bot bookkeeping with no hand-written logic changes.

Nits — 4 non-blocking

• The failing validate-tests/validate-code/changes checks have no detail provided, so their cause can't be verified from what's given — if this is a stale check re-run or CI infra issue rather than a real break, it's worth confirming before merge since release PRs should be low-risk by construction.
• package-lock.json is a large generated artifact (~21k lines) but that's expected for a lockfile diff and doesn't need manual review.
• Since this PR bundles version bumps for engine, mcp, and miner together, confirm release-please's grouping config is intentional (i.e., these packages are meant to always version together) rather than an artifact of a misconfigured release-please manifest.
• 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: 13 registered-repo PR(s), 13 merged, 277 issue(s).
Contributor context	✅ Confirmed Gittensor contributor	JSONbored; Gittensor profile; 13 PR(s), 277 issue(s).
Improvement	ℹ️ Insufficient signal	risk: low · value: insufficient-signal · LLM: minor

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: 13 PR(s), 277 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

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 92.54%. Comparing base (c896797) to head (130ac52).
✅ All tests successful. No failed tests found.

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #8594   +/-   ##
=======================================
  Coverage   92.54%   92.54%           
=======================================
  Files         796      796           
  Lines       79855    79855           
  Branches    24136    24136           
=======================================
  Hits        73905    73905           
  Misses       4804     4804           
  Partials     1146     1146           

Flag	Coverage Δ
backend	93.72% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

[JSONbored]

Closing as stale: this branch conflicts with current main (mergeable=CONFLICTING) and release-please's own idempotent recompute (just triggered manually) didn't rewrite it, since no new commit landed in the tracked engine-and-dependents group since it was last generated -- release-please only rewrites a Release PR's content when its own computed diff changes, it doesn't proactively rebase for base-branch drift alone.

Not hand-resolving the conflict (touches package-lock.json + the release-please manifest, both generated/release-please-owned state) -- per this repo's own established pattern, generated release state gets regenerated, never manually patched. Closing so release-please opens a fresh, non-conflicting PR on its next run.