Make the bindings resolvable on iOS

[jcant0n]

The package has shipped runtimes/ios-arm64/native/libJoltC.a since its first release, and no consumer could ever have used it: every DllImport named "JoltC", the project built one TFM where __IOS__ is never defined, and the targets file linked nothing on iOS. Held until the pattern was proven in Evergine.Bindings.CesiumNative, which shipped it to nuget.org this morning as 2026.8.9.34.

What changes

• The generator emits Native.Dll / Native.Conv instead of literals — the shape VuforiaGen uses, Vuforia being the one package in this fleet confirmed working on iOS in a real Evergine project. One line changed; 1280 declarations regenerated.
• Native.cs switches on __IOS__ to "__Internal" — the only name that reaches symbols linked into the executable.
• The project multi-targets net10.0;net10.0-ios, so __IOS__ is actually defined.
• The targets file gains the iOS block that went green in Cesium, verbatim in shape: the injected _FrameworkNativeReference (the shape that was actually validated), ForceLoad (the linker keeps only referenced members and every entry point here is reached from managed code) and SmartLink (iOS links with -dead_strip; without -u roots the strip removes what ForceLoad brought in).

Jolt is simpler than Cesium in the two places that cost rounds there

• The archive is self-contained by construction — JoltC and Jolt merged, no vcpkg dependencies — so the duplicate-symbol failure class cannot occur.
• The file keeps its libJoltC.a name: with __Internal the name is irrelevant, unlike wasm where the module name comes from the file name.

The smoke leg ships with its instrument already corrected

nm dumps to a file (never nm | grep -q under pipefail, which reports the opposite of the truth at volume), and the assertion requires JoltC_Init to be a T — a defined global — because a name alone matches an unresolved reference just as well.

Verified locally, as far as Windows allows

net10.0       __Internal: False
net10.0-ios   __Internal: True
lib/: net10.0, net10.0-ios26.0  +  buildTransitive  +  both iOS archives
desktop smoke vs the multi-targeted package: PASS (48 steps, y=0.480, unchanged)

The iOS leg itself needs a CD artifact to run against; that is the next step after merging.

[github-actions]

API gate: additive

Every symbol that existed still exists, unchanged. Nothing that compiled before stops compiling.

Target framework	Added	Removed
net10.0	+0	-0

_{Enum and constant values are part of the measured surface: a renumbering keeps compiling and sends the wrong number to the driver, so it counts as a removal.}