v1.2.1

Pytxo v1.2.1

Pytxo v1.2.1 hardens the repository commit boundary introduced in v1.2.0.
The release refuses ambiguous authority, stale review packages, failed
verification, partial platform publication, and hosted services that start
without the authentication their public bind requires.

[added]

• A dedicated verification-actor receipt records the effective permission
  profile, execution domain, environment, network posture, timeout, and bounded
  output separately from the agent receipt.
• A deterministic commit-boundary fixture and recorded demo path cover a
  successful reviewed Apply and a stale-package refusal without provider
  latency or model variance.
• Release control, demo, and readiness documents record the exact verification
  evidence and the known risks accepted for this cut.

[changed]

• Source builds now require Rust 1.88. The terminal UI uses Ratatui 0.30.2,
  removing affected LRU and optional FUSE versions from the release graph.
• Cloud repository upload requires repository configuration plus an explicit
  host consent phrase. Local fallback after a transport failure is separately
  opt-in.
• Desktop carries exact run, agent, and execution-domain identity through Work,
  History, approvals, review, and recovery. Partial snapshots remain visibly
  partial.
• The canonical release workflow requires the complete five-platform CLI
  matrix, one Windows x64 Desktop installer, checksums, immutable action
  revisions, protected-main ancestry, and exact version parity.

[fixed]

• Failed or verification-failed tasks cannot unlock dependent work, and failed
  runs no longer return false success after the ledger settles.
• Stop persists process creation identity, refuses PID reuse, terminates the
  process tree, confirms exit, and preserves the cancelled terminal state.
• Verifier commands use a minimal environment, permission and network gates, a
  process-tree deadline, and bounded output. Unsupported cloud verification
  fails closed.
• Folder trust is an out-of-band ceiling for global, per-agent, and every
  project-root profile. Offline entitlement fallback cannot authorize a more
  privileged profile.
• Cloud sync and cache egress reject protected paths, symlinks, special files,
  credential-shaped content, and unsafe fallback.
• Paddle webhooks require a configured secret, fresh signature, allowlisted
  price identity, durable replay state, and persisted ownership before changing
  entitlements.
• Hosted Link and cloud-sandbox processes refuse unauthenticated public binds.
  Browser-to-Desktop account return remains disabled until it uses one-time
  authorization codes.
• SQLite migrations are transactional and schema-checked before advancing the
  version. MCP raw reads respect DeepSpace fidelity caps, and error envelopes
  are sanitized by default.
• Run Review requires an explicit confirmation naming the path count and
  package digest. Apply revalidates affected paths, preserves unrelated drift,
  and records stale refusal as a failed attempt.
• CLI and npm installers verify checksums and embedded versions before atomic
  replacement.

Scope

Reviewed Apply remains limited to Orbit and Galaxy, one execution domain, and
one repository root. Pytxo applies only the prepared package and reconciles
interrupted attempts through its local journal. Desktop remains Windows-first.

Install

npm i -g pytxo@1.2.1
pytxo doctor

Release assets:

• https://github.com/Pytxo-dev/pytxo-releases/releases/tag/v1.2.1

Previous: v1.2.0.

Full Changelog: v0.10.0...v1.2.1