`docker stack deploy` briefly tears down and recreates tasks in Swarm's
internal bookkeeping, so `docker stack ps` can transiently return nothing
right after a deploy even when the service is healthy. A single `sleep 5`
followed by one check produced a false-alarm-looking "nothing found in
stack: vaultwarden" on an otherwise-successful deploy (2026-08-25).
Now retries up to 6 times, 5s apart (~30s total) before printing a WARNING
with a manual-check command. Does not fail the pipeline on its own --
verify was already informational, not a hard gate.
No changes to provision-secrets or deploy steps.
admin