Telegram alert sweep leaves an orphaned program copy in repos that used a different path #853

New issue

Open

opened 2026-08-16 05:51:43 +00:00 by coilyco-ops · 0 comments

coilyco-ops commented

2026-08-16 05:51:43 +00:00

Owner

The roller migrates a step to scripts/alert-telegram.py but never removes a
program copy the migrated step no longer calls. Two repos carry the alert at a
different path and will be left with an orphan:

coilyco-bridge/agentic-os-kai - scripts/ci/alert-telegram.py, called by
sync-repo-registry.yml, sync-repo-digests.yml, build-catalog-graph.yml.

coilyco-flight-deck/infrastructure is exempt: it authors the program, takes no
install copy, and keeps calling its own scripts/actions/ path.

The orphan is inert, not harmful. It is dead code that still reads like a live
alert path, and it holds the direct-to-Telegram transport the migration is
retiring, so anyone reading it later gets the wrong picture of how alerting
works.

Deliberately not folded into the roller in #852. Deleting files in consumer
repos is a wider blast radius than adding them, and the sweep should be
observed once before the roller is given that.

Options, in order of preference:

A targeted PR per affected repo after the sweep lands. Two repos, small.
Teach the roller to delete an alert program that no workflow references,
guarded so it only fires when a migration actually happened in that run.

Blocked on: the fleet sweep running, which is blocked on #852.

The roller migrates a step to `scripts/alert-telegram.py` but never removes a program copy the migrated step no longer calls. Two repos carry the alert at a different path and will be left with an orphan: * `coilyco-bridge/agentic-os-kai` - `scripts/ci/alert-telegram.py`, called by `sync-repo-registry.yml`, `sync-repo-digests.yml`, `build-catalog-graph.yml`. `coilyco-flight-deck/infrastructure` is exempt: it authors the program, takes no install copy, and keeps calling its own `scripts/actions/` path. The orphan is inert, not harmful. It is dead code that still reads like a live alert path, and it holds the direct-to-Telegram transport the migration is retiring, so anyone reading it later gets the wrong picture of how alerting works. Deliberately not folded into the roller in #852. Deleting files in consumer repos is a wider blast radius than adding them, and the sweep should be observed once before the roller is given that. Options, in order of preference: 1. A targeted PR per affected repo after the sweep lands. Two repos, small. 2. Teach the roller to delete an alert program that no workflow references, guarded so it only fires when a migration actually happened in that run. Blocked on: the fleet sweep running, which is blocked on #852.

coilyco-ops added the

role/sysadmin

priority

labels

2026-08-25 08:02:08 +00:00

coilyco-ops added the

autonomy

async-consult

label

2026-08-25 09:30:59 +00:00

coilyco-ops added this to the Observability and alerting milestone

2026-08-29 06:09:20 +00:00