docs: consolidate server runtime and deployment RFCs

[aaltshuler]

What & why

The server plan still spans four drafts whose recovery assumptions predate detached publication and final table pins. Consolidate them into one current proposal for operation ownership, bounded completion, exact outcomes and schema/query deployment without process restart or graph reset.

• Supersede RFCs 0034, 0035, 0036 and the September 10 server lifecycle RFC, preserving their historical bodies and reciprocal links.
• Separate drained online activation (E1) from independent historical reads (E2), and retain explicit authorization, crash, retention and resource gates.
• Record RFC 0065 as superseded by accepted RFC 0067, which already describes that private-branch design as subsumed.
• Update active consumer references and the separate server-testing proposal, including the landed engine-DST concurrency boundary, exact no-op outcomes and ledger revision semantics.

Backing issue / RFC

• Is an RFC PR: Server runtime and online deployment

Checklist

• Change is focused: consolidate the server plan and reconcile its dependencies.
• Tests added/updated for behavior changes: N/A; documentation only.
• Public docs updated if user-facing surface changed: N/A; no runtime behavior changes.
• 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 and git diff --cached --check — passed.
• One-off metadata/body assertions — all five supersession relationships are reciprocal; archived design bodies are preserved.
• Rust tests — not rerun for documentation-only changes. The RFC labels earlier engine evidence and its limits; it claims no server qualification from those runs.

Notes for reviewers

The replacement remains draft / not-started; supersession does not accept it or claim implementation. Storage, GQT/DST, schema-gate and test-harness proposals retain their own decisions. Review the new proposal's increment gates before implementing new contracts.