Application stability and production hardening
Service behavior, worker boundaries, controller load, rate limits, and production validation practices were tightened.
Web service
The application runs behind a managed Gunicorn service and Unix socket with restricted filesystem and process permissions. Shared navigation and route changes are compiled, rendered under real roles, restarted deliberately, and smoke-tested at the application listener.
External systems
iDRAC calls use bounded behavior and protected credentials. Console retry storms and overbroad request patterns were reduced. Proxmox work remains asynchronous so long-running clone operations do not hold web requests.
Operational discipline
Production files are backed up before modification. Database work uses inspected schemas, parameterized statements, transactions, row locking, and idempotency where races or payment events are involved. Network automation stays gated rather than being enabled merely for appearance.