From an independent review of the branch:
- Windows: a version's folder is complete with its engine AND its scripts,
and a folder is removed whole or not at all (moved aside first, which
Windows refuses while its engine runs). A cleanup during a trial could
leave the next version's engine without its scripts, an app with no
interface until the next release.
- The job that ends the engine with the zeron.exe wrapper is made only for
an update's trial: elsewhere Ctrl+C reaches both, and the job would cut
the engine's own clean shutdown short.
- A beta record with no claim (the old app's switch, before `chosen` was
recorded) is a choice: the beta it installs keeps it one rather than
claiming it, so a stable release doesn't move it.
- A claim a stable release ended is recorded as such, not as a choice of
Stable that would let a beta be sent back to an older release.
- An install the old app's updater moved here leaves the GitHub feed (no
beta channel beside it) for the edge's at its first launch as the zgx
app, however it arrived; a package no longer brings its feed.
- release.yml fails loudly when it can't read the beta manifest: claim-only
betas reach a stable release through that copy alone.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-authored-by: zeronsh[bot] <346184242+zeronsh[bot]@users.noreply.github.com>
Channel (Wing's decision): an install on beta only because a beta download
claimed it moves to stable when a stable build reaches it, once, recorded
and logged at that build's first launch, and read so by any updater before
that (an engine's remote update included). One whose person chose beta stays
on beta: the record now says `chosen`, and a later beta's claim doesn't
overwrite it.
Windows, from an independent review:
- A first-start completion takes its own version's package first (a GitHub
release's own download path, or the edge's manifest-<version>.json that
release.yml and zgx-beta.yml now publish), so a withdrawn or newer latest
can't strand an install.
- A package with no beta\<version> folder installs as the old app: the way
back works over a zgx install.
- The engine the zeron.exe wrapper starts is in a job that ends with the
wrapper (children break away), so a failed trial's watchdog can't leave it
running while the old version restores data.
- The engine in beta\<version>\engine counts as the installation, so a
zgx install updates from another device; its updates come as the package.
- zeron-update.json is replaced only when it names a default feed, and not
during a trial.
- The beta-feed copy reads the beta manifest from the bucket, and leaves it
when unsure.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-authored-by: zeronsh[bot] <346184242+zeronsh[bot]@users.noreply.github.com>
Starting up, the app called a kept session signed out after 20 s, showed
"Can't load this chat" until the first connection, on every launch with a chat
open, and made calls give up with `offline` while the old engine was still
exiting. Those are all the same mistake: no answer yet taken for a bad one.
Now a launch with an engine it can start waits for it, however long. A session
on disk stays restoring until the engine says otherwise; the chat stays loading;
calls wait; the sidebar's foot and Settings don't read as signed out. An engine
that answered and went is said as unreachable only after the 20 s it always was.
With no session kept, or no engine to start, nothing changes.
No second engine is started while one holds the data dir: it could only queue
for the lock (up to 7 of them in an 80 s drain). One starts as soon as it's let go.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
A beta build there now follows update-channel.json, so it updates from
releases/beta and can go back to Stable; stable builds and every engine stay on
stable, and the macOS floor stays macOS's. On Linux a beta's directory isn't
named as a version, or the shipped engine reads it as newer and restarts into
itself whenever it's idle. On Windows a beta updates from its package, its
scripts and stable's zeron.exe as its engine under beta\<version>; stable's
single-exe update is unchanged. zgx finds its scripts beside the binary, and
the Windows beta has a window subsystem and Zeron's icon.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-authored-by: zeronsh[bot] <346184242+zeronsh[bot]@users.noreply.github.com>
* zgx: Zeron's interface on zgx (app, design system, plugins, onboarding, Zeron Preview)
A new desktop app in apps/zgx: Zeron's interface written in Luau on zgx,
its design system, built-in plugins (Git, GitHub, Parallax scenes) and
theme templates, plus the engine and edge work it needs (plugin services
and agent tools, the agent registry, project icons, profile, organisation
admin, onboarding, plugin signing keys) and a separate Zeron Preview
package and workflow (preview-v* tags, off until enabled).
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* Fix Linux and Windows builds: Listener's signing_in, Command::as_std on Windows
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* Engine: plugin watchers ignore reads (inotify loop), per-component snapshot paths, Windows create-over-folder is DestinationExists
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* zgx as a beta channel of Zeron.app; shared CLI, launch and notify crates; update channels
- Update channels (stable/beta) with semver prereleases, cross-channel installs, ZeronEngineVersion and a macOS 13 floor for beta; "Get beta updates" in the current app's Check for Updates.
- The command line moves into crates/cli and engine start-up into crates/launch, shared by the current app, zeron-engine and zgx; zgx hands engine commands to the bundle's Zeron Engine helper.
- zgx beta packaging and .github/workflows/zgx-beta.yml (beta-v* tags, gated by ZGX_BETA_ENABLED); the separate Preview packaging is removed.
- Templates install from links with updates, an Unverified badge for unknown authors, the Archived settings page, the Cloud repository picker, palette sub-steps without scope tabs.
- Git plugin refreshes on file changes; GitHub plugin batches, tiers and throttles its polling; failed PR watches retry with backoff.
- zgx f81d5e99.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* zgx: registry agents' sign-in state, methods and icons; PR badges isolated per session
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* Harness: registry sign-in uses the crate's Child (Windows build)
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
---------
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
- Update channels (stable/beta) with semver prereleases, cross-channel installs, ZeronEngineVersion and a macOS 13 floor for beta; "Get beta updates" in the current app's Check for Updates.
- The command line moves into crates/cli and engine start-up into crates/launch, shared by the current app, zeron-engine and zgx; zgx hands engine commands to the bundle's Zeron Engine helper.
- zgx beta packaging and .github/workflows/zgx-beta.yml (beta-v* tags, gated by ZGX_BETA_ENABLED); the separate Preview packaging is removed.
- Templates install from links with updates, an Unverified badge for unknown authors, the Archived settings page, the Cloud repository picker, palette sub-steps without scope tabs.
- Git plugin refreshes on file changes; GitHub plugin batches, tiers and throttles its polling; failed PR watches retry with backoff.
- zgx f81d5e99.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>