Expand CI compatibility matrix to twenty verified samples

NOTES.md

@@ -1,7 +1,7 @@
 # CI API availability observations
 
 See the [CI API compatibility matrix](docs/ci-api-compatibility.md) for the
-per-API tables covering thirteen VM, ISO and modern x64/ARM64 samples, with exact
+per-API tables covering 20 VM, ISO and modern x64/ARM64 samples, with exact
 versions, file hashes and machine-readable results. The six-sample notes below
 describe the original VM corpus and its subsequent ISO follow-up.
 
@@ -40,6 +40,9 @@ in x64 `10.0.19041.1865` and `10.0.22000.318`, and the original investigation
 finds it present in `10.0.26100.8328`. This brackets Windows 10 servicing
 observations without identifying the first update adding the export. The
 CodeIntegrity-RE `iso-corpus-index.json` records the exact files and hashes.
+The Windows 10 ARM64 21H2 sample additionally exports it in CI
+`10.0.19041.1566`; this does not establish x64 availability at that revision.
+The matrix keeps architecture-specific observations separate.
 A header declaration,
 import-library symbol, or `NTDDI_VERSION >= NTDDI_WIN10` alone does not make an
 unconditional static import loadable on the older samples. Callers supporting
@@ -47,6 +50,10 @@ those samples must avoid that import or use optional resolution with an
 explicit unavailable/fallback path. `CiSetTrustedOriginClaimId` likewise cannot
 be assumed available on every Windows 10 build; it is a CI-global setter.
 
+The original modern x64 sample has display `FileVersion` **26100.8328**, but
+its numeric fixed version is **26100.9444**. The matrix records both under the
+same SHA-256 identity and uses numeric fixed versions in its tables.
+
 ## Exact sampled files
 
 - Windows 10 1507: `10.0.10240.16463` x64, SHA-256