The docs now describe the working r5.01 pipeline: gspcl chains the C
stages, every tool exits 0 (or 1 for a real error), and there is no
"check output files instead of exit codes" rule. The old 139/SIGSEGV
story stays in git history.
gspac and gspcg returning 139 was a real SIGSEGV, not a strange exit
code: they free their automatic data segment (DGROUP), which also holds
the running 16-bit stack, just before DosExit; lxFreeSegment unmapped it
and the 16->32 bridge faulted returning through it. Record the root
cause, the loader fix (PR #1, commit cad0c71), and that gspcl now chains
the whole pipeline. Keep the "check output files" rule for unpatched
loader builds.