fix(plan-groomer): avoid crash on empty DIGEST with zero findings

`${DIGEST:?}` aborts the script when DIGEST is unset/empty (i.e. when no
upstream checker findings exist). Replace with null-safe `${DIGEST:-}` so
the report-only mode exits cleanly on a clean week.
This commit is contained in:
seahaven-openswe[bot] 2026-08-04 12:13:28 +00:00
parent a82092f4ca
commit a0bd8632b5

View file

@ -298,7 +298,7 @@ if [ "$NOTIFY" -eq 1 ] && [ "$DRY_RUN" -eq 0 ]; then
# is REPORT-ONLY and must not auto-write. The composed digest is available in $DIGEST. # is REPORT-ONLY and must not auto-write. The composed digest is available in $DIGEST.
log "--notify requested but inert in this phase (D3: report-only; auto-write is a later toggle). No push." log "--notify requested but inert in this phase (D3: report-only; auto-write is a later toggle). No push."
fi fi
: "${DIGEST:?}" >/dev/null 2>&1 || true # DIGEST is composed for the future seam; keep it referenced. DIGEST="${DIGEST:-}" # DIGEST is composed for the future seam; keep it referenced.
log "REPORT-ONLY: groomed plan written to the mode-600 report; nothing posted (D3)." log "REPORT-ONLY: groomed plan written to the mode-600 report; nothing posted (D3)."
exit 0 exit 0