AntFleet

Receipt · cdf9ffa0-3

ADMANAGE_API_KEY missing is documented as 'Hard-fails' but script actually exits 0

docs-gapmediumclosed in 4b9b492closed in 1 hour
repo 6f7fc663·PR #4·reviewed 2 days ago·2 days ago

The finding

  • scripts/postprocess-admanage.sh:18
  • scripts/postprocess-admanage.sh:46-50
  • scripts/postprocess-admanage-create.sh:22
  • scripts/postprocess-admanage-create.sh:49-54
The header comments in both scripts assert a hard-fail on missing key, but both scripts actually emit a warning and `exit 0` — i.e. soft-fail. This is a deceptive comment that an auditor will rely on when assessing safety posture. The behavior may even be intentional (so CI doesn't fail when key isn't injected for forks/PRs), but the docs must match the code.

Fix

Either change the header to 'Soft-fails (warns + notifies) if ADMANAGE_API_KEY is not set' or change the exit to `exit 1` to actually hard-fail.

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

114.5s · error

openai

claude-opus-4-7

131.1s · error

Total

wall-clock review time · est. inference cost

131.1s · $0.40

Sweeper

closed at SHA 4b9b492

closed in 1 hour

internal review id · cdf9ffa0

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 · ADMANAGE_API_KEY missing is documented as 'Hard-fails' but script actually exits 0