No functional change from 0.1.0 / 0.2.0. This release exists to close a supply-chain gap.
Why
0.1.0 and 0.2.0 were published from a laptop. Four CI attempts had died on EOTP — each package's npmjs.com Publishing access was rejecting every token type, and that was only diagnosed afterwards. Shipping the payment-signing takeover fix mattered more than the attestation at that moment, so they went out unsigned.
These versions publish through .github/workflows/publish.yml, so both carry a provenance attestation tying the tarball to this repo, this commit, and this workflow — verifiable in Sigstore's public transparency log.
@blockrun/core resolves wallet keys and signs x402 payments. It was the last package in this org without a verifiable build chain, which is the wrong package for that gap.
0.1.0 and 0.2.0 stay correct and installable. npm does not allow attaching an attestation to an already-published version, which is the only reason this is a new release rather than a re-sign.
Known, not fixed here
pnpm-lock.yaml pins @blockrun/llm at 3.9.0, not 3.10.0 — the release that moved the Solana packages to optional peers and keeps bigint-buffer (GHSA-3gc7-fjrx-p6mg, unpatched) out of dependency trees. Published consumers are unaffected; they resolve ^3.9.0 to 3.10.0 themselves. This repo's dev tree and CI still install the old one. Fixing it needs a real pnpm install to regenerate the lockfile, not a hand edit.