agentgui 1.0.1076 → 1.0.1077
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.
- package/AGENTS.md +4 -0
- package/package.json +1 -1
package/AGENTS.md
CHANGED
|
@@ -1,5 +1,9 @@
|
|
|
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.
|