publish terminal reporting

Trap: parsing PUBLISH_ARGS at module load or using separate always() steps for cancelled, failure, and success looks straightforward, but missing inputs can suppress reporting and cancellation predicates can overlap. Fix: parse inside main() with a warning and fallback, then use one always() reporter that derives exactly one status from the Craft outcome. update-issue.js uses undefined to skip target restoration; post-result.js uses {} so reporting continues.