Yoetz v0.2.1 — Linux and WSL compatibility fixes

Yoetz 0.2.1 is a patch release in the 0.2 public-alpha line. It fixes significant bugs
that rejected Linux and WSL subscription review and native plugin approval, improves platform
and storage diagnostics, and repairs privacy-receipt service reads. It also includes the complete
0.2 baseline: Codex, Claude Code, and Cursor integrations, bounded observation, session recovery,
and guided upgrades. The prepared 0.2.0 candidate was not tagged or published; 0.2.1 supersedes it.

Python and npm packages both use 0.2.1. The public protocol namespace remains 0.1;
package releases and immutable wire-schema versions advance independently.

Highlights

• Linux subscription review can start. Codex subscription setup now selects the exact
  Linux x86_64 evaluator cell instead of rejecting it with codex_runtime_platform_unsupported.
  WSL 2 Linux userspace uses that path; actual WSL acceptance remains untested. macOS arm64
  keeps its own cell, and a mismatched binding fails before launch (#716, #717).
• Linux plugin approval uses PAM. Cursor and Claude Code plugin lifecycle operations can
  request the invoking Linux account's password at a trusted terminal. A disposable worker
  bounds PAM work; cancellation, timeout, missing-console and failed-authentication paths stay
  closed. Preview names the mechanism and platform. This implementation includes WSL Linux
  userspace, but does not establish completed native-host or WSL acceptance (#719, #726).
• Platform failures explain the next step. Linux and WSL diagnostics distinguish sandbox,
  credential-store, filesystem and runtime-cell facts. Native Windows receives an explicit WSL
  path instead of an opaque stateful-command error; installation guidance tells users which
  side of Windows runs each command (#709, #710, #720–#725, #727).
• Reviewer usage survives restart. Subscription reviewer token usage is persisted with its
  attempt and provenance. Missing usage is not invented, and historical events keep their
  original shape (#715, #718).
• Privacy-receipt service reads are registered. Ordinary control clients can retrieve and
  list receipts, and the catalog decodes network-egress receipts. Two remaining CLI rendering
  and local-receipt schema defects are called out below (#730, #729).

What this release does not claim

• Real WSL 2 has not been tested. Ubuntu x86_64 evaluator smoke demonstrated device login,
  login reuse, two Luna/high semantic reviews, usage, service restart/unlock, provenance,
  production-client network-receipt reads, logout and rollback. It does not establish WSL
  mount behavior, distribution shutdown/relaunch, networking or sandbox-policy acceptance.
• Linux Claude Code and Cursor native-host acceptance remains incomplete. Scripted PAM
  evidence and an evaluator smoke run do not prove a human-authorized plugin lifecycle,
  native model use, observation coverage or clean workflow closure (#719, #722).
• Two privacy-receipt CLI bugs remain open: datetime rendering can crash (#731), and a
  local-receipt purpose can violate the control schema and break listing (#732). The service
  read repair does not mean every advertised receipt CLI path succeeds.
• The package version does not widen the supported-cell allowlist or erase evidence gaps.
  See the public claims,
  release-gate ledger
  and Linux/WSL runbook.

Install

uv tool install --managed-python --python 3.14.6 "yoetz==0.2.1"

For a one-off run: uvx "yoetz==0.2.1". With uv already installed: npx yoetz@0.2.1.
The npm package delegates to the exact Python version. Existing users can run yoetz upgrade
for package, migration and host-refresh guidance; replacing the package alone does not activate
new plugin bytes in an already-running host.

Release integrity

The tagged workflow builds and tests one candidate, publishes those exact Python and npm bytes,
and compares registry downloads with the candidate. Its release assets include SHA256SUMS,
NPM_SHA256SUMS, SBOM, capability and support matrices, known limitations, the release-evidence
bundle and VERIFY.md. Consult the actual attached evidence for the tested cells and outcomes.

Full changelog

• #704: landing setup guidance.
• #705: current-candidate release verification.
• #708: landing layout and installation clarity.
• #710: platform-aware agent installation guide.
• #713: mobile landing layout and explicit
  experimental Linux/WSL platform wording.
• #729: integrates #717, #718, #726 and #727,
  plus the privacy-receipt control/catalog repair.
• 0.2 baseline notes:
  the earlier changes included in this release, with their per-PR references.

Full changelog from the last public tag.

Yoetz v0.1.0 — public alpha

Yoetz v0.1.0 — public alpha

Yoetz v0.1.0 is the first usable public release: a local-first evidence ledger and review engine
for agent work. It records bounded facts that participants publish, checks that record with
versioned policy packs, and produces receipts whose wording stays inside the evidence actually
available.

Highlights

• A six-operation protocol: start, publish_work, check, respond, status, and
  receipt, with the same contracts over CLI and MCP.
• Local-first trust: one per-user service owns keys, decrypted state, SQLite writers, privacy
  policy, and provider dispatch. CLI, MCP, and the terminal interface are bounded clients.
• Honest completion receipts: coverage, provenance, freshness, findings, and limitations remain
  separate. A clean deterministic check is never presented as proof that work is correct.
• A full-screen terminal experience: first run, status, privacy, provider, integration, service,
  and receipt flows share one interface without moving confidential input into the UI.
• Privacy-gated semantic review: optional model review stays behind explicit provider binding,
  reauthenticated policy authority, minimization, secret scanning, and durable egress receipts.
• Codex integration without inflated claims: Yoetz ships Codex skill, plugin, MCP, hook, and
  observation machinery, but v0.1.0 deliberately advertises no tested Codex version or capability
  profile. Installation or registration alone is not support evidence.
• Recoverable local durability: encrypted task bundles, generation-fenced SQLite writers,
  backup/restore, forward-only migrations, and explicit operational recovery surfaces.

Install

The canonical package is the Python distribution:

uv tool install --managed-python --python 3.14.6 "yoetz==0.1.0"
yoetz

For a one-off run:

uvx "yoetz==0.1.0"

Or, when uv is already installed:

npx yoetz@0.1.0

The npm package is a dependency-free launcher. It bundles no Python and no Yoetz implementation;
it delegates unchanged arguments and terminal I/O to uvx yoetz==0.1.0.

What the alpha does not claim

• It has not received the two independent threat reviews required for the first non-alpha release.
• It publishes no verified Codex-version, hook-observation, provider-endpoint, keyring/platform, or
  structural subject-capture support cell where release-bound evidence is absent.
• It makes no support-mailbox availability or response-time promise.
• On Linux, approved external-command checks fail closed in v0.1.0 because the bubblewrap launch
  profile is not release-certified. Built-in deterministic checks and the ledger remain available;
  Yoetz does not claim that an external command ran when its sandbox boundary is unavailable.
• It does not claim bit-for-bit reproducible Python archives, package signing, or broad platform
  support beyond the exact release jobs and artifacts that passed.
• Semantic output is advisory. Yoetz records challenges and provenance; it does not replace code,
  security, or maintainer review.

These are bounded release statements, not fine print. The exact claim inventory and dated
dispositions are in
docs/public-claims.json
and
docs/OPEN_QUESTIONS.md.

Release integrity

The tag workflow builds each distribution once, tests the candidate artifacts, records SHA-256
checksums and build provenance, assembles the release evidence and capability matrices, then
crosses dedicated publication environments. PyPI publishes first. npm then publishes the exact
approved launcher tarball through trusted publishing. The GitHub release attaches both candidates
and the evidence bundle. Post-publication jobs download the public artifacts and compare them to
the approved bytes. The immutable schema tree is deployed from the exact candidate before tagging
and the workflow re-fetches every hosted file for byte comparison.

Inspect the attached SHA256SUMS, npm checksum file, candidate manifests, SBOM, support matrix,
known limitations, and release-evidence bundle alongside the wheel, source archive, and npm
tarball.

Security and support

Report vulnerabilities through GitHub private vulnerability reporting, with
support@yoetz.dev as the fallback. Use repository issues for ordinary bugs and support. See
SECURITY.md and
CODE_OF_CONDUCT.md.

Full changelog

This first public alpha has no previous usable release to compare against. The complete feature,
fix, privacy, durability, integration, and upgrade notes are in
CHANGELOG.md.