Linux distros like Fedora atomic, bazzite, and uBlue use /var/home as the home path. Avoid this being blocked as a system path by checking if the workspace is under home BEFORE checking if its a system path

Captures the design philosophy authored by Aron Prins (lead UI/UX) so
contributors have a written bar to design against before touching primary
surfaces. Modestly expanded from the source doc with concrete examples
(mobile stress test, decision checklist, surface-by-surface guidance) but
keeps the original principles and voice intact.

Linked from CONTRIBUTING.md docs list.

Co-Authored-By: Claude Opus 4.7 (1M context) <[email protected]>

The System settings pane (settingsPaneSystem) had no Save Settings button.
Users could type a new password or click Disable Auth but had no way to
submit the password change since Save was only in Appearance/Preferences panes.

- Added Save Settings button to System pane
- Added 5 tests verifying the fix and preventing regression

…viewed (#1140)

- Track unread job IDs in _cronNewJobIds Set alongside _cronUnreadCount
- Render green dot indicator on cron items with new completions
- Add has-new-run CSS class to Last Output card for unviewed jobs
- Clear unread state only when user opens specific job detail (not on panel open)
- Add pulse animation for new-run dots
- Badge count decrements per-job instead of resetting on panel switch

7 test cases covering:
- External symlink dirs listed with correct type/is_dir/target
- Browsing into external symlink dirs via workspace-relative path
- Self-referencing symlinks filtered (ln -s . link)
- Ancestor symlinks filtered (ln -s .. link)
- Cycle symlinks inside symlink targets filtered
- Symlink file entries with size
- Path traversal still blocked with symlink support

… tree

When workspace contains symlinks pointing outside the workspace root
(e.g. ln -s /root/obsidian ~/workspace/obsidian), the directory listing
could recurse infinitely if the symlink target contains a symlink back to
the workspace or its ancestors.

The original cycle detection only ran when the symlink target was inside
the workspace root, missing the common case of external symlinks.

Changes:
- Move cycle detection outside the workspace-relative check so it runs
  for all symlinks regardless of target location
- Skip symlinks that point to the workspace root, the current directory,
  or any ancestor of the current directory
- Properly type symlink entries with 'type: symlink' and 'is_dir' field
  so the frontend can render them correctly (folder icon + expand arrow)
- Maintain workspace-relative paths for entries inside symlink targets
  so navigation continues to work across the workspace boundary

CI locale tests require all English keys present in every locale.
Added status_profile, status_started, status_tokens, status_no_tokens,
status_unknown with English placeholder values to ru, es, de, zh.

…arted time (#463)

- Backend: session_status() now includes input_tokens, output_tokens,
  total_tokens, estimated_cost (previously only in /usage endpoint)
- Frontend: cmdStatus() shows provider, profile, started timestamp,
  token usage with cost, alongside existing fields
- i18n: added status_profile, status_started, status_tokens,
  status_no_tokens, status_unknown keys in en, zh-Hant, ko locales
- Tests: extended test_status_returns_summary to verify new fields

- messages.js: compute per-turn token/cost delta from cumulative usage
  at done event and store as _turnUsage on the last assistant message
- ui.js: render per-turn usage on each assistant bubble that has
  _turnUsage, replacing the misleading cumulative-total-on-last-bubble
- The context ring/composer footer still shows cumulative totals
- Preserves backwards compatibility: old messages without _turnUsage
  simply won't show inline usage (no visual regression)

…1145 #1146 #1149 #1156 #1157 #1159 #1161 #1162 #1165 #1166)

…sessions remain visible when the user enables CLI session display

PR #1143 changed read_importable_agent_session_rows() default to exclude cron
sessions, but get_cli_sessions() is the function that serves the "show CLI
sessions" sidebar feature. The exclusion should only apply inside all_sessions()
(the default WebUI session list), not at the CLI import layer.

Blockers:
- messages.js: capture prevIn/prevOut/prevCost before S.session overwrite (#1159)
- workspace.py safe_resolve_ws+list_dir: block symlink targets in system dirs (#1149)
- models.py: pass exclude_sources=None in get_cli_sessions() — done earlier (#1143)

Minor:
- panels.js: derive _cronUnreadCount from _cronNewJobIds.size (no phantom counts)
- ui.js: tighten _isContextCompactionMessage to role===assistant only (#1142)
- workspace.py: add HOME sanity guard in resolve_trusted_workspace (#1165)

- ui.js: revert _isContextCompactionMessage guard (test validates role===tool check)
- routes.py: apply _hide_from_default_sidebar to deduped_cli in /api/sessions
- panels.js: restore _cronUnreadCount var with Set.size sync in updateCronBadge

This reverts commit 08c61e1.