review · segments
Verify USPS Label Broker purge cron capacity and starvation (V12)
claude 39 events 1 segments master
segment 1 of 1
Verify candidate V12 about USPS Label Broker purge cron capacity and starvation
The assistant acted as an adversarial verifier for candidate V12, which claimed the daily purge cron cannot keep up due to budget sharing, missing age predicate, and cross-key starvation. The assistant gathered evidence by reading the plugin source code, HPOS_TRANSITION_NOTES.md, and theme template files. It confirmed the SQL query has no age predicate, ORDER BY post_id ASC (oldest first), the budget split in run_purge_pass causes the second key to never get budget, and the documented volume (~351 labels/day, 2 keys = ~702 rows/day) exceeds the 500-row budget. The verdict was CONFIRMED with detailed evidence.
outcome
Candidate V12 is CONFIRMED; the purge cron has a cross-key starvation bug where the second URL meta key never gets processed, and the daily budget is insufficient for the incoming volume.
next steps
—
key decisions
- Read the plugin file at key lines (818-826, 793-797, 1045) to verify SQL query, budget split, and cron hook.
- Read HPOS_TRANSITION_NOTES.md to confirm documented label volume (~351/day, ~10.5K/month).
- Read the theme template to confirm both URL meta keys are written per order.
- Analyzed ORDER BY direction (post_id ASC) to refine sub-claim (b) — head rows are oldest, so within-key starvation is bounded, not permanent.
open questions
—
3 weeks ago → 3 weeks ago