Operational readiness

Provider-specific operational commands cannot be documented until the Lovable-connected infrastructure proof selects and verifies identity, SQL, server execution, object storage, secrets, and deployment boundaries.

Required evidence

• Environment inventory and ownership for development, test, and production.
• Private-by-default object storage configuration and anonymous-access test.
• SQL migration, backup, restore, and connection-privilege procedures.
• Identity bootstrap, invitation, deactivation, session revocation, and recovery procedures.
• Secret creation, rotation, and incident-revocation boundaries.
• Audit append-only enforcement and administrative access controls.
• Upload reconciliation and orphan cleanup procedure.
• Correlation-ID lookup across CLI, service logs, SQL/storage workflow, and audit events.
• Release signing, public-key rotation, artifact publication, rollback, and compromised-release response.
• At least one non-production SQL restore and one end-to-end file recovery exercise.

Runbooks to create after the infrastructure proof

1. Deploy and rollback backend services.
2. Apply and verify database migrations.
3. Restore SQL and validate object references.
4. Reconcile incomplete uploads and orphan objects.
5. Bootstrap and recover the global administrator.
6. Investigate an authorization denial by correlation ID.
7. Revoke sessions for a deactivated or compromised user.
8. Publish, withdraw, and supersede a CLI release.
9. Rotate manifest signing keys without stranding installed clients.
10. Respond to suspected credential or artifact compromise.

Publication rule

Never publish placeholder operational commands as executable guidance. A runbook becomes official only after the commands have been executed successfully in the named non-production environment, outputs and rollback have been captured, and secrets have been removed from the record.