Verify archived v4 status and replication documentation against released behavior #732

Page or URL

• reference_versioned_docs/version-v4/operations-api/operations.md (set_status persistence)
• reference_versioned_docs/version-v4/replication/clustering.md (cluster_status field names)
• reference_versioned_docs/version-v4/replication/overview.md (destructive schema-operation replication)

What's wrong?

The v5 reliability-guide review in #671 identified analogous statements in the archived v4 reference whose released behavior has not been verified. This is an investigation task, not a confirmed v4 defect: v5 behavior alone is not evidence that the v4 text is wrong. The repository instructions keep archived-version changes separate from current v5 work.

Check the three contracts against the applicable released v4 core/Pro source and, where source is inconclusive, a disposable runtime. Record the exact tag/commit and evidence for status persistence, cluster-status response fields, and replication defaults for drop_database, drop_table, and drop_attribute. Correct archived prose only where that evidence shows a mismatch; otherwise close this audit with the evidence that the current wording is accurate.

Priority: P3. This is an off-roadmap documentation audit with no confirmed defect or customer incident. Effort: Low; the audit is bounded to three named contracts. No matching archived-v4 epic or committed release was found, so parent and milestone are unset.

Review-Deferral: 0d6e0904b0f240aa severity=minor category=documentation

_{🤖 Generated by OpenAI Codex; posted via @Ethan-Arrowood.}