What problem does it solve? Batching multiple on-chain actions (feed, commit, buyRelics, applyRelics, monthly action) into one checkout() transaction risks inconsistent ordering, mismatched payment handling, and divergent behavior versus executing actions individually. This Skill enforces a canonical execution order, deterministic validation, and exact payment reconciliation so the batched flow matches manual sequence semantics. ## Core Features & Use Cases - Canonical Execution Order: Enforces the fixed sequence payFeedCost → commitDaily → buyRelics → applyRelics → monthly action, with phase gates preserved in batch mode. - Deterministic Validation: Standardized revert selectors such as INVALID_PHASE, INSUFFICIENT_PAYMENT, INSUFFICIENT_STOCK, and MONTHLY_RATE_LIMIT for reliable frontend error mapping. - Payment Reconciliation: Requires msg.value >= totalCost and refunds the excess to the sender using a safe pattern, emitting events as if actions ran individually. - Use Case: When editing the checkout(CheckoutParams) contract function or the cart-building UI, use this Skill to verify equivalence between the batched transaction and the manual action sequence, including refund correctness and stock-change reverts. ## Quick Start Review my checkout() contract changes against the canonical batch ordering, validation rules, and payment reconciliation checklist.