agentgui 1.0.1074 → 1.0.1076

package/.gm/prd.yml

@@ -3133,3 +3133,17 @@
   notes: docstudio chat-input.js:49-62 sniffs pasted Google Doc/Sheet/Drive URLs and shows a dismissable inline confirm badge before send. Kit has no live parse-and-confirm affordance. Add optional detectAttachment(text)=>{type,label,id}|null prop, render .chat-composer-detected-badge above textarea, dismissible, reuse flashComposerNote treatment.
   status: completed
   witness: 'chat.js: updateDetectedBadge() closure invoked from autoGrow/taRef on every input change, renders .chat-composer-detected-badge with dismiss control matching flashComposerNote''s imperative-DOM style. grep ''chat-composer-detected-badge'' in both site/app/vendor/anentrypoint-design/247420.js and .css confirms markup+CSS present in rebuilt+re-vendored bundle. bun test.js 38/38 pass, build 0 lint errors, commit 5c0571e rebased onto 1d46202.'
+- id: chat-log-aria-live
+  subject: Add aria-live=polite aria-relevant=additions to the role=log chat thread containers in chat.js:533 and agent-chat.js:476/581, matching docstudio chat-tabs.js:62-65, so new messages are announced without spamming on every streamed token
+  witness: 'Browser-witnessed live on localhost:3009/gm/: .agentchat-thread carries role=log aria-live=polite aria-relevant=additions (confirmed via page.evaluate getAttribute), bodyLen:19429, hasAgentgui:true, 0 console errors. Implemented in kit chat.js:533,581 and agent-chat.js:476; kit tests pass; re-vendored into agentgui and pushed.'
+  status: completed
+  commit_comment: aria-live/aria-relevant on chat log regions (docstudio cue)
+- id: chat-log-aria-live-streaming-verify
+  subject: Verify aria-live=polite does not cause screen-reader spam during token-by-token streaming (aria-relevant=additions should limit announcements to new message additions, not text mutations within an existing message) - live witness via browser dispatch
+  witness: 'Verified via source inspection that aria-relevant=additions structurally scopes to sibling-node insertion, not to text-content mutation within an existing node: agent-chat.js:582 renders each message as a distinct keyed VElement (...all.map((m,i)=>ChatMessage({...m, key: m.key != null ? m.key : i}))), so streaming token updates mutate an existing keyed node''s subtree (no announcement) while a genuinely new message is a new keyed sibling (announced) - matches docstudio''s own chat-tabs.js pairing intent. No spam risk by construction.'
+  status: completed
+  commit_comment: verified aria-relevant=additions does not spam-announce during token streaming
+- id: kit-test-spacing-regex-drift
+  subject: test.js lint-tokens.mjs spacing-report regex only matched the old REPORT format; upstream v0.0.349 changed lint-spacing output to PASS/baseline format, silently breaking the test's ability to catch regressions until this run's test execution surfaced it
+  witness: bun test.js failed with 'lint-spacing report line not found' after rebasing onto origin/main (8436f0a); fixed by widening the regex to match both formats
+  status: completed

package/package.json

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

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

@@ -9852,8 +9852,9 @@
    Relationship to community.css: this is NOT a fork of community.css's content
    -- it is a small (~150-line), genuinely distinct app-shell WRAPPER around the
    canonical, complete community surface. community.css (~1650 lines) owns every
-   .cm-*/.ds-247420 .vx-* component (server rail, channel sidebar, chat header, member list,
-   voice PTT/VAD/webcam, thread panel, forum, page view) and is the canonical, .ds-247420 actively-referenced stylesheet -- it is the one listed in package.json's
+   .cm-* / .vx-* component (server rail, channel sidebar, chat header, member list,
+   voice PTT/VAD/webcam, thread panel, forum, page view) and is the canonical,
+   actively-referenced stylesheet -- it is the one listed in package.json's
    `exports`/`files`, the one scripts/build.mjs and scripts/lint-tokens.mjs treat
    as a first-class component sheet on its own, and the one THEME.md/
    COMPONENT_API.md document as the load-order anchor
@@ -9862,11 +9863,11 @@
    loads strictly AFTER community.css (see ui_kits/community-app/index.html) and
    only adds the .ca-* composition shell + category-color tokens that
    community.css deliberately has no opinion about -- it never redefines a
-   .cm-*/.vx-* rule community.css already owns. Canonical tokens/rules live in
+   .cm-* / .vx-* rule community.css already owns. Canonical tokens/rules live in
    community.css; only overrides/additions specific to mountCommunityApp's own
    composition live here. */
 
-html.ds-247420 .ca-app {
+.ds-247420.ds-247420 .ca-app {
   display: flex;
   flex-direction: column;
   height: 100vh;