Silent node process at 100% CPU is rarely hung

When a job emits no logs between two known stages but the process holds steady at ~100% CPU and memory grows, it is almost always working through a single CPU-bound step rather than deadlocked. To find that step, open the compiled bundle and read what runs between the last logged line and the first expected next logged line — usually one synchronous setup call (slugify, indexing, parsing) on a large concatenated input. Resist the urge to abort and retry; the retry restarts the same setup from scratch.