v1.5.0 — record a failed pipeline stage as failed

Added

• defprod-stamp --fail — records the in-progress stage as failed via the failChangeStage case. Use it in a CI failure trap: unlike --cancel it does not revert the stage to not-started, so an aborted run is no longer indistinguishable from one that never began. Takes no --stage (the server resolves the in-progress stage); pair it with --note carrying the reason.
• defprod-stamp --help / -h — prints usage and exits 0. Also a capability-probe surface: a CI caller can grep --help for a flag name to find out whether the installed copy supports it, instead of discovering the gap as a mid-pipeline Unknown argument failure.

Changed

• A bad argument now prints usage to stderr alongside the existing Unknown argument message.
• README documents --fail vs --cancel: prefer --fail in a failure trap; --cancel is for deliberate abandonment.

Compatibility

No breaking changes. --start, --cancel, --stage and the default finish behaviour are unchanged, and --help previously exited 2, so no working caller relied on its old behaviour.

--fail requires a DefProd backend exposing the failChangeStage case. Against an older backend the call is rejected and logged to stderr — the pipeline still exits 0, as ever.

Upgrade

npm install -g @defprod/scripts
# or
npx @defprod/scripts defprod-stamp --help