ProcLease v0.1.8 experimental preview

ProcLease v0.1.8 is an experimental patch release for agent retries and Linux
sandbox failure handling. Runtime dependencies and the Rust 1.89 minimum are
unchanged.

Explicit retry reuse

Some agent hosts change their environment between tool calls. Ordinary keyed
retries still require the original environment. The new
run --reuse --key REQUEST_ID observes the retained job with its original
environment and never launches, renews or resurrects anything. Command,
canonical directory and all other launch options must still match. An absent,
collected or incomplete key fails without starting a job.

Mismatch diagnostics name differing fields rather than disclosing values.
Keep command prefixes and launch options unchanged when retrying. See the
lease rules.

Conservative Linux supervision

• A Unix control-socket preflight runs before reserving a job. Socket-denied
  launches leave no job and do not consume a retry key. Read-only reuse of an
  existing job remains available.
• Saved Linux PIDs are interpreted only from a complete matching execution
  context. Foreign or unverifiable contexts have unavailable metrics and never
  justify PID-based cleanup or inferred completion.
• A recent foreign-context stopping record gets a bounded finalization window
  so a healthy keeper can write its final state. It becomes unknown if
  finalization cannot be verified.
• Verified keeper-finalized history still follows the existing 24-hour/newest
  100 collection limits across reboots or namespace changes. The proof requires
  observed group absence after cleanup and no future lifecycle writer.
  Uncertain groups and unfinalized or legacy records remain protected where
  absence cannot be established, retaining their logs and retry keys.

Jobs active or stopping at a Linux reboot can remain unknown afterwards.
Restricted procfs access can disable PID-derived absence checks and metrics.
There is no forced-history deletion command; do not delete unverified records
merely to hide them or signal a PID copied from disk.

Agent workflows and limits

The documentation includes a macOS Next.js 16.4.5 polling recipe for both
Turbopack and Watchpack. It is an application opt-in, not an automatic ProcLease
configuration change. It retains the host sandbox and bundler.

The compatibility matrix
records scoped macOS and native Linux measurements made before packaging this
release. Default-Claude Linux Vite/Next workflows passed; the tested Linux
Codex workspace sandbox and strict Claude Bash sandbox remain unsupported.
Those profiles do not preserve the required supervisors across tool calls;
strict Claude also denies Unix sockets. The new diagnostics do not bypass those
restrictions. A host-supported persistent execution context is a requirement,
not a demonstrated workaround.

The suite contains 25 unit and 56 lifecycle tests. Release automation runs
formatting, Clippy, tests, optimized builds and archive/installer smoke checks
natively on macOS ARM64/Intel and Ubuntu 22.04 ARM64/x64 (glibc). These are not
new real-agent workflow measurements. The macOS deployment minimum is 15.0;
Windows and Linux musl/Alpine binaries are not provided.

Installation

Review this release's install.sh, then run:

sh install.sh --skills both
proclease --version

The installer verifies archive SHA-256 checksums and atomically replaces the
CLI without sudo or Rust. Omit --skills both for CLI-only installation.
Existing unrelated skill directories and links are preserved. Cargo installs
the CLI only; the portable skill is separate:

cargo install proclease --version 0.1.8 --locked

Upgrading does not replace running keepers or watch sessions and does not
restart or stop managed work. Status, logs and readiness never renew leases.
ProcLease manages only services it launched; descendants that leave the managed
process group can escape cleanup. Retention protection requires cooperating
clients and keepers.

macOS binaries are not Developer ID signed or notarized. Both remain required
before stable promotion and deferred for this experimental prerelease.
Checksums verify bytes, not publisher identity. The CLI-only crate provides a
docs.rs overview, README and source rather than a library API.

Created by Jared Chu, with Codex and Claude contributions. See the README for credits.