Omega v0.2.0-rc19

--zero-base crashes in this build. Do not use the flag here.
Launching with it panics before any window appears:
cannot read workspace::Workspace while it is already being updated
(crates/gpui/src/app/entity_map.rs:164). Verified against this published
disk image, not only against source. Omega launches normally without the flag.
Fixed after this candidate was cut, in 79d864a2cc. See omega#99.

Final release candidate in this series. Development continues with local dev
builds rather than further candidates.

Commit: dc6b6f5008c782c7eaa0c903ae3ef2e876b674f8

Signed with Developer ID Application: OpenAgents, Inc. (HQWSG26L43), notarized,
and stapled. Both the app and the disk image carry the ticket. Gatekeeper
accepts the package.

Correction

The original notes for this release said zero base opens a single Exo thread.
That is wrong for this build, and the error was mine: the claim was written from
the source tree rather than from launching the packaged artifact. The flag
panics here.

Two defects made it unusable, both found after the cut:

• The mode panicked before any window opened, because panel initialisation read
  the workspace entity while it was mid-update. This is not a debug assertion,
  so release builds crash too.
• A fresh profile was a dead end: the action gate refused the one action that
  completes onboarding, so setup could never finish, across restarts.

Neither was visible to cargo check, cargo test or clippy, because the mode is
reachable only through a command-line flag.

What is in the build

Everything except zero base behaves as in rc18. The signing, notarization and
brand gates all passed for this package.