StateCarry v0.2.0

StateCarry v0.2.0 introduces a project-centered workflow for returning to interrupted work.

What changed

• Keep a durable current task, discussions and return points while refreshing generated analysis.
• Review the exact scope of changes before preparing or sending a Codex request. Verification, execution, result comparison and acceptance remain separate actions.
• Track release policies and delivery progress separately from implementation completion.
• Read local Codex conversation records incrementally and improve desktop development build isolation.

Upgrading from v0.1.x

The first launch performs a one-time database transition. Project registrations, connection settings, selected conversation references and app/auth settings are preserved. Original project files and original Codex conversations are unchanged.

Previously stored analysis, copied source records, task choices, discussions, execution/release records and content caches are cleared. If you need to retain that old StateCarry content, back up your StateCarry data before upgrading. Newly created v0.2.0 content is retained on subsequent launches.

Unresolved external executions block the transition until their state is resolved; the transition does not resend or cancel them. Legacy Resume and work-context API routes are replaced by project-owned routes under /api/v1/projects.

Validation

• Source: 053487b3ad7fdfc7c613716e2d52c7dc9bbab850.
• All six local verification stages passed without cached results: 81 test files, 662 tests.
• GitHub verification passed.
• Signed and Apple-notarized app and DMG; stapled-ticket, signature and Gatekeeper checks passed.
• The packaged app launched and restarted with isolated application data, served the project UI and reported version 0.2.0.

The download below targets Apple Silicon macOS. The update manifest and compressed app bundle support the stable-channel updater.