GameCult/Thing
Watch
9
0
Fork
You've already forked Thing
 0
Code Issues Pull requests 1 Projects Releases Packages Wiki Activity Actions

Clarify Unity CultLib dependency boundary

Browse source
This commit is contained in:
Meta Vens 2026-07-09 01:26:33 +01:00
commit 07a6deb904
1 changed files with 5 additions and 1 deletions
Download patch file Download diff file Expand all files Collapse all files

6
docs/eve-migration-roadmap.md
View file

@ -352,7 +352,11 @@ Recently cut:
`org.gamecult.eve.unity-uitoolkit` to Aetheria's Unity `testables`, runs
`GameCult.Eve.UnityUIToolkit.Tests` in Unity batchmode, writes XML and log
artifacts under `artifacts/aetheria-unity-editmode`, and restores
`Packages/manifest.json` before returning. This proves the incubating test
`Packages/manifest.json` before returning. The Brokkr/CultMesh DLL references
in the Unity test asmdef are Unity package assembly plumbing: CultLib already
owns the .NET/NuGet dependency story. EveUnity's split blocker is proving how
the Unity package resolves those assemblies after it leaves Eve incubation,
not inventing a dependency system for CultLib. This proves the incubating test
lifecycle; it does not make Eve own Unity's final runtime lifecycle.
- Aetheria now has repeatable Unity package consumer-build evidence for the
Eve UI Toolkit runtime. `scripts/run-aetheria-unity-package-smoke.ps1`