Track binary image assets with Git LFS

coilyco-ops commented

2026-07-09 15:49:56 +00:00

Member

Set up Git LFS for the remaining tracked image assets before the Rust/Bevy rewrite grows the asset set.\n\nCurrent findings from the read-only surface session:\n\n* No .gitattributes exists in the repo.\n* git lfs is not installed in the current surface container, so the engineer should verify availability in the feature container and install it there if needed before committing.\n* 59 image files are currently tracked as regular Git blobs.\n* Largest current image: Assets/Resources/Art/dirt.png at about 2.7 MB.\n* Repo pack is about 50 MB.\n\nRequested implementation:\n\n* Add .gitattributes entries for common binary image asset types used by the project, at least png, jpg, jpeg, psd, tga, bmp, gif, webp, exr, and hdr.\n* Convert currently tracked matching assets to LFS pointers with git lfs migrate import or the repo-appropriate equivalent.\n* Keep Unity .meta files as normal text files.\n* Verify git lfs ls-files shows the expected image assets.\n* Commit and land through the normal ward engineer flow.\n\nThis is prep work for the Unity-to-Rust/Bevy migration.

coilyco-ops commented

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

Author

Member

WARD-RESERVATION: held 🔒

reservation details

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

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

coilyco-ops referenced this issue

2026-07-09 15:57:43 +00:00

Bring factory-game-v3 into the agentic-os repo baseline #5

coilyco-ops referenced this issue from a commit

2026-07-09 15:57:47 +00:00

Track image assets with Git LFS

coilyco-ops closed this issue

2026-07-09 15:57:47 +00:00

coilyco-ops commented

2026-07-09 15:58:27 +00:00

Author

Member

WARD-OUTCOME: done ✅

details

workflow: normal; review summary: review gate skipped by ~/.ward/config.yaml default
felt: mechanical but straightforward
confidence: high
surprises: git lfs was missing and the first import rewrote local history, so I landed a fresh commit from origin/main instead
follow-ups: none

WARD-OUTCOME: done ✅ <details><summary>details</summary> workflow: normal; review summary: review gate skipped by ~/.ward/config.yaml default felt: mechanical but straightforward confidence: high surprises: git lfs was missing and the first import rewrote local history, so I landed a fresh commit from origin/main instead follow-ups: none </details>

coilyco-ops referenced this issue

2026-07-09 16:51:45 +00:00

Verify and upload Git LFS asset objects #6

coilyco-ops referenced this issue

2026-08-06 08:14:14 +00:00

Integrate accepted 100px sprites into the local Bevy viewer without LFS #59

coilyco-ops referenced this issue

2026-08-06 22:57:27 +00:00

AGENTS.md still describes the repo as a Unity/C# migration baseline #85

coilyco-ops referenced this issue from a commit

2026-08-06 22:58:53 +00:00

docs: describe the repo as it is, not as a migration (closes #85)