{{-- "We are updating" — one panel, used in both places it can appear. It showed up twice with two different faces: the console's own overlay in the app's light tokens while the application was still up, and then this, the 503 page, once the containers went down. Two designs for one event, one replacing the other mid-update. Reported as "the first screen must not be there", and rightly. The styles are inline and self-contained rather than Tailwind classes, because the other place this renders is the 503 page — shown while the application is mid-deploy or freshly installed, exactly when the Vite manifest may not exist. A stylesheet reference there would throw instead of rendering the reassurance the visitor came for. Prefixed class names: this is injected into the console's own document, which has a stylesheet of its own, and `.badge` is not a name to claim globally. --}}
{{ __('updating.badge') }}

{{ __('updating.title') }}

{{ $body ?? __('updating.body') }}

{{-- Only in the console. A customer looking at the 503 has no use for a deployment step, and an operator watching a run that is stuck has no use for anything else: "läuft gerade" alone is what sends somebody to the shell. The markup is Alpine-driven and inert wherever Alpine is not — which is why it is behind a flag rather than always present. --}} @if ($detail ?? false)

{{ $starting ?? '' }}


            
@endif

{{ __('updating.auto') }}