[rubentalstra]

What changed and why

The v0.0.2 release: the product version moves from 0.0.1 to 0.0.2 and the [Unreleased] entries move into the [0.0.2] - 2026-10-20 section. The milestone v0.0.2 holds no open issue (#23, #24, #25 and #26 closed).

This release publishes the first crates, each on its own version line (the two-line model of #23): ihe-iti 0.0.39 and nl-generic-functions 0.0.25, in that order, as scripts/release/publish-crates.sh lists them. Their versions moved in #29 and #30, so Cargo.lock is unchanged here (cargo update -w changes nothing). The release lane packages and attests ihe-iti-0.0.39.crate and nl-generic-functions-0.0.25.crate, and its crates leg waits on the crates-io environment for the owner.

After the merge, the signed tag v0.0.2 goes on the merge commit.

Licensing of contributions

• I accept the terms in CONTRIBUTING.md § Licensing of contributions: I have the right to submit this work, I license it under the project licence of the version it lands in, and I grant the Licensor the relicensing right stated there.

Checklist

• Every conformance decision cites the specification (the IHE ITI Technical Framework, PIXm, PDQm, HL7 FHIR R4, HL7 v2), never memory and never another implementation.
• Rust gates pass, once the workspace has a member: cargo fmt --all --check, cargo clippy --workspace --all-targets -- -D warnings with and without --all-features, cargo nextest run --workspace --locked, cargo doc with RUSTDOCFLAGS=-D warnings, and cargo deny check.
• Every refusal the change adds has an asserted negative test, and no test was weakened to pass.
• Shell and workflow files are clean: shellcheck --severity=style, actionlint, zizmor --min-severity=low .github/, and the self-test of every script the change touches.
• CHANGELOG.md has the [0.0.2] section.
• No patient data, real identifier, key, token or password in a fixture, test or example.
• Every commit is signed.
• No AI or assistant attribution anywhere in the commits or this PR.