agentgui 1.0.1024 → 1.0.1026

package/.gm/.gm-continue-count

@@ -0,0 +1 @@
+1

package/.gm/memories/mem-0c444abde86202f6-1681.md

@@ -0,0 +1,8 @@
+---
+key: mem-0c444abde86202f6-1681
+ns: default
+created: 1783677428217
+updated: 1783677428217
+---
+
+agentgui 31st run addendum (2026-07-10): confirming gm-continue pass caught that the gui-ux-craft workflow's light-theme-contrast lens had crashed mid-run (API connection error) and never actually produced findings - a real coverage gap, not a clean pass. Dedicated follow-up audit computed real WCAG contrast ratios (not eyeballed) and found 6 genuine light-theme failures the crashed lens would have caught: chat avatar initials using raw --mascot/--accent-ink on tinted backgrounds (2.03:1/3.65:1), tool-done status text using --success/--green-2 (3.18:1/2.88:1) instead of the text-safe --green, --amber measuring 4.26:1 on --bg-2 (narrowly failing AA on the background it actually renders on, despite being tuned for --paper), --danger measuring 4.25:1 on --bg-2 for the same reason (auth-error banner), raw --mascot as button/CLI text (3.11:1), and --sun being essentially unusable everywhere it's used (1.1-1.5:1 against every app background) - retired in favor of --amber. All fixed with the same pattern as the 22nd-run --accent->--accent-ink precedent: separate text-safe 'deep' tokens from fill/border tokens, and always check contrast against the ACTUAL background a token renders on (--bg-2 card surfaces, not just --paper) not just the token's own design-time tuning target. LESSON for gm-continue: when a workflow notification includes a `failures` array naming a lens that errored out, that lens's scope is unaudited work, not a null result - it belongs in the confirming PLAN pass as its own row, the same as any other unaudited surface. Kit pushed df04d69, agentgui pushed 03002cf, CI green (Test/Deploy GH Pages/Publish and Release/Auto-Declaudeify all success).

package/.gm/memories/mem-3602d11d7bce9446-1057.md

@@ -0,0 +1,8 @@
+---
+key: mem-3602d11d7bce9446-1057
+ns: default
+created: 1783677456828
+updated: 1783677456828
+---
+
+agentgui Live History Stream Wiring (2026-05-05): site/app/js/app.js opens an SSE EventSource on navTo('history') via B.streamHistory(base, onEvent) and closes it on tab exit; state.live = {es, connected, lastEventTs, error, eventCount}. Event dispatch loop: 'hello' sets connected=true; 'event' pushes into state.events + increments the matching session counter only when data.sid===selectedSid; 'conversation' calls refreshHistory() to reload the session list; 'error' sets live.error. Renders are throttled via requestAnimationFrame to avoid an event-storm during burst loads. The FIRST request to any /v1/history/* endpoint triggers ccsniff's loadOnce(), a synchronous walk of every JSONL file under ~/.claude/projects (override via CLAUDE_PROJECTS_DIR) - in the original test env this was 299 files/80MB/69k events, a 30-90s startup latency during which health-check timeouts are normal and expected; subsequent requests are fast (cached index). The endpoints are served by ccsniff's Express router mounted in-process from server.js, no external proxy.

package/.gm/prd.yml

@@ -2550,3 +2550,35 @@
   subject: FileRow native selection prop names (marked/onMark) diverge from shared selected/onToggleSelect contract
   witness: design/src/components/files.js FileRow+FileCell params renamed marked/onMark->selected/onToggleSelect internally; FileGrid own marked/onMark stay as documented public compat alias (COMPONENT_API.md:112); kit build 0 lint errors; browser-witnessed checkbox select-all/individual/clear-selection + BulkBar flow at localhost:3010/gm/#tab=files, 0 console errors
   status: completed
+- id: light-theme-contrast-audit
+  subject: gui-ux-craft workflow hunt:light-theme-contrast lens failed (API error, connection closed mid-response) and never produced findings - light theme contrast was never actually audited this run
+  witness: dedicated audit agent computed real WCAG contrast ratios (not eyeballed) for every light-theme token pairing, found 6 real failures (avatar text x2, tool-done status, amber on bg-2, danger on bg-2, mascot btn/cli, sun unusable) all landed as separate resolved rows; kit pushed df04d69
+  status: completed
+- id: contrast-aicat-avatar-mascot
+  subject: chat.css:2159 .chat-msg.aicat .chat-avatar initials use raw --mascot (2.03:1) on tinted bg, fails 4.5:1
+  witness: design/app-shell.css:2163 color changed from var(--mascot) to var(--mascot-deep) (5.45:1 vs 2.03:1); kit build+lint clean, browser-witnessed data-theme=paper served CSS contains mascot-deep at that rule
+  status: completed
+- id: contrast-you-avatar-accent-ink
+  subject: chat.css:2156 .chat-msg.you .chat-avatar --accent-ink on tinted bg measures 3.65:1, short of 4.5:1
+  witness: design/app-shell.css:2158 tint mix reduced from 26pct to 18pct (lighter bg raises contrast against fixed --accent-ink text); kit build clean
+  status: completed
+- id: contrast-tool-done-success-text
+  subject: chat.css:878 tool-done status text uses --success/--green-2 (3.18:1 paper, 2.88:1 bg-2), fails 4.5:1 for text
+  witness: design/chat.css:878 tool-done status text color changed var(--success)->var(--green) (5.18:1 vs 3.18:1/2.88:1), fill background kept on --success for the 3:1-only non-text tint
+  status: completed
+- id: contrast-amber-dash-status-bg2
+  subject: chat.css:584,772 --amber status text on .ds-dash-card (bg-2) measures 4.26:1, narrowly fails 4.5:1 AA on the bg it actually renders on
+  witness: 'design/colors_and_type.css:54 --amber #8A6512->#7C570F (computed 5.21:1 on --bg-2 vs prior 4.26:1), also updated print-media duplicate at app-surfaces.css:222; browser-witnessed live getComputedStyle --amber == #7C570F'
+  status: completed
+- id: contrast-danger-auth-error-bg2
+  subject: app-shell.css:4247 .ds-auth-error --danger text on --panel-1(=bg-2) measures 4.25:1, fails AA on actual render background (PASSWORD-gate login error banner)
+  witness: design/colors_and_type.css:67 --danger oklch lightness 0.55->0.50 for AA margin on --bg-2 (was 4.25:1); browser-witnessed live getComputedStyle --danger == oklch(0.50 0.18 25)
+  status: completed
+- id: contrast-mascot-btn-cli-text
+  subject: app-shell.css:4215,4289 raw --mascot used as button/CLI text (3.11:1), fails 4.5:1; icon-only raw-mascot uses are fine (non-text 3:1)
+  witness: design/app-shell.css:4215,4291 .ds-btn-mascot and .ds-cli-warn text color changed var(--mascot)->var(--mascot-deep) (5.45:1 vs 3.11:1); icon-only raw-mascot non-text uses left untouched per audit
+  status: completed
+- id: contrast-sun-unusable-retire
+  subject: --sun (#F5C344) measures 1.46:1 paper/1.32 bg-2/1.14 bg-3, fails even 3:1 non-text everywhere used (toast border, tree-node border, community spinner/text)
+  witness: design/app-shell.css:3162(toast.warning border),3875(tree-node is-prd-add border) and community.css:364(voice-connecting text),385-386(spinner border) all switched var(--sun)->var(--amber); --sun measured 1.1-1.5:1 everywhere used, --amber now 5.21:1 text-safe
+  status: completed

package/AGENTS.md

@@ -1,5 +1,9 @@
 # AgentGUI — Agent Notes
 
+## Light-theme contrast fixes (2026-07-10) — thirty-first run, confirming pass addendum
+
+The 31st run's `gui-ux-craft` workflow had a `failures` array naming `hunt:light-theme-contrast` as crashed (API connection error) — that lens never ran, so light theme was never actually audited despite the workflow otherwise completing. Caught during the mandatory `gm-continue` confirming pass, not the original run. A dedicated follow-up agent computed real WCAG contrast ratios (not eyeballed) and found 6 genuine failures: chat avatar initials on raw `--mascot`/`--accent-ink` over tinted backgrounds (2.03:1/3.65:1), tool-done status text on `--success`/`--green-2` (3.18:1 paper / 2.88:1 on the card bg it actually renders on), `--amber` measuring only 4.26:1 on `--bg-2` despite being tuned for 4.5+:1 on `--paper`, `--danger` the same shape (4.25:1 on `--bg-2`, the PASSWORD-gate auth-error banner), raw `--mascot` as button/CLI text (3.11:1), and `--sun` being unusable everywhere it's used (1.1-1.5:1 against every app background) — retired in favor of `--amber`. Same fix pattern as the 22nd run's `--accent`->`--accent-ink` precedent: a separate text-safe "deep"/darkened token for text, the original stays for fills/borders (3:1 threshold). **Standing rule: always check a color token's contrast against the ACTUAL background it renders on in the real DOM (e.g. a status pill's tinted card, not just the page's base `--paper`) — a token tuned and commented as "4.5+:1 on paper" can still fail AA on every card/panel surface built on top of `--bg-2`/`--bg-3`.** **gm-continue standing rule: a workflow notification's `failures` array naming a crashed lens is unaudited scope, not a null result — it goes into the confirming PLAN pass as its own row, same as any unaudited surface.** Kit pushed `df04d69`, agentgui pushed `03002cf`, all 4 CI workflows green.
+
 ## Maximal usability/negative-space/predictability sweep (2026-07-10) — thirty-first run
 
 User asked to "max the gui usability practicality... predictable, good looking, use negative space properly" via wfgy-method-grade critique. Ran a fresh `gui-ux-craft` workflow (32 agents, 19 confirmed) plus a targeted live-browser negative-space audit agent in parallel, then landed the highest-value findings from both. Kit (`../design`): ConfirmDialog `destructive` prop was dead code (delete confirms always rendered `primary`, never `danger`) — real predictability bug, fixed + browser-witnessed the delete dialog button now carries `btn-primary danger`. Settings panels had a 56px gap between stacked Panels (32px `.panel` margin + 24px grid gap stacking) vs 24px everywhere else — zeroed the margin inside `.settings-grid`, witnessed 24px consistent. `.ds-page-header-dense-lede` and `.chat-composer-context` both hard-clipped with `nowrap`+ellipsis at <=480px with no way to recover the text — both now wrap at that breakpoint (kept desktop's single-line ellipsis). History empty-state sub-line used the misapplied `.lede` (fs-xl) style, rendering LARGER than its own title — removed the misapplied class + fixed the title's own hardcoded `1.05rem` to `var(--fs-lg)` token. Small-caps section labels (`panel-head`, `table th`) drifted from the canonical `.t-label` size (`--fs-xs` vs `--fs-tiny`) — unified. `FileRow`/`FileCell` internal selection props renamed `marked/onMark` -> `selected/onToggleSelect` to match the shared multi-select contract (FileGrid's own `marked`/`onMark` stay as its documented public alias). `ConversationList` search-mode blew away already-visible rows to a full skeleton on every debounced re-search — guarded on `!sessions.length`, matching `files.js`'s sibling pattern. App copy-tone: "sidebar" (used nowhere else) -> "the rail"; internal-jargon `agent: 'external session'` -> `'other tool'`; "session" -> "conversation" vocabulary unified across resume banner/toasts/labels; raw sid slice in resume banner replaced with a human session-title lookup (`resumeSidLabel()`), falling back to the slice only when no title is known; settings projects-folder fact gained the same copy button its sibling root rows already had. Perf: `prism-core.min.js` (a classic UMD script, not an ES module) now gets a `rel=preload as=script` hint alongside the existing `modulepreload` hints for marked/dompurify; History tab re-fetch on every entry now gated on staleness (>5s) instead of unconditional; bulk file delete/move patch `state.files.entries` locally and render immediately instead of awaiting a second full directory round-trip (backgrounded as reconciliation) — scoped to the bulk paths only, the highest-traffic case. Kit docs: README gained a "multi-agent chat shell" bullet naming the flagship `WorkspaceShell`/`AgentChat`/etc surface (previously undiscoverable from a first read), `COMPONENT_API.md` documents `FileRow`'s `move` action and scopes the `freddie.js` re-exports as demo-site-only. **A concurrent gm session was independently working the same `../design` repo this run — its commits (`df5b566`..`68b615b`) landed my kit edits before I reached CONSOLIDATE; verified via `git log`/`rev-parse HEAD==origin/main` rather than re-pushing.** Browser-witnessed every fix live at 1280px+420px on a no-PASSWORD localhost:3010 instance (settings gaps, empty-state hierarchy, danger delete button, mobile wrap, files checkbox/BulkBar flow after the prop rename): 0 console errors throughout. **Standing rule reaffirmed: `prd-resolve` witness_evidence must be distinct per row — a byte-identical witness across rows is refused by plugkit as a rubber-stamp tell; write what THAT row specifically changed, every time.**
@@ -222,21 +226,7 @@ Surfaced 2026-05-04 while validating the chat surface in `site/app/`. Fix applie
 
 ## Live History Stream Wiring (2026-05-05)
 
-**`site/app/js/app.js` opens SSE EventSource on navTo('history'); first /v1/history/* request triggers 30-90s loadOnce() synchronous walk.**
-
-The live history feature wires the in-process ccsniff `/v1/history/stream` SSE endpoint via `B.streamHistory(base, onEvent)` on tab entry and closes the EventSource on tab exit. State shape: `state.live = { es, connected, lastEventTs, error, eventCount }`.
-
-Event dispatch loop:
-- `hello` event: set `connected=true`
-- `event` event: if `data.sid === selectedSid` push into `state.events`, increment matching session counter
-- `conversation` event: call `refreshHistory()` to reload session list
-- `error` event: set `live.error`
-
-Throttle renders via `requestAnimationFrame` to avoid event storm during burst loads.
-
-**First request to `/v1/history/*` triggers loadOnce() that walks all JSONL files under ~/.claude/projects** (env default; override with `CLAUDE_PROJECTS_DIR`). In our test env: 299 files, 80MB, 69k events -> 30-90s startup latency. Health check timeouts during this window are normal and expected. Subsequent requests are fast (cached index).
-
-The endpoints are served by ccsniff's Express router mounted in-process from `server.js`. No external proxy.
+`site/app/js/app.js` opens an SSE EventSource on `navTo('history')` (`B.streamHistory`, `state.live` shape, hello/event/conversation/error dispatch, rAF-throttled renders) against ccsniff's in-process `/v1/history/stream`; first `/v1/history/*` request triggers a 30-90s synchronous JSONL walk (`CLAUDE_PROJECTS_DIR`) — health-check timeouts during that window are normal. Full detail in rs-learn (recall "agentgui Live History Stream Wiring").
 
 ## Runtime CDN: GUI loaded from unpkg (2026-05-29)
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "agentgui",
-  "version": "1.0.1024",
+  "version": "1.0.1026",
   "description": "Multi-agent ACP client with real-time communication",
   "type": "module",
   "main": "electron/main.js",

package/site/app/vendor/anentrypoint-design/247420.css

@@ -53,7 +53,10 @@
      the originals (#FF5A1F / #D9A93A) which were tuned on ink and fail on
      paper (2.9:1 / 2.0:1). */
   --flame:       #C53E00;
-  --amber:       #8A6512;
+  /* #8A6512 measured 4.5+:1 on --paper but only 4.26:1 on --bg-2, which the
+     dashboard card status text actually renders on - darkened for margin on
+     both backgrounds (5.21:1 on --bg-2). */
+  --amber:       #7C570F;
   --sky:         #3A6EFF;
   --warn:        #E0241A;
   /* Syntax-token aliases: light values pass 4.5:1 on paper; the dark blocks
@@ -63,7 +66,9 @@
   --code-fn:      #B84300;
   --code-str-alt: var(--mascot-deep);
   --code-num:     #946300;
-  --danger:      oklch(0.55 0.18 25);
+  /* 0.55 lightness measured 4.70:1 on --paper but only 4.25:1 on --bg-2 (the
+     auth-error banner's actual background) - darkened for AA margin on both. */
+  --danger:      oklch(0.50 0.18 25);
   --success:     var(--green-2);
   --live:        var(--green);
 
@@ -2661,12 +2666,12 @@
 }
 .ds-247420 .chat-msg:hover .chat-avatar { transform: scale(1.03); box-shadow: 0 1px 4px color-mix(in oklab, var(--fg) 6%, transparent); }
 .ds-247420 .chat-msg.you .chat-avatar {
-  background: color-mix(in oklab, var(--accent) 26%, var(--bg-3));
+  background: color-mix(in oklab, var(--accent) 18%, var(--bg-3));
   color: var(--accent-ink);
 }
 .ds-247420 .chat-msg.aicat .chat-avatar {
   background: color-mix(in oklab, var(--mascot) 26%, var(--bg-2));
-  color: var(--mascot);
+  color: var(--mascot-deep);
 }
 
 .ds-247420 .chat-stack {
@@ -3654,7 +3659,10 @@
 
 .ds-247420 .toast.error { border-color: var(--warn); }
 .ds-247420 .toast.success { border-color: var(--green-2); }
-.ds-247420 .toast.warning { border-color: var(--sun); }
+/* --sun measures well under 3:1 against every app background (1.1-1.5:1) -
+   a border effectively invisible in light theme; --amber is the tuned sibling
+   warning tone already used for this exact severity elsewhere. */
+.ds-247420 .toast.warning { border-color: var(--amber); }
 
 @media (max-width: 480px) {
   .ds-247420 .toast {
@@ -4363,7 +4371,7 @@
 .ds-247420 .ds-tree-node.is-phase { border-color: var(--accent); background: var(--bg-3); font-weight: 600; }
 .ds-247420 .ds-tree-node.is-deviation { border-color: var(--warn); background: var(--danger-surface); color: var(--warn); }
 .ds-247420 .ds-tree-node.is-mutable-resolve { border-color: var(--success); }
-.ds-247420 .ds-tree-node.is-prd-add { border-color: var(--sun); }
+.ds-247420 .ds-tree-node.is-prd-add { border-color: var(--amber); }
 .ds-247420 .ds-tree-node-ts { margin-right: 8px; color: var(--fg-3); }
 .ds-247420 .ds-tree-node-pills { margin-left: 6px; }
 .ds-247420 .ds-tree-node-reason { margin-top: 2px; color: var(--fg-2); }
@@ -4706,7 +4714,9 @@
 .ds-247420 .ds-toggle-btn { min-width: 78px; }
 .ds-247420 .ds-toggle-label { margin-left: 8px; color: inherit; opacity: 0.7; }
 .ds-247420 .ds-btn-warn { color: var(--warn); }
-.ds-247420 .ds-btn-mascot { color: var(--mascot); }
+/* Raw --mascot text measures 3.11:1 on paper (fails 4.5:1); --mascot-deep is
+   the text-safe tone, same accent/accent-ink split used everywhere else. */
+.ds-247420 .ds-btn-mascot { color: var(--mascot-deep); }
 .ds-247420 .ds-savebar {
   position: sticky; bottom: 8px; display: flex; align-items: center;
   justify-content: flex-end; gap: 8px; flex-wrap: wrap; padding: 10px;
@@ -4780,7 +4790,7 @@
 .ds-247420 .ds-cli-cmt .cmd { color: var(--fg-3); }
 .ds-247420 .ds-cli-out .cmd { color: var(--fg-2); }
 .ds-247420 .ds-cli-ok .prompt, .ds-247420 .ds-cli-ok .cmd { color: var(--accent-ink); }
-.ds-247420 .ds-cli-warn .prompt, .ds-247420 .ds-cli-warn .cmd { color: var(--mascot); }
+.ds-247420 .ds-cli-warn .prompt, .ds-247420 .ds-cli-warn .cmd { color: var(--mascot-deep); }
 .ds-247420 .ds-cli-log .prompt { color: var(--fg-3); }
 .ds-247420 .ds-cli-log .cmd { color: var(--fg-2); font-family: var(--ff-mono); }
 .ds-247420 .ds-term-body { padding: 14px 18px; display: flex; flex-direction: column; gap: 4px; background: var(--bg-2); border-radius: var(--r-1); }
@@ -5169,7 +5179,9 @@
 }
 
 .ds-247420 .cm-channel-item.voice-connecting {
-  color: var(--sun);
+  /* --sun measures 1.1-1.5:1 against every app background - amber is the
+     tuned text-safe warning tone used for this severity elsewhere. */
+  color: var(--amber);
 }
 
 .ds-247420 .cm-ch-icon {
@@ -5190,8 +5202,8 @@
   width: 12px;
   height: 12px;
   border-radius: 50%;
-  border: 2px solid color-mix(in oklab, var(--sun) 30%, transparent);
-  border-top-color: var(--sun);
+  border: 2px solid color-mix(in oklab, var(--amber) 30%, transparent);
+  border-top-color: var(--amber);
   flex-shrink: 0;
 }
 
@@ -7327,8 +7339,11 @@
 .ds-247420 .chat-msg .chat-tool.tool-running .chat-tool-status { color: var(--accent-ink); background: color-mix(in oklab, var(--accent) 12%, transparent); }
 .ds-247420 .chat-msg .chat-tool.tool-error .chat-tool-status { color: var(--flame); background: color-mix(in oklab, var(--flame) 12%, transparent); }
 /* Completed tool: a positive (success) tone so done reads distinctly from the
-   neutral pill and from the accent-toned running pill (--success = green-2). */
-.ds-247420 .chat-msg .chat-tool.tool-done .chat-tool-status { color: var(--success); background: color-mix(in oklab, var(--success) 12%, transparent); }
+   neutral pill and from the accent-toned running pill. --success/--green-2
+   measures under 4.5:1 as TEXT on paper/bg-2 (fine at 12%-tint fill/non-text
+   use) - --green is the text-safe deep tone, same split the accent/accent-ink
+   pair already uses. */
+.ds-247420 .chat-msg .chat-tool.tool-done .chat-tool-status { color: var(--green); background: color-mix(in oklab, var(--success) 12%, transparent); }
 .ds-247420 .chat-tool-body { border-top: var(--bw-hair) solid var(--rule); padding: var(--space-2) var(--space-3); display: flex; flex-direction: column; gap: var(--space-2); }
 /* details' intrinsic min-content sizing: an unbroken token in the pre must not
    widen the tool card past the bubble column. */
@@ -9240,7 +9255,7 @@
   /* Re-assert the paper-tuned signal tokens so token-derived foregrounds
      (status discs, error text, tool cards) print with light-theme colours
      rather than the dark-theme-derived values inherited under auto-dark. */
-  .ds-247420 { --flame:#C53E00; --amber:#8A6512; --warn:#E0241A; --sky:#3A6EFF; --bg:var(--paper); --fg:var(--ink); }
+  .ds-247420 { --flame:#C53E00; --amber:#7C570F; --warn:#E0241A; --sky:#3A6EFF; --bg:var(--paper); --fg:var(--ink); }
   .ds-247420 #app { min-height: auto; display: block; height: auto; }
   .ds-247420 .skip-link, .ds-247420 .status-dot, .ds-247420 .history-actions, .ds-247420 .chat-composer { display: none !important; }
   .ds-247420 .app, .ds-247420 .app-main, .ds-247420 .panel, .ds-247420 .chat, .ds-247420 .chat-thread {