---
name: KROW Design System Gaps and Escalations
description: Known missing tokens, open design questions, and items requiring escalation to PM or design system owner
type: project
---

## Open Escalations (as of 2026-03-18)

### 1. No Dark Theme Token Definitions
**Severity:** High
**Detail:** `ui_colors.dart` defines a single light `ColorScheme`. Tag colors (`tagActive`, `tagPending`, `tagFreeze`, `tagError`) have no dark mode equivalents. No dark theme has been configured in `UiTheme`.
**Action:** Escalate to design system owner before any dark mode work. Until resolved, do not attempt dark mode overrides in feature widgets.

### 2. V2 History API — trackedHours Sign Convention
**Severity:** Medium
**Detail:** `GET /staff/profile/benefits/history` returns `trackedHours` as a positive integer. There is no `transactionType` field to distinguish accruals from deductions (used hours). Design assumes accrual-only for now with `+` prefix in `UiColors.textSuccess`.
**Action:** Escalate to PM/backend. Recommend adding `transactionType: "ACCRUAL" | "USAGE"` or signed integer to distinguish visually.

### 3. Missing Localization Keys for Benefits History
**Severity:** Low (implementation blocker, not design blocker)
**Detail:** New keys under `benefits.history.*` need to be added to both `en.i18n.json` and `es.i18n.json` in `packages/core_localization/lib/src/l10n/`. Must be coordinated with Mobile Feature Agent who runs `dart run slang`.
**Action:** Hand off key list to Mobile Feature Agent.
