agentgui 1.0.1076 → 1.0.1078
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
|
@@ -0,0 +1,8 @@
|
|
|
1
|
+
---
|
|
2
|
+
key: mem-15c73aca528535cb-2183
|
|
3
|
+
ns: default
|
|
4
|
+
created: 1784299879288
|
|
5
|
+
updated: 1784299879288
|
|
6
|
+
---
|
|
7
|
+
|
|
8
|
+
agentgui 46th run (2026-07-17): fourth docstudio design-cue pass, same directive repeated. Fresh Explore-agent survey of /config/docstudio (told what runs 42-45 already shipped) found only 1 genuinely new candidate after exhausting low-hanging fruit: chat.js's two role=log chat-thread containers (chat.js:533,581) and agent-chat.js's one (agent-chat.js:476) gained aria-live=polite aria-relevant=additions, matching docstudio chat-tabs.js:62-65, so new messages announce to screen readers without spamming on streamed tokens - verified via source that aria-relevant=additions only fires on new keyed-sibling insertion (agent-chat.js:582's per-message keyed map), not in-place text mutation during streaming, so no live-dispatch witness was needed for that corner case. A second candidate (self-retry dropdown trigger, docstudio chat-model-selector.js) was explicitly skipped since no async-populated dropdown exists in the kit yet to wire it to - avoided speculative unused plumbing. Also fixed an unrelated hygiene bug surfaced mid-rebase: kit test.js's lint-tokens.mjs spacing-report regex only matched the old "[lint-spacing] REPORT — N raw" format; upstream v0.0.349's ratcheted-spacing-lint change reformatted stdout to "PASS — N <= baseline N", silently breaking the regression check - widened regex to match both formats. Kit rebased cleanly onto v0.0.348/v0.0.349 (one dist-only conflict, resolved by rebuilding dist/247420.js fresh). Kit pushed 8436f0a->f81f93d, all 3 kit CI checks green. agentgui re-vendored, browser-witnessed live on localhost:3009/gm/ (bodyLen:19429, hasAgentgui:true, 0 console errors, .agentchat-thread confirmed via page.evaluate to carry role=log aria-live=polite aria-relevant=additions), pushed e84cf26->639b78e->fef8222, all 4 CI checks green each push. Standing observation: the Test workflow's bun-install step sometimes takes ~13 minutes (likely npm registry propagation delay for a freshly-published kit version) before completing green - not a hang, just slow; worth waiting rather than treating as stuck if the job's own step-by-step status (via gh api repos/.../actions/jobs/<id>) shows genuine progression rather than a frozen step.
|
|
@@ -0,0 +1,8 @@
|
|
|
1
|
+
---
|
|
2
|
+
key: mem-cfd4d894370c63c3-1288
|
|
3
|
+
ns: default
|
|
4
|
+
created: 1784299896638
|
|
5
|
+
updated: 1784299896638
|
|
6
|
+
---
|
|
7
|
+
|
|
8
|
+
agentgui-44th-run-docstudio-followup-full-detail: follow-up to 43rd run's docstudio design-cue pass. Fresh research agent surveyed docstudio source vs current kit (told what already existed). 5 candidates implemented: ChatMessage error/onRetry inline destructive-toned per-turn failure notice (chat.js); generic Avatar({name,src,fallback,size}) primitive in content.js consolidating duplicated letter-fallback-disc logic; FileSkeleton gained role=status/aria-busy/aria-label matching sibling skeletons. Verified no-change-needed: backdrop-dismiss dialogs already did strict e.target===e.currentTarget check. Real bug from mandatory browser witness: AgentChat's error/onRetry wiring was gated on !isAssistant but agentgui's sendChat() always pushes an eager assistant placeholder, so the gate was corrected to key on trailing-message-position instead of role; separately a stray closing brace from removing a redundant Alert banner caused a real SyntaxError blanking the live page, caught on first post-deploy witness dispatch, fixed, re-witnessed clean. Standing lesson: a same-session "verify no change needed" pass is not a substitute for re-running the live browser witness on code that WAS changed. Kit pushed 3417592->f362528->03c9028->17ee86c, agentgui pushed f08f698, all CI green.
|
package/AGENTS.md
CHANGED
|
@@ -1,12 +1,16 @@
|
|
|
1
1
|
# AgentGUI — Agent Notes
|
|
2
2
|
|
|
3
|
+
## Docstudio design-cue follow-up (2026-07-17) — forty-sixth run
|
|
4
|
+
|
|
5
|
+
Fourth docstudio-cue pass, same directive repeated a fourth time. A fresh Explore-agent survey of `/config/docstudio` (told explicitly what runs 42-45 already shipped — toasts/Skeleton/Alert/Badge-tone/dialogs/breadcrumbs/inline-error-retry/Avatar/sidePanel/sortable-Table/streamingSince/coarse-pointer Enter-gating/CountdownDialog/PermissionMenu/detectAttachment/RTL support) came back with the low-hanging fruit exhausted: only 1 genuinely new, verified-missing candidate survived (a second, "self-retry dropdown trigger" candidate had no existing async-populated-dropdown call site in the kit to wire it to, so it was explicitly skipped as speculative unused plumbing rather than implemented). Landed: `chat.js`'s two `role=log` chat-thread containers (`chat.js:533`,`581`) and `agent-chat.js`'s one (`agent-chat.js:476`) gained `aria-live="polite" aria-relevant="additions"`, matching docstudio's `chat-tabs.js:62-65` pairing, so new messages announce to screen readers without spamming on every streamed token — verified by source that `aria-relevant=additions` only fires on new keyed-sibling insertion (`agent-chat.js:582`'s `...all.map((m,i)=>ChatMessage({...m,key:...}))`), not on in-place text mutation within an existing message's subtree during streaming. Also fixed, as a genuinely unrelated hygiene issue surfaced mid-rebase: `test.js`'s `lint-tokens.mjs spacing report` check regexed for the old `[lint-spacing] REPORT — N raw` format, but upstream `v0.0.349`'s "ratcheted spacing lint" consolidation changed the script's own stdout to `PASS — N <= baseline N`, silently breaking the regression check's ability to catch anything post-rebase — widened the regex to match both formats. Kit built+tested (`bun test.js` all pass post-fix), rebased cleanly onto `v0.0.348`/`v0.0.349` (one dist-only conflict, resolved by rebuilding `dist/247420.js` fresh rather than hand-merging generated code — the standing discipline). Kit pushed `8436f0a`→`f81f93d`, all 3 kit CI checks green (ci/Publish/Deploy-GH-Pages). agentgui re-vendored both dist files, browser-witnessed live on `localhost:3009/gm/` (`bodyLen:19429`, `hasAgentgui:true`, 0 console errors, `.agentchat-thread` confirmed via `page.evaluate` to carry `role=log aria-live=polite aria-relevant=additions`), pushed `e84cf26`→`639b78e`, all 4 CI checks green (Test/Publish-and-Release/Auto-Declaudeify/Deploy-GH-Pages) — the `Test` job's `bun install` step took an unusually long ~13 minutes this run (likely npm-registry propagation delay for the just-published kit version) before completing green; not a hang, just slow.
|
|
6
|
+
|
|
3
7
|
## Docstudio design-cue follow-up (2026-07-17) — forty-fifth run
|
|
4
8
|
|
|
5
9
|
Third docstudio-cue pass, same directive repeated. A fresh Explore-agent survey of `/config/docstudio` (told explicitly what the 43rd/44th runs already shipped — toasts/Skeleton/Alert/Badge-tone/dialogs/breadcrumbs/inline-error-retry/Avatar/sidePanel/sortable-Table) returned 5 new candidates, all implemented in the kit: `ChatComposer`/`AgentChat` gained a `streamingSince` prop rendering a `role=status` tabular-nums elapsed-time counter next to the stop control while streaming (docstudio `chat-input.js:71-96`), self-ticking via an interval keyed off the passed timestamp so re-renders don't reset it; Enter-to-send is now gated behind a module-cached `matchMedia('(pointer:coarse)')` check (docstudio `chat-input.js:116-125`) — coarse-pointer devices insert a newline and see "Tap Send to send" instead of the Enter hint; a `CountdownDialog({title,message,seconds,onExpire,actions})` primitive landed in `files-modals.js` (docstudio `google-reconnect.js:41-75`'s live sign-out countdown), composing over the same `Modal()`/`Backdrop()` shell `ConfirmDialog`/`PromptDialog` already use in that file rather than `editor-primitives.js`'s standalone `Dialog` — a deviation from the initial spec once the actual established pattern was traced; a `PermissionMenu({categories,approved,onToggle,onToggleAll})` primitive landed in `overlay-primitives.js` (docstudio `tool-approval-panel.js`'s roving-tabindex `menuitemcheckbox` list), mirroring `Dropdown`'s existing open/close/outside-click wiring; `ChatComposer` gained an optional `detectAttachment(text)=>{type,label,id}|null` prop rendering a dismissible `.chat-composer-detected-badge` above the textarea (docstudio `chat-input.js:49-62`'s pasted-URL sniff), built as imperative DOM matching `flashComposerNote`'s own style rather than a VElement tree. Implementation delegated to a background worktree agent; `bun test.js` 38/38 pass, `node scripts/build.mjs` 0 lint errors across all 7 lints. A concurrent upstream release (`v0.0.344`/`v0.0.345`, RTL `applyDirection`/`getDirection` support) landed mid-pass — rebased cleanly, `dist/247420.js` rebuilt fresh post-rebase (dist is gitignored in the kit repo but tracked via a separate publish step), re-tested. Kit pushed `5c0571e`→`1d46202`. agentgui re-vendored both dist files, browser-witnessed live on `localhost:3009/gm/` (`bodyLen:19739`, `hasAgentgui:true`, 0 pageErrors), grep-confirmed all 5 feature-specific strings (`CountdownDialog`, `PermissionMenu`, `chat-composer-elapsed`, `chat-composer-detected-badge`) present in the re-vendored bundle before pushing.
|
|
6
10
|
|
|
7
11
|
## Docstudio design-cue follow-up (2026-07-17) — forty-fourth run
|
|
8
12
|
|
|
9
|
-
|
|
13
|
+
5 candidates landed (ChatMessage error/onRetry, Avatar primitive, FileSkeleton aria-busy); a mandatory browser witness caught a real syntax-crash from a stray brace. Full detail in rs-learn (recall "agentgui-44th-run-docstudio-followup-full-detail"). Kit pushed `3417592`→`17ee86c`, agentgui pushed `f08f698`, all CI green.
|
|
10
14
|
|
|
11
15
|
## Docstudio design-cue pass (2026-07-17) — forty-third run
|
|
12
16
|
|