Bump CI image to Rust-enabled agentic-os dev-base #14

Closed
opened 2026-07-09 19:24:42 +00:00 by coilyco-ops · 2 comments
Member

coilyco-flight-deck/agentic-os#382 landed Rust toolchain support in the dev-base image. Its outcome says downstream repos can bump to v0.230.0.

factory-game-v3 is still pinned to forgejo.coilysiren.me/coilyco-flight-deck/agentic-os:v0.227.0 in .forgejo/workflows/ci.yml, while scripts/test-gate.sh now runs cargo test --workspace. CI will fail on the old image because cargo/rustc are absent.

Update the Factory Game CI image tag to the Rust-enabled aos image and verify the gate.

Acceptance criteria:

  • .forgejo/workflows/ci.yml uses forgejo.coilysiren.me/coilyco-flight-deck/agentic-os:v0.230.0 or the current Rust-enabled successor if a newer tag exists.
  • ward exec test passes in the repo.
  • The Forgejo CI gate on main goes green after the bump lands.
  • Do not change the Rust simulation code unless a real compatibility issue appears under the new image.

Context:

  • First Rust slice landed in factory-game-v3 on main.
  • agentic-os#382 added Rust to dev-base and closed with follow-up guidance to bump downstream repos to v0.230.0.
  • This is a downstream image-tag/config fix, not a new gameplay implementation task.
`coilyco-flight-deck/agentic-os#382` landed Rust toolchain support in the dev-base image. Its outcome says downstream repos can bump to `v0.230.0`. `factory-game-v3` is still pinned to `forgejo.coilysiren.me/coilyco-flight-deck/agentic-os:v0.227.0` in `.forgejo/workflows/ci.yml`, while `scripts/test-gate.sh` now runs `cargo test --workspace`. CI will fail on the old image because `cargo`/`rustc` are absent. Update the Factory Game CI image tag to the Rust-enabled aos image and verify the gate. Acceptance criteria: * `.forgejo/workflows/ci.yml` uses `forgejo.coilysiren.me/coilyco-flight-deck/agentic-os:v0.230.0` or the current Rust-enabled successor if a newer tag exists. * `ward exec test` passes in the repo. * The Forgejo CI gate on `main` goes green after the bump lands. * Do not change the Rust simulation code unless a real compatibility issue appears under the new image. Context: * First Rust slice landed in `factory-game-v3` on `main`. * `agentic-os#382` added Rust to dev-base and closed with follow-up guidance to bump downstream repos to `v0.230.0`. * This is a downstream image-tag/config fix, not a new gameplay implementation task.
Author
Member

WARD-RESERVATION: held 🔒

reservation details

Holder: container engineer-codex-factory-game-v3-14 on host kais-macbook-pro-2.local.

Reserved by ward agent --harness codex (reserved 2026-07-09T19:24:47Z). 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-gaming/factory-game-v3#14 · branch issue-14 · harness codex · workflow direct-to-main
  • Run: engineer-codex-factory-game-v3-14 · ward v0.493.0 · dispatched 2026-07-09T19:24:47Z
  • 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.493.0).

— Codex, via ward agent

<!-- ward-agent-reservation --> WARD-RESERVATION: held 🔒 <details><summary>reservation details</summary> Holder: container `engineer-codex-factory-game-v3-14` on host `kais-macbook-pro-2.local`. Reserved by `ward agent --harness codex` (reserved 2026-07-09T19:24:47Z). 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-gaming/factory-game-v3#14` · branch `issue-14` · harness `codex` · workflow `direct-to-main` - **Run:** `engineer-codex-factory-game-v3-14` · ward `v0.493.0` · dispatched `2026-07-09T19:24:47Z` - **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.493.0). </details> </details> <!-- ward-agent-signature --> — Codex, via `ward agent`
Author
Member

WARD-OUTCOME: done

details

workflow: direct-to-main; review summary: review gate skipped by ~/.ward/config.yaml default
felt: straightforward, with one environment-only Rust toolchain gap
confidence: high
surprises: the repo gate passed once cargo was installed locally
follow-ups: none

WARD-OUTCOME: done ✅ <details><summary>details</summary> workflow: direct-to-main; review summary: review gate skipped by ~/.ward/config.yaml default felt: straightforward, with one environment-only Rust toolchain gap confidence: high surprises: the repo gate passed once cargo was installed locally follow-ups: none </details>
Sign in to join this conversation.
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-gaming/factory-game-v3#14
No description provided.