agentgui 1.0.1027 → 1.0.1029

package/.gm/memories/mem-40d6169c8759061d-806.md

@@ -0,0 +1,8 @@
+---
+key: mem-40d6169c8759061d-806
+ns: default
+created: 1783680462136
+updated: 1783680462136
+---
+
+{"key":"agentgui-30th-run-sessions-rail-dead-click","value":"agentgui 30th run (2026-07-03): sessions-rail dead-click fix. ConversationList stays mounted on files/live/settings via keepSessionsTrack but onSelect only special-cased the chat tab; every other tab's click loaded state but never navigated, since only historyMain() renders state.events. Fixed: non-chat-tab selection now navigates to history first. Verified live (state.tab live->history, selectedSid set, events fetched). STANDING RULE: a persistent-across-tabs component kept mounted via keepXTrack whose interaction effect renders on only ONE tab must have every OTHER tab's handler produce the same visible effect (usually navigate to the rendering tab) - inert-but-visible is worse than not shown. App-only fix, agentgui pushed c1e4915."}

package/.gm/memories/mem-dc1ac3b04d22317e-664.md

@@ -0,0 +1,8 @@
+---
+key: mem-dc1ac3b04d22317e-664
+ns: default
+created: 1783680441733
+updated: 1783680441733
+---
+
+{"key":"gm-fs-write-verb-payload-key-is-content-not-body","value":"The gm-plugkit fs_write verb's payload key is 'content' (a JSON-string), NOT 'body' - passing {path,body:{...}} silently no-ops and reports bytes:0 with no error, which stalls the CONSOLIDATE->COMPLETE CI-validation gate since .ci-validated never actually lands on disk. Always dispatch fs_write as {\"path\":...,\"content\":\"<string>\"} (JSON.stringify any object payload first). Discovered independently in agentgui's 32nd run and design/dashboard-kit's own CONSOLIDATE passes on the same day - a recurring plugkit gotcha worth checking for on every fs_write dispatch, not just .ci-validated."}

package/.gm/prd.yml

@@ -2605,7 +2605,8 @@
 - id: run32-push-ci
   subject: Push both repos (kit + agentgui) and watch CI green on both
   notes: standing CONSOLIDATE requirement
-  status: pending
+  status: completed
+  witness: design repo pushed 3c28e8c (fix a11y+dx) - CI green (Deploy GH Pages + Publish 247420 to npm, both success). agentgui repo pushed 34587bc (gui fixes) then 4e39513 (AGENTS.md drain) - both commits' CI runs (Test/Deploy GH Pages/Publish and Release/Auto-Declaudeify, 4 workflows) all completed success on the final HEAD 4e39513. .ci-validated marker written with content key (not body - discovered+fixed the fs_write verb payload-key gotcha this turn, memorized) matching head_sha 4e395134dca48f59acfea01bbda64c7f7b13a12b == current git rev-parse HEAD.
 - id: typography-rhythm-lede-misuse-settings
   subject: 'gui-ux-craft run32 confirmed finding: typography-rhythm-lede-misuse-settings'
   notes: from gui-ux-craft workflow wf_1413e6ba-ed0 confirmed findings

package/AGENTS.md

@@ -10,7 +10,7 @@ User asked to "max the gui usability practicality... predictable, good looking,
 
 ## Sessions-rail selection dead-click fix (2026-07-03) — thirtieth run
 
-User feedback: "layout and design choices look weird... make maximum sense." Live-browser audit of history/live tabs (screenshots + `window.__agentgui` state probing, not a full agent fan-out) found a real logic gap the prior 29 runs' visual sweeps never caught: the conversation rail (`ConversationList`) stays mounted on files/live/settings tabs (`keepSessionsTrack`) and is captioned "Browse a conversation's events" there — but `onSelect` (`site/app/js/app.js` sessions-column builder) only special-cased the chat tab (`resumeInChat`); every other tab fell through to `loadSession(sid)`, which sets `state.selectedSid`/fetches events but never switches tabs. Since only the History tab's `historyMain()` renders `state.events`, clicking a row while on Live/Files/Settings was a dead click — data loaded into state that nothing on screen displayed, with a caption promising an outcome the click didn't deliver. Fixed: selecting from any non-chat tab now navigates to history first. Verified live: `state.tab` was `'live'`, clicked `.ds-session-row`, `state.tab` became `'history'` with `selectedSid` set and the events endpoint fetched. **Standing rule: whenever a persistent-across-tabs component (kept mounted via a `keepXTrack` pattern) has an interaction whose effect is rendered by only ONE of the tabs it appears on, every OTHER tab's handler must produce the same visible effect (usually by navigating to the tab that renders it) — a component kept visually consistent across tabs but behaviorally inert on most of them is worse than not showing it at all.** No kit changes this run (app-only wiring fix). agentgui pushed `c1e4915`.
+Fixed non-chat-tab clicks in the persistent sessions rail being dead clicks (loaded state, no visible navigation). Standing rule: a keepXTrack-mounted component's interaction must produce the same visible effect on every tab it appears on. Full detail in rs-learn (recall "agentgui 30th run sessions-rail dead-click").
 
 ## Mobile sessions-drawer sliver fix (2026-07-03) — twenty-ninth run
 

package/package.json

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