coilyco-flight-deck/infrastructure
2
0
Fork 0
Code Issues 118 Pull requests Projects Releases Packages Wiki Activity Actions 2

Inline Telegram CI alerts instead of depending on the stale GitHub action mirror #522

New issue
Closed
opened 2026-07-10 08:52:54 +00:00 by coilyco-ops · 4 comments
coilyco-ops commented 2026-07-10 08:52:54 +00:00
Member
Copy link

Follow-up from the live CI-green director pass on 2026-07-10.

coilyco-flight-deck/infrastructure#521 changed affected workflows from:

uses: coilyco-flight-deck/agentic-os/actions/telegram-alert@main

to:

uses: coilysiren/agentic-os/actions/telegram-alert@main

That still leaves Forgejo CI red. Representative fresh failures after the reroll:

Each readable log still fails before checkout with:

failed to read action 'Alert Telegram on main failure', no files found after reading paths: action.yml, action.yaml, Dockerfile

The runner now fetches https://github.com/coilysiren/agentic-os, but that mirror is stale at 4dbb587ebb5d0438cd7b7f88d69fa5acb2d6c794 and its actions/ tree only has bump-formula, create-release, tag-bump, and upload-release-asset. It does not contain actions/telegram-alert/action.yml, while the Forgejo canonical repo does.

The immediate green-CI fix should not depend on the GitHub mirror catching up. The infrastructure rollout should insert an inline failure-alert step, or otherwise a self-contained step that does not require resolving any external action, matching the existing agentic-os self-dogfood pattern where failure notifications are inline to avoid stale mirror dependencies.

Acceptance:

  • scripts/telegram-ci-alert-rollout.py no longer inserts uses: coilysiren/agentic-os/actions/telegram-alert@main or any other external action for consumer repos.
  • The rollout remains idempotent and replaces existing stale Alert Telegram on main failure blocks, not only missing blocks.
  • Tests cover replacement of both stale refs:
    • coilyco-flight-deck/agentic-os/actions/telegram-alert@main
    • coilysiren/agentic-os/actions/telegram-alert@main
  • Rerun the rollout across affected repos so workflows no longer contain either stale external uses: line.
  • Verify at least one affected repo's fresh Actions run reaches the real job steps instead of failing during action resolution.

Related: #521

Follow-up from the live CI-green director pass on 2026-07-10. `coilyco-flight-deck/infrastructure#521` changed affected workflows from: ```yaml uses: coilyco-flight-deck/agentic-os/actions/telegram-alert@main ``` to: ```yaml uses: coilysiren/agentic-os/actions/telegram-alert@main ``` That still leaves Forgejo CI red. Representative fresh failures after the reroll: - https://forgejo.coilysiren.me/coilyco-flight-deck/backend/actions/runs/50 - https://forgejo.coilysiren.me/coilyco-flight-deck/infrastructure/actions/runs/983 - https://forgejo.coilysiren.me/coilyco-gaming/eco-app/actions/runs/94 - https://forgejo.coilysiren.me/coilyco-flight-deck/ward-mcp/actions/runs/16 Each readable log still fails before checkout with: ```text failed to read action 'Alert Telegram on main failure', no files found after reading paths: action.yml, action.yaml, Dockerfile ``` The runner now fetches `https://github.com/coilysiren/agentic-os`, but that mirror is stale at `4dbb587ebb5d0438cd7b7f88d69fa5acb2d6c794` and its `actions/` tree only has `bump-formula`, `create-release`, `tag-bump`, and `upload-release-asset`. It does not contain `actions/telegram-alert/action.yml`, while the Forgejo canonical repo does. The immediate green-CI fix should not depend on the GitHub mirror catching up. The infrastructure rollout should insert an inline failure-alert step, or otherwise a self-contained step that does not require resolving any external action, matching the existing `agentic-os` self-dogfood pattern where failure notifications are inline to avoid stale mirror dependencies. Acceptance: - `scripts/telegram-ci-alert-rollout.py` no longer inserts `uses: coilysiren/agentic-os/actions/telegram-alert@main` or any other external action for consumer repos. - The rollout remains idempotent and replaces existing stale `Alert Telegram on main failure` blocks, not only missing blocks. - Tests cover replacement of both stale refs: - `coilyco-flight-deck/agentic-os/actions/telegram-alert@main` - `coilysiren/agentic-os/actions/telegram-alert@main` - Rerun the rollout across affected repos so workflows no longer contain either stale external `uses:` line. - Verify at least one affected repo's fresh Actions run reaches the real job steps instead of failing during action resolution. Related: #521
coilyco-ops commented 2026-07-10 08:53:04 +00:00
Author
Member
Copy link

WARD-RESERVATION: held 🔒

reservation details

Holder: container engineer-codex-infrastructure-522 on host kais-macbook-pro-2.local.

Reserved by ward agent --harness codex (reserved 2026-07-10T08:53:04Z). 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/infrastructure#522 · branch issue-522 · harness codex · workflow direct-main
  • Run: engineer-codex-infrastructure-522 · ward v0.569.0 · dispatched 2026-07-10T08:53:04Z
  • 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.569.0).

— Codex, via ward agent

<!-- ward-agent-reservation --> WARD-RESERVATION: held 🔒 <details><summary>reservation details</summary> Holder: container `engineer-codex-infrastructure-522` on host `kais-macbook-pro-2.local`. Reserved by `ward agent --harness codex` (reserved 2026-07-10T08:53:04Z). 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/infrastructure#522` · branch `issue-522` · harness `codex` · workflow `direct-main` - **Run:** `engineer-codex-infrastructure-522` · ward `v0.569.0` · dispatched `2026-07-10T08:53:04Z` - **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.569.0). </details> </details> <!-- ward-agent-signature --> — Codex, via `ward agent`
coilyco-ops commented 2026-07-10 09:10:06 +00:00
Author
Member
Copy link

WARD-OUTCOME: done

details

workflow: direct-main; review summary: skipped because review gate skipped by ~/.ward/config.yaml default
retrospective: the inline payload removed the stale mirror dependency, and the only surprise was fixing the replacement escape before rollout
confidence: high
follow-ups: none

WARD-OUTCOME: done <details><summary>details</summary> workflow: direct-main; review summary: skipped because review gate skipped by ~/.ward/config.yaml default retrospective: the inline payload removed the stale mirror dependency, and the only surprise was fixing the replacement escape before rollout confidence: high follow-ups: none </details>
coilyco-ops commented 2026-07-10 11:06:23 +00:00
Author
Member
Copy link

WARD-RESERVATION: held 🔒

reservation details

Holder: container engineer-codex-infrastructure-522 on host kais-macbook-pro-2.local.

Reserved by ward agent --harness codex (reserved 2026-07-10T11:06:22Z). 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/infrastructure#522 · branch issue-522 · harness codex · workflow direct-main
  • Run: engineer-codex-infrastructure-522 · ward v0.580.0 · dispatched 2026-07-10T11:06:22Z
  • Comment thread: 1 included in the pre-flight read, 1 stripped (ward's own automated comments).

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

— Codex, via ward agent

<!-- ward-agent-reservation --> WARD-RESERVATION: held 🔒 <details><summary>reservation details</summary> Holder: container `engineer-codex-infrastructure-522` on host `kais-macbook-pro-2.local`. Reserved by `ward agent --harness codex` (reserved 2026-07-10T11:06:22Z). 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/infrastructure#522` · branch `issue-522` · harness `codex` · workflow `direct-main` - **Run:** `engineer-codex-infrastructure-522` · ward `v0.580.0` · dispatched `2026-07-10T11:06:22Z` - **Comment thread:** 1 included in the pre-flight read, 1 stripped (ward's own automated comments). - included: @coilyco-ops (2026-07-10T09:10:06Z) - stripped: @coilyco-ops (2026-07-10T08:53:04Z) Static container doctrine and seed boilerplate are identical every run and omitted here (they ride ward v0.580.0). </details> </details> <!-- ward-agent-signature --> — Codex, via `ward agent`
coilyco-ops commented 2026-07-10 11:15:49 +00:00
Author
Member
Copy link

WARD-OUTCOME: done

details workflow: direct-main; review summary: review gate skipped by ~/.ward/config.yaml default felt routine after switching to step-block replacement. confidence: high. surprise: origin/main advanced mid-push, so the branch needed one merge before landing. follow-up: none.
WARD-OUTCOME: done <details><summary>details</summary> workflow: direct-main; review summary: review gate skipped by ~/.ward/config.yaml default felt routine after switching to step-block replacement. confidence: high. surprise: origin/main advanced mid-push, so the branch needed one merge before landing. follow-up: none. </details>
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
main
issue-515
issue-486
issue-529
issue-500
issue-483
No results found.
Labels
Clear labels   
burndown-2026-06
Backlog burndown June 2026

  
coherence-core
Core review set for the warded control plane coherence milestone. These issues form the release spine; adjacent milestone issues are stretch or supporting work.

  
consult
A human decision, design, or external action must happen first. Fail-closed default for unlabeled/low-confidence.

  
headless
Agent can take it from open issue to merged change with no human in the loop. The auto-burndown queue.

  
interactive
Agent does the work but pauses at a human checkpoint mid-flight (design choice, destructive step, human-only verification).

  
P0
now / blocking / urgent

  
P1
next / important

  
P2
backlog / will do

  
P3
someday / low

  
P4
icebox / frozen / reopen if it becomes real

No labels
burndown-2026-06
coherence-core
consult
headless
interactive
P0
P1
P2
P3
P4
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
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/infrastructure#522
No description provided.