RAPP Brainstem Frontier v0.1.0-beta.6

RAPP Brainstem Frontier v0.1.0-beta.6 (source-only prerelease)

Release commit: 985693ee9399e737e17f75b6c02a227fdb628551

Source-only release: no locally assembled Electron applications are attached. The stable bootstraps (frontier.ps1 / frontier.sh) resolve this release automatically; the launcher and the shared Brainstem checkout both pin to the release commit.

What's fixed since beta.5

• Windows: every Frontier release install failed at commit verification (The system cannot find the path specified ×2, then a resolved-commit mismatch). beta/install.cmd expanded %ACTUAL_COMMIT_FILE% inside a parenthesized block at parse time — before it was set — so both redirects hit an empty path. Now uses delayed expansion (#179).
• CI now runs the real release path. New preflight job frontier installer (windows/macos) fetches the candidate's beta/install.cmd / beta/install.sh at the candidate commit and runs it commit-pinned from an isolated home, asserting the launcher checkout equals that commit. This path had never executed in CI before, which is how beta.4 and beta.5 both shipped broken on Windows.

Everything in beta.5 (RAPPlication twins, multi-chat Brain Surgeon, Show Mode, brandmark, Program-Files Git fix) carries forward.

Installer hashes (SHA-256, from the release commit's Git blobs)

8ebf9ac6426166095818f2b8ed406d18e8ad8067ac164150f469aef3d9aa613e  beta/install.cmd
8f237c282d01ca8a19605e1885ed92db9921face96b920451ff0a93b95f505da  beta/install.sh

Install

Windows (PowerShell): irm https://microsoft.github.io/aibast-agents-library/beta/frontier.ps1 | iex
macOS / Linux: curl -fsSL https://microsoft.github.io/aibast-agents-library/beta/frontier.sh | bash

Commit-pinned:

curl -fsSL "https://raw.githubusercontent.com/microsoft/aibast-agents-library/985693ee9399e737e17f75b6c02a227fdb628551/beta/install.sh" | BRAINSTEM_BETA_COMMIT="985693ee9399e737e17f75b6c02a227fdb628551" bash