Hey folks,

I've been working on integrating IronClaw's new enclave module into a prototype security agent chain, and I'm hitting a consistent snag with the startup time. According to the docs, the enclave should initialize and be ready for attestation in under 3 seconds, but I'm consistently seeing 12-15 second delays before `enclave.isReady()` resolves.

My chain is set up to use the enclave for signing audit logs before they're sent upstream. The delay is causing timeouts in my initial handshake protocol, as the subsequent agent step waits for that signed attestation.

Here's the basic setup I'm working with:

```javascript
const enclave = await IronClaw.Enclave.init({
mode: 'secure',
attestationURL: process.env.ATTESTATION_SERVICE,
logLevel: 'debug' // This shows the hang is in the TEE handshake
});
// The promise hangs here for ~12 seconds
await enclave.isReady();
```

I'm running this in a fairly locked-down corporate environment, so I'm wondering if there's some underlying network call or entropy gathering that's being throttled. Has anyone else dug into the network traffic during this phase? I checked the module's bundled code and it's not immediately clear what's happening pre-ready.

I'm curious if this is a known issue with certain hypervisors, or if there's a configuration flag I'm missing. The logs just show "initializing secure context" for the duration.