docs(examples): compliance_merchant uses retry_step instead of duplicating retry in extra_steps

Mirror of node-commerce 363bda4. Switch the example from extra_steps[0]
re-stating the canonical retry to retry_step REPLACING the canonical step 5
with the merchant-specific retry. extra_steps now holds only the genuinely
additional 402-payment follow-up step.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

Author: vvillait88

examples/compliance_merchant.py

@@ -45,13 +45,17 @@
 
 SUPPORT_EMAIL = "support@example.com"
 
-# Vendor-specific extension of the canonical agent_instructions block. Commerce defaults cover
-# steps 1-5 (present verify_url, poll, extract token, retry). We append steps 6-7 describing how
-# to RESUME a pending order with order_id + complete the eventual 402 payment.
+# Vendor-specific extension of the canonical agent_instructions block. The commerce default
+# covers steps 1-4 (present verify_url, poll, user verifies, extract token) plus a generic
+# "retry the original merchant request" at step 5. ``retry_step`` REPLACES that generic step 5
+# with our merchant-specific retry (include order_id to resume the pending order). ``extra_steps``
+# adds the genuinely-additional 402-payment step that comes AFTER retry.
 VERIFICATION_INSTRUCTIONS = verification_agent_instructions(
-    extra_steps=[
+    retry_step=(
         "Retry the request with header X-Operator-Token set to the operator_token value AND include the "
-        "order_id from this 403 in the body to resume the pending order.",
+        "order_id from this 403 in the body to resume the pending order."
+    ),
+    extra_steps=[
         "The retry returns 402 Payment Required with a payment challenge. Pay via tempo request or agentscore-pay pay.",
     ],
     order_ttl="Pending orders expire after 1 hour. If the order expires, start a new request.",