docs: assess post-v0.8 effectiveness

[jeffhuber]

Summary

• Add a post-v0.8 effectiveness assessment covering Code Mower, peer builders, and reviewer lanes.
• Refresh the README/current-state/release-flow docs so package baseline, v0.7/v0.8 source status, Board visibility, and adoption next steps are consistent.
• Sync the public baseline helper and release-hygiene expectations with the docs wording.

Privacy

Metadata-only documentation update. No source, diffs, transcripts, issue bodies, raw stdout/stderr, auth output, local paths by default, or secrets are added to cloud payloads or docs.

Verification

• scripts/dev-python -m unittest tests.test_release_hygiene
• scripts/dev-python scripts/privacy_scan.py
• scripts/dev-python -m ruff check src/code_mower/versioning.py tools/code_mower_versioning.py tests/test_release_hygiene.py
• scripts/dev-python -m unittest tests.test_board tests.test_lane_status tests.test_doctor_output tests.test_doctor_github_checks
• scripts/dev-python -m unittest discover -s tests

Closes #531.

[gitar-bot]

Code Review ✅ Approved

Post-v0.8 effectiveness assessment documentation covering Code Mower, peer builders, and reviewer lanes, with refreshed README, current-state, and release-flow docs for consistency across package baseline, version status, Board visibility, and adoption next steps. 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: 0965e5f8e36e41f89b52e4ddf4c17ad612a151a5
Findings: P0=0, P1=0, P2=0, P3=0 (blocker policy: any P0/P1/P2 -> BLOCKED)

Claude Audit: PASS

Summary:

Docs-only PR (branch codex/531-post-v08-assessment, non-Claude) adding a post-v0.8 effectiveness assessment doc, rewording public beta-baseline language across README/docs, and updating doctor invocation examples from --preflight to --adoption --repo OWNER/REPO. The only source changes are identical cosmetic string rewording in src/code_mower/versioning.py and its tools/ mirror, with matching test updates (normalized-whitespace assertions to tolerate line rewrapping). Cross-checked referenced links (e.g. examples/board-demo/README.md) already exist in unchanged context, numbered roadmap list renumbers without gaps/duplicates, and $REPO is exported before use in the updated build-loop doc commands. No correctness, security, or data-loss issues found.

Findings: none.