Upgrade and verify

These docs describe the latest Cayu release, named in the release manifest. Pin that version when reproducing examples. If your installed release differs, use its shipped cayu guide topics and release-matched source before applying a signature or configuration example.

cayu version
cayu inspect --json
cayu check --fail-on warning --json

Review the change

Read the target release notes and public API changes. Update the dependency constraint and lockfile together. Inspect generated-project convention changes before using a generator to add capabilities; scaffold metadata describes construction history rather than granting runtime authority.

Run deterministic tests, representative fresh evaluations, and interrupted-session recovery checks where the changed surface warrants them. A new candidate’s result may be incomparable with a baseline when its evidence, authority or judge contract changed.

Move durable state deliberately

Inspect migration status using the new release and deployment configuration. Back up before applying a supported migration. Do not assume an older binary can read a newly migrated database; use the release’s compatibility report and your rollback plan.

Read storage and the public release notes.