_shared/procedures/bin/*: a --flag passed as the last argument dies with a bare exit 1 and no message #356

New issue

Open

opened 2026-08-26 15:46:21 +00:00 by jbr870 · 0 comments

jbr870 commented

2026-08-26 15:46:21 +00:00

Owner

Spawned from finding F-PO-47-3-2 on issue #47 during decision D-PO-47-3-2.

Original scope note: Pre-existing across the helper family. Under set -e, shift 2 on a flag with no value fails and the helper exits 1 silently — the operator sees no diagnosis at all.

Disposition rationale: Recommended disposition. This is exactly the 'no shell-level error reaches the operator' class #47 is about, but living in every other helper rather than the pipeline path. #47 fixed it in the two files it owns with an explicit per-flag arity guard; sweeping the family is a separate change with its own regression surface. Resolved autonomously under the operator's standing instruction to resolve PO-47-3 as recommended.

This issue was deferred out of the parent feature's scope; it carries no PREQ yet. Run /dev:requirements --issue={new-number} to flesh it out before planning.

Spawned from finding `F-PO-47-3-2` on issue #47 during decision D-PO-47-3-2. **Original scope note:** Pre-existing across the helper family. Under set -e, shift 2 on a flag with no value fails and the helper exits 1 silently — the operator sees no diagnosis at all. **Disposition rationale:** Recommended disposition. This is exactly the 'no shell-level error reaches the operator' class #47 is about, but living in every other helper rather than the pipeline path. #47 fixed it in the two files it owns with an explicit per-flag arity guard; sweeping the family is a separate change with its own regression surface. Resolved autonomously under the operator's standing instruction to resolve PO-47-3 as recommended. This issue was deferred out of the parent feature's scope; it carries no PREQ yet. Run `/dev:requirements --issue={new-number}` to flesh it out before planning.

jbr870 added the

labels

2026-08-26 15:46:21 +00:00

jbr870 referenced this issue

2026-08-26 15:46:22 +00:00

release-pipeline-status.sh --ref returns a stale pipeline — a false green immediately before a production tag #47