Document features added for backup/restore support

Add "Features Added for Backup/Restore" section to README documenting:
- Staged Deployment (PR openstack-k8s-operators#1785): Pause deployment after infrastructure
  ready to allow database restore before services start
- Service Name Caching (PR openstack-k8s-operators#1796): Preserve service names across
  backup/restore when UniquePodNames is enabled

Update enhancement-staged-deployment-restore.md:
- Mark status as Implemented with reference to PR openstack-k8s-operators#1785
- Keep document as historical reference and context

Add link from backup-restore-ctlplane.md to enhancement document
to provide detailed context on staged deployment feature.

Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>

Author: stuggi

docs/dev/README.md

@@ -49,6 +49,15 @@ ansible-playbook restore-openstack-ctlplane.yaml
 ansible-playbook restore-openstack-dataplane.yaml
 ```
 
+## Features Added for Backup/Restore
+
+The following enhancements were implemented to enable reliable backup and restore:
+
+| Feature | PR | Description |
+|---------|-----|-------------|
+| **Staged Deployment** | [#1785](https://github.com/openstack-k8s-operators/openstack-operator/pull/1785) | Allows pausing deployment after infrastructure (MariaDB, OVN, RabbitMQ) is ready but before OpenStack services start. Enables database restore before services initialize schemas, avoiding conflicts and service restarts. See [enhancement-staged-deployment-restore.md](enhancement-staged-deployment-restore.md) for details. |
+| **Service Name Caching** | [#1796](https://github.com/openstack-k8s-operators/openstack-operator/pull/1796) | Ensures service names remain consistent across backup/restore when `UniquePodNames` is enabled. Service names are cached via webhook during initial creation and preserved when CR is recreated from backup, preventing service name changes that would break references. |
+
 ## Key Concepts
 
 ### ControlPlane vs DataPlane

docs/dev/backup-restore-ctlplane.md

@@ -178,6 +178,8 @@ flowchart TD
 - **Resume Deployment**: Removing the `deployment-stage` annotation triggers creation of OpenStack services
 - **Services Start Clean**: Keystone, Nova, etc. start with already-restored databases (no restarts needed)
 
+**Staged Deployment Feature**: The staged deployment mechanism using the `deployment-stage` annotation is a key feature for reliable restores. For detailed context on why this feature was implemented and how it works, see [enhancement-staged-deployment-restore.md](enhancement-staged-deployment-restore.md).
+
 **Important**: While we don't backup RabbitMQ queue data, we create a fresh RabbitMQ cluster on restore. The RabbitMQ default user credentials **MUST be backed up and manually restored** for EDPM/data plane deployments. See "RabbitMQ User Management" in the Scope section for details.
 
 ## Prerequisites

docs/dev/enhancement-staged-deployment-restore.md

@@ -2,14 +2,17 @@
 
 ## Metadata
 
-- **Status**: Proposed
+- **Status**: Implemented
 - **Author**: OpenStack Operator Development Team
 - **Created**: 2026-01-23
+- **Implemented**: 2026-02-10 via [PR #1785](https://github.com/openstack-k8s-operators/openstack-operator/pull/1785)
 - **Related Documentation**:
-  - [backup-restore-stateless.md](backup-restore-stateless.md)
+  - [backup-restore-ctlplane.md](backup-restore-ctlplane.md)
   - [backup-restore-ovn.md](backup-restore-ovn.md)
   - [backup-restore-pvc.md](backup-restore-pvc.md)
 
+**Note**: This document is kept as historical reference and context for the staged deployment feature. The feature is now part of the main codebase.
+
 ## Summary
 
 Add support for staged deployment to the OpenStackControlPlane controller, allowing infrastructure services (MariaDB, OVN, RabbitMQ, Memcached) to be created and paused before OpenStack services are deployed. This enables database restore to occur before services start, resulting in a cleaner and more reliable restore process.
@@ -520,7 +523,7 @@ echo "✓ All services ready"
 
 Update all restore documentation to mention staged deployment:
 
-**backup-restore-stateless.md:**
+**backup-restore-ctlplane.md:**
 ```markdown
 ## Restore Procedure