What problem does it solve? Running the digital-signature (ECP) chain of a 1C native component normally requires launching the 1C:Enterprise platform, which makes automated and CI testing impractical. This Skill explains how to exercise the full UAPKI crypto stack (INIT, OPEN, SELECT_KEY, SIGN, VERIFY) deterministically without any 1C host, using a static-kernel selftest and a native host that emulates 1C through the IComponentBase interface. ## Core Features & Use Cases - Four-level test pyramid (L0-L3): L0 checks DLL export invariants with dumpbin, L1 runs JSON scenarios against the statically linked UAPKI kernel via uapki_selftest.exe, L2/L3 drive the main DLL through native_host.exe exactly as 1C would call it. - Offline signing and verification: Uses the bundled test key test-diia.p12 with offline mode and ignoreCertStatus options, plus STRUCT-mode VERIFY for expired certificate chains. - Cross-validation against reference signatures: Case 5 verifies signatures produced by independent PRRO/DFS reference tools, skipping gracefully when the reference directory is unavailable. - Use Case: A CI pipeline runs run_tests.ps1 after a change to the crypto driver; the script builds the test executables if missing, executes all scenarios, and returns a non-zero exit code on any failure. ## Quick Start Ask the assistant to run the UAPKI crypto test levels with run_tests.ps1 for the x64 build and interpret any failing scenario or native_host case.
