A dead pod produced three hundred seconds of 'still no port' and no reason at
all, because the one Pod field that carries the reason was never queried. It
now travels into the progress line and the failure message, so an EXITED pod
says what RunPod says about it instead of leaving the cause to be guessed.

The strict-mode removal in boot.sh was one such guess: the image boots cleanly
here with a minimal environment and with a GPU exposed, so it does not
reproduce the exit. This is how the real cause gets found.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_0182DhR1eFNPQyGmDrpHbedY