coilyco-flight-deck/agentic-os

Watch

Remove ward source bootstrap from promote gate #570

New issue

Closed

opened 2026-07-15 08:35:54 +00:00 by coilyco-ops · 3 comments

coilyco-ops commented

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

Owner

The current release recovery run shows promote is still blocked by a slow ward bootstrap after the graph was decoupled.

Evidence from promote run 1393 on main head fca924d6691fa3758c14d5dbb346c0dc04a1f254:

gate job 13960 is running.
promote-release job 13961 is blocked behind gate.
Repo test gate succeeded.
Install ward from source with workflow bundle support has been running for more than 8 minutes.

This keeps main => release from being a cheap promote path even after image publishing was removed from the promote graph. The engineer should remove the ward source install and .ward load from the promote gate if they are no longer required, or replace them with the same cheap direct validation path used by ci.yml. Keep the fix narrowly scoped to promote.yml and any workflow-shape tests.

Acceptance:

promote.yml does not install ward from source on the release promotion path unless a test proves it is required.
Promote remains gated by the repo tests/pre-commit parity already added in #569.
The workflow-shape tests cover the absence of the slow ward bootstrap in promote.
PR CI is green.

The current release recovery run shows promote is still blocked by a slow ward bootstrap after the graph was decoupled. Evidence from promote run `1393` on main head `fca924d6691fa3758c14d5dbb346c0dc04a1f254`: * `gate` job `13960` is running. * `promote-release` job `13961` is blocked behind `gate`. * `Repo test gate` succeeded. * `Install ward from source with workflow bundle support` has been running for more than 8 minutes. This keeps `main => release` from being a cheap promote path even after image publishing was removed from the promote graph. The engineer should remove the ward source install and `.ward` load from the promote gate if they are no longer required, or replace them with the same cheap direct validation path used by `ci.yml`. Keep the fix narrowly scoped to `promote.yml` and any workflow-shape tests. Acceptance: * `promote.yml` does not install ward from source on the release promotion path unless a test proves it is required. * Promote remains gated by the repo tests/pre-commit parity already added in #569. * The workflow-shape tests cover the absence of the slow ward bootstrap in promote. * PR CI is green.

coilyco-ops commented

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

Author

Owner

WARDED_WORKFLOW: reservation-held

reservation details

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

Accepted by ward agent --harness codex (reserved 2026-07-15T08:36:13Z). 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#570 · branch issue-570 · harness codex · workflow pull-request-and-merge
Run: engineer-codex-agentic-os-570 · ward v0.697.0 · dispatched 2026-07-15T08:36:08Z
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-570` on host `kais-macbook-pro-2.local`. Accepted by `ward agent --harness codex` (reserved 2026-07-15T08:36:13Z). 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#570` · branch `issue-570` · harness `codex` · workflow `pull-request-and-merge` - **Run:** `engineer-codex-agentic-os-570` · ward `v0.697.0` · dispatched `2026-07-15T08:36:08Z` - **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 referenced this issue from a commit

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

fix(promote): remove ward bootstrap from gate (#570)

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

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

fix(promote): remove ward bootstrap from gate #571

coilyco-ops commented

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

Author

Owner

Confirmed after filing: promote run 1393 failed on main head fca924d6691fa3758c14d5dbb346c0dc04a1f254. Final job state:

gate failed.
promote-release stayed blocked.
Repo test gate succeeded in 1m53s.
Install ward from source with workflow bundle support failed after 13m16s.

This is now the active release blocker after #569.

Confirmed after filing: promote run `1393` failed on main head `fca924d6691fa3758c14d5dbb346c0dc04a1f254`. Final job state: * `gate` failed. * `promote-release` stayed blocked. * `Repo test gate` succeeded in 1m53s. * `Install ward from source with workflow bundle support` failed after 13m16s. This is now the active release blocker after #569.

coilyco-ops commented

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

Author

Owner

WARDED_WORKFLOW: #571

details

workflow: pull-request-and-merge; review summary: review skipped - temporary ward default pending brokered QA retrospective: the change felt direct and low-risk confidence: high surprises: none follow-ups: none

WARDED_WORKFLOW: https://forgejo.coilysiren.me/coilyco-flight-deck/agentic-os/pulls/571 <details><summary>details</summary> workflow: pull-request-and-merge; review summary: review skipped - temporary ward default pending brokered QA retrospective: the change felt direct and low-risk confidence: high surprises: none follow-ups: none </details>

coilyco-ops closed this issue

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

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

No description provided.

Rows
Columns