Verify duplicated environments at the service runtime layer

Treat environment duplication as a potentially active deployment operation. After cloning an environment, inspect each service's deployment status and running replicas before copying credentials, connecting data sources, or assuming the clone is inert. A project canvas or environment-level label is not sufficient runtime evidence.

This is a verification rule for multi-service platforms, not a claim that every duplicate starts automatically. Duplicate semantics can differ by product path and version, so confirm the current platform contract and use service-level readback before proceeding.