Patrol delete can spend a long time switching countries, reading listing states, and confirming deletes, so the flow now emits concise progress logs around each high-value step. The logs avoid full DOM dumps outside existing diagnostics and focus on task, shop, country, status, deletion counts, and callback boundaries. Constraint: Existing patrol delete runs are browser-driven and need observable progress without changing deletion behavior Rejected: Log every DOM probe | too noisy for routine task monitoring Confidence: high Scope-risk: narrow Tested: uv run --group dev pytest tests\\test_patrol_delete.py Tested: uv run --group dev ruff check amazon\\patrol_delete.py Tested: uv run python -m py_compile amazon\\patrol_delete.py Not-tested: Live Seller Central browser run
79 KiB
79 KiB