docs: sync from backend ca2b1c4 — marketplace e2e smoke runner

11 - Testing/Testing Overview.md

@@ -23,6 +23,7 @@ seller, payment scanner, delivery, payout, dispute, and deployment behavior.
 | [[Scanner BSC Testnet Payment Procedure]] | BSC Testnet tUSDT scanner payment procedure and failure modes. |
 | [[Notification Assertion Procedure]] | Required notification checks after every E2E business step. |
 | [[Concurrency and Performance Profile]] | Ramp test design, profiling targets, metrics, and report template. |
+| [[Marketplace E2E Smoke Runner]] | Implemented backend smoke runner, modes, commands, reports, and current dev findings. |
 | [[Smoke and Regression Procedure]] | CLI, CI, and post-deploy smoke checks. |
 | [[Testing Expansion Backlog]] | Gaps to cover before broader release confidence. |
 
@@ -74,3 +75,4 @@ The current live tested version of this path is documented in
 - Record enough evidence to reproduce a failure: request id, offer id, payment id, tx hash, chain id, token address, HTTP status, and CI build number.
 - Treat a passing local test as necessary but not sufficient for scanner/payment work. Payment changes must also be verified against dev after deploy.
 - Every live-dev test should state what remains untested or blocked.
+- Use `backend/scripts/smoke/marketplace-e2e-notifications.sh` for implemented buyer/seller smoke runs before extending scenarios manually.