v0.16.0

What's Changed

• orca: ✨ Prepare workers from an unused Sprite pool by @yasyf in #47

Full Changelog: v0.15.2...v0.16.0

v0.15.2

What's Changed

• images: 🐛 Report managed service creation failures by @yasyf in #46

Full Changelog: v0.15.1...v0.15.2

v0.15.1

What's Changed

• orca: ♻️ Verify Codex hook review at both list edges by @yasyf in #45

Full Changelog: v0.15.0...v0.15.1

v0.15.0

What's Changed

• orca: ✨ Prepare an existing owned workspace by @yasyf in #44

Full Changelog: v0.14.4...v0.15.0

v0.14.4

What's Changed

• orca: ⏱️ Record operation timings during agent startup by @yasyf in #43

Full Changelog: v0.14.3...v0.14.4

v0.14.3

Fix the 0.14.2 Namespace command launch failure. Native named-container SSH does not supply an implicit shell, so the frame expression now runs through explicit sh -c using the existing quoting. The fake models direct argument execution and has assignment and expansion regressions.

The frame protocol, decoder, direct stdin, binary streams, and status/error precedence are unchanged. Accepted E1-F1/P2 remains. Shell-local unexported LC_ALL can become exported, and _ reflects wrapper topology; the guarantee covers configured/exported locale values.

Fresh corrected native execution and Python overhead measurements remain separate acceptance work. No lifecycle or full-model success is inferred from this release.

v0.14.2

Namespace command execution preserves separate binary stdout and stderr and decodes the command exit status through framing tied to a fresh call nonce. Native transport errors, diagnostics, incomplete records, and trailing bytes prevent acceptance of a command status. Input remains attached directly to the requested child.

Configured/exported locale values are preserved. Accepted P2 risk (E1-F1). A login-shell-local, unexported LC_ALL can become exported, and shell-maintained _ reflects the Python wrapper. No dependence on those details has been demonstrated in the admitted images or reviewed callers; unrestricted process-environment identity is not claimed.

Each command adds one Python process. Fresh native byte/status checks and overhead measurements remain separate acceptance work. The 0.14.1 bootstrap change is retained.

v0.14.1

Bootstrap reads the next native startup screen immediately after it verifies that the previous gate has disappeared. It retains interval polling for loading screens, along with trust authorization, native approvals, cancellation, deadlines, hook review, and the final idle check.

Two deterministic timing cases cover ready and loading screens. Fresh runtime timing remains a separate acceptance check; this release makes no measured startup-speed claim.

v0.14.0

Namespace workspaces now use regular Compute instances through the official Go SDK. Configuration supplies the Compute endpoint, platform, volume size, exported Orca port, and duration; each profile selects an immutable image digest and machine size. Image builds push and verify the Open Container Initiative image directly.

The controller records each allocated instance before waiting for readiness, maintains its forwarding listener, and renews the lease from the provider's observed deadline. Each new gateway connection reads native authentication state again. Lease renewal requires the controller to remain available.

Sprite package installation runs independently of payload transfer and mounting. Both lanes finish before the loader and tool publication. The 0.13.4 capture scripts remain unchanged.

Live Compute lifecycle, suspended extension, volume continuity, full Orca operation, and cold-start performance require separate acceptance. The release's render comparison records compatibility with the current admitted Sprite and Namespace artifacts.

v0.13.4

Payload capture now passes --no-upgrade when downloading resident packages and installing the full capture seed. This avoids requesting upgrades for seed packages already supplied by the provider base. The existing resident startup install and archive integrity checks keep their current behavior.

A native package-only probe captured 54 resident debs and classified the declared 102-package closure with no base-version changes. The resident records matched the 54 debs previously applied in the diagnostic. A new full capture and admission remain required for the changed source fingerprint; existing archives must retain their original identities.

Independent source review and Linux and macOS CI passed. Whole cold-start performance with the new payload remains unmeasured.