docs: close server runtime RFC review gaps

[aaltshuler]

What & why

The server runtime draft left online apply ownership and deployment succession ambiguous, and its consolidation left stale compatibility and test-owner claims in related RFCs. This amendment closes those review gaps without changing executable behavior.

• Define submission-only online CLI/Core behavior, ledger-version admission, operator-established writer exclusion and stopped-writer handoff. Effectful refresh/import cannot bypass owner-only reconciliation. Preserve the Azure wrapper and gate online support on a separately qualified lease-preserving path.
• Separate submission order from the achieved deployment base so settled partial or inactive results permit corrective successors. Unresolved effects still block; stale approvals require a new validated, authorized revision. Clarify admission versus supervisor retry hints and the intentional known-unavailable 404-to-503 change.
• Rewrite RFC 0040's affected body claims for current detached publication and v11-to-v12 conversion, repair Blob test ownership and the RecoveryRequired reference, remove obsolete RFC 0067 blockers, and update the planner citation. Document draft-to-draft supersession without implying acceptance.

Backing issue / RFC

• Is an RFC PR: Server runtime and online deployment, following docs: consolidate server runtime and deployment RFCs #799.

Checklist

• Change is focused (one logical change)
• Tests added/updated for behavior changes — N/A; documentation and a citation-only Rust comment
• Public docs updated if user-facing surface changed — N/A; proposed compatibility and qualification gates are documented
• Reviewed against docs/dev/invariants.md; no hard invariant weakened or deny-list exception introduced

Local verification

• python3 scripts/check-docs.py — passed, 154 Markdown files
• bash scripts/check-agents-md.sh — passed
• typos — passed
• git diff --check — passed
• cargo fmt --all --check — passed
• Independent source/test review verified version admission, effectful refresh/import, schema-upgrade publication/completion and existing failure-test ownership. Runtime tests were not run because executable code is unchanged.

Notes for reviewers

The server RFC remains a draft. These are design and evidence requirements, not claims that online deployment or its Azure path are implemented. Writer exclusion remains an explicit deployment obligation; ledger serialization is not distributed fencing.