chore(release): cut ui-kit v1.2.0

[JSONbored]

🤖 I have created a release beep boop

1.2.0 (2026-07-25)

Features

• release: extend the release-due watcher + tarball pack-check to engine/miner/ui-kit (#8592) (25e99c2)

---

This PR was generated with Release Please. See documentation.

[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 92.54%. Comparing base (c896797) to head (4d7b114).
✅ All tests successful. No failed tests found.

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #8593   +/-   ##
=======================================
  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.

[loopover-orb]

Warning

⏸️ LoopOver review result - manual review recommended

_{Review updated: 2026-07-25 00:48:33 UTC}

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

⏸️ Suggested Action - Manual Review

Review summary
This is an automated Release Please PR that bumps @​loopover/ui-kit from 1.1.2 to 1.2.0, syncing package.json, the manifest, and CHANGELOG.md, consistent with the merged feature commit (#8592) referenced in the changelog entry. The package-lock.json diff also shows unrelated bin-path corrections for loopover-mcp/loopover-miner (dist/bin/*.js → bin/*.js), which is pre-existing drift being captured by a lockfile regeneration, not something this release PR introduces. All version/manifest/changelog numbers are consistent with each other and CI is fully green.

Nits — 2 non-blocking

• The package-lock.json bin-path changes for loopover-mcp and loopover-miner (removing the `dist/` prefix) are unrelated to the ui-kit version bump; worth confirming this reflects an intentional prior change to those packages' build output layout rather than incidental lockfile drift being carried along.
• Verify the bin path change for loopover-mcp/loopover-miner (dist/bin/*.js -> bin/*.js) was an intentional, already-reviewed change in a prior PR, since it's unrelated to this release but shows up in this lockfile diff.

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	⚠️ 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	⚠️ 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: clean · 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).
• Related work: Titles/paths share 4 meaningful terms. (PR #8594)

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:

• ui-kit-v1.2.0

🌻