The operator reported that automatic outreach did not work, authorized repair, chose Telegram, and explicitly confirmed ownership of the existing EventHorizon shared-business-versus-gameplay-repair decision: “Yes, send it to my Telegram.” This authorizes delivery of that request, not either product decision or restarting issue automation.
There were no configured escalation contacts. One open request (escalation 1, cycle 98225) was assigned to a planning worker account rather than an authenticated human. It had only a pending internal projection and no external delivery. Configuring contacts did not backfill existing requests. Backend server-only did not dispatch notifications; the ordinary loop also admitted escalation-analysis work and therefore could not be restarted under the stop order. No inbound Telegram reply handler exists.
PR 4398, merged revision a15b05fd43a3e110224dd534100dc8ade116fe83, separates delivery from analysis and runs delivery every 30 seconds in server-only mode. Authenticated request/contact APIs remain usable while the answer endpoint remains blocked. Saving a contact backfills only its owner's open requests. Pending deliveries require an enabled contact and open request, use a five-minute claim lease, batches of ten, twenty-second connector timeouts and existing bounded retries. Successful receipts are preserved. Network ambiguity can still cause a retry after an unconfirmed send; exactly-once transport is not claimed.
Messages lead with a bounded, readable question. Full Rust tests and isolated PostgreSQL delivery-boundary, backfill, priority and answer/resumption regressions passed. The merged source tree matches the tested branch. No independent reviewer or provider CI result is claimed; Actions remain stopped.
The existing authenticated, allowlisted operator's Gitea profile supplied the Telegram destination; Telegram getChat verified it as private. The private mapping is stored in the existing operator-managed autocoder-secrets under AUTOCODER_ESCALATION_TELEGRAM_DESTINATIONS_JSON, with reference operator-ax-bechju1. All unrelated Secret keys were preserved with resourceVersion checking. No chat ID or credential is recorded here. The repository deployment already imports this Secret.
A guarded transaction reassigned only the confirmed EventHorizon request to the operator and made its question readable, retaining the previous owner and original wording in the request's evidence. No decision was recorded and no cycle or worker was resumed. The message recommends fixing existing gameplay first and asks for an answer in the current Codex conversation because Telegram replies are not connected.
The exact merged backend was deployed as generation 2386, image sha-a15b05fd43a3, digest sha256:b90f5b7c36478f7685b95b48ed46043905db9f9c42749227c058b85138939e47. Rollout and immutable image readiness passed; a deployment receipt was retained. Server-only arguments were preserved. The idle supervised worker and frontend were not changed.
The actual authenticated contact PUT API backfilled one Telegram delivery, using a short-lived administrator verification session for the independently authenticated and allowlisted user; that session was revoked. This verifies the application API, not the OAuth login exchange. The paused application's dispatcher recorded outbox 2 delivered at 2026-09-15T05:34:46.405707Z, attempts 1, no error. No manual sendMessage call substituted for the application path. This is transport acceptance; the operator has been asked to confirm arrival and readability.
The protected cycles 98225, 98295 and 97925 retained identical state and evidence before/after delivery; zero workers were running and the same single queued task remained. General automation remains stopped. Issues 1571 and 1447 retain their existing verification/acceptance gates. This one-request delivery does not prove future legacy worker-owned request routing or automatic creation of final-acceptance requests.
The temporary test database port-forward, image builder and task-scoped registry credentials were removed. Bounded operational evidence is retained under /home/ax_julian/temp/operator-telegram-outreach pending operator verification, with cleanup review due 2026-09-22.
Deployment uses the existing exact-generation rollout verifier and retains the previous server-only image/revision for rollback. Disable the configured contact to suppress future claims if outreach must stop. Preserve the request's original evidence and all delivery receipts. Do not restart the ordinary loop as a notification repair.