0.2.10

• Pin Wrangler to 4.136.0 (npm published it after the 0.2.9 freeze; caught by
  the source-drift lane).

0.2.9

• Converge the thirteen ci-workflows reusable callers and
  config/reusable-workflow-pins.json on the signed 0.1.26 tag.
• Pin bash-language-server to 5.8.1 in the contract and both installers.
• Recompile the hash-locked test requirements: packaging 26.3, pygments 2.21.0.
• Correct the Herdr version reference in AGENTS.md to the installed 0.9.1.

0.2.8

• Pin uv to 0.12.17 after independently hashing the linux x86_64 and aarch64
  GitHub release tarballs against the published sha256 files.
• Pin difftastic to 0.71.0 after hashing both linux release tarballs.
• Pin Herdr to 0.9.1 (herdrdev/herdr, tag object 8544776), hashing the
  macOS aarch64 and both linux release assets.
• Pin Telegram Desktop to 7.2.9, hashing td-setup-linux-x64-7.2.9.tar.xz;
  the icon asset pin stays on commit a1e89e1 because the blobs are
  byte-identical at the v7.2.9 tag.
• Pin doctl to 1.169.0 and Stripe CLI to 1.51.0, hashing both linux
  architecture tarballs for each.
• Pin resend-cli to 2.21.1 and wrangler to 4.135.0 from npm registry
  dist.integrity metadata.
• Pin @openai/codex to 0.155.1 from npm registry dist.integrity.
• Pin atuin to 18.22.0 against the published upstream .sha256 assets.
• Pin the Homebrew installer package to 7.0.4, hashing the .pkg download.
• Pin Google Cloud CLI to 585.0.0, hashing both linux release tarballs.
• Keep Node.js on the 24.x LTS line (24.21.0); the 26.x major is out of
  scope for a pin refresh.
• Track difftastic's new asset naming: 0.71.0 publishes
  difft-<version>-<triple>.tar.gz instead of difft-<triple>.tar.gz.
• Make every pinned-download RETURN trap self-clearing and unset-safe: an
  early failure return used to leave the trap armed globally, so the next
  function return re-fired it with archive/stage unbound and the real
  error surfaced as unbound variable under set -u.
• Deduplicate evidence-gate artifacts by run_attempt: a --failed rerun
  leaves the earlier attempt's platform-* artifact in the download set, and
  the gate used to read its stale result: failure even after the lane
  proved green on retry. Only the newest attempt per lane instance is
  verified now; same-attempt duplicates still fail.

0.2.7

• Pin uv to 0.12.15 after independently hashing the linux x86_64 and aarch64
  GitHub release tarballs against the published sha256 files.
• Pin Dart to 3.13.4 after independently hashing both linux SDK zips against
  the dart-archive .sha256sum files.
• Pin resend-cli to 2.21.0 from the npm registry.
• Pin wrangler to 4.131.2 from the npm registry.

0.2.6

• Pin osv-scanner to 2.6.0 after independently hashing the linux amd64 and
  arm64 GitHub release binaries against osv-scanner_SHA256SUMS.
• Pin JetBrains kotlin-lsp to 263.4702.0 from download-cdn.jetbrains.com,
  verifying both architecture tarballs against the published .sha256 files.

0.2.5

• Name desktop-server in the --profile error and document
  --docker-mode rootful|rootless for a host that builds locally. Installer
  behaviour was already that in 0.2.4; the comment lagged.
• Pin reusable workflows to current module mains.

0.2.4

• Hash root-owned 0600 privilege records through root_exec when the applying
  user cannot read them. An interrupted contract upgrade that already published
  a different adapter JSON is asided and replaced; helper and policy still
  never replace.

0.2.3

• Ubuntu privilege can take a new contract JSON when helper and policy already
  match this source: aside the prior contract and records, then publish. A
  partial transaction that is not that completed-bundle case still fail-closes.
• Apply still runs strict verify before writing a device receipt, but does not
  compare a prior receipt to the state this apply is about to record. Standalone
  verify.sh --strict still does.

0.2.2

• Keep Ubuntu --plan from calling bun pm bin -g or bun pm ls -g when
  describing npm user_tools. Those probes create ~/.bun/install/global
  before they can answer, so a plan wrote into the home it only describes.
  Hosted unit tests missed it because they do not have bun on PATH.

0.2.1

• Republish the 0.2.0 contract: tag 0.2.0 landed on the merge commit, which
  GitHub does not attach to a pull request, so release evidence lookup refused
  publication. This tag is the PR-head commit after merge.
• Resolve bun's actual global bin (bun pm bin -g, including
  ~/.cache/.bun/bin) when installing resend and wrangler, instead of
  assuming ~/.bun/bin. Hosted native evidence used the cache prefix.