Say what each platform check is actually worth

[jcant0n]

The list was ten ticks and nothing else, which reads as ten platforms verified equally. They are not, and three of them are not verified at all.

Seven are checked against the real .nupkg before publishing:

• five desktop identifiers and browser-wasm drop a sphere onto a floor through the library — it has to fall, settle, and settle on the floor;
• iossimulator-arm64 is linked and its executable inspected for defined entry points (1280 T symbols, exactly what the generator emits).

And two rows say so plainly:

• ios-arm64 is indirect — a device build needs a signing identity CI does not have, though it links the same archive through the same targets file as the simulator;
• android-arm and android-arm64 are not checked at all. They are ordinary shared libraries and nothing installs the package on Android today.

A reader deciding whether to ship on a platform should be able to see which of those they are getting. The android row in particular is a gap worth advertising rather than leaving for somebody to discover — Cesium.NET has that leg and this repository does not.

[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.}