Zeroshot v10.9.0

Changes since v10.8.0.

Features

Resume runs from workspace checkpoints (#1142)

Failed local and direct-target runs can resume at a saved node or
concurrent group, restoring its input workspace and completed
prerequisite outputs. Plain zeroshot resume RUN_ID restarts the
original graph on the latest retained workspace.

Snapshots now live in one encrypted, deduplicated Restic repository per
recovery lineage. Full filesystem copies exist only in private temporary
staging directories and are removed after each operation. Successful
lineages delete their checkpoint repository; failed or lost runs retain
it for recovery.

Prepare shared workspaces with run-scoped environments (#1159)

Add optional setup and startup scripts to prepare one workspace shared
by workers and reviewers. Environments are concrete run inputs,
independent of profiles: Docker and hosted targets accept environment,
while the CLI accepts --environment FILE or --no-environment.
Omission lets the host choose a default; {} explicitly selects the
base environment.

Profiles remain portable graph and agent settings. The engine has no
environment catalog, user/org ownership, repository defaults, or saved
environment references. Local execution has no environment picker and
rejects preparation hooks in both validation and launch. Cloud provides
scoped storage and repository selection in Zero Cloud
#319, embedding
the generic hosted environment editor.

Fixes

Account for cumulative Codex usage (#1160)

Codex reports cumulative token usage when it resumes a conversation.
Record only the increase since the previous report so node revisits and
execution-scoped corrections do not count earlier turns again. Reset the
saved count when counters decrease or a fresh conversation starts,
including retries whose first turn has no usage report.

Addresses #1155. Collecting partial usage for timed-out or force-stopped
turns remains a separate follow-up.

Recover the merged formatter update summary (#1162)

Release 10.9.0 stops while generating notes because the already-merged
Prettier update (#1136) has Dependabot's HTML body without a Summary
section. Recover its concise summary by exact immutable commit ID,
following the existing historical-recovery convention. All other commits
still require their own nonempty Summary section.

Compile Unix process cleanup on macOS (#1163)

The 10.9.0 release cannot compile on macOS because Unix process-group
cleanup calls a helper declared only for Linux. Make the ESRCH check
available on every Unix platform. Add required macOS compilation of the
product and test targets, including the embedded UI, to catch
platform-gating regressions in ordinary CI.

Documentation

Explain workspace restart and resume (#1156)

Document default restart and checkpoint resume where users encounter the
CLI, including concurrent-group boundaries, retained workspace behavior,
and fresh credential handling. Clarify that a raw GH_TOKEN must be
exported again for private checkout or Git delivery, describe the
existing OECP recovery fields, and regenerate the CLI and protocol
references. This changes documentation only; the wire shape and runtime
behavior stay unchanged.

Maintenance

Raise production line coverage above 95% (#1153)

• raise production-only native coverage to 95.018% lines, 91.773%
  regions, and 93.185% functions
• add compact contract matrices for process cleanup, CLI/update
  behavior, checkpoints, transport framing, hosted lifecycle, protocol
  bounds, and UI shutdown while consolidating related fixtures
• exclude test implementation from measurement and report aggregate
  goals plus a 75% line/region floor for every material production file as
  observational warnings; no material file is below that floor

Close remaining production coverage gaps (#1154)

• raise production coverage above the repository targets with
  branch-focused contract tests
• cover local/remote routing, resume recovery, portable delegation,
  credential persistence, Restic discovery, provider parsing, target
  serving, HTTP classification, merge-plan validation, subscription
  failures, real stdin, and signal-shutdown boundaries
• consolidate redundant assertions, avoid process-global mocks and port
  races, and keep the added test runtime negligible
• enforce 95% lines, 92% regions/functions, and 80% per-file material
  coverage as real CI gates

Add full-repository Opcore check and badge (#1158)

• Add an Opcore 0.3.2 full-source CI check and README badge, with Fast
  and native Rust providers on the committed tree.
• Resolve every finding from the full check through focused Rust,
  Python, and UI changes. The UI refactors preserve editor behavior while
  bringing source within the checked policy.
• Exclude only the two PowerShell test scripts that Opcore cannot parse;
  the existing Windows CI lane continues to run them.
• Reject unknown Python run/submit option names before native I/O and
  cover the mounted editor’s edit-to-save flow in response to review
  feedback.

Eliminate process fixture races (#1157)

• prevent Linux ETXTBSY flakes with one flock handoff for freshly
  written Unix test executables, shared by unit and integration fixtures
• give inherited lease descriptors and aborted listener tasks a bounded
  scheduler window to release instead of requiring same-poll cleanup
• preserve the underlying checkpoint and GitHub transport errors in
  assertion output

Bump prettier from 3.9.6 to 3.9.8 in the development-dependencies group (#1136)

Update the development formatter Prettier from 3.9.6 to 3.9.8.

Upgrade

npm install -g @the-open-engine-company/zeroshot@10.9.0