coilyco-flight-deck/agentic-os

Watch

Fix Telegram alert action resolution from stale mirror #411

New issue

Closed

opened 2026-07-10 04:51:46 +00:00 by coilyco-ops · 2 comments

coilyco-ops commented

2026-07-10 04:51:46 +00:00

Member

Fix CI failure resolving local Telegram alert action from stale GitHub mirror

Main CI is failing before the intended job body runs:

forgejo-runner-2(version:v12.10.1) received task 8316 of job test, be triggered by event: push
🚀  Start image=forgejo.coilysiren.me/coilyco-flight-deck/agentic-os:latest
☁️  git fetch 'https://github.com/actions/checkout' # ref=v6
☁️  git fetch 'https://github.com/coilyco-flight-deck/agentic-os' # ref=main
⚙️ [runner]: failed to read action 'Alert Telegram on main failure', no files found after reading paths: action.yml, action.yaml, Dockerfile
failed to read action 'Alert Telegram on main failure', no files found after reading paths: action.yml, action.yaml, Dockerfile

Live facts checked from this director surface:

Forgejo main contains actions/telegram-alert/action.yml at latest commit 748bf56060ef feat: add Telegram CI alert action.
https://raw.githubusercontent.com/coilyco-flight-deck/agentic-os/main/actions/telegram-alert/action.yml returns 404.
The failing runner log shows the job fetching https://github.com/coilyco-flight-deck/agentic-os while resolving the workflow checkout/action state, so the local action path is coupled to GitHub mirror freshness.
The failing workflows call uses: ./actions/telegram-alert from release.yml, dep-bump.yml, freshness.yml, and mirror-to-github.yml.

Implementation goal:

Stop main CI from failing when the Telegram alert action exists on Forgejo canonical but is absent or stale on the GitHub mirror.
Preserve the intended behavior: alert Telegram only on main failure.
Prefer a robust fix for failure-path alerting. A failure alert path should not depend on a local action that may be missing from the checked-out workspace. Inlining the small alert implementation in each workflow, adding a committed script invoked by run:, or forcing checkout/action resolution to Forgejo canonical are all acceptable if the result is reliable under Forgejo runner behavior.
If the local composite action remains, ensure every job that calls it has a checkout containing the action before the call, from Forgejo canonical, not from a stale mirror.

Acceptance criteria:

The workflows no longer fail with failed to read action 'Alert Telegram on main failure'.
The alert path still uses TELEGRAM_BOT_TOKEN and TELEGRAM_RED_CHAT_ID secrets without leaking them.
The fix accounts for Forgejo canonical vs GitHub mirror timing.
Run the available workflow/lint validation for the edited YAML/action/script surfaces.

Fix CI failure resolving local Telegram alert action from stale GitHub mirror Main CI is failing before the intended job body runs: ```text forgejo-runner-2(version:v12.10.1) received task 8316 of job test, be triggered by event: push 🚀 Start image=forgejo.coilysiren.me/coilyco-flight-deck/agentic-os:latest ☁️ git fetch 'https://github.com/actions/checkout' # ref=v6 ☁️ git fetch 'https://github.com/coilyco-flight-deck/agentic-os' # ref=main ⚙️ [runner]: failed to read action 'Alert Telegram on main failure', no files found after reading paths: action.yml, action.yaml, Dockerfile failed to read action 'Alert Telegram on main failure', no files found after reading paths: action.yml, action.yaml, Dockerfile ``` Live facts checked from this director surface: * Forgejo `main` contains `actions/telegram-alert/action.yml` at latest commit `748bf56060ef feat: add Telegram CI alert action`. * `https://raw.githubusercontent.com/coilyco-flight-deck/agentic-os/main/actions/telegram-alert/action.yml` returns `404`. * The failing runner log shows the job fetching `https://github.com/coilyco-flight-deck/agentic-os` while resolving the workflow checkout/action state, so the local action path is coupled to GitHub mirror freshness. * The failing workflows call `uses: ./actions/telegram-alert` from `release.yml`, `dep-bump.yml`, `freshness.yml`, and `mirror-to-github.yml`. Implementation goal: * Stop main CI from failing when the Telegram alert action exists on Forgejo canonical but is absent or stale on the GitHub mirror. * Preserve the intended behavior: alert Telegram only on main failure. * Prefer a robust fix for failure-path alerting. A failure alert path should not depend on a local action that may be missing from the checked-out workspace. Inlining the small alert implementation in each workflow, adding a committed script invoked by `run:`, or forcing checkout/action resolution to Forgejo canonical are all acceptable if the result is reliable under Forgejo runner behavior. * If the local composite action remains, ensure every job that calls it has a checkout containing the action before the call, from Forgejo canonical, not from a stale mirror. Acceptance criteria: * The workflows no longer fail with `failed to read action 'Alert Telegram on main failure'`. * The alert path still uses `TELEGRAM_BOT_TOKEN` and `TELEGRAM_RED_CHAT_ID` secrets without leaking them. * The fix accounts for Forgejo canonical vs GitHub mirror timing. * Run the available workflow/lint validation for the edited YAML/action/script surfaces.

coilyco-ops commented

2026-07-10 04:51:58 +00:00

Author

Member

WARD-RESERVATION: held 🔒

reservation details

Holder: container engineer-codex-agentic-os-411 on host kais-macbook-pro-2.local.

Reserved by ward agent --harness codex (reserved 2026-07-10T04:51:57Z). Concurrent ward agent runs are blocked until it finishes or the reservation goes stale (1h TTL). --force overrides.

Do not comment on or edit this issue to steer the run while it is reserved. The engineer seeded the body once at launch and never re-reads it, so a comment or edit reaches only human readers, never the running engineer. A correction goes to a new issue, dispatched fresh. That is the only channel that reaches a run in flight. Where the forge supports it, ward locks this conversation to make that a road-block rather than a convention (ward#494).

run seed context — what this run is carrying (ward#609)

Resolved: coilyco-flight-deck/agentic-os#411 · branch issue-411 · harness codex · workflow direct-main
Run: engineer-codex-agentic-os-411 · ward v0.554.0 · dispatched 2026-07-10T04:51:57Z
Comment thread: 0 included in the pre-flight read, 0 stripped (ward's own automated comments).

Static container doctrine and seed boilerplate are identical every run and omitted here (they ride ward v0.554.0).

— Codex, via ward agent

WARD-RESERVATION: held 🔒 <details><summary>reservation details</summary> Holder: container `engineer-codex-agentic-os-411` on host `kais-macbook-pro-2.local`. Reserved by `ward agent --harness codex` (reserved 2026-07-10T04:51:57Z). Concurrent `ward agent` runs are blocked until it finishes or the reservation goes stale (1h TTL). `--force` overrides. **Do not comment on or edit this issue to steer the run while it is reserved.** The engineer seeded the body once at launch and never re-reads it, so a comment or edit reaches only human readers, never the running engineer. A correction goes to a **new issue, dispatched fresh**. That is the only channel that reaches a run in flight. Where the forge supports it, ward locks this conversation to make that a road-block rather than a convention (ward#494). <details><summary>run seed context — what this run is carrying (ward#609)</summary> - **Resolved:** `coilyco-flight-deck/agentic-os#411` · branch `issue-411` · harness `codex` · workflow `direct-main` - **Run:** `engineer-codex-agentic-os-411` · ward `v0.554.0` · dispatched `2026-07-10T04:51:57Z` - **Comment thread:** 0 included in the pre-flight read, 0 stripped (ward's own automated comments). Static container doctrine and seed boilerplate are identical every run and omitted here (they ride ward v0.554.0). </details> </details>  — Codex, via `ward agent`

coilyco-ops referenced this issue from a commit

2026-07-10 05:04:53 +00:00

fix(ci): inline telegram failure alerts

coilyco-ops closed this issue

2026-07-10 05:04:53 +00:00

coilyco-ops commented

2026-07-10 05:05:54 +00:00

Author

Member

WARD-OUTCOME: done

details

workflow: direct-main; review summary: skipped by ~/.ward/config.yaml default
felt: the mirror-safe inline alert path was straightforward once the failure mode was pinned down
confidence: high
surprises: the blocking work was disk pressure in the hook gate, not the code change
follow-ups: none

WARD-OUTCOME: done <details><summary>details</summary> workflow: direct-main; review summary: skipped by ~/.ward/config.yaml default felt: the mirror-safe inline alert path was straightforward once the failure mode was pinned down confidence: high surprises: the blocking work was disk pressure in the hook gate, not the code change follow-ups: none </details>

coilyco-ops referenced this issue

2026-07-24 00:12:06 +00:00

Add a prep-safe Telegram CI alert renderer and reliability contract #632

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference

coilyco-flight-deck/agentic-os#411

No description provided.

Rows
Columns