Repository navigation
SightMesh v0.11.0
Experimental release. The fork-loop trigger is fixed and native disk limits are active, but broad unattended promotion still requires sustained real-load observation.
What changed
- Added a Python SDK and flat CLI built around human-readable task keys and prompt strings.
- Made worker starts idempotent through stable task identity and cdesktop's exact-once native launch journal.
- Added atomic batch reservation, fully prevalidated command batches, one active lease, fixed child budgets, explicit successor epochs, and a three-attempt circuit breaker.
- Kept recovery checkpoints content-addressed inside the task worktree instead of copying transcripts.
- Prevented child lifecycle delivery from resolving back to the originating child.
- Pinned cdesktop
v0.2.6-20260831200904, which stops Codex before rollout or free-disk limits are breached.
Evidence
- Commit:
e326eba646315143d52fc3eddbd9b3d5dbea79c2 - Main compatibility workflow: https://github.com/clarkipeng/sightmesh/actions/runs/33438986107
- Test suite: 330 passed locally and on Python 3.11, 3.12, and 3.13
- Pinned cdesktop package checksum and executable verification: passed
- Wheel and source distribution build, isolated install, and metadata validation: passed
Boundaries
SightMesh owns semantic task identity and lifecycle policy. cdesktop owns visible workspaces, native sessions, worktrees, transcripts, exact-once launch effects, and local storage enforcement. Git owns source state. Repowire owns cross-workspace contact.
The cdesktop runtime is currently pinned to the SightMesh fork release while upstream proposals cdesktop-ai/cdesktop#17 and #18 remain under review.
Upgrade
Install SightMesh v0.11.0 through the normal local installer. The runtime lock installs the verified cdesktop package. Existing workspace and ownership state is preserved. Keep incident workspace 3184-cr-mgr8 archived rather than respawning its old manager.