Release checklist

Release requirements

• The public npm package metadata, runtime image references, release notes, and current install commands identify version 0.2.0.
• adapter init, adapter preflight, and adapter preview remain aligned with the current package version and loopback-only safety model.
• adapter preflight validates the capability contract, profile support, and configured read-only evidence endpoints with stable diagnostics.
• The wallet lifecycle HTTP surface is opt-in and requires durable state plus bearer authentication.
• cashu-ts and CDK lifecycle adapters run funded mint, swap, send, receive, restore, and reconcile lanes against pinned Nutshell and mintd mints.
• cashu-ts and CDK melt recovery use an authenticated Lightning settlement probe before treating a paid quote as terminal.
• Lifecycle reports redact raw seeds, tokens, invoices, proof secrets, and wallet keys.
• Wallet-doctor capture v2 drops ciphertext, signatures, proof secrets, and wallet private keys; semantic integrity checks bind its canonical digest and exact relay/mint observations.
• The NIP-60 wallet doctor collects read-only multi-relay state, never publishes events, and never moves value.
• wallet-doctor check independently recaptures the named relay and mint state and fails closed on mismatch, incomplete evidence, unsafe transport, or error findings.
• Untrusted relay and mint inputs are bounded before expensive parsing or curve operations.
• The funded wallet-doctor lane (pnpm test:doctor:funded) runs nine scenarios against a real mint, three relays, and the lab reference fixture.
• Pull-request CI verifies the npm tarball, Docker demo, funded wallet matrices, two mint implementations, generated adapters, browser portal, and v0.2.0 release metadata.
• npm provenance and the GitHub Release bind v0.2.0 to the tagged source commit.
• First-party reproducible evidence: run npx --yes cashu-fault-lab@0.2.0 demo from the published registry package and retain its secret-redacted JSON, HTML, provenance metadata, and screenshots.

External validation blockers

• Integrate an independent wallet receiver maintained outside this repository.
• Obtain hands-on feedback from external Cashu wallet maintainers.
• Operate independent read-only ledger, mint, and Lightning evidence authorities for qualifying wallets.
• Run at least two qualifying implementation pairs against two distinct mint identities.
• Independently reproduce or verify source and build provenance for qualifying adapter images.
• Complete public-relay Nostr hardening and independent interoperability review.
• Exercise wallet-doctor check against capture bundles produced by wallets outside this repository.

Publication requirements are complete. External validation blockers do not prevent the v0.2.0 developer preview; they prevent certification and strong independent interoperability claims.