[krafczyk]

Summary

• Bump package metadata and dryml.__version__ to 0.3.0b2, including the installed-wheel version assertion.
• Separate unreleased beta-two notes from the published beta-one baseline.
• Update the release guide with both version locations and the beta-two tag commands.

Verification

• Packaging and documentation checks: 54 passed, including offline sdist/wheel builds and installed-artifact imports/version checks.
• Focused Method import checks with JAX_PLATFORMS=cpu: 11 passed.
• Representative good-enough suite with JAX_PLATFORMS=cpu: pytest reported 4,246 passed, 37 skipped across both phases. The runner exceeded its 20-minute timeout during shutdown after reporting all results, so this is not a clean runner exit. The initial run encountered JAX CUDA out-of-memory; CPU selection matches CI.
• git diff --check passed. Exhaustive tests were not run.

Release steps after merge

The existing workflows publish on tag pushes, not on this PR or its merge. Follow docs/releasing.md after review and green CI:

1. Tag the merged, reviewed commit as test-v0.3.0b2 and push that tag to trigger the TestPyPI rehearsal.
2. Verify the rehearsal and installation from TestPyPI.
3. Tag the same commit as v0.3.0b2 and push that tag to publish to PyPI and create the GitHub release with its wheel.

Release tags have not been created or pushed.