fix: make consolidated repo pre-commit configs root-aware

coilyco-ops commented

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

Member

Both mods/.pre-commit-config.yaml and unity/.pre-commit-config.yaml currently invoke the agentic-os catalog hooks from the consolidated repository root. A full run fails on the existing tree before evaluating new changes: the root README.md and AGENTS.md are absent, nested mods and Unity Markdown violates root-only layout, and the existing scoped AGENTS.md and CLAUDE.md files violate the current load-point rule. Decide the canonical post-consolidation trifecta and context layout, configure documented exclusions for distributed mod READMEs and vendored Unity docs, then restore one green root-level pre-commit entry point. Package-publishing issue #6 records targeted trufflehog, build, lint, tests, workflow parsing, and archive checks separately.

coilyco-ops commented

2026-07-23 05:58:29 +00:00

Author

Member

WARDED_WORKFLOW: reservation-released

release details

Run never started. ward container reap released container engineer-codex-eco-mods-7 (--harness codex): it exited without launching the agent (smoke-test death, ward#222/#264/#595), so it did no work and the launch intent it took is retracted. Nothing is running on this issue. It needs re-dispatch. A ward agent director re-queues it automatically. A manual ward agent retry no longer needs --override-reservation.

— Codex, via ward agent

WARDED_WORKFLOW: reservation-released <details><summary>release details</summary> Run never started. `ward container reap` released container `engineer-codex-eco-mods-7` (`--harness codex`): it exited without launching the agent (smoke-test death, ward#222/#264/#595), so it did no work and the launch intent it took is retracted. Nothing is running on this issue. It needs re-dispatch. A `ward agent director` re-queues it automatically. A manual `ward agent` retry no longer needs `--override-reservation`. </details>  — Codex, via `ward agent`

coilyco-ops added the

autonomy

headless

label

2026-07-23 05:58:33 +00:00

coilyco-ops commented

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

Author

Member

WARDED_WORKFLOW: reservation-released

release details

Run never started. ward container reap released container engineer-codex-eco-mods-7 (--harness codex): it exited without launching the agent (smoke-test death, ward#222/#264/#595), so it did no work and the launch intent it took is retracted. Nothing is running on this issue. It needs re-dispatch. A ward agent director re-queues it automatically. A manual ward agent retry no longer needs --override-reservation.

— Codex, via ward agent

WARDED_WORKFLOW: reservation-released <details><summary>release details</summary> Run never started. `ward container reap` released container `engineer-codex-eco-mods-7` (`--harness codex`): it exited without launching the agent (smoke-test death, ward#222/#264/#595), so it did no work and the launch intent it took is retracted. Nothing is running on this issue. It needs re-dispatch. A `ward agent director` re-queues it automatically. A manual `ward agent` retry no longer needs `--override-reservation`. </details>  — Codex, via `ward agent`

coilyco-ops commented

2026-07-23 07:26:06 +00:00

Author

Member

WARDED_WORKFLOW: reservation-held

reservation details

Holder: launch intent for container engineer-codex-eco-mods-7 on host kais-macbook-pro-2.local.

Accepted by ward agent --harness codex (reserved 2026-07-23T07:26:05Z). 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/eco-mods#7 · branch issue-7 · harness codex · workflow merge-remote-main
Run: engineer-codex-eco-mods-7 · ward v0.793.0 · dispatched 2026-07-23T07:26:04Z
Reservation: held
Comment thread: 2 included in the pre-flight read, 0 stripped (ward's own automated comments).
- included: @coilyco-ops (2026-07-23T05:58:29Z), @coilyco-ops (2026-07-23T07:23:46Z)

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-eco-mods-7` on host `kais-macbook-pro-2.local`. Accepted by `ward agent --harness codex` (reserved 2026-07-23T07:26:05Z). 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/eco-mods#7` · branch `issue-7` · harness `codex` · workflow `merge-remote-main` - **Run:** `engineer-codex-eco-mods-7` · ward `v0.793.0` · dispatched `2026-07-23T07:26:04Z` - **Reservation:** held - **Comment thread:** 2 included in the pre-flight read, 0 stripped (ward's own automated comments). - included: @coilyco-ops (2026-07-23T05:58:29Z), @coilyco-ops (2026-07-23T07:23:46Z) 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:47:31 +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 mods/Mods/UserCode/BunWulfBiochemical/Assets/ChemicalLaboratory.unity3d 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 `mods/Mods/UserCode/BunWulfBiochemical/Assets/ChemicalLaboratory.unity3d` 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

priority

P3

label

2026-07-29 03:47:54 +00:00

coilyco-ops added

and removed

labels