PR Pipeline — Authorize → Validate → Review → Merge / auth (pull_request) Successful in 3s
PR Pipeline — Authorize → Validate → Review → Merge / validate (pull_request) Successful in 5s
PR Pipeline — Authorize → Validate → Review → Merge / lint (pull_request) Successful in 7s
PR Pipeline — Authorize → Validate → Review → Merge / ai-review (pull_request) Successful in 6s
PR Pipeline — Authorize → Validate → Review → Merge / gate (pull_request) Successful in 2s
Intent requires a production run log, not only the unit-level dry run. This is a real scan of the live 25-entry fleet through scripts/disk-gc-plan.py: CT 111 (tdunna) at 84% AMBER is alerted as report-only and no gc-executor row is emitted for it; the owned hosts acerpve .9 (77%) and amdpve .15 (76%) still receive gc-executor. No GC command was run against 192.168.68.129.