eidotter 0.46.0 → 0.47.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (61) hide show
  1. package/README.md +8 -5
  2. package/dist/components/Brand/components/Wordmark.d.ts +2 -1
  3. package/dist/components/Brand/components/Wordmark.js +3 -2
  4. package/dist/components/CalendarHeatmap/components/CalendarHeatmap.d.ts +2 -2
  5. package/dist/components/CalendarHeatmap/components/CalendarHeatmap.js +2 -2
  6. package/dist/components/ChecklistRow/components/ChecklistRow.d.ts +1 -1
  7. package/dist/components/ChecklistRow/components/ChecklistRow.js +1 -1
  8. package/dist/components/CopyButton/components/CopyButton.d.ts +1 -1
  9. package/dist/components/CopyButton/components/CopyButton.js +1 -1
  10. package/dist/components/DisplayMenu/components/DisplayMenu.d.ts +8 -5
  11. package/dist/components/DisplayMenu/components/DisplayMenu.js +69 -10
  12. package/dist/components/EmptyState/components/EmptyState.d.ts +1 -1
  13. package/dist/components/EmptyState/components/EmptyState.js +1 -1
  14. package/dist/components/Gauge/components/Gauge.js +1 -1
  15. package/dist/components/HoldToComplete/components/HoldToComplete.d.ts +1 -1
  16. package/dist/components/HoldToComplete/components/HoldToComplete.js +1 -1
  17. package/dist/components/LedgerRow/components/LedgerRow.d.ts +1 -1
  18. package/dist/components/LedgerRow/components/LedgerRow.js +1 -1
  19. package/dist/components/ProgressRing/components/ProgressRing.d.ts +1 -1
  20. package/dist/components/ProgressRing/components/ProgressRing.js +1 -1
  21. package/dist/components/RetroEffects/components/RetroEffects.d.ts +54 -0
  22. package/dist/components/RetroEffects/components/RetroEffects.js +124 -4
  23. package/dist/components/RetroEffects/components/index.d.ts +1 -1
  24. package/dist/components/RetroEffects/index.d.ts +1 -1
  25. package/dist/components/SectionHeading/components/SectionHeading.d.ts +1 -1
  26. package/dist/components/SectionHeading/components/SectionHeading.js +2 -2
  27. package/dist/components/Stat/components/Stat.js +1 -1
  28. package/dist/components/registry.d.ts +12 -1
  29. package/dist/components/registry.js +101 -98
  30. package/dist/eidotter.css +1 -1
  31. package/dist/index.d.ts +4 -3
  32. package/dist/index.es.js +731 -603
  33. package/dist/index.umd.js +3 -3
  34. package/dist/terminal/cga-amber.json +94 -0
  35. package/dist/terminal/cga-mode4-p0.json +94 -0
  36. package/dist/terminal/cga-mode4-p1.json +94 -0
  37. package/dist/terminal/cga-mode5.json +94 -0
  38. package/dist/terminal/dos-86.json +94 -0
  39. package/dist/utils/displayTheme.d.ts +32 -4
  40. package/dist/utils/displayTheme.js +33 -7
  41. package/guidelines/README.md +14 -2
  42. package/guidelines/components.md +9 -0
  43. package/guidelines/design-principles.md +1 -0
  44. package/guidelines/figma-architecture.md +1 -2
  45. package/guidelines/terminal-target.md +44 -0
  46. package/llms.txt +19 -19
  47. package/migrations/0.47.0.md +209 -0
  48. package/migrations/README.md +2 -0
  49. package/package.json +12 -6
  50. package/src/styles/dos-utilities.css +13 -3
  51. package/src/styles/shadcn.css +37 -2
  52. package/src/styles/theme.amber-paper.css +11 -7
  53. package/src/styles/theme.cga-amber.css +7 -7
  54. package/src/styles/theme.cga-mode4-p0.css +7 -7
  55. package/src/styles/theme.cga-mode4-p1.css +7 -7
  56. package/src/styles/theme.cga-mode5.css +7 -7
  57. package/src/styles/theme.dos-86.css +79 -0
  58. package/src/styles/theme.light.css +7 -7
  59. package/src/styles/{theme.amber-mono.css → theme.pure-amber.css} +8 -8
  60. package/src/styles/tokens.css +65 -23
  61. package/tailwind.preset.cjs +4 -2
@@ -45,7 +45,6 @@ How eiDotter's design system is structured across Figma files, how those files r
45
45
  | **V.37 / "❖ Pattern Lab"** | `V4tIz3sAMRx7H9wMYeesA6` | UntitledUI-full component fork — the component-authoring reference the npm package is built against. **Not a foundation**; aliases nothing in the production chain. Unpublished as a team library. |
46
46
  | ~~"Foundation"~~ | `qlEyN6zHPX4XOohJefJ4bZ` | **Abandoned first attempt** on Molly Helmuth's DS. **Out of scope — never subscribe to or alias.** Named "Foundation" and shares V.37's "❖" glyph, so easily confused with `KoGTFX8`; it is neither the foundation nor V.37. Frozen palette-pattern source for DMNC-922 only. |
47
47
  | **DOSBTS_fig** | `1Hemp6DehvK1a5uMrPJyhr` | Amber CGM app. Adoption target. |
48
- | **calendar-365** | `npu5c86H9QHBB4fluVUjKJ` | App; future adoption candidate. |
49
48
 
50
49
  ## Token tier taxonomy (DMNC-916)
51
50
 
@@ -98,7 +97,7 @@ iOS DS, macOS DS, and V.37 are documented from snapshots/memory — give each a
98
97
 
99
98
  How an app file adopts the DS. Goal: **no visual change** — every alias must resolve to the same hex the local literal had. Proven on DOSBTS_fig (DMNC-1002).
100
99
 
101
- 0. **Confirm the app is in the eidotter DOS design language.** Adoption is *not* for every portfolio Figma file. If the app has its own bespoke palette and aesthetic, it is **not a DS consumer** — skip it. Example: `calendar-365`'s "Sunburst Tokens" are a *light* print-calendar palette (black/gray text, near-white pastel month wedges, gold spoke) with **zero** value-matches to Foundation — forcing adoption would be wrong. Only DOS-amber apps (DOSBTS, DOOMBTS, EatThisDie, …) adopt.
100
+ 0. **Confirm the app is in the eidotter DOS design language.** Adoption is *not* for every portfolio Figma file. If the app has its own bespoke palette and aesthetic, it is **not a DS consumer** — skip it. Example: a print-calendar app's "Sunburst Tokens" are a *light* print-calendar palette (black/gray text, near-white pastel month wedges, gold spoke) with **zero** value-matches to Foundation — forcing adoption would be wrong. Only DOS-amber apps (DOSBTS, DOOMBTS, EatThisDie, …) adopt.
102
101
  1. **Enable libraries** in the app file: Assets → Libraries → enable **eiDotter Foundation** (+ the relevant platform DS, e.g. iOS DS for an iOS app). *Manual Figma UI step — the bridge cannot toggle subscriptions.*
103
102
  2. **Inventory + value-match** the app's local collection (`figma_get_variables` with `resolveAliases`); for each var, find the Foundation var with the **same resolved hex** (keys live in `figma-snapshots/foundation-keys.json`).
104
103
  3. **Re-point matches to aliases**, batched ≤86/call. What can alias **today**:
@@ -0,0 +1,44 @@
1
+ # Terminal target
2
+
3
+ Terminals are an official output of the token pipeline, next to CSS, Tailwind, Swift and Figma. The pipeline writes one JSON file per DOS theme: the colours a terminal needs, resolved to hex, and nothing else.
4
+
5
+ ## What it produces
6
+
7
+ `npm run build-tokens` (and `npm run build`) writes `dist/terminal/<theme>.json` for the themes with a full 16-colour palette: `cga-amber`, `cga-mode4-p0`, `cga-mode4-p1` and `cga-mode5`. `pure-amber` (Pure Amber, formerly `amber-mono`) and `amber-paper` get no file (nor does the `amber-mono` alias): they collapse the palette to one phosphor, so their ANSI green and cyan are dark browns and the lighter signal steps are fixed colours that do not belong to them, which does not make a usable terminal palette (a terminal file that fails contrast is worse than none). The modern `light` theme is not a terminal theme. A deliberate monochrome terminal variant would need its own mapping and is an open design question. The `dos-86` theme (DMNC-1643) gets a file because it is in the `themes` list; its 15 roles and 16 ANSI slots equal the DOS-86 terminal theme's, screen #050300 included. The files ship in the package; import them as `eidotter/terminal/<theme>.json`.
8
+
9
+ ```jsonc
10
+ {
11
+ "name": "eiDotter cga-amber",
12
+ "roles": { "screen": "#050300", "text": "#FFB000", /* 15 roles */ },
13
+ "ansi": { "black": "#050300", "red": "#FF5555", /* 16 slots, in ANSI order */ },
14
+ "effects": { "scanline": { "intensity": 0.6 }, /* the shared-core effect tokens */ }
15
+ }
16
+ ```
17
+
18
+ - **`roles`** say what each colour is for: `screen`, `text`, `textDim`, `textStrong`, `decoration`, `cursor`, `selection`, `raised`, `error`, `success`, `warning`, `prompt`, `info`, `addedFill`, `removedFill`. A target maps from roles, never from raw colours.
19
+ - **`ansi`** holds the 16 terminal slots: `black`, `red`, `green`, `yellow`, `blue`, `magenta`, `cyan`, `white`, then the same eight with a `bright` prefix.
20
+ - **`effects`** is every shared-core `effect.*` token (scanlines, phosphor, vignette, flicker) at the values eiDotter's web effects use. The web-only extension (`effect.web.*`) is left out, as it is for Swift.
21
+
22
+ ## Where it comes from
23
+
24
+ `src/tokens/terminal.tokens.json` holds the role layer and the ANSI slots as references into eiDotter's own colour tokens. `style-dictionary.config.mjs` resolves it once per theme, layered over the base tokens and that theme, so a role lands on whatever the theme says. Adding a DOS theme to the `themes` list there is enough to get its terminal file.
25
+
26
+ Two kinds of value:
27
+
28
+ - **References** to `color.cga.*` and the alert surfaces. These follow the theme's palette.
29
+ - **Fixed values**, the same in every theme: the tint (`#1A1000`) and four lighter signal steps (`#FF8888`, `#FFFF99`, `#9999FF`, `#FF9AFF`). They are not CGA colours; they exist so the bright ANSI row has a step above each normal colour.
30
+
31
+ ## Two departures from ANSI convention
32
+
33
+ Both are deliberate, so a program that prints in these slots stays readable on the phosphor.
34
+
35
+ 1. **`white` is emphasis, not white.** The slot holds the strong amber (`textStrong`), so it stays in the phosphor. Pure white is `brightWhite`.
36
+ 2. **`brightBlack` is readable.** Programs print secondary text (comments, hints, dimmed output) in the slot that convention makes near-invisible dark grey. Here it holds the soft secondary text colour (`textDim`).
37
+
38
+ ## Contrast
39
+
40
+ `text`, `textDim`, `error`, `success`, `warning`, `prompt` and `info` are tested at 4.5:1 against `screen` for every emitted theme, with no exceptions (`src/styles/terminal.test.ts`). The test also asserts that `pure-amber`, its alias `amber-mono`, `amber-paper` and `light` are not emitted, so adding one back is a deliberate act.
41
+
42
+ ## What is not here
43
+
44
+ Application files (Windows Terminal, iTerm2, Ghostty, kitty, Alacritty, VS Code, Claude Code and the rest) are not generated in this repo. They are generated from these JSON files in the DOS-86 terminal theme's own repository, which reads `eidotter/terminal/<theme>.json` when eiDotter is installed.
package/llms.txt CHANGED
@@ -4,10 +4,10 @@
4
4
 
5
5
  ## Quick Facts
6
6
  - 63 components (Accordion, AIText, Alert, Badge, Bench, Brand (Logo, Mark, Wordmark, BrandLockup), Breadcrumb, Button, CalendarHeatmap, Card, Chat (ChatMessage, ChatHistory, ChatInput, ChatContainer), Checkbox, ChecklistRow, CmdPalette, CommandPrompt, Connector, CopyButton, DecayStrip, DisplayMenu, DosDialog, DosFigure, DosWindow, EmptyState, FilterBar, Footer, Gauge, Header, HeaderButton, HoldToComplete, Icon, IconButton, InlineExpand, InlineLink, Input, LabeledProgress, LedgerRow, LegalPage, Lightbox, Meter (MeterGroup), Modal, Nav, Notification, PageShell (PageSection), Progress, ProgressRing, RangeBar, RetroEffects, SectionHeading, Select, Separator, SeriesBars, Skeleton, Stat, Switch, Tabs, Tag, Terminal, TextScramble, TimelineContainer, TimelineFeed, TimelineNode, TimelinePage, VitalsStrip)
7
- - Amber theme is the default (amber-on-black phosphor CRT); a light theme ("amber in daylight") is in progress (DMNC-1058). Components paint via semantic roles so they re-theme — do not hardcode dark-only assumptions.
7
+ - `dos-86` is the default theme (0.47, DMNC-1643): amber-on-black phosphor CRT with honest functional colours (error red, success green, warning yellow, info cyan), component text in JetBrains Mono Nerd Font with headings in the display face (Perfect DOS VGA 437), and calm long-reading CRT effects. Under Pure Amber everything stays in the display face. Pure Amber (`pure-amber`, formerly `amber-mono`, deprecated alias) is the previous all-amber default, still bundled and selectable; a site keeps it with `themes={{ dosDark: 'pure-amber' }}` plus `data-theme="pure-amber"` on first paint. Light themes: `light`, `amber-paper`. Components paint via semantic roles so they re-theme — do not hardcode dark-only assumptions.
8
8
  - CSS custom properties + Tailwind preset
9
9
  - React 18/19, Tailwind 3/4 compatible
10
- - Published on npm: `npm install eidotter` (current v0.41.x)
10
+ - Published on npm: `npm install eidotter` (current v0.47.x)
11
11
  - Consumer imports: `eidotter/styles` (required); `eidotter/themes/<name>.css` (optional theme); `eidotter/utilities` (optional `.dos-*` classes for raw HTML/MDX/prose; 12 classes; v0.19.4+)
12
12
 
13
13
  ## Key Principle
@@ -16,7 +16,7 @@ NEVER hardcode colors. Paint via SEMANTIC ROLES (not raw primitives) so componen
16
16
  - Tailwind: `text-dos-text-brand` (amber), `bg-dos-bg-primary`, etc. — prefer semantic `dos-*` utilities over raw `cga-*`
17
17
 
18
18
  ## Theme defaults (adoption posture)
19
- Apps default to the amber theme and offer the light theme via a consistent settings toggle (e.g. in settings). The DS is the default starting point; deviate only by deliberate exception. DS changes reach products through a preview + approval gate (before/after + the principle that drove each change). See `guidelines/design-principles.md` Part 4.
19
+ Apps default to the `dos-86` theme (amber with honest functional colours) and offer the other themes (LIGHT = `dos-86-light` on a `dos-86` site, `amber-paper` on a Pure Amber site, PURE = Pure Amber where a site opts in) through DisplayMenu, the one theme control. The DS is the default starting point; deviate only by deliberate exception. DS changes reach products through a preview + approval gate (before/after + the principle that drove each change). See `guidelines/design-principles.md` Part 4.
20
20
 
21
21
  ## Files for AI Agents
22
22
  - CLAUDE.md: Coding instructions, component patterns, and token reference
@@ -27,8 +27,8 @@ Apps default to the amber theme and offer the light theme via a consistent setti
27
27
 
28
28
  ## Upgrading
29
29
  - Every minor with breaking/visible changes ships a guide at `node_modules/eidotter/migrations/<version>.md` (index: `migrations/README.md`).
30
- - Read every guide between the installed and the target version, oldest first, and follow its checklist. Guides: `migrations/0.41.0.md`, `migrations/0.43.0.md`, `migrations/0.44.0.md`, `migrations/0.45.0.md`, `migrations/0.46.0.md`.
31
- - 0.x caret gotcha: `^0.40.x` never resolves to 0.41.0; bump the range explicitly, to `^0.46.0`.
30
+ - Read every guide between the installed and the target version, oldest first, and follow its checklist. Guides: `migrations/0.41.0.md`, `migrations/0.43.0.md`, `migrations/0.44.0.md`, `migrations/0.45.0.md`, `migrations/0.46.0.md`, `migrations/0.47.0.md`.
31
+ - 0.x caret gotcha: `^0.40.x` never resolves to 0.41.0; bump the range explicitly, to `^0.47.0`.
32
32
 
33
33
  ## Token Categories
34
34
  - `--color-semantic-*`: USE THESE for components (background, text, border, status)
@@ -110,27 +110,27 @@ Components originate from different projects. Use `getComponentsByOrigin(project
110
110
 
111
111
  | Component | Origin | Used By |
112
112
  |-----------|--------|---------|
113
- | Alert | eidotter | rizomorf, steuerdash |
113
+ | Alert | eidotter | rizomorf |
114
114
  | Accordion | eidotter | rizomorf |
115
115
  | AccordionFill | eidotter | rizomorf |
116
- | Badge | eidotter | rizomorf, steuerdash |
116
+ | Badge | eidotter | rizomorf |
117
117
  | Breadcrumb | rizomorf | rizomorf |
118
- | Button | eidotter | spacewar, rizomorf, pomodoke-calendar, steuerdash |
119
- | Card | eidotter | rizomorf, steuerdash |
120
- | Checkbox | eidotter | steuerdash |
118
+ | Button | eidotter | rizomorf |
119
+ | Card | eidotter | rizomorf |
120
+ | Checkbox | eidotter | (none) |
121
121
  | CommandPrompt | eidotter | rizomorf |
122
122
  | Icon | eidotter | rizomorf |
123
- | Input | eidotter | steuerdash |
124
- | Modal | eidotter | pomodoke-calendar |
125
- | Progress | eidotter | steuerdash |
126
- | RetroEffects | spacewar | spacewar, rizomorf |
127
- | Stat | steuerdash | steuerdash |
123
+ | Input | eidotter | (none) |
124
+ | Modal | eidotter | (none) |
125
+ | Progress | eidotter | (none) |
126
+ | RetroEffects | eidotter | rizomorf |
127
+ | Stat | eidotter | (none) |
128
128
  | Switch | eidotter | (none) |
129
- | Tabs | eidotter | steuerdash |
129
+ | Tabs | eidotter | (none) |
130
130
  | Terminal | eidotter | rizomorf |
131
- | Tag | eidotter | lifelines, rizomorf |
132
- | TimelineContainer | lifelines | lifelines |
133
- | TimelineNode | lifelines | lifelines, rizomorf |
131
+ | Tag | eidotter | rizomorf |
132
+ | TimelineContainer | eidotter | (none) |
133
+ | TimelineNode | eidotter | rizomorf |
134
134
  | ChatMessage | eidotter | (none yet) |
135
135
  | ChatHistory | eidotter | (none yet) |
136
136
  | ChatInput | eidotter | (none yet) |
@@ -0,0 +1,209 @@
1
+ # Upgrading to eidotter 0.47.0
2
+
3
+ From 0.46.x. Coming from older versions, read the earlier guides first
4
+ ([0.41.0](./0.41.0.md), [0.43.0](./0.43.0.md), [0.44.0](./0.44.0.md),
5
+ [0.45.0](./0.45.0.md), [0.46.0](./0.46.0.md)).
6
+
7
+ 0.47.0 changes the default theme. The new default, `dos-86`, is amber text
8
+ with honest functional colours: errors are red, success green, warnings
9
+ yellow, info cyan. Component text is set in the body face, JetBrains Mono
10
+ Nerd Font; headings keep the DOS display face. Its CRT effects are calmer,
11
+ tuned for long reading. The
12
+ previous default is now called Pure Amber (`pure-amber`) and stays available,
13
+ unchanged; a site can keep it as its default with two lines.
14
+
15
+ ## Who must act
16
+
17
+ - Sites that set `data-theme` from `resolveDisplayTheme()` / DisplayMenu
18
+ without passing `dosDark`: the site turns `dos-86` on upgrade, with new
19
+ functional colours and a new body typeface. Check pages (sections 2 and 3),
20
+ or keep Pure Amber (section 4).
21
+ - Sites that hard-code `data-theme="amber-mono"` or `"pure-amber"`: nothing
22
+ changes. Rename `amber-mono` to `pure-amber` when convenient (section 6).
23
+ - Sites that set no `data-theme` at all: nothing changes (section 5).
24
+ - Sites that mount `RetroEffects`: the effects calm down under `dos-86`
25
+ (section 7).
26
+
27
+ ## 1. How to bump
28
+
29
+ ```bash
30
+ npm install eidotter@^0.47.0
31
+ npm ls eidotter # 0.47.0 or later
32
+ ```
33
+
34
+ Commit the lockfile. 0.x carets do not cross minors: `^0.46.0` never
35
+ resolves to 0.47.0.
36
+
37
+ ## 2. Visible: the default theme is `dos-86`
38
+
39
+ **What changed.** `resolveDisplayTheme()` and `displayMenuItems()` default
40
+ `dosDark` to `'dos-86'` (it was `'amber-mono'`). `eidotter/styles` now
41
+ bundles the `dos-86` theme as well as Pure Amber, so
42
+ `data-theme="dos-86"` works without an extra import.
43
+
44
+ Under `dos-86`, compared with Pure Amber:
45
+
46
+ - Text, borders, links, the focus ring, the card surface and the AI
47
+ provenance colours are the same.
48
+ - The ground is the DOS-86 screen colour `#050300` (Pure Amber: `#020003`).
49
+ - Functional colours are honest: error text, borders and status `#FF5555`,
50
+ success `#55FF55`, warning `#FFFF55`, info `#00AAAA`; alert grounds are dark
51
+ tints (`#430500`, `#122010`, `#352800`, `#0A1828`).
52
+ - The critical and destructive fill (`--color-semantic-background-error`:
53
+ Button `destructive`, the health family's critical tone) is `#D00000` with
54
+ white text (5.7:1). It is not a CGA colour: it reaches 3:1 on the screen
55
+ (3.6:1) and the card surface (3.7:1), which CGA red `#AA0000` (2.7:1) does
56
+ not.
57
+ - Warnings read as yellow everywhere a component signals one, including
58
+ Alert and Notification `warning`, which use the brand amber under Pure
59
+ Amber.
60
+ - The CGA hue primitives (`--color-cga-red`, `--color-cga-green`, ...) take
61
+ their honest values, so your own CSS that uses a primitive directly follows.
62
+
63
+ **How to find it.** `grep -rn "resolveDisplayTheme\|displayMenuItems" src`
64
+ in your app. A call without a `dosDark` in its `themes` argument now resolves
65
+ to `dos-86`.
66
+
67
+ **What to do.** Look at pages with alerts, notifications, badges, form
68
+ errors, destructive buttons, progress bars and the health components. If the
69
+ honest colours are what you want, nothing else to do. If your own CSS paints
70
+ a meaning with a primitive (`--color-cga-red`), use the semantic role instead
71
+ (`--color-semantic-text-error`).
72
+
73
+ **How to verify.** With the theme switch at its defaults, `<html>` has
74
+ `data-theme="dos-86"` and an error Badge is red.
75
+
76
+ ## 3. Visible: body text in JetBrains Mono under `dos-86`
77
+
78
+ **What changed.** Under `dos-86` all non-heading component text (labels,
79
+ buttons, badges, inputs, menus, body copy, card text, timeline labels)
80
+ renders in JetBrains Mono Nerd Font, the body face. Real headings, display
81
+ numbers (Stat, Gauge and VitalsStrip values), window and dialog strip
82
+ titles, the wordmark and the Header brand keep the display face, Perfect DOS
83
+ VGA 437. Terminal and CommandPrompt keep the bitmap face. The size stays the
84
+ one body size (16px).
85
+
86
+ **What this means on a page.**
87
+
88
+ - The body face is about 20% wider than the display face at the same size,
89
+ so text wraps sooner in tight containers (narrow cards, table cells, phone
90
+ rows, fixed-width labels). Check those at 320 and 390.
91
+ - The body face has real weights: anything set bold renders bold. The
92
+ display face has one weight, so `font-weight` did nothing before. Remove
93
+ bold you did not mean.
94
+ - A site that stays on Pure Amber (section 4) keeps the display face
95
+ everywhere, exactly as in 0.46.
96
+
97
+ **What to do.** Look at dense pages and phone widths. Abbreviate labels
98
+ that now wrap (do not widen their containers). Use `font-dos-heading` for
99
+ your own headings if you want them in the display face under every theme;
100
+ `font-dos` follows the theme.
101
+
102
+ **How to verify.** Under `dos-86`, a Button label computes to
103
+ `"JetBrains Mono Nerd Font"` and an `<h1>` from `.dos-h1` to
104
+ `"Perfect DOS VGA 437"`.
105
+
106
+ ## 4. Keep Pure Amber as your default (two lines)
107
+
108
+ ```tsx
109
+ const THEMES = { dosDark: 'pure-amber' }; // pass to displayMenuItems and resolveDisplayTheme
110
+ ```
111
+
112
+ ```html
113
+ <html data-theme="pure-amber"> <!-- first paint, before hydration -->
114
+ ```
115
+
116
+ Both lines are needed: the first keeps the menu and the resolved theme on
117
+ Pure Amber, the second keeps the first paint from flashing another theme.
118
+ Pure Amber resolves exactly as the default did in 0.46 (a test in the
119
+ package pins every colour, shadow and focus-ring value). LIGHT still picks
120
+ `amber-paper`: the default light theme follows the dark theme, so a Pure Amber
121
+ site keeps `amber-paper` exactly as on 0.46, while a `dos-86` site gets
122
+ `dos-86-light`. To offer both, pass `{ dosDark: 'dos-86', dosPure: 'pure-amber' }`
123
+ (DOS-86 by default, a PURE switch for Pure Amber) or
124
+ `{ dosDark: 'pure-amber', dosPure: 'dos-86' }` (the other way round).
125
+
126
+ A site that passes only `dosPure: 'pure-amber'` now gets the PURE row by
127
+ default (before, the default dark theme was Pure Amber itself, so there was
128
+ nothing to switch).
129
+
130
+ ## 4b. Visible: LIGHT on a `dos-86` site is `dos-86-light`
131
+
132
+ **What changed.** `resolveDisplayTheme()` and `displayMenuItems()` default
133
+ `dosLight` from the dark theme: `dos-86-light` when the resolved `dosDark` is
134
+ `dos-86`, `amber-paper` otherwise. `dos-86-light` is `amber-paper` with the
135
+ body face (JetBrains Mono Nerd Font) for non-heading text, so toggling LIGHT
136
+ no longer changes the width of the header on a `dos-86` site (DisplayMenu
137
+ trigger 151px vs 144px at 1280 before). Colours are identical to
138
+ `amber-paper`. The theme ships inside `eidotter/themes/amber-paper.css`; the
139
+ new export `eidotter/themes/dos-86-light.css` points at the same file.
140
+
141
+ **What to do.** Use the helper: nothing else. A site that sets `data-theme`
142
+ itself from the helper gets the new name. A site that hard-codes
143
+ `data-theme="amber-paper"` for LIGHT keeps the old look and the old shift;
144
+ switch it to `dos-86-light` if its dark theme is `dos-86`. Pass
145
+ `dosLight: 'amber-paper'` to keep `amber-paper` on a `dos-86` site. Anything
146
+ that matches `[data-theme="amber-paper"]` in your own CSS needs
147
+ `[data-theme="dos-86-light"]` added.
148
+
149
+ **Still shifts by design.** `dos-86` to `pure-amber` (the PURE switch) and
150
+ `dos-86` to `light` (the DOS switch on a site with a modern theme) change
151
+ the text face, so the header changes width there.
152
+
153
+ ## 5. Not changed: a page that sets no `data-theme`
154
+
155
+ The bare `:root` of `tokens.css` is unchanged. A page that never sets
156
+ `data-theme` renders exactly as on 0.46: neither Pure Amber nor `dos-86`, but
157
+ the token defaults (secondary-amber body text `#B87C1A`, ground `#020003`, a
158
+ mix of amber and honest functional roles). This was already true before
159
+ 0.47: the default theme has always applied through the `data-theme`
160
+ attribute. To get a theme, set `data-theme="dos-86"` or
161
+ `data-theme="pure-amber"` on `<html>`.
162
+
163
+ ## 6. Deprecated: the name `amber-mono`
164
+
165
+ `amber-mono` is the old name of Pure Amber. `data-theme="amber-mono"`,
166
+ `.theme-amber-mono`, `eidotter/themes/amber-mono.css` and
167
+ `dosDark: 'amber-mono'` keep working for at least two minors and select the
168
+ same rule and file as `pure-amber`. There is no runtime warning. Replace
169
+ them with `pure-amber`.
170
+
171
+ ## 7. Visible: calmer CRT effects under `dos-86`
172
+
173
+ **What changed.** Under `dos-86` the effect tokens take the long-reading
174
+ values without a `preset` prop: scanlines 0.20 at a 3px pitch and still (no
175
+ drift), no flicker, aperture grille 0.06 (faint vertical red, green and blue
176
+ stripes), vignette 0.22 at spread 0.20, bloom 0.22 when `bloom` is on. Pure
177
+ Amber and the other themes keep the 0.46 values. Effects still render only
178
+ where you mount `RetroEffects`; nothing appears on a site that does not.
179
+
180
+ **What to do.** Nothing, unless you want the old monitor under `dos-86`:
181
+ redefine the tokens on `<html>` (for example
182
+ `--effect-scanline-intensity: 0.6`), or turn the grille off with
183
+ `<RetroEffects mask={false} />`. Do not add an effects toggle to a site.
184
+
185
+ **Glow.** The glow stays per element (`glowMode="element"`, the default).
186
+ `glowMode="sampled"` (glow sampled from the rendered picture, an SVG filter
187
+ on the html element) is opt-in under every theme: it costs scroll
188
+ performance on long pages without GPU rasterisation.
189
+
190
+ **How to verify.** Under `dos-86` the scanlines do not move and nothing
191
+ flickers; dev tools show `--effect-mask-intensity` resolving to `0.06` on
192
+ the overlay.
193
+
194
+ ## Checklist
195
+
196
+ 1. Bump to `^0.47.0` and commit the lockfile.
197
+ 2. Decide the site's default: `dos-86` (do nothing) or Pure Amber (section 4).
198
+ 3. Put the default in one named constant that feeds `displayMenuItems`,
199
+ `resolveDisplayTheme` and the first-paint `data-theme`.
200
+ 4. Look at alerts, notifications, badges, form errors, destructive buttons and
201
+ the health components under the chosen default; under `dos-86` also check
202
+ wrapping and bold in tight containers at 320 and 390 (section 3).
203
+ 5. Replace `amber-mono` with `pure-amber` in markup, CSS and imports.
204
+ 6. If you mount `RetroEffects`, check the calmer monitor under `dos-86`.
205
+
206
+ ## Jumping several versions
207
+
208
+ Walk the earlier guides first. The theme helpers this guide talks about
209
+ arrived in 0.46.0 and DisplayMenu in 0.45.0.
@@ -38,6 +38,7 @@ node_modules/eidotter/migrations/0.43.0.md
38
38
  node_modules/eidotter/migrations/0.44.0.md
39
39
  node_modules/eidotter/migrations/0.45.0.md
40
40
  node_modules/eidotter/migrations/0.46.0.md
41
+ node_modules/eidotter/migrations/0.47.0.md
41
42
  ```
42
43
 
43
44
  It is also exported, so tooling can resolve a guide by path:
@@ -52,3 +53,4 @@ It is also exported, so tooling can resolve a guide by path:
52
53
  | [0.44.0](./0.44.0.md) | Headings never AI-marked; `PageShell` inherits background and font; one-word Header brand never splits; `CmdPalette` cursor removed; adopt `LegalPage` `embedded` |
53
54
  | [0.45.0](./0.45.0.md) | Header brand title never wraps (the icon drops first); `Switch` label colour follows the theme; adopt `DisplayMenu` as the one theme control |
54
55
  | [0.46.0](./0.46.0.md) | One body size (16px) in every component; flush-left page column; non-sticky Header shows the page ground; adopt `HeaderButton` and the display theme helpers |
56
+ | [0.47.0](./0.47.0.md) | The default theme is `dos-86` (honest functional colours, body face for non-heading text, calmer CRT effects, `dos-86-light` for LIGHT); keep Pure Amber with `dosDark: 'pure-amber'` plus `data-theme="pure-amber"`; `amber-mono` is a deprecated alias of `pure-amber` |
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "eidotter",
3
- "version": "0.46.0",
3
+ "version": "0.47.0",
4
4
  "type": "module",
5
5
  "description": "A DOS Themed Design System",
6
6
  "main": "./dist/index.umd.js",
@@ -33,13 +33,17 @@
33
33
  "./fonts.css": "./src/styles/fonts.css",
34
34
  "./tokens.css": "./src/styles/tokens.css",
35
35
  "./shadcn.css": "./src/styles/shadcn.css",
36
- "./themes/amber-mono.css": "./src/styles/theme.amber-mono.css",
36
+ "./themes/pure-amber.css": "./src/styles/theme.pure-amber.css",
37
+ "./themes/amber-mono.css": "./src/styles/theme.pure-amber.css",
38
+ "./themes/dos-86.css": "./src/styles/theme.dos-86.css",
37
39
  "./themes/cga-amber.css": "./src/styles/theme.cga-amber.css",
38
40
  "./themes/cga-mode4-p0.css": "./src/styles/theme.cga-mode4-p0.css",
39
41
  "./themes/cga-mode4-p1.css": "./src/styles/theme.cga-mode4-p1.css",
40
42
  "./themes/cga-mode5.css": "./src/styles/theme.cga-mode5.css",
41
43
  "./themes/light.css": "./src/styles/theme.light.css",
42
44
  "./themes/amber-paper.css": "./src/styles/theme.amber-paper.css",
45
+ "./themes/dos-86-light.css": "./src/styles/theme.amber-paper.css",
46
+ "./terminal/*": "./dist/terminal/*",
43
47
  "./icons": {
44
48
  "types": "./dist/icons/published.d.ts",
45
49
  "import": "./dist/icons/published.js"
@@ -62,6 +66,7 @@
62
66
  "dist/utils",
63
67
  "dist/hooks",
64
68
  "dist/icons",
69
+ "dist/terminal",
65
70
  "tailwind.preset.cjs",
66
71
  "public/favicon.svg",
67
72
  "src/styles/fonts.css",
@@ -82,12 +87,13 @@
82
87
  ],
83
88
  "scripts": {
84
89
  "dev": "vite",
85
- "build": "vite build && node scripts/flatten-css-layers.mjs && node scripts/externalize-fonts.mjs && tsc -p tsconfig.build.json && npm run build-components && npm run build-icons",
90
+ "build": "vite build && node scripts/flatten-css-layers.mjs && node scripts/externalize-fonts.mjs && tsc -p tsconfig.build.json && npm run build-components && npm run build-icons && npm run build-terminal",
86
91
  "build-components": "tsc -p tsconfig.components.json && node scripts/finalize-component-emit.mjs",
87
92
  "build-icons": "node scripts/icons/build-barrels.mjs && tsc -p tsconfig.icons.json",
88
93
  "fetch-icons": "node scripts/icons/fetch-svgs.mjs",
89
94
  "generate-icons": "node scripts/icons/build-tsx.mjs && node scripts/icons/build-barrels.mjs",
90
95
  "prepublishOnly": "npm run build",
96
+ "build-terminal": "node style-dictionary.config.mjs --only=terminal",
91
97
  "build-tokens": "node style-dictionary.config.mjs && node scripts/generate-shadcn-shim.mjs && node scripts/generate-tailwind-safelist.mjs",
92
98
  "lint": "eslint src/ --report-unused-disable-directives --max-warnings 0",
93
99
  "lint-tokens": "node scripts/lint-token-refs.mjs",
@@ -147,7 +153,7 @@
147
153
  "devDependencies": {
148
154
  "@eslint/js": "^10.0.1",
149
155
  "@figma/plugin-typings": "^1.142.0",
150
- "@figma/rest-api-spec": "^0.45.0",
156
+ "@figma/rest-api-spec": "^0.46.0",
151
157
  "@storybook/addon-a11y": "^10.2.7",
152
158
  "@storybook/addon-designs": "^12.0.0",
153
159
  "@storybook/addon-docs": "^10.2.7",
@@ -169,7 +175,7 @@
169
175
  "axe-playwright": "^2.2.2",
170
176
  "chromatic": "^18.13.2",
171
177
  "cross-env": "^10.1.0",
172
- "dotenv": "^17.3.1",
178
+ "dotenv": "^18.0.9",
173
179
  "eslint": "^10.13.0",
174
180
  "eslint-plugin-react-hooks": "^7.0.1",
175
181
  "figma-js": "^1.16.1-0",
@@ -182,7 +188,7 @@
182
188
  "postcss": "^8.5.8",
183
189
  "remark-gfm": "^4.0.1",
184
190
  "storybook": "^10.2.7",
185
- "style-dictionary": "5.5.2",
191
+ "style-dictionary": "5.7.0",
186
192
  "tailwindcss": "^4.3.3",
187
193
  "tailwindcss-react-aria-components": "^2.0.1",
188
194
  "ts-jest": "^29.4.15",
@@ -26,15 +26,25 @@
26
26
  * ========================================================================== */
27
27
 
28
28
  /* Display tier — Perfect DOS VGA 437 (single-weight; pixel-perfect vectors).
29
- * Applied at zero specificity via :where() so consumer overrides win. */
29
+ * Applied at zero specificity via :where() so consumer overrides win.
30
+ * Headings read the heading family, always the display face (DMNC-1643). The
31
+ * page shell, labels and code read the component text family, which is the
32
+ * display face too except where a theme points it at the body face (dos-86). */
30
33
  :where(
31
- .dos-page,
32
34
  .dos-hero,
33
35
  .dos-h1,
34
36
  .dos-h2,
35
37
  .dos-h3,
36
38
  .dos-h4,
37
- .dos-h5,
39
+ .dos-h5
40
+ ) {
41
+ font-family: var(--typography-font-family-heading), var(--typography-font-family-fallback);
42
+ font-weight: var(--typography-font-weight-regular, 400);
43
+ font-synthesis: none;
44
+ }
45
+
46
+ :where(
47
+ .dos-page,
38
48
  .dos-label,
39
49
  .dos-code
40
50
  ) {
@@ -48,7 +48,7 @@
48
48
  --chart-5: 34 100% 30%;
49
49
  }
50
50
 
51
- [data-theme="amber-mono"], .theme-amber-mono {
51
+ [data-theme="pure-amber"], [data-theme="amber-mono"], .theme-pure-amber, .theme-amber-mono {
52
52
  --background: 280 100% 1%;
53
53
  --foreground: 41 100% 50%;
54
54
  --card: 240 50% 1%;
@@ -83,6 +83,41 @@
83
83
  --chart-5: 34 100% 30%;
84
84
  }
85
85
 
86
+ [data-theme="dos-86"], .theme-dos-86 {
87
+ --background: 36 100% 1%;
88
+ --foreground: 41 100% 50%;
89
+ --card: 240 50% 1%;
90
+ --card-foreground: 41 100% 50%;
91
+ --popover: 240 50% 1%;
92
+ --popover-foreground: 41 100% 50%;
93
+ --primary: 41 100% 50%;
94
+ --primary-foreground: 36 100% 1%;
95
+ --secondary: 240 50% 1%;
96
+ --secondary-foreground: 41 100% 50%;
97
+ --muted: 240 50% 1%;
98
+ --muted-foreground: 37 75% 41%;
99
+ --accent: 41 100% 50%;
100
+ --accent-foreground: 36 100% 1%;
101
+ --destructive: 0 100% 41%;
102
+ --destructive-foreground: 0 0% 100%;
103
+ --border: 41 100% 50%;
104
+ --input: 41 100% 50%;
105
+ --ring: 41 100% 50%;
106
+ --sidebar: 36 100% 1%;
107
+ --sidebar-foreground: 41 100% 50%;
108
+ --sidebar-primary: 41 100% 50%;
109
+ --sidebar-primary-foreground: 36 100% 1%;
110
+ --sidebar-accent: 240 50% 1%;
111
+ --sidebar-accent-foreground: 41 100% 50%;
112
+ --sidebar-border: 41 100% 50%;
113
+ --sidebar-ring: 41 100% 50%;
114
+ --chart-1: 41 100% 50%;
115
+ --chart-2: 37 75% 41%;
116
+ --chart-3: 27 96% 81%;
117
+ --chart-4: 120 100% 67%;
118
+ --chart-5: 34 100% 30%;
119
+ }
120
+
86
121
  [data-theme="cga-amber"], .theme-cga-amber {
87
122
  --background: 36 100% 1%;
88
123
  --foreground: 37 5% 66%;
@@ -258,7 +293,7 @@
258
293
  --chart-5: 33 17% 10%;
259
294
  }
260
295
 
261
- [data-theme="amber-paper"], .theme-amber-paper {
296
+ [data-theme="amber-paper"], [data-theme="dos-86-light"], .theme-amber-paper, .theme-dos-86-light {
262
297
  --background: 41 100% 50%;
263
298
  --foreground: 280 100% 1%;
264
299
  --card: 42 100% 45%;
@@ -2,7 +2,7 @@
2
2
  * Do not edit directly, this file was auto-generated.
3
3
  */
4
4
 
5
- [data-theme="amber-paper"], .theme-amber-paper {
5
+ [data-theme="amber-paper"], [data-theme="dos-86-light"], .theme-amber-paper, .theme-dos-86-light {
6
6
  --color-cga-black: #ffb000; /** Reverse video: the darkest CGA value becomes the amber ground. */
7
7
  --color-cga-blue: #2c1203; /** Amber monochrome */
8
8
  --color-cga-green: #411f06; /** Amber monochrome */
@@ -23,12 +23,12 @@
23
23
  --color-cga-amber-bright: #1a1000; /** Reverse video: hover/active peaks go darker, not lighter. */
24
24
  --color-cga-amber-dim: #7a4500; /** Reverse video: dim amber becomes mid brown (4.3:1 on ground, 3.5:1 on shade). */
25
25
  --color-cga-amber-glow: rgba(0, 0, 0, 0); /** Reverse video has no phosphor bloom: transparent, so raw amber-glow rules render nothing. */
26
- --color-cga-red-glow: rgba(255, 85, 85, 0.5); /** Red glow at 50% opacity */
27
- --color-cga-green-glow: rgba(85, 255, 85, 0.5); /** Green glow at 50% opacity */
28
- --color-cga-cyan-glow: rgba(85, 255, 255, 0.5); /** Cyan glow at 50% opacity */
29
- --color-cga-magenta-glow: rgba(255, 85, 255, 0.5); /** Magenta glow at 50% opacity */
30
- --color-cga-blue-glow: rgba(85, 85, 255, 0.5); /** Blue glow at 50% opacity */
31
- --color-cga-white-glow: rgba(255, 245, 224, 0.5); /** Warm white glow at 50% opacity */
26
+ --color-cga-red-glow: rgba(255, 85, 85, 0.5019607843137255); /** Red glow at 50% opacity */
27
+ --color-cga-green-glow: rgba(85, 255, 85, 0.5019607843137255); /** Green glow at 50% opacity */
28
+ --color-cga-cyan-glow: rgba(85, 255, 255, 0.5019607843137255); /** Cyan glow at 50% opacity */
29
+ --color-cga-magenta-glow: rgba(255, 85, 255, 0.5019607843137255); /** Magenta glow at 50% opacity */
30
+ --color-cga-blue-glow: rgba(85, 85, 255, 0.5019607843137255); /** Blue glow at 50% opacity */
31
+ --color-cga-white-glow: rgba(255, 245, 224, 0.5019607843137255); /** Warm white glow at 50% opacity */
32
32
  --color-cga-true-green: #00aa00; /** True CGA green — functional success / in-range. */
33
33
  --color-cga-true-red: #aa0000; /** True CGA red — functional error / out-of-range. */
34
34
  --color-cga-true-cyan: #00aaaa; /** True CGA cyan — functional info / sensor. */
@@ -104,3 +104,7 @@
104
104
  --effects-bloom-center: rgba(2, 0, 3, 0); /** No bloom on reverse video. */
105
105
  --effects-crt-background: #ffb000; /** CRT screen background, amber ground. */
106
106
  }
107
+
108
+ [data-theme="dos-86-light"], .theme-dos-86-light {
109
+ --typography-font-family-primary: var(--typography-font-family-body); /** Same declaration as theme.dos-86.tokens.json: the component text family points at the body face (JetBrains Mono Nerd Font), so toggling LIGHT on a dos-86 site does not change text width. Headings, display numbers and the brand keep the display face. */
110
+ }
@@ -22,13 +22,13 @@
22
22
  --color-cga-amber: #ffb000; /** P3 phosphor amber (602nm) */
23
23
  --color-cga-amber-bright: #fdca9f; /** P3 phosphor amber bright */
24
24
  --color-cga-amber-dim: #9a5700; /** P3 phosphor amber dim */
25
- --color-cga-amber-glow: rgba(255, 176, 0, 0.5); /** Amber glow at 50% opacity */
26
- --color-cga-red-glow: rgba(255, 85, 85, 0.5); /** Red glow at 50% opacity */
27
- --color-cga-green-glow: rgba(85, 255, 85, 0.5); /** Green glow at 50% opacity */
28
- --color-cga-cyan-glow: rgba(85, 255, 255, 0.5); /** Cyan glow at 50% opacity */
29
- --color-cga-magenta-glow: rgba(255, 85, 255, 0.5); /** Magenta glow at 50% opacity */
30
- --color-cga-blue-glow: rgba(85, 85, 255, 0.5); /** Blue glow at 50% opacity */
31
- --color-cga-white-glow: rgba(255, 245, 224, 0.5); /** Warm white glow at 50% opacity */
25
+ --color-cga-amber-glow: rgba(255, 176, 0, 0.5019607843137255); /** Amber glow at 50% opacity */
26
+ --color-cga-red-glow: rgba(255, 85, 85, 0.5019607843137255); /** Red glow at 50% opacity */
27
+ --color-cga-green-glow: rgba(85, 255, 85, 0.5019607843137255); /** Green glow at 50% opacity */
28
+ --color-cga-cyan-glow: rgba(85, 255, 255, 0.5019607843137255); /** Cyan glow at 50% opacity */
29
+ --color-cga-magenta-glow: rgba(255, 85, 255, 0.5019607843137255); /** Magenta glow at 50% opacity */
30
+ --color-cga-blue-glow: rgba(85, 85, 255, 0.5019607843137255); /** Blue glow at 50% opacity */
31
+ --color-cga-white-glow: rgba(255, 245, 224, 0.5019607843137255); /** Warm white glow at 50% opacity */
32
32
  --color-cga-true-green: #00aa00; /** True CGA green — functional success / in-range. */
33
33
  --color-cga-true-red: #aa0000; /** True CGA red — functional error / out-of-range. */
34
34
  --color-cga-true-cyan: #00aaaa; /** True CGA cyan — functional info / sensor. */
@@ -22,13 +22,13 @@
22
22
  --color-cga-amber: #ffff00;
23
23
  --color-cga-amber-bright: #ffff00;
24
24
  --color-cga-amber-dim: #00ff00;
25
- --color-cga-amber-glow: rgba(255, 255, 0, 0.5);
26
- --color-cga-red-glow: rgba(255, 85, 85, 0.5); /** Red glow at 50% opacity */
27
- --color-cga-green-glow: rgba(85, 255, 85, 0.5); /** Green glow at 50% opacity */
28
- --color-cga-cyan-glow: rgba(85, 255, 255, 0.5); /** Cyan glow at 50% opacity */
29
- --color-cga-magenta-glow: rgba(255, 85, 255, 0.5); /** Magenta glow at 50% opacity */
30
- --color-cga-blue-glow: rgba(85, 85, 255, 0.5); /** Blue glow at 50% opacity */
31
- --color-cga-white-glow: rgba(255, 245, 224, 0.5); /** Warm white glow at 50% opacity */
25
+ --color-cga-amber-glow: rgba(255, 255, 0, 0.5019607843137255);
26
+ --color-cga-red-glow: rgba(255, 85, 85, 0.5019607843137255); /** Red glow at 50% opacity */
27
+ --color-cga-green-glow: rgba(85, 255, 85, 0.5019607843137255); /** Green glow at 50% opacity */
28
+ --color-cga-cyan-glow: rgba(85, 255, 255, 0.5019607843137255); /** Cyan glow at 50% opacity */
29
+ --color-cga-magenta-glow: rgba(255, 85, 255, 0.5019607843137255); /** Magenta glow at 50% opacity */
30
+ --color-cga-blue-glow: rgba(85, 85, 255, 0.5019607843137255); /** Blue glow at 50% opacity */
31
+ --color-cga-white-glow: rgba(255, 245, 224, 0.5019607843137255); /** Warm white glow at 50% opacity */
32
32
  --color-cga-true-green: #00aa00; /** True CGA green — functional success / in-range. */
33
33
  --color-cga-true-red: #aa0000; /** True CGA red — functional error / out-of-range. */
34
34
  --color-cga-true-cyan: #00aaaa; /** True CGA cyan — functional info / sensor. */
@@ -22,13 +22,13 @@
22
22
  --color-cga-amber: #00ffff;
23
23
  --color-cga-amber-bright: #fffcf7;
24
24
  --color-cga-amber-dim: #00ffff;
25
- --color-cga-amber-glow: rgba(0, 255, 255, 0.5);
26
- --color-cga-red-glow: rgba(255, 85, 85, 0.5); /** Red glow at 50% opacity */
27
- --color-cga-green-glow: rgba(85, 255, 85, 0.5); /** Green glow at 50% opacity */
28
- --color-cga-cyan-glow: rgba(85, 255, 255, 0.5); /** Cyan glow at 50% opacity */
29
- --color-cga-magenta-glow: rgba(255, 85, 255, 0.5); /** Magenta glow at 50% opacity */
30
- --color-cga-blue-glow: rgba(85, 85, 255, 0.5); /** Blue glow at 50% opacity */
31
- --color-cga-white-glow: rgba(255, 245, 224, 0.5); /** Warm white glow at 50% opacity */
25
+ --color-cga-amber-glow: rgba(0, 255, 255, 0.5019607843137255);
26
+ --color-cga-red-glow: rgba(255, 85, 85, 0.5019607843137255); /** Red glow at 50% opacity */
27
+ --color-cga-green-glow: rgba(85, 255, 85, 0.5019607843137255); /** Green glow at 50% opacity */
28
+ --color-cga-cyan-glow: rgba(85, 255, 255, 0.5019607843137255); /** Cyan glow at 50% opacity */
29
+ --color-cga-magenta-glow: rgba(255, 85, 255, 0.5019607843137255); /** Magenta glow at 50% opacity */
30
+ --color-cga-blue-glow: rgba(85, 85, 255, 0.5019607843137255); /** Blue glow at 50% opacity */
31
+ --color-cga-white-glow: rgba(255, 245, 224, 0.5019607843137255); /** Warm white glow at 50% opacity */
32
32
  --color-cga-true-green: #00aa00; /** True CGA green — functional success / in-range. */
33
33
  --color-cga-true-red: #aa0000; /** True CGA red — functional error / out-of-range. */
34
34
  --color-cga-true-cyan: #00aaaa; /** True CGA cyan — functional info / sensor. */