coilyco-flight-deck/agentic-os

Watch

Fix promote gate failure after release decoupling #568

New issue

Closed

opened 2026-07-15 08:07:00 +00:00 by coilyco-ops · 5 comments

coilyco-ops commented

2026-07-15 08:07:00 +00:00

Owner

After issue 564 landed as PR 566, release promotion is no longer blocked by the image publish DAG, but the current promote gate is still failing before release can advance.\n\nCurrent state at 2026-07-15T08:06Z:\n\n* main: 51940edb47, Decouple release branch promotion from dev-base image publishing (#566)\n* release: 24980330c2, still the old failed release head\n* main exact-head runs:\n * ci.yml 1385 success\n * mirror-to-github.yml 1386 success\n * promote.yml 1387 was the push-trigger run and was cancelled by the manual retry\n * promote.yml 1389 was manually dispatched on main and failed\n\nRun 1389 details from the Forgejo job page:\n\n* job 13920 gate failure, duration 15m43s\n* Set up job success, 3m21s\n* actions/checkout success, 4s\n* Cache pre-commit envs success, 3s\n* Repo test gate failure, 12m15s\n* Install ward, ward doctor, alert, and complete job are marked failure/skipped-after-failure at 0s\n* promote-release stayed blocked, so release did not move\n\nThe raw log helper still returns 404 for this job: . Please diagnose the repo gate failure on this current main SHA, repair it, and get promote-release to advance release so at least one release.yml run can complete successfully.

After issue 564 landed as PR 566, release promotion is no longer blocked by the image publish DAG, but the current promote gate is still failing before release can advance.\n\nCurrent state at 2026-07-15T08:06Z:\n\n* main: 51940edb4792bff002cc7d2c277d2bc7131d4cc6, Decouple release branch promotion from dev-base image publishing (#566)\n* release: 24980330c233d1338be428a16a0a2750f24a3749, still the old failed release head\n* main exact-head runs:\n * ci.yml 1385 success\n * mirror-to-github.yml 1386 success\n * promote.yml 1387 was the push-trigger run and was cancelled by the manual retry\n * promote.yml 1389 was manually dispatched on main and failed\n\nRun 1389 details from the Forgejo job page:\n\n* job 13920 gate failure, duration 15m43s\n* Set up job success, 3m21s\n* actions/checkout success, 4s\n* Cache pre-commit envs success, 3s\n* Repo test gate failure, 12m15s\n* Install ward, ward doctor, alert, and complete job are marked failure/skipped-after-failure at 0s\n* promote-release stayed blocked, so release did not move\n\nThe raw log helper still returns 404 for this job: . Please diagnose the repo gate failure on this current main SHA, repair it, and get promote-release to advance release so at least one release.yml run can complete successfully.

coilyco-ops commented

2026-07-15 08:07:26 +00:00

Author

Owner

WARDED_WORKFLOW: reservation-held

reservation details

Holder: launch intent for container engineer-codex-agentic-os-568 on host kais-macbook-pro-2.local.

Accepted by ward agent --harness codex (reserved 2026-07-15T08:07:25Z). Concurrent ward agent runs are blocked until this intent becomes visible or the intent is released. The stale-intent fallback is still TTL-bounded (3h TTL). --override-reservation 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#568 · branch issue-568 · harness codex · workflow pull-request-and-merge
Run: engineer-codex-agentic-os-568 · ward v0.697.0 · dispatched 2026-07-15T08:07:21Z
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.697.0).

— Codex, via ward agent

WARDED_WORKFLOW: reservation-held <details><summary>reservation details</summary> Holder: launch intent for container `engineer-codex-agentic-os-568` on host `kais-macbook-pro-2.local`. Accepted by `ward agent --harness codex` (reserved 2026-07-15T08:07:25Z). Concurrent `ward agent` runs are blocked until this intent becomes visible or the intent is released. The stale-intent fallback is still TTL-bounded (3h TTL). `--override-reservation` 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#568` · branch `issue-568` · harness `codex` · workflow `pull-request-and-merge` - **Run:** `engineer-codex-agentic-os-568` · ward `v0.697.0` · dispatched `2026-07-15T08:07:21Z` - **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.697.0). </details> </details>  — Codex, via `ward agent`

coilyco-ops commented

2026-07-15 08:07:44 +00:00

Author

Owner

Correction: the raw-log helper command that returned 404 was: ward ops forgejo actions logs coilyco-flight-deck agentic-os 1389 13920 1. The rest of the issue body is accurate.

Correction: the raw-log helper command that returned 404 was: `ward ops forgejo actions logs coilyco-flight-deck agentic-os 1389 13920 1`. The rest of the issue body is accurate.

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

2026-07-15 08:12:54 +00:00

fix(promote): align repo gate with ci #569

coilyco-ops commented

2026-07-15 08:20:04 +00:00

Author

Owner

WARDED_WORKFLOW: #569

details

workflow: pull-request-and-merge; review summary: skipped (in-container review gate intentionally skipped because temporary ward default pending brokered QA) felt: small and mechanical. The fix was workflow parity, not a code-path chase. confidence: high surprises: the PR CI settled cleanly once promote stopped preferring ward. follow-ups: none

WARDED_WORKFLOW: https://forgejo.coilysiren.me/coilyco-flight-deck/agentic-os/pulls/569 <details><summary>details</summary> workflow: pull-request-and-merge; review summary: skipped (in-container review gate intentionally skipped because temporary ward default pending brokered QA) felt: small and mechanical. The fix was workflow parity, not a code-path chase. confidence: high surprises: the PR CI settled cleanly once promote stopped preferring ward. follow-ups: none </details>

coilyco-ops commented

2026-07-15 08:20:46 +00:00

Author

Owner

{
  "verdict": "pass",
  "summary": "The PR aligns promote with ci and the head SHA passed local validation and Forgejo CI.",
  "evidence": [
    "`promote.yml` now runs `uv run pytest` and `pre-commit run --all-files` directly.",
    "`tests/test_pull_request_ci_workflow.py` pins the gate shape.",
    "Local `ward exec test` and `ward exec pre-commit-all` passed.",
    "Forgejo PR #569 ci.yml completed successfully for commit `07cbe1d2c47bf46c6dfb5dc06e8387811c2c66f5`."
  ],
  "risks": [],
  "next_steps": []
}

```json { "verdict": "pass", "summary": "The PR aligns promote with ci and the head SHA passed local validation and Forgejo CI.", "evidence": [ "`promote.yml` now runs `uv run pytest` and `pre-commit run --all-files` directly.", "`tests/test_pull_request_ci_workflow.py` pins the gate shape.", "Local `ward exec test` and `ward exec pre-commit-all` passed.", "Forgejo PR #569 ci.yml completed successfully for commit `07cbe1d2c47bf46c6dfb5dc06e8387811c2c66f5`." ], "risks": [], "next_steps": [] } ```

coilyco-ops closed this issue

2026-07-15 08:24:08 +00:00

coilyco-ops commented

2026-07-15 09:16:48 +00:00

Author

Owner

WARDED_WORKFLOW: blocked 🛑

details

workflow: pull-request-and-merge; review summary: review gate intentionally skipped because the temporary ward default pending brokered QA.

The release retry hit a missing draft source tag. release.yml failed on core-draft-d1ca18e7e53ed1918f0f0571f374a53985a21ed9 not found, and the draft-publish rerun was cancelled before it could finish. Confidence: medium. Surprise: the image publish path is still timing-sensitive after branch promotion. Follow-up: rerun dev-base-publish.yml to completion, then rerun release.yml once the draft family exists.

WARDED_WORKFLOW: blocked 🛑 <details><summary>details</summary> workflow: pull-request-and-merge; review summary: review gate intentionally skipped because the temporary ward default pending brokered QA. The release retry hit a missing draft source tag. `release.yml` failed on `core-draft-d1ca18e7e53ed1918f0f0571f374a53985a21ed9` not found, and the draft-publish rerun was cancelled before it could finish. Confidence: medium. Surprise: the image publish path is still timing-sensitive after branch promotion. Follow-up: rerun `dev-base-publish.yml` to completion, then rerun `release.yml` once the draft family exists. </details>

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#568

No description provided.

Rows
Columns