autostockstaple-log-analysis

Search maafw logs for successful AutoStockBuyItemValleyIVTask or AutoStockBuyItemWulingTask clicks, then match each click box to the AutoStockInStapleItemName OCR box. Only count an item as purchased if its AutoStockStapleQuantityControl Buy branch succeeded and reached the confirm-buy path.

Recognition only means the item entered the quantity-control decision flow. If AutoStockStapleQuantityControl Exclude succeeded instead of Buy, the item was judged as not needed at current stock levels and must be reported as recognized but not purchased.

Large jumps near a scene switch usually mean the bill currency changed between ValleyIV and Wuling, not that one purchase consumed the difference. Check whether the task switched between AutoStockInStapleValleyIV and AutoStockInStapleWuling before attributing the change to a purchase.

No. AutoStockpileMain is a separate task driven by go-service gift-pack selection logic, while AutoStockStapleMain is driven by pipeline nodes like AutoStockBuyItemValleyIVTask. Mixing them produces incorrect purchase lists.

Track the file containing the matching task_id rather than relying on filename timestamps. A task may start in one maafw.bak file while later files only contain initialization content, so never conclude no purchase happened without checking all relevant rotated logs.

Add candidate-item logging at AutoStockBuyItemValleyIVTask and AutoStockBuyItemWulingTask, stop-reason logging at AutoStockTargetCanNotBuy nodes, and branch logging at AutoStockStapleQuantityControl Buy and Exclude nodes with region, item name, and current bill in the payload.