Link an iOS application against the package, and check it took

[jcant0n]

The last identifier without a leg, and the only one where a green build proves nothing on its own.

iOS loads nothing. Apple only allows dynamic libraries that ship inside the app bundle as frameworks, so CesiumC builds a static archive and the package's targets file links it into the executable. Two things have to hold, and neither is visible from any other leg:

• the targets file has to put the archive on the link line, and
• Native.Dll has to have compiled to "__Internal", because once linked only that name reaches the symbols.

Get either wrong and every build still succeeds. The failure arrives at the first P/Invoke, in somebody else's application.

So the leg does not stop at building

It opens the .app and checks two things:

• the executable is over ten megabytes — cesium-native merged in is tens, and one that linked none of it comes out at a couple;
• cesium_async_system_create is among its defined symbols, which is exactly what would be missing if the name had stayed "CesiumNativeC".

The simulator, and the limit is stated rather than hidden

A device build needs a signing identity and a provisioning profile a runner does not have. Both identifiers link the same archive through the same targets file, so what this says about ios-arm64 is indirect.

Branched after #16 landed, so this file now carries all five legs: five desktop identifiers, wasm, android and ios.

[github-actions]

API gate: additive

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

Target framework	Added	Removed
net10.0-ios	+0	-0
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.}