From 07a6deb90477ca0f0d30a35bdc1b237a3df95b03 Mon Sep 17 00:00:00 2001 From: Meta Vens Date: Thu, 9 Jul 2026 01:26:33 +0100 Subject: [PATCH] Clarify Unity CultLib dependency boundary --- docs/eve-migration-roadmap.md | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/docs/eve-migration-roadmap.md b/docs/eve-migration-roadmap.md index 9b5c5f6..b1a3fda 100644 --- a/docs/eve-migration-roadmap.md +++ b/docs/eve-migration-roadmap.md @@ -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`