chore(test): подтвердить права очереди в браузере с JWT

docs/ux-ui/acceptance/browser-outbox-jwt-2026-10-08.json

@@ -0,0 +1,45 @@
+{
+  "date": "2026-10-08",
+  "backendSource": "8782054",
+  "frontendSource": "b55588f",
+  "database": "mmapp_acceptance_20261007",
+  "authRequired": true,
+  "browserHttpMocks": false,
+  "realSignedJwt": true,
+  "reader": {
+    "retryButtonDisabled": true,
+    "bypassHttpStatus": 403,
+    "sqlUnchanged": true,
+    "mutationCalls": 0,
+    "reloadSeesCommittedQueue": true
+  },
+  "forgedSignature": {
+    "httpStatus": 401,
+    "sqlUnchanged": true,
+    "mutationCalls": 0
+  },
+  "writer": {
+    "httpStatuses": [
+      200
+    ],
+    "riskAcknowledgementRequired": true,
+    "saved": {
+      "id": "acceptance-browser-jwt-1791445526386",
+      "status": "pending",
+      "resolution_version": 1,
+      "retry_count": 0
+    },
+    "captionDoesNotClaimDelivery": true
+  },
+  "retryRequests": 3,
+  "mutationCalls": 1,
+  "historyRows": 0,
+  "externalSenderCalls": 0,
+  "mobileFits": true,
+  "pageErrors": [],
+  "limits": [
+    "Separate fixture JWT key/issuer in isolated process, actual Portal login not tested",
+    "Synthetic PostgreSQL row; sender/scheduler stopped, no actual Telegram message",
+    "Reader direct POST uses browser fetch; forged signature checked via real HTTP API request context"
+  ]
+}