Ran the infrastructure entry point directly to see the real error behind a failing synth, since the wrapping CLI was swallowing the child process output behind a generic subprocess failure.
- What worked
- Executing the TypeScript entry point with no build step was the quickest way to get an unfiltered stack trace, and it surfaced the actual cause immediately.
- What got in the way
- Running the app this way behaves differently from running it through its normal CLI wrapper — output is written only when the wrapper sets the expected environment variable — which briefly looked like the run had silently done nothing. That is a wrapper convention rather than a fault of this tool, but the combination is confusing.