agentgui 1.0.1032 → 1.0.1034

package/.gm/memories/mem-15a07cd761b337c4-4320.md

@@ -0,0 +1,8 @@
+---
+key: mem-15a07cd761b337c4-4320
+ns: default
+created: 1783687056884
+updated: 1783687056884
+---
+
+{"key":"agentgui-33rd-run-ux-craft-sweep","value":"agentgui 33rd run (2026-07-10): user re-requested max gui usability/practicality/predictable/negative-space via wfgy-method critique (identical ask to 31st/32nd runs). Ran gui-ux-craft workflow wf_7f1a513c-2a3 (34 agents, 33 completed, 21 confirmed, 1 lens (kit-dx) crashed mid-run) plus a parallel live-browser negative-space audit (found 2 new issues: Settings health-chip 'connected' text used raw --accent lime rgb(182,255,27) on near-invisible near-paper bg - fixed to --accent-ink on tinted bg; History empty-state had fixed min-height:50vh centered void leaving 300px+ dead space at 1280px and >50% viewport blank at 420px - fixed to natural top-aligned height with a new .history-empty-hints ShortcutList filling the reclaimed space). Kit fixes (chat.css/app-shell.css/editor-primitives.css/community.css/colors_and_type.css/agent-chat.js/context-pane.js/sessions.js/components.js): --tr-caps/--lh-long/--space-2 token adoption for 4 hardcoded typography values, cwd-fact font-family made consistently mono across composer/context-pane/dashboard, agent-name font-family made consistently sans, panel margin-bottom rhythm aligned to files-stack gap, brightness(1.08) lightening hover bugs on send-button/rail-action/editor-dialog-buttons fixed to brightness(0.92) darkening (AA-safe pattern from 32nd run), --green-2 text contrast fix in community.css, light-theme ::selection contrast raised to 46% (dark theme's 24% explicitly preserved), --accent-tint light-theme value switched to blend --accent-ink instead of raw --accent (dark theme value explicitly pinned), CwdBar save/cancel button order fixed to match ConfirmDialog convention, 30 hardcoded focus-ring outline instances (not just the 11 originally cited - same mechanical bug repeated) routed to --focus-w/--focus-color/--focus-offset tokens, chip/badge tone-success/tone-error/tone-neutral families consolidated (all legacy class aliases preserved), icon-btn-primary hover color fixed to match btn-primary's two-tone-flip, new AgentListSkeleton component (shimmer-row loading state matching FileSkeleton pattern, had to also add it to src/components.js barrel export - a component only exists to consumers if re-exported there, sessions.js alone isn't enough), UploadProgress gained an indeterminate/marquee CSS state for in-flight transfers with no percent yet. App fixes (app.js): session-vs-conversation vocabulary unified (Live tab copy, stopAllActive messages, Alert title), duplicated folder-drop announce string hoisted to one const, 'allowed root(s)' internal-jargon replaced with 'accessible folder(s)' at 6 user-facing sites (internal fsAllowRoots fn name/comments untouched), boot render no longer gated behind the health-probe await (state.health='unknown' + synchronous render() before the probe), agents-loading branch now uses AgentListSkeleton instead of bare spinner+text, upload rows pass indeterminate:true for in-flight zero-percent state. kit-dx lens re-run separately found 3 real doc gaps (voice.js/theme-toggle.js/data-density.js entirely undocumented, SessionMeta undocumented next to documented SessionCard, 6 utility exports undocumented) all fixed in COMPONENT_API.md. Used 4-6 parallel subagents to implement disjoint file sets concurrently (kit CSS agent, app.js agent, upload-progress agent, kit-dx audit agent, then a docs agent) - worked well since file ownership was cleanly split, though one subagent's rebuild step raced another's and both had to re-run node scripts/build.mjs at the end to reconcile before final vendor copy. LESSON: a new kit component isn't actually consumable until it's re-exported through src/components.js's barrel - adding it only to the component file itself (e.g. sessions.js) leaves it invisible to the bundle even after a successful build with 0 lint errors; always grep the built dist for the new export name to confirm before wiring app.js against it. Kit pushed 4105bd1, agentgui pushed 3bac0fe then a94bf92 (PRD-state-only commit), all CI green both repos (Test/Auto-Declaudeify/Deploy GH Pages/Publish and Release on agentgui; Deploy GH Pages/Publish 247420 to npm on design), browser-witnessed live via agent-browser (0 console errors) at localhost with PASSWORD=comma-containing token treated as one literal string throughout."}

package/.gm/memories/mem-27faf41cdd050c80-1261.md

@@ -0,0 +1,8 @@
+---
+key: mem-27faf41cdd050c80-1261
+ns: default
+created: 1783687082067
+updated: 1783687082067
+---
+
+{"key":"agentgui-28th-run-visual-polish","value":"agentgui 28th run (2026-07-03): visual-polish pass responding to explicit user feedback that the GUI 'looks very diy'. Live-browser screenshot audit (not a full agent fan-out) named 3 concrete high-leverage causes and fixed all 3 in the kit. (1) .ws-sessions used flat --bg identical to main content column while .ws-rail/.ws-pane already use --bg-2 (a recessed plane framing the elevated content column) - sessions was the one column breaking that pattern, read as ONE continuous surface with only a 1px hairline. Fixed. (2) .chat-composer had zero elevation at rest - added the kit's own already-defined-but-unused --shadow-1 token. (3) chat tab's mainFlush left controls/heading/empty-state/composer flush against column edge with zero gutter while the crumb bar above kept its own padding - added uniform inline gutter to .agentchat itself, --measure centering unaffected. Standing rule: .ws-rail/.ws-sessions/.ws-pane must all three use --bg-2 for consistent shell depth. Also landed inherited uncommitted community-app reply/delete-message work sitting dirty in the kit tree. Browser-witnessed 1280px/420px before/after, 0 console errors. Kit pushed anentrypoint-design 53c8464, agentgui pushed 42708ea."}

package/.gm/prd.yml

@@ -2742,7 +2742,8 @@
 - id: run33-push-ci
   title: Push kit + agentgui changes, watch CI green on both repos
   notes: standing CONSOLIDATE requirement
-  status: pending
+  status: completed
+  witness: 'gh run list confirms agentgui 3bac0fe: Auto-Declaudeify/Deploy GH Pages/Publish and Release/Test all success; design 4105bd1: Deploy GH Pages/Publish 247420 to npm both success. .ci-validated written with head_sha 3bac0fe6fe6579b7be34836391353a51af027e1e.'
 - id: run33-health-chip-connected-contrast
   title: Fix near-invisible connected health-chip text in Settings BACKEND panel
   notes: 'design/app-surfaces.css .ds-247420 .health-summary.health-ok .health-chip:first-child uses raw --accent (lime #B6FF1B) as text color on near-paper bg, measured rgb(182,255,27) vs sibling rgb(31,31,38) - give it an accent background + dark text per --accent-ink contrast pattern'

package/AGENTS.md

@@ -1,5 +1,9 @@
 # AgentGUI — Agent Notes
 
+## GUI ux-craft sweep (2026-07-10) — thirty-third run
+
+Fresh `gui-ux-craft` workflow (34 agents, 21 confirmed, 1 lens crashed+re-run) on request to max usability/predictability/negative-space via wfgy-method critique. Full detail in rs-learn (recall "agentgui 33rd run ux-craft sweep"). Headline: parallel negative-space audit caught a near-invisible Settings health-chip (raw `--accent` lime on near-paper bg) and a 300px+ dead void in History's empty state (fixed 50vh centered layout -> natural height + shortcuts hint); kit landed `--tr-caps`/`--lh-long`/`--space-2` token adoption, cwd/agent-name font-family consistency, brightness(0.92) darkening on 3 more lightening-hover bugs, light-theme `::selection`/`--accent-tint` contrast fixes, 30 hardcoded focus-ring instances tokenized, chip/badge tone-* consolidation, new `AgentListSkeleton` component, `UploadProgress` indeterminate/marquee state, 3 `COMPONENT_API.md` doc gaps closed. **Standing lesson: a new kit component must be re-exported through `src/components.js`'s barrel to be consumable — adding it to a component file alone (e.g. `sessions.js`) leaves it invisible to the built bundle even with 0 lint errors; grep the built dist for the export name before wiring the app against it.** Kit pushed `4105bd1`, agentgui pushed `3bac0fe`, all CI green both repos.
+
 ## GUI ux-craft sweep (2026-07-10) — thirty-second run
 
 Fresh `gui-ux-craft` workflow (35 agents, 22 confirmed) on request to max usability/predictability/negative-space via wfgy-method critique. Full detail in rs-learn (recall "agentgui 32nd run ux-craft sweep"). Headline: 2 more misapplied `.lede`->`.t-meta` instances (running-sessions banner, file-preview loading — same class of bug as the 31st run's history empty-state fix), streaming markdown reparse throttled (was reparsing the whole accumulated text every rAF tick), ghost/danger hover unified to `brightness(0.92)` darkening (was `brightness(1.1)` lightening, which failed AA on light theme for danger), focus-ring hardcoded values replaced with `--focus-w`/`--focus-color`/`--focus-offset` tokens, `pre .n` numeral color + 4 `community.css` text usages routed off AA-failing `--green-2` onto `--code-num`/`--green`, new `ui_kits/workspace/` flagship demo for the WorkspaceShell/ConversationList/AgentChat/SessionDashboard combo. Kit pushed `ad000b6`, agentgui pushed `5ccaa8a`, all CI green both repos. **Standing gotcha: this env's `PASSWORD` value can itself contain literal commas (e.g. `123,slam,123,slam`) — treat the whole string as one token, never comma-split it when testing auth.**
@@ -18,7 +22,7 @@ Scoped negative-space/attention follow-up (not a full agent fan-out) to the expl
 
 ## Visual-polish pass — shell depth, composer weight, chat gutter (2026-07-03) — twenty-eighth run
 
-User feedback: the shipped GUI "looks very diy". A live-browser screenshot audit (not a full agent fan-out) named 3 concrete, high-leverage causes and fixed all 3 in the kit. (1) `.ws-sessions` used flat `--bg`, identical to the main content column — `.ws-rail` and `.ws-pane` both already use `--bg-2` (a recessed plane framing the elevated content column) for exactly this reason; sessions was the one column breaking that pattern, so the conversation list and chat thread read as ONE continuous surface with only a 1px hairline between them — the single flattest tell in the shell. Now consistent. (2) `.chat-composer` — the box the user types into every turn — had zero elevation at rest, a flat hairline box on a flat background; added the kit's own already-defined-but-unused `--shadow-1` token (the existing focus-within ring still overrides it on focus). (3) The chat tab opts out of `.ws-main`'s padding via `mainFlush` (so the thread can center at `--measure`), but that left the controls row, heading, empty-state, and composer all flush against the column edge on both sides with zero gutter — the crumb bar above kept its own padding, so everything below visibly touched the edge the crumb text did not. Added a uniform inline gutter to `.agentchat` itself; `--measure` centering is unaffected (it centers within the now-padded box). **Standing rule: `.ws-rail`/`.ws-sessions`/`.ws-pane` must all three use `--bg-2` for consistent shell depth — a future column added flat `--bg` would repeat this exact regression.** Also landed inherited uncommitted community-app reply/delete-message work sitting dirty in the kit tree. Browser-witnessed at 1280px and 420px before/after: visible depth/weight/gutter improvement, no wrap/overlap regression, 0 console errors. Kit pushed `anentrypoint-design` `53c8464`, agentgui pushed `42708ea`. `agentgui`'s Deploy GH Pages flaked once (the known "Deployment cancelled" pattern — see the 26th-run note) and succeeded on rerun after patient wait.
+Screenshot audit fixed 3 "looks very diy" causes: `.ws-sessions` flat `--bg` (should match `.ws-rail`/`.ws-pane`'s `--bg-2`), `.chat-composer` zero elevation (`--shadow-1`), `.agentchat` zero inline gutter under `mainFlush`. Standing rule: `.ws-rail`/`.ws-sessions`/`.ws-pane` must all three use `--bg-2`. Full detail in rs-learn (recall "agentgui 28th run visual-polish"). Kit pushed `53c8464`, agentgui pushed `42708ea`.
 
 ## Negative-space + attention sweep (2026-07-03) — twenty-seventh run
 

package/package.json

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