v0.12.3 — Asset Store submission build

The Asset Store submission is a UPM package, not a .unitypackage. Same code; the difference is that package.json declares glTFast and Newtonsoft JSON and Package Manager installs them for the buyer. A .unitypackage carries no dependency information at all, so that route makes every buyer install two packages by hand before anything compiles.

For the submission

Polyfork-UPM.zip unzips into <project>/Packages/ so the manifest lands at Packages/com.polyfork.connector/package.json. Then Window ▸ Tools ▸ Asset Store ▸ Validator (Validation Type: UPM), and Uploader ▸ UPM Packages.

It is the store build: Polyfork ▸ Update Package is stripped, because re-adding this package from its git URL is programmatic package manipulation under 2.5.1.e.

Fixed

• The test assembly compiled in consumer projects. Polyfork.Connector.Tests references UnityEngine.TestRunner, UnityEditor.TestRunner and nunit.framework.dll, all from com.unity.test-framework, with no define constraint — so a project without Test Framework got unresolved references out of a package it never asked to test. Now gated on UNITY_INCLUDE_TESTS, which Unity sets only for a package in the project's testables. This never reached the .unitypackage, which excludes Tests/, so it was specific to UPM and git installs, which is now the format being shipped.
• The store build no longer carries .github or .gitignore.

Other artifacts

File	For
Polyfork.unitypackage	Distribution outside the store. Install glTFast and Newtonsoft first.
Polyfork-AssetStore-source.zip	The Assets/ folder layout, if you ever need Unity to export a .unitypackage.
Git URL	https://github.com/lucas-martinic/polyfork-unity-connector.git, resolves dependencies on its own.