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

[JSONbored]

🤖 I have created a release beep boop

1.1.0 (2026-07-17)

Features

• ui-kit: port state-views.tsx primitives into @loopover/ui-kit (#6539) (8eb1933), closes #6506

Fixes

• config: scrub remaining pre-rename gittensory references (23152da)
• config: scrub remaining pre-rename gittensory references (e4b0f8c)
• ui: add a shared bg-surface-code token for the always-dark code surface (#6957) (334ee58)

---

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	872137a	Commit Preview URL Branch Preview URL	Jul 17 2026, 07:05 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 (872137a).
⚠️ Report is 6 commits behind head on main.
✅ All tests successful. No failed tests found.

Additional details and impacted files

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

Warning

⏸️ LoopOver review result - manual review recommended

_{Review updated: 2026-07-17 19:21:24 UTC}

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

⏸️ Suggested Action - Manual Review

Review summary
This is a standard release-please automated version bump PR for @​loopover/ui-kit (1.0.0 → 1.1.0), updating the package.json version, manifest, CHANGELOG, and package-lock.json entry to match commits already merged to main. The only non-mechanical change is a whitespace fix in the `keywords` array indentation in package.json, which is harmless. Diff content is coherent with the PR title/description and matches the standard release-please pattern documented in the repo's release workflow.

Nits — 3 non-blocking

• Verify the failing CI checks (validate-code, validate, Build UI preview artifact, security, validate-tests (4)) aren't caused by something in this release branch specifically vs. flaking, though CI outcome itself isn't a code defect to block on here.
• None needed beyond the standard release-please merge — confirm package-lock.json's per-workspace version bump matches 1.1.0 throughout (only one hunk shown here) before merging.
• Readiness score is below the configured threshold — Use the readiness panel as advisory maintainer context; the score does not block this PR.

Concerns raised — review before merging

• 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.

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: 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: 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: not available
• Official Gittensor activity: 33 PR(s), 336 issue(s).
• Related work: Titles/paths share 9 meaningful terms. (PR #7005)
• Related work: Titles/paths share 9 meaningful terms. (PR #7004)
• Related work: Titles/paths share 9 meaningful terms. (PR #7003)
• 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:

• ui-kit-v1.1.0

🌻