docs: derive Production state from live admissions

[abrichr]

Summary

• remove fixed Beta, Experimental, browser-reference, and interim qualification labels from current public product pages
• derive each Production label from the exact current signed admission record, with expiry and revocation checks, no older-release fallback, cache-busted authority reads, and newest-refresh-wins rendering
• require all seven active target admissions plus matching unyanked wheel and source artifacts for the five default PyPI packages before the site shows product-wide Production
• define the exact qualified-workflow contract and its three-trial-per-task-per-condition evidence minimum, including silent-incorrect-success and over-halt counts
• publish the complete eight-outcome transaction contract
• document the released Chromium attach recorder, resize and monitor transitions, atomic output, capture-time secret handling, and the governed boundary for extension acquisition
• render the managed Flow artifact tuple from one structured registry and guard it in docs CI

This replaces the static maturity approach in #127 and keeps the useful browser attach and version-authority work on current main.

Validation

• node --test tests/js/production_lifecycle.test.cjs — 9 passed
• uv run pytest tests/ -q — 210 passed
• uv run python scripts/validate_docs.py
• uv run python scripts/render_production_lifecycle.py --check
• uv run python scripts/check_published_version_claims.py --offline
• uv run python scripts/check_published_version_claims.py --require-network
• targeted Ruff, Actionlint, and diff checks