Bump Factory Game CI to the corrected Bevy dev-base image #28

New issue

Closed

opened 2026-07-23 08:22:11 +00:00 by coilyco-ops · 2 comments

coilyco-ops commented

2026-07-23 08:22:11 +00:00

Member

Failure

Forgejo Actions run 23 remains red after two attempts:

https://forgejo.coilysiren.me/coilyco-gaming/factory-game-v3/actions/runs/23/jobs/0/attempt/2

The exact producer defect is already captured in:

coilyco-flight-deck/agentic-os#619

The pinned full dev-base image v0.255.0 lacks libwayland-dev and libxkbcommon-dev on both architectures. The Bevy workspace reaches wayland-sys and fails because wayland-client.pc is absent. Run 22 was green before the Bevy shell entered the workspace.

Agentic OS #619 has a source fix, but its corrected immutable image release was blocked by a separate runner cancellation. This consumer needs an explicit follow-through once the producer tag exists.

Scope

Coordinate with agentic-os #619 and identify the first corrected immutable full-image tag.
Bump the Factory Game CI pin to that tag.
Do not install shared Wayland/XKB dependencies ad hoc in this repository's gate.
Run the workspace test gate in the exact pinned image and verify the Bevy/Winit native compile succeeds.
Record the producer tag and verification evidence.

Acceptance

CI uses a corrected immutable agentic-os tag.
pkg-config --exists wayland-client succeeds in that image.
cargo test --workspace passes with the Bevy shell included.
Forgejo Actions run 23's failure class is no longer reproducible.

## Failure Forgejo Actions run 23 remains red after two attempts: https://forgejo.coilysiren.me/coilyco-gaming/factory-game-v3/actions/runs/23/jobs/0/attempt/2 The exact producer defect is already captured in: https://forgejo.coilysiren.me/coilyco-flight-deck/agentic-os/issues/619 The pinned full dev-base image `v0.255.0` lacks `libwayland-dev` and `libxkbcommon-dev` on both architectures. The Bevy workspace reaches `wayland-sys` and fails because `wayland-client.pc` is absent. Run 22 was green before the Bevy shell entered the workspace. Agentic OS #619 has a source fix, but its corrected immutable image release was blocked by a separate runner cancellation. This consumer needs an explicit follow-through once the producer tag exists. ## Scope - Coordinate with agentic-os #619 and identify the first corrected immutable full-image tag. - Bump the Factory Game CI pin to that tag. - Do not install shared Wayland/XKB dependencies ad hoc in this repository's gate. - Run the workspace test gate in the exact pinned image and verify the Bevy/Winit native compile succeeds. - Record the producer tag and verification evidence. ## Acceptance - CI uses a corrected immutable agentic-os tag. - `pkg-config --exists wayland-client` succeeds in that image. - `cargo test --workspace` passes with the Bevy shell included. - Forgejo Actions run 23's failure class is no longer reproducible.

coilyco-ops commented

2026-07-23 08:23:43 +00:00

Author

Member

WARDED_WORKFLOW: reservation-held

reservation details

Holder: launch intent for container engineer-codex-factory-game-v3-28 on host kais-macbook-pro-2.local.

Accepted by ward agent --harness codex (reserved 2026-07-23T08:23:42Z). 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-gaming/factory-game-v3#28 · branch issue-28 · harness codex · workflow merge-remote-main
Run: engineer-codex-factory-game-v3-28 · ward v0.793.0 · dispatched 2026-07-23T08:23:38Z
Reservation: held
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.793.0).

— Codex, via ward agent

WARDED_WORKFLOW: reservation-held <details><summary>reservation details</summary> Holder: launch intent for container `engineer-codex-factory-game-v3-28` on host `kais-macbook-pro-2.local`. Accepted by `ward agent --harness codex` (reserved 2026-07-23T08:23:42Z). 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-gaming/factory-game-v3#28` · branch `issue-28` · harness `codex` · workflow `merge-remote-main` - **Run:** `engineer-codex-factory-game-v3-28` · ward `v0.793.0` · dispatched `2026-07-23T08:23:38Z` - **Reservation:** held - **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.793.0). </details> </details>  — Codex, via `ward agent`

coilyco-ops commented

2026-07-23 17:46:54 +00:00

Author

Member

Rescue review found no engineer-authored work to preserve.

Run boundary - Ward failed during the fresh checkout before the model launched.
Blocker - Forgejo LFS reports that the tracked object for Assets/200 Smoke & Fog & Mist Texture/BlackAndWhite/Smoke (89).png is missing from remote storage.
Repository state - the engineer produced no source analysis, diff, commit, branch, or verification.
Redispatch - an operator must restore the missing LFS object and confirm a normal fresh clone completes before another engineer starts.

Rescue review found no engineer-authored work to preserve. * Run boundary - Ward failed during the fresh checkout before the model launched. * Blocker - Forgejo LFS reports that the tracked object for `Assets/200 Smoke & Fog & Mist Texture/BlackAndWhite/Smoke (89).png` is missing from remote storage. * Repository state - the engineer produced no source analysis, diff, commit, branch, or verification. * Redispatch - an operator must restore the missing LFS object and confirm a normal fresh clone completes before another engineer starts.

coilyco-ops added the

autonomy

async-consult

priority

labels

2026-07-29 03:48:01 +00:00

coilyco-ops added

and removed