BitSquare/Codeman
2
0
Fork 0
mirror of https://github.com/Ark0N/Codeman.git synced 2026-10-07 16:09:43 +02:00
Code Issues Packages Projects Releases Wiki Activity

fix(cli-registry): merge-time fixes for the run-button accents (#463)

Browse Source 
- mobile.css: gemini and antigravity run/gear rules get `!important` like
  pi/omp/grok/deepseek, so the gear half no longer keeps the skin accent
  while the body takes the mode colour (two-tone button on the default skin).
- test/skin-themes.test.ts: static guard that every run mode with a base
  `.btn-toolbar.btn-run.mode-<id>` rule also has a resting rule inside the
  `html:not([data-skin="og"])` block; ids are derived from the stylesheet.
- stock.ts: grok's accent comment names zinc-300 (border/badge colour);
  gemini's accent is #8ab4f8 to match its tab badge and run-mode dot, noted
  as the one exception to the border-colour method.
- types.ts: "(below)" -> "(above)".
- docs/cli-registry.md, CLAUDE.md: `accent` is now measured, not transcribed.

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
This commit is contained in:
Codeman maintainer
2026-09-23 11:40:03 +02:00
parent 13e652e43f
commit 10f87428c3
6 changed files with 58 additions and 24 deletions
Download Patch File Download Diff File Expand all files Collapse all files
src/web/public/mobile.css
+17 -16
View File
@@ -949,40 +949,41 @@ html.mobile-init .file-browser-panel {
border-color: rgba(16, 185, 129, 0.5);
}
/* Gemini mode colors on mobile */
/* Gemini mode colors on mobile. Same `!important` rationale as the pi block below. */
.btn-toolbar.btn-run.mode-gemini,
.btn-toolbar.btn-run-gear.mode-gemini {
background: #10243f;
border-color: rgba(96, 165, 250, 0.3);
color: #dbeafe;
background: #10243f !important;
border-color: rgba(96, 165, 250, 0.3) !important;
color: #dbeafe !important;
}
.btn-toolbar.btn-run.mode-gemini:active,
.btn-toolbar.btn-run-gear.mode-gemini:active {
background: #174ea6;
border-color: rgba(96, 165, 250, 0.5);
background: #174ea6 !important;
border-color: rgba(96, 165, 250, 0.5) !important;
}
/* Antigravity mode colors on mobile */
/* Antigravity mode colors on mobile. Same `!important` rationale as the pi block below. */
.btn-toolbar.btn-run.mode-antigravity,
.btn-toolbar.btn-run-gear.mode-antigravity {
background: #0b2b33;
border-color: rgba(34, 211, 238, 0.3);
color: #cffafe;
background: #0b2b33 !important;
border-color: rgba(34, 211, 238, 0.3) !important;
color: #cffafe !important;
}
.btn-toolbar.btn-run.mode-antigravity:active,
.btn-toolbar.btn-run-gear.mode-antigravity:active {
background: #0e7490;
border-color: rgba(34, 211, 238, 0.5);
background: #0e7490 !important;
border-color: rgba(34, 211, 238, 0.5) !important;
}
/* Pi mode colors on mobile.
`!important` is load-bearing here, not noise: styles.css nests its skin rules
inside `html:not([data-skin="og"])`, so a bare `.btn-toolbar.btn-run` in there
resolves to (0,2,1) and outranks this (0,2,0) `.mode-pi` pair regardless of
load order. The antigravity block right above omits it and is consequently
dead on every non-og skin (i.e. on the default) — do not copy that. */
inside `html:not([data-skin="og"])`, so a bare `.btn-toolbar.btn-run` or
`.btn-toolbar.btn-run-gear` in there outranks this `.mode-pi` pair regardless
of load order. Without it the gear half keeps the skin accent while the body
takes the nested block's mode colour, so the split button renders two-tone
(gemini and antigravity shipped that way until they got `!important` too). */
.btn-toolbar.btn-run.mode-pi,
.btn-toolbar.btn-run-gear.mode-pi {
background: #33121f !important;