chore(release): cut engine v3.2.1

[JSONbored]

🤖 I have created a release beep boop

3.2.1 (2026-07-17)

Fixes

• config: recognize federatedIntelligence manifest block in lint and preview (95ba59a)
• config: recognize federatedIntelligence manifest block in lint and preview (1c80fb8)

---

This PR was generated with Release Please. See documentation.

[superagent-security]

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

[codecov]

Codecov Report

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

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #7109   +/-   ##
=======================================
  Coverage   93.75%   93.75%           
=======================================
  Files         692      692           
  Lines       68808    68808           
  Branches    18781    18781           
=======================================
  Hits        64511    64511           
  Misses       3302     3302           
  Partials      995      995           

Flag	Coverage Δ
shard-1	43.78% <ø> (ø)
shard-2	36.84% <ø> (ø)
shard-3	33.14% <ø> (ø)
shard-4	34.47% <ø> (ø)
shard-5	32.29% <ø> (ø)
shard-6	45.76% <ø> (ø)

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

[loopover-orb]

Caution

🛑 LoopOver review result - fixes required

_{Review updated: 2026-07-17 21:52:57 UTC}

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

🛑 Suggested Action - Manual Review

Review summary
This is an automated release-please version bump PR cutting engine v3.2.1, propagating the version across package.json, the release manifest, expected-engine.version, CHANGELOG.md, and package-lock.json in lockstep. The mechanical changes are internally consistent and correctly synchronized across all four files. CI shows several failures (validate, validate-code, validate-tests-merge, security, changes) which are concerning for a release PR but are not visible as code defects in this diff.

Nits — 5 non-blocking

• The duplicate 'config: recognize federatedIntelligence manifest block' fix entry appears twice in the changelog (two separate commit hashes for what reads as the same fix) — worth confirming this isn't a duplicate commit that should have been squashed.
• CI failures on validate, validate-code, and security checks should be investigated before merging this release PR even though they aren't visible as defects in the diff itself.
• Verify the two changelog entries for 'federatedIntelligence manifest block' truly correspond to distinct commits/changes and aren't a duplicate release-please entry.
• Confirm the failing CI checks (validate, validate-code, security, changes) are resolved or understood before tagging/publishing this 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-code

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: 32 registered-repo PR(s), 25 merged, 368 issue(s).
Contributor context	✅ Confirmed Gittensor contributor	JSONbored; Gittensor profile; 32 PR(s), 368 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: 32 PR(s), 368 issue(s).
• Related work: Titles/paths share 9 meaningful terms. (PR #7108)
• Related work: Titles/paths share 9 meaningful terms. (PR #7107)
• Related work: Titles/paths share 9 meaningful terms. (PR #7108, PR #7107)

Contributor next steps

• Start here: Treat this as maintainer-lane context rather than normal contributor-lane activity.
• Then work through the remaining 5 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 -- #7114 fixed release-please-config.json so engine's release and its dependents (mcp, miner) now land as one combined PR/commit, structurally eliminating the ordering race that made this PR's own branch stale. Closing to let release-please regenerate correctly under the new config.