chore(tests): проверить доставку Telegram и сохранить границы повтора

docs/ux-ui/acceptance/telegram197-summary-2026-10-13.json

@@ -0,0 +1,42 @@
+{
+  "date": "2026-10-13",
+  "block": "12.5.197",
+  "humanReceipt": {
+    "confirmed": true,
+    "message1": 1,
+    "message2": 2
+  },
+  "providerAcceptedMessages": 3,
+  "livePartialCases": [
+    "dedupe",
+    "two independent sender processes",
+    "controlled receipt suppression after real provider acceptance",
+    "unknown not automatically resent"
+  ],
+  "liveResumeCases": [
+    "reader 403",
+    "missing duplicate ack 400",
+    "admin CAS 200",
+    "stale version 409",
+    "provider accepted explicit resend",
+    "sent state and history committed"
+  ],
+  "dryProvider": {
+    "fullScenarioPassed": true,
+    "realOwnedPostgreSQL": true,
+    "realPortalJWT": true,
+    "telegramNetwork": false
+  },
+  "cleanup": {
+    "threeOwnedDatabasesAndRolesRemoved": true,
+    "ownPortalUsersRemoved": true,
+    "temporaryBotPrivateFileRemoved": true
+  },
+  "limitations": [
+    "First complete live run failed asserting immediate resend sent=1; outcome was not captured. Cause remains unresolved.",
+    "Successful live retry used a new owned unknown-row fixture; it was not continuation of the same database transaction chain.",
+    "Lost receipt was injected after provider acceptance, not a physical WAN disconnect.",
+    "No single uninterrupted full live pass claimed."
+  ],
+  "runtimeChanged": false
+}