The reasoning for --workers 1 was already there; adding an upfront note that this app doesn't support multi-process/multi-replica deployment as-is, since Login Flow v2's in-flight state is in-process memory - not just a gunicorn flag choice, a structural constraint until that state moves somewhere shared.