eLLMsha 2026.10.14-patch.10

v2026.10.14 Patch 10 — release automation and installer downloads

Published on 2026-10-14 at 08:41:25 UTC (11:41 Europe/Kyiv), from exact tag revision c672615577a72013d45acc24d64622b5d1195157. The twelfth hosted run passed signed/notarized macOS and unsigned Windows packaging, all four Linux/amd64 image builds and isolated smoke checks, full-sized image archive handoff, and GitHub/GHCR publication. Independent checks of all eight downloaded assets, macOS signature/notarization and anonymous pulls of all four GHCR images passed. Release artifact and distribution acceptance is complete. Installed native updater and native Windows runtime/upgrade acceptance remain unverified. Earlier CI results below retain their original candidate dates and provenance.

Released changes

• Build native macOS Apple Silicon and Windows x86_64 installers from the root repository's exact maintained-fork revisions.
• Build the Linux VPS stack as versioned GHCR images with a release deployment compose file.
• Check the latest published eLLMsha GitHub release from the desktop and show a download action beside the sidebar toggle.
• Download and verify the complete platform installer, then open its DMG or EXE through the operating system. Opening an installer does not automatically terminate running agent tasks or replace the application.
• Keep signing keys in CI secrets and a temporary runner keychain. Every CI macOS build requires a Developer ID Application identity and notarization; Windows installers remain unsigned. Manual verification does not publish a release.

Acceptance status

Final public artifact and distribution checks: PASS. All eight uploaded assets were downloaded independently and matched their GitHub API sizes and SHA-256 digests. Individual installer hashes and build metadata also passed verifyReleaseArtifacts against the exact release root and its nine gitlinks. Both app bundles extracted from the public DMG and ZIP passed the expected Developer ID Application identity/team and app/helper designated requirements, strict deep signature verification, stapled-ticket validation and Gatekeeper assessment (source=Notarized Developer ID). DMG integrity verification passed and the image was detached. Anonymous pulls of all four GHCR images passed, including version/SHA/latest digest consistency, Linux/amd64 platform and OCI labels.

These are the verified individual installer checksums, distinct from the historical Actions archive digests below:

Public installer	Bytes	SHA-256
eLLMsha-2026.10.14-patch.10-mac-arm64.dmg	804,062,017	62c1fce2876ec91632f2625129e1f45233a17494701d6312a223ca3ecbbcecf6
eLLMsha-2026.10.14-patch.10-mac-arm64.zip	840,263,790	ad3fd9fd5f86dcdda9b0ec984a75adadf5015660ac333e774ea8f505d130ae69
eLLMsha-2026.10.14-patch.10-win-x64.exe	474,215,284	d87a1498643f1afabaabe812350360d20a8d05e89a98051dc570d5e42a824f27

Deferred runtime checks: the preserved Patch 9 installation lacks Patch 10's ReleaseInstaller and still uses legacy quitAndInstall. Real acceptance of the new downloader requires an installed Patch 10 and a genuinely newer published release because same-version downloads are rejected; a mock feed does not establish that result. Native Windows installation/runtime/upgrade QA remains unverified. These distribution checks did not launch or replace the production app, restart tasks or change its profile.

The following build and test records retain their original historical scope.

The required AionUI publication gate passed 3,448 tests (5 skipped), strict lint, formatting, TypeScript and translations. Focused updater checks passed 64/64; release pipeline helper checks passed 17/17 and workflow validation passed. Light/Dark renderer fixture checks used mocked IPC and did not open an actual installer. All four Linux/amd64 images, including the full web/Core/RS image, passed hosted builds and isolated smoke checks in the eleventh run. The seventh through tenth runs passed Developer ID signed/notarized macOS packaging and unsigned Windows NSIS installer creation, verification and artifact upload; the tenth run was subsequently canceled. Installed native updater behavior and native Windows installation/runtime/upgrade QA remain unverified. Independent reviews repaired a cancellation race and a stale latest-image promotion path.

A dedicated Developer ID Application certificate was issued and its key match verified. All six signing/notarization secret names are present in the GitHub release environment, restricted to main and release tags. Actual signed/notarized macOS CI acceptance passed in the seventh run below. Windows installer creation does not establish Windows runtime or upgrade acceptance.

The first hosted verification run found two packaging-environment defects: Windows incorrectly required an npm .cmd shim despite using Bun, and macOS reached Node's approximately 2 GiB heap limit during Chrome MCP bundling after Rust release compilation succeeded. The Windows prerequisite repair was reviewed and pushed. Desktop CI now gives Node a bounded 4096 MiB heap; an isolated Chrome MCP bundle using the same Node 24.11.0 completed successfully, focused contracts passed, and independent review found no blocker. Failed packaging also retains non-secret dependency/Rust caches for retries. The second run was deliberately stopped before repeating the known macOS failure. Failed and canceled evidence is retained; neither run is package acceptance.

The version date matches the actual publication date in Europe/Kyiv, following the project's release-date rule.

The third hosted verification run built and verified the unsigned macOS arm64 installers and uploaded the artifact at source 45036f3. That unsigned run did not establish Developer ID/notarization or installed-app acceptance. Windows passed Chrome MCP bundling, then found a separate Unix-style electron-vite shell invocation rejected by Windows cmd. Cache retention after this failure succeeded. The launcher repair uses checkout-local JS entries with Node and separate arguments for both Vite and builder, including retry paths. It passed 12 root contracts, 16 UI build-script tests and independent review. Windows installer acceptance was still pending after that run; it subsequently passed in the fifth run below.

The final launcher publication gate passed 3,450 UI tests (5 skipped), lint, formatting, types and translations. The complete root release/helper contracts passed 25/25. The retry packaging behavior contract and build-script suite passed 19/19, followed by independent review. AionUI source 8bd8228 is published; these source checks do not replace hosted installer acceptance.

The fourth verification run was canceled when the maintainer clarified the required single-pipeline policy: macOS always signed/notarized, Windows unsigned. Signing is now independent of publish; a missing Apple secret or failed signing/notarization stops verification too. The changed pipeline/helper contracts passed 28/28 and Actionlint passed. These checks establish configuration behavior, not completed Apple notarization.

The fifth verification run completed at source 021315b:

• The Windows job passed NSIS installer creation, installer verification and artifact upload. This establishes hosted packaging acceptance for the unsigned Windows x86_64 installer; native Windows installation, runtime and upgrade QA remain unverified.
• The macOS job successfully prepared the signing keychain and notarization credentials. Electron-builder 26.15.2 then rejected the configured signing identity's full Developer ID Application: prefix. The generic DMG retry packaged an unsigned app, and stapled-ticket validation correctly failed with exit 65 because no notarization ticket existed. No accepted macOS artifact was uploaded by this run; Developer ID signing and notarization acceptance were still pending at that point.
• The image and publication jobs were skipped. This run published neither a GitHub release nor GHCR images.

The signing repair preserves the full certificate name for native validation while stripping the builder-forbidden prefix only from its selector. Prepackaged recovery now validates the app/helper certificate, team and designated requirements, plus the notarization ticket and Gatekeeper for public builds, before repacking. Early configuration validation rejects partial/hash selectors with a clear error. The complete root contracts passed 30/30, targeted UI packaging tests passed 24/24, the actual electron-builder 26.15.2 selector contract passed using synthetic identity metadata, and independent review passed. The required AionUI just push gate passed 3,455 tests / 5 skipped, lint, formatting, types and translations; source a13cf1d is pushed. These source checks did not establish signed/notarized hosted acceptance; the sixth run below exposed the next blocker.

The sixth hosted run, at source 3f14ed5, selected the Developer ID identity and began macOS signing. It then failed with EMFILE (too many open files) while scanning the bundled Tencent dependency tree. The strengthened prepackaged-recovery gate blocked retrying that incomplete result; that run did not establish an accepted signed/notarized macOS artifact or successful notarization. The Windows job completed installer creation, verification and artifact upload successfully. Native Windows runtime and upgrade QA remain unverified. The image and publication jobs were skipped.

The macOS descriptor repair preloads the installed builder's existing file-open queue only for signed macOS packaging, including retries. An unchanged local signing dependency scan of 55,814 files reproduced EMFILE at hard limit 10,240; with the preload it completed and returned exactly the same 450 binary paths as the successful high-limit baseline, with no descriptors left open. No files were excluded and signing/notarization gates remain unchanged. The complete root contracts passed 31/31 and independent read-only review passed. Those local checks established dependency traversal only; the seventh hosted run below subsequently verified signing and notarization. The date-only AionUI candidate rollover to 2026.10.14-patch.10 passed the required just push gate: 3,455 tests / 5 skipped, lint, formatting, types and translations; source 115ac01 is pushed.

Seventh hosted run — desktop packaging accepted

The seventh verification run, at root source 7478190 with AionUI 115ac01, passed both desktop jobs:

• macOS arm64: PASS. The retained log records successful notarization at 2026-10-13T21:23:36Z, followed by app acceptance with source=Notarized Developer ID at 2026-10-13T21:29:36Z. Installer verification and artifact upload passed.
• Windows x86_64: PASS. Unsigned NSIS creation, installer verification and artifact upload passed. Native Windows installation, runtime and upgrade QA remain unverified.
• Linux images: blocked. Source-context preparation failed with ENOENT while inspecting aioncore/.opencode/skills/cron. No images were published; the publication job was skipped. Installed native updater acceptance and broader regression freedom are not established by these packaging results.

These are the GitHub Actions artifact archive sizes and SHA-256 digests, not checksums of the individual DMG, ZIP or EXE installers:

Actions artifact	Archive bytes	Archive SHA-256
ellmsha-desktop-mac-arm64-2026.10.14-patch.10	1,612,518,502	4f5bb4a05ae1c17920af677cfbdcdceb9e9192d2d6fdcd62950f8694ef4fa7cf
ellmsha-desktop-win-x64-2026.10.14-patch.10	474,411,481	0f5b827d173f9ed80df44c69eef3f10f6fea5791e1e6cb3d99730f643bc34d36

The source-context repair excludes ambient .opencode, .aionrs and .agents entries while retaining strict rejection of unexpected broken or external symlinks. Reproducing the exact root 7478190 archive plus all nine pinned submodule archives failed with the original ENOENT; the repaired sanitizer passed, excluding 18 forbidden paths while preserving SHA-256-identical bytes for all 6,958 retained regular files and leaving one valid symlink unchanged. The unchanged full local prepare-context refused standalone submodule registrations; registrations were not changed, so this proves archive sanitization only, not a completed full-context build. The full Docker, release and launcher test set passed 38/38 on Node 24.11.0. Bounded independent read-only review passed; hosted Linux image verification was still pending after that repair.

Eighth hosted run — Linux source validation blocked

The eighth verification run, at exact root source 4fecded151179dcaa8b4ad9789516216ae8799a1, passed both desktop jobs: signed/notarized macOS arm64 and unsigned Windows x86_64, including installer verification and artifact upload.

Tracked source-context preparation also passed. The actual Linux web image build then failed at docker/aionui.Dockerfile:60 with OCU source pin mismatch. The confirmed cause and source repair are recorded below; that run did not establish a successful Linux build. Subsequent memory image builds, smoke checks and image publication were skipped, as was the release publication job. An uploaded image-job evidence archive does not establish that images were built or published. Installed native updater and native Windows runtime/upgrade acceptance remain unverified.

The following are this run's GitHub Actions archive metadata, not individual installer checksums; the seventh-run records above remain historical evidence:

Actions artifact	Artifact ID	Archive bytes	Archive SHA-256
ellmsha-desktop-mac-arm64-2026.10.14-patch.10	11869896759	1,612,524,780	d1dc259288c5b3b50634ead14b83ebc10a7fa649b1a22a7436e85c18aac3e173
ellmsha-desktop-win-x64-2026.10.14-patch.10	11869528639	474,299,824	4307e653867f99fcff162c8e1eb49e023fcc56eef0c1b00426308dd410fc8d72

The OCU mismatch was traced to the blanket .agents exclusion removing the public, tracked open-codex-computer-use/.agents/plugins/marketplace.json; this changed the source digest without a component-source change. The repair allows exactly that file and its parent directories in both the context sanitizer and Docker ignore policy. Sibling agent configuration and skills remain excluded, and the expected OCU source digest is unchanged. Root cause was confirmed by independent review, and the full test set passed 39/39. An actual Docker COPY probe using the release Node image reproduced the old OCU mismatch, then passed all three unchanged OCU, Mobile MCP and Chrome MCP source digests with the repaired filters; synthetic sibling agent files stayed excluded. Bounded independent read-only review passed. This verifies source transport, not a completed hosted Linux image build.

Ninth hosted run — OCU validation still blocked

The ninth hosted run, at root b2b56d69f703be1e232868c869acadb17914f363, again passed both desktop jobs, including signed/notarized macOS packaging, and tracked source-context preparation. The actual Linux web build still failed at docker/aionui.Dockerfile:60 with OCU source pin mismatch; image and release publication were skipped. The earlier COPY probe was insufficient to establish the exact stage behavior. A base-image/locale difference was investigated as a hypothesis and subsequently ruled out by the exact-stage checks below. That run did not establish a successful hosted Linux image build.

The full b2b56d6 context from a correctly registered checkout passed the exact Go-base OCU stage prefix through source-pin verification on Linux amd64 with both the local builder and the matching BuildKit 0.33.1 version, retaining the original OCU digest 516ea577c18650e3818de3cedf5c89900060edf71bc5efdd3ecf693f2379e035. Git LFS archive expansion is now a strongly supported explanation for the CI mismatch, rather than a proven observation of that failed runner. Official Git LFS 3.8.0 reproduced an ordinary archive replacing a synthetic 127-byte pointer with its cached 27-byte object; setting GIT_LFS_SKIP_SMUDGE=1 only on the archive child preserved the 127-byte pointer. An exact OCU clone with active LFS retained both original 133-byte pointers and the unchanged source digest through the fixed archive path. The pinned checkout action applies its LFS-skip setting to its own Git child environment, not later workflow commands.

The repair sets that child-only archive environment; no global configuration, historical asset downloads or source-pin changes were needed. Focused checks passed 9/9, the full root test set passed 40/40, and final independent source review passed. Hosted verification was still pending after those local checks; the eleventh run below subsequently passed with the repaired context preparation.

Selective verification and publication handoff

The source implementation adds desktop and docker workflow-dispatch switches, both defaulting to true, with publish=false by default. Selecting neither is rejected; manual publication requires both, and tag pushes force both. Selected desktop and Docker jobs depend independently on preflight and can run in parallel. Docker-only verification (desktop=false, docker=true, publish=false) skips desktop compilation/signing and Apple-secret readiness; selected macOS builds remain signed/notarized and Windows unsigned. The Docker branch never pushes images. Only full publication transfers the tested image IDs in a same-run Docker tar artifact; after both build branches pass, the final job loads and validates exact IDs/platform/OCI labels, pushes immutable candidates, publishes the GitHub release and then promotes latest. Verification does not transfer image tar archives. The complete Docker/release/launcher test set passed 44/44, and Actionlint passed. Independent source review found no blocker. A real Docker fixture saved four isolated Linux/amd64 images, removed the originals, and loaded the archive back with identical image IDs and OCI labels; the manifest remained unchanged and unpublished. This proves local image serialization, not GitHub artifact transfer or hosted publication. The Docker-only branch subsequently passed in the eleventh run below. Full-sized image archive transfer between GitHub jobs and publication were still unverified at that point; the twelfth run below subsequently passed both. The tenth run used the previous workflow and was canceled after both desktop jobs passed; their installer artifacts remain retained. It does not validate the new selective workflow.

Eleventh hosted run — Docker-only verification accepted

The eleventh hosted run, at exact root 7755a8587cf708961b3dd01baf41710b2062600d, completed successfully. It explicitly selected desktop=false, docker=true, publish=false: desktop compilation/signing and publication were skipped. All four Linux/amd64 image builds (web with Core/RS, MemoryCore, memory hub and optional proxy), isolated service smoke checks, provenance recording and evidence artifact upload passed. This establishes hosted Docker-only verification, including the previously blocked full web image.

The uploaded ellmsha-images-2026.10.14-patch.10 evidence artifact has ID 11875920273 and archive SHA-256 dfb0ebebf1d65c8e71d9eb85f44209cb232cdc78bb2cd24dc7d537333c3e6a5c. It is a small provenance artifact, not an image tar archive or registry digest. Verification deliberately skipped image tar transfer, GHCR pushes and release publication. That verification run did not exercise full-sized same-run image archive handoff or publication; the twelfth run below subsequently passed both. Installed native updater behavior and native Windows runtime/upgrade acceptance remain unverified.

Twelfth hosted run — publication accepted

The twelfth hosted run, attempt 2, completed successfully at exact tag revision c672615577a72013d45acc24d64622b5d1195157. The first attempt's macOS job failed during stapling with a network interruption (-1005, stapler exit 68). A targeted macOS/publication retry passed; the successful Windows and image results were reused. All required desktop, image and publisher jobs are successful in the final run disposition.

The full-sized image tar save, artifact upload/download, image load and exact image-ID/platform/OCI provenance checks passed on hosted CI. Installer hash/provenance checks, immutable GHCR candidate publication, GitHub release publication and subsequent image-digest promotion to latest also passed. The public release was published at 2026-10-14T08:41:25Z, with exactly eight uploaded assets: macOS DMG/ZIP, Windows EXE, two platform checksum files, two platform build-metadata files and images.json. GitHub additionally provides source archives.

Independent public-asset hash/provenance, macOS signature/notarization/Gatekeeper and anonymous GHCR pull checks subsequently passed, as summarized in the final acceptance section above. Installed native updater acceptance remains deferred: Patch 9 still uses legacy quitAndInstall, and a genuine Patch 10 downloader test requires an installed Patch 10 plus a newer published release; same-version downloads are rejected. Native Windows installation/runtime/upgrade QA remains unverified. No production launch, application replacement, task restart or profile change was performed for this publication.