[adamcavendish]

Summary

Prepare the 0.7.2 patch release with the primary-constructor storage visibility capability already merged on main.

Problem

The published 0.7.1 baseline predates storage_visibility(), while the release metadata and compatibility check still describe 0.7.1 as the active patch boundary.

Behavior

Area	Result
Workspace crates and lockfile	Bumped to 0.7.2
Changelog	Documents Kotlin and Scala primary-constructor storage visibility and fail-closed validation
Semver check	Compares 0.7.2 against the published 0.7.1 tag with an empty allowlist
Compatibility manifest	Renamed to the 0.7.1 baseline and updated for the 0.7.1 to 0.7.2 boundary

Compatibility

This is a patch release. The semver check reports no approved compatibility breaks against tag 0.7.1. No crate publication, tag creation, or GitHub Release is performed by this PR.

Validation

• ./scripts/check-semver.sh — 223 checks passed, 31 skipped; no semver update required.
• just book — passed.
• just book-test — passed after cleaning the duplicate sigil_stitch artifacts described by the repository instructions.
• RUSTDOCFLAGS=-Dwarnings cargo doc --workspace --no-deps — passed.
• cargo fmt --all -- --check — passed.
• cargo clippy --workspace --all-targets -- -D warnings — passed.
• cargo test --workspace --lib — 150 passed.
• cargo test --test constructor_spec_tests storage_visibility -- --nocapture — 9 passed.
• just check was attempted but its full nextest run exhausted the 2.4 GiB available workspace disk during trybuild compilation; no assertion failure was reported.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ All tests successful. No failed tests found.

📢 Thoughts on this report? Let us know!