Skip to content

SightMesh 0.13.1

Choose a tag to compare

@clarkipeng clarkipeng released this 04 Sep 04:03
· 11 commits to main since this release
650b845

SightMesh 0.13.1

0.13.1 supersedes 0.13.0, which could not launch tasks. The live canary's first sightmesh start raised FenceHeldError: building the launch request resolved the repository over HTTP while the task fence was held, and the runtime guard from #85 correctly refused. The suite had passed because the cdesktop test doubles did no I/O and never tripped the guard. This release (#109):

  • Every cdesktop request made while a fence is held now runs with the gate open (fence.external_io()), and the durable decision is re-validated on (epoch, version) after the gate closes before any native dispatch: a task cancelled or replaced during the I/O never issues a launch from a stale snapshot. Covers start, failover launch, provider lookup, failure observation, checkpoint reads in replace(), and the replacement handoff (transfer_ownership takes the caller's I/O gate and a before_spawn check).
  • The managed-launch contract probe runs before the fence on every entry path (replace, failover, recovery), never under it.
  • Both test doubles trip the same fence guard in every method that stands in for HTTP, so this class fails in CI from now on; the change alone reproduced the canary failure in 50 tests before the fixes.
  • Regressions: cold-instance replace; cancel during request build issues no native launch.

Everything below shipped in 0.13.0 and is unchanged: Every kernel PR merged only after the simulator was green and an independent adversarial review approved the exact head.

  • Liveness (#84): stall/loss/budget predicates with episode-deduped wakes and a monotonic watermark; legacy kill paths deleted.
  • Observability (#83): task-local surfaces, attention queue, structural redaction of every durable write (nested JSON, bearer/basic tokens, key prefixes, JWTs, URL userinfo), drain-first update activation.
  • Routing (#85): typed-outcome failover with standard/deep route classes; every launch kind and every terminal writer goes through one per-task lifecycle fence with reload-under-lock; no network I/O can happen while a fence is held (runtime guard on every transport opener); superseded launches are stopped, never activated.
  • External runs (#106, closes #55): durable wake subscriptions and live-only output-root leases for external long-running processes; authoritative terminal receipts; lost/unknown never inferred as success; parked delivery with one dedupe key.
  • Defaults: kernel tasks launch unattended (BYPASS_PERMISSIONS) in their own worktree (#98); message ack-wait opt-in and kernel-side launch admission cap (#94); pool-credential doctrine documented (#95).
  • CI integrity: the pinned-runtime check can no longer mask an import failure (#104); the advisory edge lane installs the package before importing it (#97).
  • Release contract (#96): GitHub Release canonical, PyPI as install convenience, installers pin and verify.
  • cdesktop pin: bumped to the fork's 0.2.8 pre-release, which carries fleet-wide coding-agent admission (direct launches included), unrevivable Replace-cancelled commands, owner-fenced managed-task finalization, an atomic Codex fork budget, and the fixture-panel removal.

Known issues carried: cdesktop /workspaces/summaries latency (#100); lead-kill and stale-mail resurrection asks (#105).