eLLMsha 2026.10.14-patch.11

v2026.10.14 Patch 11 — chat controls and subagent status

Release candidate prepared on 2026-10-14 (Europe/Kyiv). Publication, installer validation and installation of this candidate are pending. The release pipeline builds signed and notarized macOS Apple Silicon installers, an unsigned Windows x86_64 installer and four Linux/amd64 VPS images in parallel; publication requires every branch to pass.

Changes

• Show and drag the desktop pet through nonactivating macOS panels, preserving the separate Dock action that opens the main window.
• Open command completion consistently at a valid slash invocation in either composer. Preserve surrounding text and caret position when selecting a command, handle empty results and input methods, and highlight known skills in the draft.
• Render BMAD document links and inline artifact buttons with readable Light/Dark colors, keyboard focus and disabled states inside their Shadow DOM.
• Keep finished or waiting subagents from becoming falsely active after a parent interaction. A genuine new child turn restores the running state; duplicate terminal events are suppressed.
• Fit subagent avatars within the available header width. Working children have animated circular borders; an ellipsis exposes the hidden children and their states. Reduced-motion preferences are respected.
• Automatically open a new Office document only when a live assistant reply in the exact current chat explicitly references it. Shared-workspace file events alone do not open unrelated spreadsheets. Existing files, historical messages and hidden content do not authorize opening; navigation cancels pending actions.

Source verification

• The required AionUI just push gate passed strict lint, formatting, TypeScript, translations and 3,511 tests, with five skipped, across 420 passing test files and one skipped file on Node 24.11.0 and Bun 1.3.9. Published source: 6a5214044e2900021f7a2dd4cde82b76bdbbf8e3.
• The required AionCore just push gate passed migration checks, lint, formatting and 8,443 tests, with 26 skipped. Published source: 388e07f99e7f7c5c6fe1eb70b505386079a9b181.
• Three independent reviews examined the diff, boundary cases and acceptance criteria. Findings about root-directory paths, files arriving during the initial folder scan and duplicate child terminal events were repaired. Subsequent focused checks passed 35 Office/Markdown tests and eight Core child-session tests.
• Earlier focused checks passed 57 composer tests, seven pet-window tests, 18 avatar/sidebar tests and 14 Core lifecycle tests. TypeScript, lint with zero errors, translations and the Electron build passed.
• Browser checks used the actual production components and styles with service/context mocks. Both composers passed slash/caret/input-method/highlight scenarios. BMAD link actions, keyboard focus and Light/Dark contrast passed. Avatar rendering at three widths stayed within its bounds, exposed the hidden list and respected reduced motion.

All 44 root release/helper contracts passed, and an independent review of the version metadata and release notes found no actionable issue. Hosted build and distribution results will be recorded after completion.

Runtime verification boundaries

An isolated Electron application received a real filesystem event for an unrelated XLSX and correctly kept its preview closed. The positive real-agent scenario stopped before document creation because its test backend reported codex runtime unavailable: bundled codex 0.162.1 is unavailable; automatic opening of a real generated file is not claimed as accepted. Current-chat positive cases and initialization/navigation races pass focused regressions. Native DOCX/PPTX generation was not run.

An isolated pet fixture created visible, nonfocused windows. Physical dragging while another application is foreground and the Dock interaction remain unverified because native automation was unavailable. Component and unit checks do not establish installed acceptance.

The working application, profile, chats and tasks were preserved during source verification. Installation of this release will take place only when agent turns are idle and after downloaded macOS bytes, signature, notarization and Gatekeeper checks pass. Native Windows runtime and upgrade acceptance remain unverified.

Distribution policy

macOS must retain the expected Developer ID Application identity and team, valid app/helper signatures and designated requirements, a stapled notarization ticket and Gatekeeper acceptance. Windows remains unsigned. publish controls publication only; it does not weaken verification. The release date must match the actual publication day in Europe/Kyiv. Build metadata and image manifests record the exact root revision and maintained-fork revisions; no earlier release tag is moved or overwritten.