chore: prepare v0.8.0 beta 1 release

[jeffhuber]

Summary

Prepare the v0.8.0-beta.1 package release:

• bump package metadata to 0.8.0b1
• update current install/release docs and generated builder-provenance package pin
• add v0.8 release notes
• add release build tooling to the contributor test extra
• ignore timestamped generated rehearsal directories

Verification

• scripts/dev-python -m unittest tests.test_release_hygiene
• scripts/dev-python -m code_mower.migration release-readiness --repo-path . --json
• scripts/dev-python -m unittest discover -s tests
• scripts/dev-python -m ruff check .
• scripts/dev-python scripts/privacy_scan.py
• scripts/dev-python scripts/actionlint_generated_workflows.py
• scripts/dev-python -m build
• scripts/dev-python -m twine check dist/*
• scripts/dev-python -m code_mower.cli migration package-install-rehearsal --package-spec . --python "$(command -v python3.12)" --json

Notes

Release readiness passed 14/14 with zero warnings. The local package-install rehearsal reported code-mower 0.8.0b1 and first-user readiness 10/10 with zero warnings. The v0.6 truth baseline and v0.6 release notes remain historical references.

[gitar-bot]

Code Review ✅ Approved

Release preparation for v0.8.0-beta.1 with package metadata bumps, documentation updates, and release notes. All verification checks passed with zero warnings. No issues found.

Options

Auto-apply is off → Gitar will not commit updates to this branch.
Display: compact → Showing less information.

Comment with these commands to change the behavior for this request:

Auto-apply	Compact
gitar auto-apply:on	gitar display:verbose

_{Was this helpful? React with 👍 / 👎 | Gitar}

[jeffhuber]

Claude audit (merge-authority lane)

Head SHA: fb0cf70343399a811909c5c2d5d1da6f253a3293
Findings: P0=0, P1=0, P2=0, P3=0 (blocker policy: any P0/P1/P2 -> BLOCKED)

Claude Audit: PASS

Summary:

Mechanical v0.8.0-beta.1 version bump (pyproject.toml, init.py, workflow templates) plus consistent doc/test updates from 0.6.0b3 references. No functional/source code changes; version strings, release tags, and test assertions line up correctly throughout.

Findings: none.