Skip to main content

max / alloy

theme: fix stale comments and remap bottom cpu colors Drop two done items from the sway HANDOFF block: Mod+d is bound and the client.* colors already match TOKENS. Rewrite the starship [time] comment, which apologized for a "readouts in Departure" deviation that the mono-only pivot removed. Remap bottom's cpu_core_colors from status.* + chrome greys to category.one..six, so a per-core line is a categorical series rather than reading as an error and off the tones reserved for chrome.
Co-Authored-By
Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Author: Max Johnson <me@maxj.phd> · 2026-07-23 02:12 UTC
Signed with PGP, not checked
Commit: cc838f37a60526614d16f9f4cbaae2e6e5a1441e
Parent: 3c3a590
3 files changed, +15 insertions, -14 deletions
@@ -95,10 +95,10 @@
95 95 show_milliseconds = false
96 96
97 97 # -------------------------------------------------------------------
98 - # Right-aligned clock — display font role (readout, not chrome).
99 - # Kept in Iosevka since starship can't switch fonts per segment;
100 - # this is a small honest deviation from the "readouts in Departure"
101 - # rule that docs/TOKENS.md sanctions for terminal contexts.
98 + # Right-aligned clock — a readout, styled in text-muted so it reads as
99 + # metadata. Mono throughout: the two-font working/display split was
100 + # dropped in the 2026-07-17 pivot (docs/DESIGN-LANGUAGE.md#typography),
101 + # so a terminal segment in IosevkaTerm is the rule now, not a deviation.
102 102 # -------------------------------------------------------------------
103 103 [time]
104 104 disabled = false
@@ -50,13 +50,18 @@
50 50 [styles.cpu]
51 51 all_entry_color = "#1a1816"
52 52 avg_entry_color = "#222d38"
53 + # Per-core lines are a categorical series, not a status readout, so they draw
54 + # from the category.* palette (docs/TOKENS.md), not from status.* — a core is
55 + # not "erroring" because it happens to be the second one. This also keeps the
56 + # series off the greyscale chrome tones (text-muted, border-strong), which are
57 + # reserved for chrome, never data.
53 58 cpu_core_colors = [
54 - "#b07840", # accent-warn
55 - "#6a2828", # accent-error
56 - "#3a5830", # accent-ok
57 - "#222d38", # text-secondary
58 - "#514b45", # text-muted
59 - "#7f786d", # border-strong
59 + "#8a4530", # category.one
60 + "#3a5830", # category.two
61 + "#304050", # category.three
62 + "#b07840", # category.four
63 + "#806080", # category.five
64 + "#305858", # category.six
60 65 ]
61 66
62 67 [styles.memory]
@@ -7,10 +7,6 @@
7 7 # HANDOFF (scaffold — refine in Helix):
8 8 # - Bar: minimal swaybar placeholder below (clock only). Replace with
9 9 # a real status_command, waybar, or the future alloy console view.
10 - # - Launcher: Mod+D is commented out (anyrun was dropped). Bind a TUI
11 - # launcher when chosen.
12 - # - Palette: client.* colors are a first pass from the niri focus-ring
13 - # values — reconcile against docs/TOKENS.md.
14 10 # - Env vars: GTK/QT/MOZ backend hints live in
15 11 # ~/.config/environment.d/alloy.conf; verify they reach sway's
16 12 # children under greetd (see the live-verification GO task).