Summary

Run the full packages/ui package test suite in CI instead of only the focused tests under packages/ui/test.

Why

packages/ui/src/** already contains package-level tests, but CI did not invoke a UI package test:ci task. That left 34 source-adjacent tests silent on pull requests.

Related Issue

Closes #869

Human Review Status

Pending

Review Focus

Please focus on whether the new unit-ui job and Turbo @opencode-ai/ui#test:ci task cover the intended UI package tests without widening CI scope beyond the package boundary.

Risk Notes

Low risk: this changes CI coverage and aligns two UI control assertions with the current design tokens. No runtime dependency or platform packaging behavior changed.

Skipped conditional checklist items:

• Platform impact: no platform, packaging, updater, signing, path, shell, or permissions surface was touched.
• Docs/release/dependency/local artifact impact: no docs, release notes, dependencies, credentials, deletion behavior, generated content, or local artifacts were committed.

How To Verify

bun --cwd packages/opencode test test/github/ci-workflow.test.ts
Result: 11 passed, 0 failed.

bun turbo test:ci --filter=@opencode-ai/ui --dry=json | jq -r '.tasks[].taskId'
Result: includes @opencode-ai/ui#test:ci, with build dependencies only.

bun turbo test:ci --filter=@opencode-ai/ui
Result: 648 passed, 0 failed across 51 files.

bun run snap sidebar
Result: 1 passed; reviewed the generated sidebar preview locally.

Screenshots or Recordings

Visual check performed with bun run snap sidebar; reviewed docs/design/preview/screenshots/sidebar.png locally for the changed sidebar/titlebar control styling.

Checklist

How to use this checklist:

• Tick a box by replacing [ ] with [x]. Do not edit, add, or remove items.
• The bot-applied label items can only be honestly ticked AFTER the PR is opened and the labeler / priority-triage bots have run — return to the PR description and tick them then.
• Most items are required. The few that are conditional are explicitly marked (conditional); for those, leave unticked if they truly do not apply and explain why in Risk Notes. All other items must be ticked before requesting human review.

• Type label — this PR carries exactly one of bug, enhancement, task, documentation. Type labels are author-added; the labeler bot does NOT assign them. Add the label in the GitHub UI, then tick this.
• Routing labels — this PR carries at least one of app, ui, platform, harness, ci. The labeler bot assigns these on PR open based on changed paths. Confirm the bot's choice (or override if wrong), then tick this.
• Priority label — this PR carries exactly one of P0, P1, P2, P3. The priority-triage bot suggests one on PR open. Confirm or override, then tick this.
• Human Review Status above is set to Pending, Approved by @<reviewer>, or Not required: <reason> (default is Pending; "not required" is restricted to bot-authored low-risk PRs).
• I linked the related issue, or stated in Summary why there is no issue.
• I described the review focus and any meaningful risks.
• I replaced the example block in How To Verify with the real verification steps and the key result for each.
• I did not introduce unrelated refactors, dependencies, generated files, or file changes beyond the stated scope.
• (conditional) I manually checked visible UI or copy changes when needed, with screenshots or recordings. Leave unticked only if no visible UI or copy changed.
• (conditional) I considered macOS and Windows impact for platform, packaging, updater, signing, paths, shell, or permissions changes. Leave unticked only if no platform/packaging surface was touched.
• (conditional) I called out docs, release notes, dependencies, permissions, credentials, deletion behavior, generated content, or local file changes when relevant. Leave unticked only if none of those surfaces was touched.
• I reviewed the final diff for unrelated changes and suspicious dependency changes.
• I am targeting dev, and my PR title and commit messages use Conventional Commits in English.