[schreck61]

What

Sets the version to 0.6.0 for the next release.

• Version: Cargo.toml and Cargo.lock, and THIRD_PARTY_LICENSES.md, regenerated with packaging/licenses.sh because it lists the app's own version.
• Places that name the current version: the opening of docs/architecture.md, the bug-report template's placeholder, and the release examples in packaging/README.md.
• docs/architecture.md, two corrections:
  • §9.4 said every screenshot came from 0.5.1 except the timing chart's close-up. Several have been retaken since, so it now says that most show 0.5.1 and the rest were retaken with the code released as 0.6.0.
  • Section 8's note on the retrained networks now says every version since 0.4.0 ships them.
• Unchanged: the Last reviewed lines in ACCESSIBILITY.md and ROADMAP.md keep 0.5.1, since those documents weren't reviewed again. Mentions of what 0.5.1 did stay as they are.

Why 0.6.0

Since 0.5.1, main has seven user-facing fixes (#15). So far only the browser version, which is rebuilt from main, has them. The library's public API also changed incompatibly:

• SavedHybrid::base_score and Hybrid::save take an Option<f64>.
• weights::load takes a parser.
• StageSpan and Hybrid have new public fields.

GOVERNANCE.md commits to Semantic Versioning, so this release is 0.6.0 rather than 0.5.2. Nothing changes for the app's users: weights files are named by the layout's key, which the T-Intersection rename didn't touch, and 0.6.0 reads every file 0.5.1 wrote.

After merging

Tag the merged commit v0.6.0 and push the tag, as in packaging/README.md's Making a release. The release workflow builds and signs every package into a draft release, which is reviewed and then published. Publishing also sends the crate to crates.io.

Testing

• cargo fmt --all --check
• cargo build --locked --release --all-targets
• cargo clippy --locked --release --all-targets -- -D warnings, and its wasm32 counterpart
• cargo test --locked --release
• packaging/licenses.sh --check
• cargo deny --locked check