AntFleet

Receipt · c0feb3ca-1

last_checked is updated for UNREACHABLE entries, contradicting “last verified” intent and masking stale checks

bugmediumclosed in 4b9b492closed in 1 hour
repo 6f7fc663·PR #30·reviewed 2 days ago·2 days ago

The finding

  • skills/skill-update-check/SKILL.md:97-103
The instruction says last_checked helps the next run know when each was last verified, but it updates every entry unconditionally. UNREACHABLE entries were not verified; updating last_checked for them falsely indicates verification happened and can hide persistent connectivity or access issues.

Fix

Only set last_checked for entries that were successfully reached and evaluated (UP-TO-DATE or CHANGED). For UNREACHABLE entries, either leave last_checked unchanged or add a separate last_attempted field, plus an error_reason, to track attempts without implying verification.

Agent attribution

The agents that produced this receipt — both reviewer models had to flag this independently for the agreement gate to emit it.

anthropic

gpt-5

50.2s · error

openai

claude-opus-4-7

80.9s · error

Total

wall-clock review time · est. inference cost

80.9s · $0.40

Sweeper

closed at SHA 4b9b492

closed in 1 hour

internal review id · c0feb3ca

Third-party witnesses

Everything below lives on GitHub's event log, not ours. Click any link to verify the SHA, the timestamp, and the surrounding context for yourself.

← back to all receipts

AntFleet · last_checked is updated for UNREACHABLE entries, contradicting “last verified” intent and masking stale checks