Fix remaining factory-game CI failure after dev-base dotnet bump #9

New issue

Closed

opened 2026-07-09 17:52:39 +00:00 by coilyco-ops · 1 comment

coilyco-ops commented

2026-07-09 17:52:39 +00:00

Member

Main is still red after #8 landed.

Current state:

#8 closed after commit fce89389b7a37c3d8e014a464979ca9343e8ced6 (fix(ci): bump dev-base image for dotnet).
Latest CI run: run 5, gate, status failure, updated 2026-07-09T17:42:15Z.
#8 outcome says v0.226.0 lacked dotnet and v0.227.0 was chosen as the next published dev-base tag. That got past the known missing-dotnet issue, but the workflow still fails.
The repo still needs a green main, not just a bounded or better-diagnosed gate.

Requested implementation:

Inspect run 5 logs and fix the remaining failure.
If tests.csproj cannot pass in current dev-base because the Unity-era C# baseline is stale, narrow or replace the CI validation with the smallest meaningful migration-baseline check that can be green today.
Preserve the bounded scripts/test-gate.sh behavior from #7 unless replacing the test surface entirely.
Keep CI pinned to an explicit dev-base tag, never :latest.
Keep LFS setup and aos baseline intact.
Update README/AGENTS/docs if the validation surface changes.

Acceptance:

A fresh push to main has green gate CI.
The repo has a validation command that is honest about the current Unity-to-Rust/Bevy transition state.

Main is still red after #8 landed. Current state: * #8 closed after commit `fce89389b7a37c3d8e014a464979ca9343e8ced6` (`fix(ci): bump dev-base image for dotnet`). * Latest CI run: run 5, `gate`, status `failure`, updated 2026-07-09T17:42:15Z. * #8 outcome says `v0.226.0` lacked `dotnet` and `v0.227.0` was chosen as the next published dev-base tag. That got past the known missing-dotnet issue, but the workflow still fails. * The repo still needs a green main, not just a bounded or better-diagnosed gate. Requested implementation: * Inspect run 5 logs and fix the remaining failure. * If `tests.csproj` cannot pass in current dev-base because the Unity-era C# baseline is stale, narrow or replace the CI validation with the smallest meaningful migration-baseline check that can be green today. * Preserve the bounded `scripts/test-gate.sh` behavior from #7 unless replacing the test surface entirely. * Keep CI pinned to an explicit dev-base tag, never `:latest`. * Keep LFS setup and aos baseline intact. * Update README/AGENTS/docs if the validation surface changes. Acceptance: * A fresh push to main has green `gate` CI. * The repo has a validation command that is honest about the current Unity-to-Rust/Bevy transition state.

coilyco-ops referenced this issue from a commit

2026-07-09 17:59:07 +00:00

fix(ci): gate on pre-commit baseline

coilyco-ops closed this issue

2026-07-09 17:59:18 +00:00

coilyco-ops referenced this issue from a commit

2026-07-09 18:02:30 +00:00

fix(ci): run gate script directly in ci

coilyco-ops referenced this issue from a commit

2026-07-09 18:08:34 +00:00

fix(docs): use repo-relative links in README

coilyco-ops commented

2026-07-09 18:10:27 +00:00

Author

Member

WARD-OUTCOME: done ✅

details

workflow: direct-to-main; review summary: review gate skipped by ~/.ward/config.yaml default
felt: the fix only made sense after the shallow-clone failure surfaced the repo-escaping README links
confidence: high
surprises: the CI break was README link hygiene, not the gate script itself
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: the fix only made sense after the shallow-clone failure surfaced the repo-escaping README links confidence: high surprises: the CI break was README link hygiene, not the gate script itself follow-ups: none </details>