chat example fails UI_Standards: runtime-injected inline style on <div> (cross-repo CI red)

[adnaan]

Summary

TestChatE2E/UI_Standards (in examples/chat/chat_e2e_test.go) fails because the rendered chat page contains a <div> carrying an inline style attribute, which the example's own UI-standards check forbids (outside [data-modal] / [data-lvt-toast-stack]):

chat_e2e_test.go:139: UI standard violations: inline style on <div>

Evidence it is runtime-injected, not in the template

• grep -rnE "style=" examples/chat/ returns nothing — there is no static inline style in the chat templates.
• The UI-standards assertion scans the live DOM at runtime: document.querySelectorAll('[style]') excluding INS/DEL, [data-modal], and [data-lvt-toast-stack]. So a <div style=…> is being inserted into the DOM after render (client bundle or a livetemplate-rendered feature), and it isn't inside the excluded toast/modal containers.

Likely cause: client v0.14.x sync drift

• The docs repo's own build workflow is currently failing on main (run of 2026-06-18), and main recently advanced via the client@v0.14.0 sync (Sync from client@v0.14.0 #80) and sync/client-v0.14.2.
• This check passed on the livetemplate cross-repo run of 2026-06-13 (older docs tree) and started failing afterward — consistent with the client bump introducing a <div style=…> (or a toast/modal wrapper whose selector no longer matches the exclusion list).

Where it surfaced

livetemplate PR #456 ("Test Docs Examples against Core Changes" job). That PR is docs+test-comment-only in core and cannot affect rendered DOM — the failure is docs/client-side. Filing here so it's tracked independently.

Suggested next steps

1. Reproduce locally: run examples/chat against the current client bundle and inspect the rendered DOM for [style] divs.
2. Determine whether the inline style comes from the v0.14 client (e.g. a toast/modal wrapper) and either fix the client or extend the chat test's exclusion selectors to match the new structure.
3. Confirm the docs main build failure is the same root cause or a separate break.