[rmcdaniel]

Records the operator decision of November 1 (#325, comment from 19:57 UTC): takeover of PHP Server databases (layouts 2.5.14 through 2.11.8) ships in 3.0.0 for self-hosted upgrades, gets no further investment, and is planned for deprecation in the 3.1.x line. Cloud cells start fresh and never use takeover.

• docs/rust-server-upgrade-takeover.md: a short Deprecation section near the top.
• docs/rust-server-upgrade.md: one line linking to it.

Docs only. No pinned-text tests reference these files. The section sits above #919's hunks in the same files, so the two don't conflict. The 3.0.0 release notes (the GitHub release body) must carry the same notice; that's tracked on #325.

🤖 Generated with Claude Code

[rmcdaniel]

General source review of exact bcdd9dc0ab10951bcbf985194fc8b7c8f35ea0d4: the passage describes planned deprecation in 3.1.x without announcing a removal version. It matches the recorded #325 handoff and retains the 3.0.x upgrade path. Backup, quiescence and stored-representation gates are unchanged. No blocking finding in this docs delta.

Small wording suggestion: use the general sentence about new installations starting with a fresh native database. The self-hosted upgrade guide does not need Cloud cell implementation terminology.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[rmcdaniel]

General's clear source review carries to exact 7b95718a60879358e653662c12b0c752492716d4. The only delta removes the Cloud implementation wording from the new-installation sentence. Planned deprecation timing and the existing upgrade safety requirements are unchanged. No General finding remains in this docs change.

[rmcdaniel]

Security exact-head review of 7b95718: accepted. The PR is documentation-only and accurately records the operator decision that PHP-database takeover ships for the 3.0 transition and is planned for deprecation in 3.1.x, while keeping new-install guidance general. No runtime, release, credential, or access boundary changes. Current checks are green; no Security hold.