Stop zero-face test fixtures from auto-importing on project load (#634) * Stop zero-face test fixtures from auto-importing on project load The zero-face/corrupted test fixtures (emptymesh.abc, zerofacemesh.abc, SlimeMolding.abc) were imported automatically whenever a project loaded the package's Tests folder. Their import hits the graceful zero-face path (AlembicMesh.cs Debug.Log), which polluted the console on startup and failed clean-console tests — our own only passed via a hardcoded exemption list, and Unity trunk's PackageIsolationTests.TestCleanConsole had no such exemption so it failed. Move the three fixtures (with their .meta) into an ignored "Fixtures~" folder so Unity no longer imports them at startup, and have the three tests copy each fixture into Assets on demand, import it, and delete it in TearDown. The user-facing zero-face Debug.Log is unchanged. Removes the now-unnecessary clean_console_exemption_list.json entries. Verified: opening AlembicHDRPLatest logs no zero-face messages on load, and the three tests pass (EditMode). Co-Authored-By: Claude Opus 4.8 (1M context) * Address review: resolve fixture path via FileUtil.GetPhysicalPath Use EditorHelper.BuildPathIfNecessary (FileUtil.GetPhysicalPath) instead of Path.GetFullPath to resolve the "Packages/.../Fixtures~" source path. This correctly maps the virtual package path to its physical location regardless of package layout (embedded, local file dependency, or package cache), matching the existing pattern in AlembicBuildPostProcess.cs. Co-Authored-By: Claude Opus 4.8 (1M context) * Fix formatting in JobBuilderExtensions.cs Re-indent the if/else command bodies to satisfy unity-meta formatting (uncrustify). The blocks kept their old switch/case indentation after the Wrench 3.x SystemType -> Host API migration. Co-Authored-By: Claude Opus 4.8 (1M context) * Address review: read-only-safe fixture copy into a temp folder - Copy fixtures into a dedicated Assets/TempAlembicFixtures folder instead of the Assets root, so a same-named user asset can't be clobbered, and TearDown can delete the whole folder (removing the .meta files too). - Strip the read-only attribute after copying: package-cache files are read-only and File.Copy preserves that, which would break Unity's .meta update on import and block overwriting a leftover copy. - Drop the redundant ImportAsset call; AssetDatabase.Refresh already imports the new files. Co-Authored-By: Claude Opus 4.8 (1M context) * Restore clean-console exemption entries The clean-console brick (wind-xu/clean_console_test_brick@v0.4.0) crashes on an empty exemption list (UnboundLocalError in exempt_messages). Emptying the list was an unnecessary cleanup; the real fix is moving the fixtures to the ignored Fixtures~ folder so they never auto-import. Keep the (now inert) entries so the brick runs. Co-Authored-By: Claude Opus 4.8 (1M context) * Remove clean-console exemption list The zero-face fixtures no longer auto-import (moved to Tests/Editor/Fixtures~), so there are no package-specific console messages to exempt. Delete the exemption file entirely rather than keep inert entries: the clean-console brick guards the call with `if os.path.exists(exemption_file)`, so a missing file cleanly skips exemption injection (an empty "messages" list instead crashes the brick with UnboundLocalError). Co-Authored-By: Claude Opus 4.8 (1M context) * Store zero-face fixtures as .abc.bytes so they ship in the package The previous "Fixtures~" folder is stripped by package pack (only Documentation~/Samples~ are kept), so the fixtures were absent when the package is tested from the registry, and the three tests failed with DirectoryNotFoundException. Store them instead as ".abc.bytes" in a normal Fixtures folder: Unity imports them as inert TextAssets (the AlembicImporter never runs on load, so no zero-face console logs), and they ship as normal package assets. The tests copy each .bytes payload to a real .abc on demand and import it. Co-Authored-By: Claude Opus 4.8 (1M context) * Add folder meta for Tests/Editor/Fixtures Package pack drops folders that lack a committed .meta, so the Fixtures folder (and its .abc.bytes fixtures) was absent from the packed package and the tests failed with DirectoryNotFoundException. Commit the folder meta so the folder ships, matching Tests/Runtime/Data.meta. Co-Authored-By: Claude Opus 4.8 (1M context) * Load .bytes fixtures via AssetDatabase GUID, not a package path The fixtures ship in upm-ci's split "com.unity.formats.alembic.tests" package, but the previous code resolved them against the main package's path (Packages/com.unity.formats.alembic/Tests/...), which has Tests stripped -> DirectoryNotFoundException in CI. Look the .bytes TextAsset up by GUID (AssetDatabase.GUIDToAssetPath), which resolves to whichever package it's imported from (the .tests package in CI, the package itself locally), and write its bytes to a temp .abc to import. Co-Authored-By: Claude Opus 4.8 (1M context) * Add CHANGELOG entry for zero-face test fixture change Co-Authored-By: Claude Opus 4.8 (1M context) --------- Co-authored-by: Claude Opus 4.8 (1M context)