v1.0.1 — newest tag, and its number understates it

Read the number with care. v1.0.1 is the newest tag in this repository, not a patch on the v1.0 line. It contains v1.1.0 and v1.2.0 and 90 further commits, features included.

Verified: git merge-base --is-ancestor v1.2.0 v1.0.1 succeeds, and git log v1.2.0..v1.0.1 is 90 commits.

Beyond v1.2.0 it adds, among others:

• feat(scheduler): checkpointed recovery — lifecycle controller, bounded host executor, persisted dispatcher heartbeat, recovery lifecycle metrics, portable recovery CLI
• feat(telemetry): tool cache job events
• fix(scheduler): heartbeat only on real progress; verify lock close durability
• fix(tool-cache): persist runner diagnostic events

This is the commit NDDev-OpenNetwork/ci-workflows pins in catalog/tools.yml (470c95c3), so it is the tag with a live consumer. It is marked latest because it is genuinely the newest, and this note exists so nobody reads the version number as a promise of a small change.

The numbering is recorded as it happened rather than corrected by a new tag, because moving a consumer's pin is a separate decision.

v1.2.0 — browser-capable integration image

• feat(image): publish the Chromium-capable integration contract
• build(provider): publish the browser capability schema

Contains v1.1.0 and v1.0.0.

v1.1.0 — trusted fast cache claims

• feat(cache): grant trusted fast job claims — the nddev-linux-fast class receives a one-use, repository-bound cache claim rather than none.

Contains v1.0.0.

v1.0.0 — immutable tool cache

First tagged release of the fleet's public engine.

• feat(cache): resilient immutable tool fetches
• fix(fleet): wake only active capacity waiters

Consumers pin composite actions by commit SHA. This release exists so that a consumer pinning by release finds something, which until now it did not — the repository carried four tags and zero published releases.