chore(release): cut engine v3.2.0

[JSONbored]

🤖 I have created a release beep boop

3.2.0 (2026-07-17)

Features

• api: add a REST route + CLI mirror for loopover_check_test_evidence (#6810) (d45d8fd), closes #6749
• config: make sweepWatchdog staleness threshold configurable (#6594) (#6639) (0e313c8)
• engine: add a stable, versioned getTrackRecordSummary read API (2958302)
• engine: add selfLoopAutonomy to AmsPolicySpec (bd614bf)
• engine: add selfLoopAutonomy to AmsPolicySpec (880b973), closes #6559
• engine: define a shared TrustSignal type for ORB/AMS reputation bridging (7ee0670)
• engine: define a shared TrustSignal type for ORB/AMS reputation bridging (145a279)
• mcp: CLI mirror for loopover_draft_pr_body (#6974) (13bd48b)
• mcp: CLI mirror for loopover_explain_gate_disposition (#6966) (4966070)
• mcp: validate .loopover.yml offline by extracting buildFocusManifestValidation into @loopover/engine (#6425) (22faecf), closes #6269
• miner: add read-only chat grounding over the existing miner MCP tools (#6570) (ed16fef), closes #6517
• miner: consult selfLoopAutonomy in decideNextAction's pass-to-handoff step (#6581) (7a275c7), closes #6560
• orb: add the opt-in federated collector transport client (push/pull) (#6537) (8ab3472), closes #6479
• orb: export a signed, anonymized federated calibration bundle (opt-in) (#6505) (53ce7b2), closes #6478
• orb: trust-gate inbound federated bundles per the #6477 key-trust design (#6649) (729254a)
• review: bridge a submitter's AMS track record into ORB reputation, upgrade-only (#6566) (97a1938), closes #6485
• review: give LOOPOVER_REVIEW_PLANNER a per-repo config override (b429292)
• review: give LOOPOVER_REVIEW_PLANNER a per-repo config override (73eb87d)
• selfhost: make LOOPOVER_REVIEW_DRAFT and LOOPOVER_AUTO_FILE_DRIFT_ISSUES .loopover.yml-controllable (85e8301)
• selfhost: make LOOPOVER_REVIEW_DRAFT and LOOPOVER_AUTO_FILE_DRIFT_ISSUES .loopover.yml-controllable (0d3f4cb)
• selfhost: make LOOPOVER_REVIEW_OPS and LOOPOVER_PUBLIC_STATS .loopover.yml-controllable (87c3e6b)
• selfhost: make LOOPOVER_REVIEW_OPS and LOOPOVER_PUBLIC_STATS .loopover.yml-controllable (bc2f899)
• selfhost: make LOOPOVER_SWEEP_WATCHDOG and LOOPOVER_PR_RECONCILIATION .loopover.yml-controllable (3ac9501)
• selfhost: make LOOPOVER_SWEEP_WATCHDOG and LOOPOVER_PR_RECONCILIATION .loopover.yml-controllable (7ca394a), closes #6558

Fixes

• config: scrub remaining pre-rename gittensory references (23152da)
• config: scrub remaining pre-rename gittensory references (e4b0f8c)
• correct four stale 'improvementSignal not wired yet' comments (#6691) (2d493cd)
• discovery-index: cap the untrusted response candidate list (#6774) (ff46459)
• discovery-index: cap the untrusted response candidate list (#6774) (ca5c81a)
• engine: align predicted-gate collision risk with live-gate twin (#6671) (2df475c), closes #6629
• engine: cap predicted-gate's local linked-issue extractor at the canonical 50 (#6771) (fcf41bc)
• engine: cap predicted-gate's local linked-issue extractor at the canonical 50 (#6771) (0fe3e99)
• engine: exclude inline code spans in predicted-gate extractLinkedIssueNumbers (e6ef456)
• engine: exclude inline code spans in predicted-gate extractLinkedIssueNumbers (#6630) (6ac8c1f)
• engine: exclude lockfiles and dependency manifests from trivial-churn detection (ed882b7)
• engine: exclude lockfiles and dependency manifests from trivial-churn detection (a2d8306)
• engine: exempt generated/vendored/minified files from missing-test-evidence signal (2c59771)
• engine: exempt generated/vendored/minified files from the missing-test-evidence signal (203e7c7)
• engine: filter maintainer-authored manifest fields out of public findings (99aeead)
• engine: filter maintainer-authored manifest fields out of public findings (5f5a6fc), closes #6770
• engine: floor percentComplete at 0 so it stays in its documented 0-100 range (#6773) (ab9cb63)
• engine: floor percentComplete at 0 so it stays in its documented 0-100 range (#6773) (84543ed)
• engine: honor no-issue rationale in predicted preflight (#6645) (8b20ad6), closes #6628
• engine: stop the collision report using unscoped issue.linkedPrs for risk escalation (d95d4a6)
• engine: stop unscoped issue.linkedPrs from inflating collision risk (38fec26)
• engine: treat non-finite calibration inputs as cold-start / safe clamp (#6651) (d4b5a81), closes #6627
• miner: forward HOME and the real coding-agent credential to CLI subprocesses (4a852de)
• miner: forward HOME and the real coding-agent credential to CLI subprocesses (e327370), closes #6875
• miner: grant the claude-cli driver Read/Bash access, not just edits (615dd46)
• miner: grant the claude-cli driver Read/Bash access, not just edits (664aebe), closes #6840
• review: close cohort/score gaps in public-comment sanitizers (b2c66d7)
• review: correlate screenshot-table presence-mode evidence to the PR head SHA (9bf58f6)
• review: correlate screenshot-table presence-mode evidence to the PR head SHA (8c5230a)
• review: redact cohort/miner-originated/human-originated/raw-trust and bare score in public sanitizers (77fd09e)
• signals: make shouldPublishPrIntelligenceComment respect commentMode for oss_maintainer (#6776) (#6853) (fa8f577)
• track-record: exempt the GitHub login line from the public-field blocklist scan (#6772) (4328d08)
• track-record: exempt the GitHub login line from the public-field blocklist scan (#6772) (7ed6328)

---

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

[superagent-security]

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

[codecov]

Bundle Report

Bundle size has no change ✅

[codecov]

Codecov Report

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

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #7005      +/-   ##
==========================================
- Coverage   93.74%   93.74%   -0.01%     
==========================================
  Files         692      692              
  Lines       68740    68687      -53     
  Branches    18768    18759       -9     
==========================================
- Hits        64443    64390      -53     
  Misses       3302     3302              
  Partials      995      995              

Flag	Coverage Δ
shard-1	43.79% <ø> (ø)
shard-2	36.84% <ø> (ø)
shard-3	33.35% <ø> (ø)
shard-4	33.90% <ø> (+<0.01%)	⬆️
shard-5	32.21% <ø> (ø)
shard-6	45.76% <ø> (ø)

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 18:56:42 UTC}

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

🛑 Suggested Action - Manual Review

Review summary
This is an automated release-please version bump for @​loopover/engine 3.1.1 -> 3.2.0: package.json version, expected-engine.version, .release-please-manifest.json, CHANGELOG.md, and package-lock.json entries are all updated consistently, including bumping the loopover-mcp/loopover-miner internal dependency ranges from ^3.0.0 to ^3.2.0. The keywords array whitespace fix in package.json is incidental formatting noise from release-please's file rewrite, not a functional change. The diff is internally consistent and mechanical, matching its stated intent as a release cut.

Nits — 4 non-blocking

• package.json's keywords array indentation fix (removing extra leading spaces on 'engine') is unrelated formatting churn bundled into the version bump, though harmless.
• The external brief's 'no published SLSA/sigstore attestation' and 'long-file' package-lock.json flags are expected noise for a lockfile-inclusive release commit, not real defects.
• Confirm the failed CI checks (validate-code, validate-tests, security, changes) aren't caused by this version bump itself versus pre-existing failures on main before merging the release.
• Diff looks like trivial or whitespace-only churn — Reduce whitespace-only or formatting-only churn and keep the diff focused on substantive changes.

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)

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: 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)
• Related work: Titles/paths share 9 meaningful terms. (PR #7003)
• Related work: Titles/paths share 9 meaningful terms. (PR #7002)
• Additional title-only matches omitted; title-only overlap does not block.

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]

🤖 Created releases:

• engine-v3.2.0

🌻