docs(unity): unity/README.md and unity/AGENTS.md still describe the pre-consolidation three-repo world #29

New issue

Closed

opened 2026-08-20 06:16:16 +00:00 by coilyco-ops · 0 comments

coilyco-ops commented

2026-08-20 06:16:16 +00:00

Member

unity/README.md and unity/AGENTS.md came across verbatim in the import commit and were never rewritten for their new home. Both read as if the Unity project were still its own repository.

What is wrong

Wrong repo identity. Both files call the project eco-mods-assets and describe it as a standalone repo. It is now the unity/ directory of eco-mods.

Dead cross-references. They point at eco-mods-public, eco-mods-assets-embeded, and eco-mods-assets on github.com. All three are deprecated. The canonical set is coilyco-gaming/{eco-app, eco-mods, eco-ops} on Forgejo, and the embedded assets are now the sibling unity-embedded/ directory in this same repo.

Retired command surface. unity/AGENTS.md routes every dev command through coily and names coily exec pre-commit-all. The coily spelling is retired. The live verb is just pre-commit-all from unity/justfile, which the file does not mention.

Retired tooling reference. unity/README.md says bundles are copied out by invoke copy-assets. There is no invoke anywhere in the repo. The verb is just copy-assets, which routes to mods/scripts/mods.py and has its own defects tracked separately.

Stale release claim. unity/AGENTS.md says the project ships no release of its own and that consumer repos publish the bundles. The consumers it names no longer exist, and this repo's own CI publishes install-ready packages.

A GitHub cross-reference convention link at the bottom of both files points at an agentic-os issue by the old coilysiren/agentic-os slug.

What is still correct

Keep these, they are the load-bearing parts:

The Assets/, Packages/, ProjectSettings/, AssetBundles/, Builds/ layout description.
Vendored content under Assets/ is upstream and should not be edited or moved, and excludes beat edits for it.
Never hand-edit .meta files, Unity manages them.
Never use --no-verify.

Scope

Docs only. No code or asset changes. The trifecta rule means unity/docs/FEATURES.md should get the same read while someone is in there.

`unity/README.md` and `unity/AGENTS.md` came across verbatim in the import commit and were never rewritten for their new home. Both read as if the Unity project were still its own repository. ## What is wrong **Wrong repo identity.** Both files call the project `eco-mods-assets` and describe it as a standalone repo. It is now the `unity/` directory of `eco-mods`. **Dead cross-references.** They point at `eco-mods-public`, `eco-mods-assets-embeded`, and `eco-mods-assets` on `github.com`. All three are deprecated. The canonical set is `coilyco-gaming/{eco-app, eco-mods, eco-ops}` on Forgejo, and the embedded assets are now the sibling `unity-embedded/` directory in this same repo. **Retired command surface.** `unity/AGENTS.md` routes every dev command through `coily` and names `coily exec pre-commit-all`. The `coily` spelling is retired. The live verb is `just pre-commit-all` from `unity/justfile`, which the file does not mention. **Retired tooling reference.** `unity/README.md` says bundles are copied out by `invoke copy-assets`. There is no `invoke` anywhere in the repo. The verb is `just copy-assets`, which routes to `mods/scripts/mods.py` and has its own defects tracked separately. **Stale release claim.** `unity/AGENTS.md` says the project ships no release of its own and that consumer repos publish the bundles. The consumers it names no longer exist, and this repo's own CI publishes install-ready packages. **A GitHub cross-reference convention link** at the bottom of both files points at an agentic-os issue by the old `coilysiren/agentic-os` slug. ## What is still correct Keep these, they are the load-bearing parts: * The `Assets/`, `Packages/`, `ProjectSettings/`, `AssetBundles/`, `Builds/` layout description. * Vendored content under `Assets/` is upstream and should not be edited or moved, and excludes beat edits for it. * Never hand-edit `.meta` files, Unity manages them. * Never use `--no-verify`. ## Scope Docs only. No code or asset changes. The trifecta rule means `unity/docs/FEATURES.md` should get the same read while someone is in there.

coilyco-ops referenced this issue

2026-08-20 06:31:32 +00:00

pre-commit fails on four catalog hooks, and the pyproject opt-out written for two of them is inert #31