docs: activate CK-07R1 readiness transition

[douglasmonsky]

Summary

• record CK-07R1A0 acceptance at exact main and make CK-07R1 Conditional Ready only after this authority merges and exact-main verifies
• make the planner-valid lifecycle receipt a future CK-07R1 acceptance output, not a pre-dispatch dependency
• classify PR CK-07R1: correct lifecycle preparation scale #394 head 98a9b5b82951d136644a5fe5f8a70d320131ba08 and its Python 3.14 ordinary.2000_call_tail failure as stale, superseded, read-only

Safety and scope

• preserves maximum_new_end_to_end_runs=1, all prior attempt identities/timestamps, writer-only receipt digest 935e4427b93e67c5ca649b773b0b3895dafac87f49bc76d7ed8917dff2f0250d, budgets 5000/120000/100/500/500, package ceilings sdist 2,000,000 / wheel 1,000,000, and fail-closed rules
• no lifecycle implementation, benchmark, production qualification, PR CK-07R1: correct lifecycle preparation scale #394 update, downstream readiness, or worker creation
• exactly one future CK-07R1 successor is gated from exact main after this authority is merged and verified

Validation

• focused authority/DAG/ledger/scope/schema checks: 28 passed
• just v: 1,367 passed; invariant lane 13 passed; pyright/release checks passed
• just vc: 1,367 passed; invariant lane 13 passed; pyright/build/dist checks passed
• one final independent read-only reviewer completed; actionable findings addressed within scope