Parks packaging must keep fountain texture references portable across workstations. What should the validator enforce?

Parks packaging must keep fountain texture references portable so any twin consumer can find materials without relying on personal folders. Enforcing relative searchable paths for fountain textures inside the package binds looks to the published layout: textures remain under the package or its documented search roots and stay discoverable as the package moves between workstations and CI. Absolute paths to each artist’s personal Downloads folder create a one-machine package, leaving other workstations and overnight farms unable to find the textures. Empty assetPath strings prevent textures from resolving, defeating the purpose of packaging. Only UNC shares that ignore the published package layout tie the twin to network topology and bypass the package’s portable structure, making offline review copies and mirrored caches fail unpredictably. Exam caveat: relative searchable paths still depend on the city’s search-path or resolver configuration including the package roots used at runtime; publishing without the texture files or resolving against different roots in CI can still break references. Practical check: after packaging a fountain asset, inspect its texture assetPath values, confirm they are package-relative or searchable rather than personal Downloads absolutes, move the package directory to a second workstation, open the stage, and verify that fountain materials resolve without manually relinking textures.