Release v4.51.4 — CLI hardening for multi-project sweeps · Canonry/canonry

Patch release. Closes the gap where main carried two CLI fixes that hadn't reached the npm artifact since 4.51.3.

Fixes (from #608)

fix(cli): cnry run --all --all-locations is per-project-smart — in a multi-project sweep, a project with zero configured locations no longer takes down the whole run. The CLI drops --all-locations per-project for 0-location projects and runs a single locationless sweep instead, same as cnry run <project> would. Single-project cnry run <project> --all-locations on a 0-location project still fails loud (explicit user error). This is what was 400-ing on demand-iq / gjelina-hotel.
fix(cli): handle the 207-array fan-out response in triggerRunAll — projects WITH locations were displaying as (failed) in the --all summary table even when every per-location run queued fine. The response is now normalized (single object or array), one results row per dispatched run, with a LOCATION column when any row carries one.

CLI-only. No API change. No behavior change for any 4.51.3 caller that wasn't already in the failing edge case.
npm @ainyc/canonry@latest → 4.51.4. Verified: fresh npm install + canonry --version → 4.51.4.

npm install -g @ainyc/canonry

🤖 Generated with Claude Code