Gate shared ops Telegram delivery and pairing in the portal adapter

PlasticDigits commented

2026-11-01 04:45:06 +00:00

Owner

Prepare authorized reuse of @cl8y_ops_bot in the portal application. The API uses nonsecret readiness; only the worker receives the bot token. Delivery and polling require separate explicit switches. The poller refuses webhook conflicts, preserves the existing allowed_updates filter, and accepts only exact private pairing commands.

Generic relay infrastructure, credential custody, operator tooling and operational receipts are maintained in the private cl8y-security repository. This PR final diff contains only the application adapter and its documentation; no infrastructure or credential artifacts are added.

Validation: five focused API tests passed and independent review reran them. Application code is unchanged from reviewed138bd04; dffbf05 rehomes generic infrastructure and corrects documentation. Source preparation only: no runtime release, credential injection, polling, webhook mutation or message sends. The owner has the token; hidden CLI enrollment is being prepared privately. Live consumer and actual worker egress verification remain pending. Existing SMTP and schema6 remain unchanged. Issue3 Telegram delivery acceptance remains open.

Prepare authorized reuse of @cl8y_ops_bot in the portal application. The API uses nonsecret readiness; only the worker receives the bot token. Delivery and polling require separate explicit switches. The poller refuses webhook conflicts, preserves the existing allowed_updates filter, and accepts only exact private pairing commands. Generic relay infrastructure, credential custody, operator tooling and operational receipts are maintained in the private cl8y-security repository. This PR final diff contains only the application adapter and its documentation; no infrastructure or credential artifacts are added. Validation: five focused API tests passed and independent review reran them. Application code is unchanged from reviewed138bd04; dffbf05 rehomes generic infrastructure and corrects documentation. Source preparation only: no runtime release, credential injection, polling, webhook mutation or message sends. The owner has the token; hidden CLI enrollment is being prepared privately. Live consumer and actual worker egress verification remain pending. Existing SMTP and schema6 remain unchanged. Issue3 Telegram delivery acceptance remains open.

PlasticDigits added 1 commit

2026-11-01 04:45:06 +00:00

Prepare explicitly gated shared ops Telegram delivery and isolated HTTPS relay 138bd047ba

PlasticDigits added 1 commit

2026-11-01 05:08:23 +00:00

Keep Telegram infrastructure proposal in private security repository dffbf0543c

PlasticDigits changed title from ~~Prepare gated reuse of the ops Telegram bot and isolated HTTPS relay~~ to Gate shared ops Telegram delivery and pairing in the portal adapter

2026-11-01 05:08:46 +00:00

PlasticDigits merged commit 357d15da9f into main

2026-11-01 05:19:25 +00:00

PlasticDigits referenced this pull request from a commit

2026-11-01 05:19:27 +00:00

Merge pull request 'Gate shared ops Telegram delivery and pairing in the portal adapter' (#22) from ops/shared-ops-telegram into main

PlasticDigits referenced this pull request

2026-11-01 05:49:16 +00:00

Email and Telegram warnings on security timer starts with deduplication and low-noise delivery #3

PlasticDigits referenced this pull request

2026-11-01 06:23:37 +00:00

Email and Telegram warnings on security timer starts with deduplication and low-noise delivery #3

Rows
Columns

Gate shared ops Telegram delivery and pairing in the portal adapter #22