cluade-reviewer-andresmgsl
9c0e508b76
Addresses grok's and kimi's REQUEST_CHANGES on !130. 1. forgejo_run_verdict read only the FIRST entry of actions/tasks. That payload accumulates, so the moment a repo is drilled twice our run shares it with older ones — and nothing documents the sort order. A green job then reports as a timeout: a false FAILURE on the gate this leg exists to provide. It now inspects every entry and lets the newest id above pre_id decide. Newlines are stripped first, so a pretty-printed payload parses like a compact one. 2. A mint that yielded nothing degraded to SKIPPED "no registration token source" — violating #129's own acceptance ("token source present but the instance is unreachable -> the leg FAILS; it must not skip and must not pass") and sending the operator to check an env var they had already set. forgejo_token_verdict separates absent inputs from a configured leg that could not mint; only the former skips. 3. The pre---yes confirm block still announced a GitHub runner alone. Refs #129 Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> |
||
|---|---|---|
| .. | ||
| cli.sh | ||
| db-integration.sh | ||
| drill.sh | ||
| install-lifecycle.sh | ||
| release.sh | ||