Summary

Aligns confirmed chrome/sidebar icon density outliers in the shared Icon registry so they read more consistently at 16px sidebar rows and 20px controls.

Updated icons: new-session, branch, worktree, models, link, github, code, code-lines, bubble-5, and glasses.

Why

Closes #523.

The audit found several traced fill icons with lower or mismatched perceived stroke density. new-session was the clearest outlier, and additional chrome/sidebar icons had similar 16px/20px balance issues. branch and link were regenerated from the approved imagegen/Potrace candidates, then adjusted to avoid the too-heavy/clipped result from the first pass.

Related Issue

Closes #523

Human Review Status

Pending. A human should make the final merge decision after reviewing the final diff and verification evidence.

Review Focus

Please focus on the 16px and 20px perceived density of the updated icons, especially new-session, branch, link, code, code-lines, bubble-5, and glasses.

Risk Notes

UI-only SVG path replacements in packages/ui/src/components/icon.tsx. No message flow, Session Timeline, scroll logic, state, data, dependencies, or generated assets are changed.

file-tree was left unchanged: the earlier black-block symptom was a local preview fill-rule/import issue, not a product icon defect.

How To Verify

UI typecheck: bun --cwd packages/ui typecheck -> passed (tsgo --noEmit)
App typecheck: bun --cwd packages/app typecheck -> passed (tsgo -b)
Diff check: git diff --check -> passed
Comparison preview: refreshed and checked _chrome-sidebar-icon-before-after.html at 16 / 20 / 40 / 72 px
Electron manual check: PAWWORK_CI_SMOKE=true PAWWORK_CI_SMOKE_HOME=/tmp/pawwork-i523-electron-pr-smoke bun run dev:desktop -> verified dev Electron (com.github.Electron, localhost:5173) home/sidebar/settings chrome renders

Screenshots or Recordings

Visible UI was checked locally with the generated before/after comparison page:

/Users/yuhan/workspace/dev/pawwork/docs/design/preview/_chrome-sidebar-icon-before-after.html
/tmp/pawwork-i523-before-after-branch-link-refined.png

The preview artifacts are local-only and intentionally not committed.

Checklist

• Human review status is stated above as pending, approved, or not required
• I linked the related issue, or stated why there is no issue
• This PR has type, primary area, and priority labels, or I requested maintainer labeling
• I described the review focus and any meaningful risks
• I listed the relevant verification steps and the key result for each
• I did not introduce unrelated refactors, dependencies, generated files, or file changes beyond the stated scope
• I manually checked visible UI or copy changes when needed, with screenshots or recordings
• I considered macOS and Windows impact for platform, packaging, updater, signing, paths, shell, or permissions changes
• I called out docs, release notes, dependencies, permissions, credentials, deletion behavior, generated content, or local file changes when relevant
• 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