v0.80.0

Added

• Pause a running run and resume it later, right where it left off (#1190).
  A run's owner can now park a running issue, task, prompt or self-improve run on demand, after the milestone in flight (the default) or immediately with --now, which drops the turn in flight and discards work since the last checkpoint, and resume it later with the remaining budget untouched, since the clock stops rather than resetting while it waits. The worker publishes a checkpoint before parking, so if that publish fails the run stays running and the owner is told in its activity feed instead of losing the park silently; resuming continues the same session on the original worker or recovers the branch and re-plans only the unfinished milestones on another. Reachable from the run page (a ‖ Pause ▾ menu, a pending-pause chip, a Resume button), the CLI (uzi run pause <id> [--now|--cancel], uzi run resume <id>), and the TUI (a ‖ paused word and detail line, read-only).
• Three light themes: Dawn, Hall, and Shadow (#1167).
  Each keeps the dark factory somewhere on screen: Dawn stays dark only on machine surfaces (the run activity feed, code/log/CLI blocks); Hall adds a dark sidebar and mobile top bar; Shadow additionally keeps a board card, run row, or run header dark while that run is actively working, staying light with a rust accent while it waits on a human. All three share one WCAG 2.2 AA-verified light palette and reuse ember's own dark values for every dark surface, so a machine pane looks identical across every theme.
• A System / Lights on / Lights off appearance mode, with one theme held per polarity and matching admin instance defaults (#1167).
  Settings → Appearance now holds a mode alongside a "Lights on theme" and a "Lights off theme"; System follows the OS's prefers-color-scheme live, with no reload. An admin can set the same four fields (mode, light theme, dark theme, typeface) as instance-wide defaults from Admin → Instance settings; the legacy single "Default theme" keeps feeding the dark slot, so nobody's screen changes on upgrade.
• A bundled IBM Plex typeface option (#1167).
  Settings → Appearance gains a Typeface choice: System (the platform default) or IBM Plex, shipped with the app so switching to it makes no external font request and the System choice downloads nothing.
• Further foundational work toward a Codex-based worker lane (#1171, #1106).
  Behind the scenes and not user-visible yet: completes the Codex production adapter and execution-safety milestone (M3b), building on the credential and packaging groundwork shipped in 0.79.0.

Changed

• The slow run-health flag is now a budget-relative "near timeout" warning instead of a bare wall-clock timer (#1170).
  It fires once a run's active running time (wall clock since start, gate waits excluded) has used a configurable share of its wall-clock budget (default 85%, health_near_timeout_pct replacing health_slow_seconds); the flag reads "near timeout" everywhere, and the badge, TUI, and CLI human views now count down the time left to the deadline (e.g. 1h 5m left) instead of the time since it was raised, while Slack relabels the flag and glyph without a countdown and the machine-readable health field keeps reporting slow.
• Workers enumerate a repo's skills from both .agents/skills and .claude/skills (#1205, #1206).
  A cloned repo that keeps one real .agents/skills tree with .claude/skills as a directory symlink (the cross-agent layout) is now read correctly: the worker reads both real roots, .claude/skills winning on a name collision, and rejects a symlinked skills-root parent so the containment boundary still holds.
• The Codex credential import flow and status badges now explain themselves (#1177).
  The Codex credential import screen and the per-worker Codex credential status badges carry clearer labels and help text, so importing a Codex credential and reading its state no longer needs outside context.

Fixed

• TUI in-progress milestone markers render correctly with several milestones running (#1176).
  The in-progress milestone glyph no longer falls back to a mismatched font, and the per-milestone micro-bars now blink for each in-progress milestone instead of only one cell when several are in progress at once.
• The admin per-user usage breakdown's SHARE% column sums to 100% (#1185).
  Independent per-row rounding could make the column total 101%; the shares are now apportioned so they add up to exactly 100%.