Skip to content

Yoetz v0.2.5 — session recovery and setup fixes

Latest
Latest

Choose a tag to compare

View all tags
@github-actions github-actions released this 24 Sep 05:27
· 220 commits to main since this release
v0.2.5
84a4b24
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

This patch in the 0.2 public-alpha line improves session recovery, setup, observation reporting,
and completion checks across the existing Codex, Claude Code, and Cursor integrations. It includes
the fixes on main after v0.2.4; richer task interaction remains outside this release.

Changes

  • Reattach an exact known session even when independent tasks share the workspace. Automatic
    recovery retains task identity, workspace fences, and admission checks (#811, #815).
  • Recover cold hook attachment within host budgets and expose capture recovery, delivery loss,
    quarantine, and pending-operation state more clearly (#790, #792).
  • Report differences between a completion claim and the effective plan, and prevent unrelated
    command gaps from invalidating otherwise qualifying finding-repair proof (#793, #794).
  • Preserve setup approvals and inspect the selected installation. Identify Linux Cursor IDE
    installations without launching them (#795, #796).
  • Fit Claude's startup instructions within its observed MCP rendering limit while retaining
    recovery guidance and reporting plugin-managed versus bare MCP registration (#791).
  • Offer opt-in required startup for native Claude and Cursor plugins, with owner controls,
    scope-bound plan checks, and same-task pending-operation recovery (#797).
  • Add unattended dogfood CI for Codex, Claude, and Cursor Agent CLI on macOS arm64, Linux x86-64,
    and Ubuntu under WSL 2 (#803).

Verification and limits

Release issue #801 tracks the exact release
revision and the package, CI, dogfood, and publication gates; results are added as each gate
completes. Tagged Release
publishes the tested Python and npm artifacts and attaches checksums, an SBOM, and release
evidence to GitHub. The public protocol namespace remains 0.1; previously released schema bytes
remain unchanged.

The pre-version source revision 2e3268340a6d2866d8ae1383fd70b2109ee01a0f passed
CI and all nine
dogfood lanes. Each lane
reported a successful native session with task mapping, a drained observation queue, and
successful AI-powered review both before and after service restart. Those runs used development
packages still numbered 0.2.4; the release issue separately records checks of the 0.2.5 candidate.

These are bounded installation, ledger, observation-delivery, and recovery checks, not a claim of
complete recording or correctness. Transient hook/drain budget diagnostics remain visible even
when final queues drain. The hosted macOS Claude lane uses --plugin-dir; the macOS Cursor lane
uses MCP only and does not establish hook activation. Native macOS approval dialogs, full desktop
activation, Windows-side Cursor Remote WSL, and comprehensive retained-content coverage are not
established by this matrix. See dogfood CI and
required startup for the precise acceptance boundaries.

Supported platform claims remain macOS arm64 and glibc Linux x86-64, including Linux under WSL 2.
Native Windows remains unsupported; Linux arm64 remains an explicitly untested platform cell.
OS identity checks, repository trust, observation consent, and provider disclosure permissions
remain separate requirements.

Assets 17
Loading