v0.3.9

Merge pull request #170 from zuohaisu/agent/chore-seal-0-3-9

chore(release): set version 0.3.9

v0.3.8

Merge pull request #168 from zuohaisu/agent/chore-seal-0-3-8

Seal 0.3.8: herdr capability matrix and walkthrough fixes

v0.3.7

Merge pull request #123 from zuohaisu/agent/release-0.3.7

Set Viva version to 0.3.7

v0.3.6

Merge pull request #83 from zuohaisu/agent/fix-clippy-fetch-update

fix: replace deprecated AtomicUsize::fetch_update with compare_exchange

v0.3.5

Viva 0.3.5: terminal scenes, resilient office client, byte-boundary-s…

v0.3.4

Merge pull request #73 from zuohaisu/agent/feat-pane-drag-resize

feat: drag pane dividers and the sidebar edge in the workbench

v0.3.3

Merge pull request #71 from zuohaisu/agent/feat-update-auto-restart

feat: restart the resident server automatically after viva update

v0.3.2

Summary

Patch release from owner-merged main commit a29da82649f6bd2f181096ba6e46c5fe56496f49 (PR #70). Includes the changes merged since v0.3.0:

• Workbench chrome: sidebar, palette, shared pane borders and client version indicator (PR #61).
• Workbench viewport, diff-overlay and split-size/rollback hardening.
• PTY setup: retain the controlling-terminal fd through fork/exec, report TIOCSCTTY failures, use atomic CLOEXEC fd duplication and RAII cleanup (PR #70).

0.3.1 was prepared in PR #67 but was not published to npm. This release publishes the current merged 0.3.2 source; no old release tag or package was overwritten.

Validation

• Owner-merged main CI passed: https://github.com/zuohaisu/viva/actions/runs/37438101155
• cargo test --workspace, bash packaging/npm/test-local.sh, cargo metadata --locked --no-deps --format-version 1, and git diff --check passed in an isolated worktree. Existing prerequisite-dependent ignored tests remain ignored, not claimed as passes.
• Both macOS release builds and startup smokes passed: https://github.com/zuohaisu/viva/actions/runs/37439204470
• Official npm registry exposes 0.3.2 with latest for @zuohaisu/viva, @zuohaisu/viva-darwin-arm64 and @zuohaisu/viva-darwin-x64; all gitHead values match the merged source.
• Clean registry install with npm install --prefix <fresh-directory> @zuohaisu/viva@latest --registry=https://registry.npmjs.org --no-audit --no-fund --ignore-scripts reports viva 0.3.2; sandbox init and doctor passed on macOS arm64.
• SHA-256 checks passed for both GitHub release archives. Both npm platform binaries are byte-identical to their GitHub release binaries; both binaries report 0.3.2 (x64 smoke under Rosetta, not Intel hardware acceptance).

Safety and limitations

• No authority widening, protected-branch push or self-merge. Publication used the existing tag-triggered release workflow, platform packages before wrapper.
• The AGENTS.md patch/version rule is not yet mechanically enforced by CI, and main merge alone does not trigger release publication; the existing flow requires a version tag.
• Finite PTY test runs do not prove absence of every race; issue #63 resize EBADF remains independently unconfirmed.

v0.3.0

Viva 0.3.0 — V15 workbench series (file browser, PR cleanup, handoff,…

v0.2.1

Viva v0.2.1

Added

• viva update: upgrade this installation to a newer stable version.
• viva update --check: check the installation's release channel without replacing the executable or installing packages.
• Global npm installations upgrade through npm at their original prefix, keeping the wrapper and platform package in sync.
• Standalone macOS installations use official GitHub Release artifacts: bounded HTTPS download, SHA-256 verification, version probe and atomic executable replacement. Failed native validation preserves the old binary; equal/older versions are not installed.

First upgrade from v0.2.0 or earlier

Older binaries do not have viva update; install v0.2.1 once first:

npm install --global @zuohaisu/viva@0.2.1
viva --version
viva update --check

For standalone installations, download viva-macos-arm64.tar.gz (Apple Silicon) or viva-macos-intel.tar.gz (Intel) and its SHA-256 checksum from this release.

Safety and limitations

• Updates do not open/migrate VIVA_HOME, alter member/task/history records, stop agents or restart servers. Activate the installed server explicitly with viva server-restart, then reconnect the TUI.
• Native updates replace only the executable; refresh bundled Pi extension sources separately if needed. Checksums provide integrity, not an independent publisher signature.
• Local npm installs update with npm install @zuohaisu/viva@latest inside their project. npm owns its installation/failure behavior; native atomic replacement guarantees do not apply to npm package installation.
• No sudo, automatic background upgrades or overwrite of Cargo build outputs.

Publication and verification

• Source: owner-merged PR #52, commit 4dbd8a30f49ba5af6d337907e32f5e1ef0c9e8d6. The annotated v0.2.1 tag records actor, publication action, timestamp and owner authorization.
• Release workflow: both macOS targets built and passed real version/init/doctor/export smoke checks; GitHub release and npm publication jobs succeeded.
• npm registry confirms @zuohaisu/viva, @zuohaisu/viva-darwin-arm64, and @zuohaisu/viva-darwin-x64 version and latest dist-tag 0.2.1. Initial brief registry propagation delays resolved; publication was not skipped.
• Downloaded both GitHub archives and verified their SHA-256 files. Downloaded npm binaries match the corresponding GitHub binaries byte-for-byte for both architectures.
• A real npm global installation at a temporary prefix ran viva --version, viva update --check, and the already-current viva update successfully; no VIVA_HOME was created. The downloaded Intel standalone binary also reports 0.2.1 and checks the GitHub channel successfully. No existing user installation or resident server was modified.
• cargo test -p viva --lib update::tests::live_github_release_updates_only_sandbox_binary -- --ignored --nocapture passed against the published v0.2.1 Intel artifact: real HTTPS/checksum/version/atomic-replacement path, temporary sandbox only.

Retained validation caveat

The existing parallel PTY instability is not fixed by this release. Post-merge Rust CI attempt 1 failed the neighbor-isolation test; attempt 2 failed the high-volume test with zero output. Attempt 3 passed the unchanged full suite. No code, tests, concurrency settings or checks were weakened/skipped for those reruns; the original failures remain evidence.