diff --git a/docs/design-tokens.md b/docs/design-tokens.md index 64e0f97..bc71c8f 100644 --- a/docs/design-tokens.md +++ b/docs/design-tokens.md @@ -40,6 +40,8 @@ Application rules: - Use `.ops-headline-h2` and `.ops-headline-h3` for readable section and card headings. - Do not remove mono from sigils, readiness status, telemetry, or controls. - Prefer `.ops-mono` or `.ops-eyebrow` when a component needs explicit tactical voice. +- Use `.ops-telemetry-label`, `.ops-telemetry-value`, and `.ops-telemetry-detail` inside telemetry chips instead of one-off muted or attention text mixes. +- Telemetry attention states should use the mapped `data-tone="attention"` rail and register treatment. Do not restyle them as full warning banners. ### Tracking scale @@ -175,12 +177,14 @@ Application rules: - Reserve clipped panel notches for the app shell, first-level section cards, and key repeated controls. - Use `ops-flat-panel` for secondary decision zones and narrative guidance inside a section. - Use `ops-inline-alert` for non-critical banners that need tone without a full notched frame. +- Use `.ops-recovery-support-panel` for steady backup, undo, and storage guidance blocks that need cockpit structure without alert escalation. - Use `tactical-subpanel` only when a nested control truly needs cockpit framing. - Use `tactical-subpanel-strong` when a detail brief or selected-state summary should read one step higher than surrounding support strips. - Use `tactical-chip-panel` for compact meta blocks, legends, and grouped facts that should feel inset rather than flat. - Keep these utilities inside the current cockpit language. They are not a license to add decorative glow, blur, or card-rounding. - Use tone chip panels for import, restore, recovery, and fault guidance instead of repeating inline gradient stacks. - Use uniform calm `SignalCard` chrome for backup summary signals. Express caution with the left spine or an inline tone chip rather than recoloring the entire card amber when the state is an intended safety lock. +- Accordion status chips stay in `.ops-export-accordion-status` so badge alignment remains stable across open and collapsed recovery panels. Frame emphasis: @@ -217,6 +221,16 @@ Application rules: - Do not recreate cockpit focus treatment with ad hoc `focus-visible:ring-*` Tailwind stacks in component markup. - Keep `ops-focus-ring-chip` on the clipped chip surface itself. If the focusable element is a parent shell, proxy focus to the chip surface instead of inventing a new ring pattern. +History selection chrome: + +- `--ops-history-selection-bg`, `--ops-history-selection-bg-strong`, and `--ops-history-selection-border` are selection-only accents for the history grid and mobile week selector. +- Use `.ops-history-selection-axis-header` on the selected desktop day header. +- Use `.ops-history-selection-axis` on cells that belong to the selected desktop day column. +- Use `.ops-history-selection-row-header` on the selected desktop sector row header. +- Use `.ops-history-selection-node` on the exact selected desktop cell or selected mobile day. +- Keep `aria-selected`, `aria-current`, and `aria-pressed` as the semantic source of truth. These classes are visual reinforcement only. +- Do not use readiness status colors for selection axes. Status colors remain reserved for the cell payload, badges, and spines. + ## Notch geometry Shared notch sizes live in `src/styles/index.css`. diff --git a/src/components/HeaderTelemetry.tsx b/src/components/HeaderTelemetry.tsx index 6bc7b51..1adf502 100644 --- a/src/components/HeaderTelemetry.tsx +++ b/src/components/HeaderTelemetry.tsx @@ -182,7 +182,7 @@ function TelemetryChip({ ].join(' ')} > - + {isAttention ? (