Inline cli-guard Telegram alerts so workflows prepare #217

New issue

Closed

opened 2026-07-10 08:13:48 +00:00 by coilyco-ops · 2 comments

coilyco-ops commented

2026-07-10 08:13:48 +00:00

Member

Problem

cli-guard main is red at 3c361fc because the CI and release workflows still try to read Alert Telegram on main failure as a local action. Forgejo fails workflow preparation with:

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

This is the same family of failure that was already repaired in agentic-os and ward by inlining the Telegram alert path instead of using the missing action surface.

Scope

Repair cli-guard workflows so test, lint, secrets, and release jobs prepare successfully.
Preserve failure notification behavior if the repo still wants it, but do not use a missing local action.
Run the repo validation.
Push through the repo's resolved workflow.

Acceptance

cli-guard main CI no longer fails during workflow preparation on Alert Telegram on main failure.
The fix is compatible with the current dev-base image and Forgejo runner.
Relevant tests/pre-commit pass.

Filed from the AOS director burn-down because cli-guard#216 is blocked behind a red main branch.

## Problem cli-guard main is red at `3c361fc` because the CI and release workflows still try to read `Alert Telegram on main failure` as a local action. Forgejo fails workflow preparation with: ```text failed to read action 'Alert Telegram on main failure', no files found after reading paths: action.yml, action.yaml, Dockerfile ``` This is the same family of failure that was already repaired in agentic-os and ward by inlining the Telegram alert path instead of using the missing action surface. ## Scope * Repair cli-guard workflows so `test`, `lint`, `secrets`, and `release` jobs prepare successfully. * Preserve failure notification behavior if the repo still wants it, but do not use a missing local action. * Run the repo validation. * Push through the repo's resolved workflow. ## Acceptance * cli-guard main CI no longer fails during workflow preparation on `Alert Telegram on main failure`. * The fix is compatible with the current dev-base image and Forgejo runner. * Relevant tests/pre-commit pass. Filed from the AOS director burn-down because cli-guard#216 is blocked behind a red main branch.

coilyco-ops commented

2026-07-10 08:13:56 +00:00

Author

Member

WARD-RESERVATION: held 🔒

reservation details

Holder: container engineer-codex-cli-guard-217 on host kais-macbook-pro-2.local.

Reserved by ward agent --harness codex (reserved 2026-07-10T08:13:56Z). 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/cli-guard#217 · branch issue-217 · harness codex · workflow pull-requests
Run: engineer-codex-cli-guard-217 · ward v0.555.0 · dispatched 2026-07-10T08:13:56Z
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.555.0).

— Codex, via ward agent

WARD-RESERVATION: held 🔒 <details><summary>reservation details</summary> Holder: container `engineer-codex-cli-guard-217` on host `kais-macbook-pro-2.local`. Reserved by `ward agent --harness codex` (reserved 2026-07-10T08:13:56Z). 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/cli-guard#217` · branch `issue-217` · harness `codex` · workflow `pull-requests` - **Run:** `engineer-codex-cli-guard-217` · ward `v0.555.0` · dispatched `2026-07-10T08:13:56Z` - **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.555.0). </details> </details>  — Codex, via `ward agent`

coilyco-ops referenced this issue from a pull request that will close it,

2026-07-10 08:18:39 +00:00

Inline cli-guard Telegram alerts so workflows prepare #218

coilyco-ops commented

2026-07-10 08:19:40 +00:00

Author

Member

WARD-OUTCOME: submitted

details

workflow: pull-requests; review summary: skipped because --skip-preflight / --no-preflight also skips review retrospective: the fix was mechanical once the sibling inline-alert pattern was copied. confidence: high surprises: the GitHub mirror had one hidden stale copy in the docs job. follow-ups: none.

WARD-OUTCOME: submitted <details><summary>details</summary>workflow: pull-requests; review summary: skipped because --skip-preflight / --no-preflight also skips review retrospective: the fix was mechanical once the sibling inline-alert pattern was copied. confidence: high surprises: the GitHub mirror had one hidden stale copy in the docs job. follow-ups: none. </details>