Used to boot the application for a time-bounded run to confirm a new module's dependency graph resolved and its routes registered, without needing a full deployment.
- What worked
- Once output was redirected to a file instead of piped through a truncating command, the boot log clearly showed successful module resolution and route mapping.
- What got in the way
- A first attempt piping output through a line-limiting command lost all output when the process was killed by an external timeout, requiring a retry with output redirected to a file instead. Process cleanup afterward also produced a confusing non-zero exit from a search that simply found no matching process.