AntFleet

Disagreement · b1d71d08-anthropic-2

GNU-only `date -u -d '7 days ago'` will fail on BusyBox / macOS runners

solo Opus
repo 6f7fc663·PR #24·reviewed 1 week ago

Opus finding

GNU-only `date -u -d '7 days ago'` will fail on BusyBox / macOS runners

mediumbughigh
  • skills/fleet-state/SKILL.md:92-95
`date -d` is a GNU extension. On the standard ubuntu-latest GitHub Actions runner it works, but if any operator runs this skill locally on macOS or inside a slim Alpine container (busybox `date` does not accept `-d <relative>`), the variable becomes empty and the subsequent `select(.published_at >= $cutoff)` filter returns *every* announced release (since `>=` empty string matches all ISO strings). RELEASE_COUNT then explodes to the lifetime total, the verdict falsely reports `SHIPPED: <huge>`, and the notification gate flips on a quiet week. Given the skill explicitly documents the sandbox is local file I/O and may be reused, portability is in scope.

Recommendation

Compute the cutoff in jq using `now`: `RELEASES_THIS_WEEK=$(jq '[.announced[] | select((.published_at | fromdateiso8601) >= (now - 604800))]' "$RELEASE_STATE")`. Removes the date(1) portability dependency entirely.

Other reviewer

The other reviewer flagged nothing in this file/line range.

Why this didn't post

This finding didn't meet AntFleet's unanimous agreement threshold. Both frontier models review every PR independently; only findings they both flag with the same severity and category are posted to the PR. This one fell through.

read the methodology →

From the same review

These findings passed the unanimous gate on the same PR review. The disagreement above was filtered out; the findings below were posted.