GetRuntimeAttestationReport: how is the report verified?

I am trying to understand whether GetRuntimeAttestationReport can be used for independent security verification.

The Microsoft documentation says the API returns a signed report from the Secure Kernel and accepts a 32-byte nonce.

Could Microsoft clarify:

1. What key or certificate signs the report?
2. How can a separate/off-device verifier validate that signature?
3. Is the 32-byte nonce covered by the signature?
4. What exactly is included in the Driver and Code Integrity reports?
5. Does the Code Integrity report prove the effective App Control / WDAC state, including:
   • UMCI enabled;
   • enforcement vs audit mode;
   • supplemental policies;
   • Dynamic Code Security?
6. Does the report prove which user-mode process requested it, or the EXE/DLLs used by that verifier?
7. Is there a standard way to bind later local observations, such as WSL files/configuration, to the same attested state and nonce?

If these properties are not supported or not publicly documented, an explicit confirmation would also be useful.

I am looking for authoritative Microsoft documentation or an answer from the Windows security/runtime-attestation team, rather than community inference.

Thank you.