feat: US-001 - Fix crypto KeyObject metadata (asymmetricKeyType, asymmetricKeyDetails)

Author: NathanFlurry

CLAUDE.md

@@ -50,6 +50,7 @@
 
 - use pnpm, vitest, and tsc for type checks
 - use turbo for builds
+- after changing `packages/core/isolate-runtime/src/inject/require-setup.ts` or Node bridge code that regenerates the isolate bundle, rebuild in this order: `pnpm --filter @secure-exec/nodejs build` then `pnpm --filter @secure-exec/core build`; the conformance runner executes built `dist` output, not just source files
 - keep timeouts under 1 minute and avoid running full test suites unless necessary
 - use one-line Conventional Commit messages; never add any co-authors (including agents)
 - never mark work complete until typechecks pass and all tests pass in the current turn; if they fail, report the failing command and first concrete error
@@ -198,6 +199,8 @@ Follow the style in `packages/secure-exec/src/index.ts`.
 
 ## Documentation
 
+- all public-facing docs (quickstart, guides, API reference, landing page, README) must focus on the **Node.js runtime** as the primary and default experience — do not lead with WasmVM, kernel internals, or multi-runtime concepts
+- code examples in docs should use the `NodeRuntime` API (`runtime.run()`, `runtime.exec()`) as the default path; the kernel API (`createKernel`, `kernel.spawn()`) is for advanced multi-process use cases and should be presented as secondary
 - WasmVM and Python docs are experimental docs and must stay grouped under the `Experimental` section in `docs/docs.json`
 - docs pages that must stay current with API changes:
   - `docs/quickstart.mdx` — update when core setup flow changes

docs/nodejs-conformance-report.mdx

@@ -12,18 +12,18 @@ description: Node.js v22 test/parallel/ conformance results for the secure-exec
 | Node.js version | 22.14.0 |
 | Source | v22.14.0 (test/parallel/) |
 | Total tests | 3532 |
-| Passing (genuine) | 704 (19.9%) |
+| Passing (genuine) | 730 (20.7%) |
 | Passing (vacuous self-skip) | 34 |
-| Passing (total) | 738 (20.9%) |
-| Expected fail | 2723 |
+| Passing (total) | 764 (21.6%) |
+| Expected fail | 2697 |
 | Skip | 71 |
 | Last updated | 2026-03-25 |
 
 ## Failure Categories
 
 | Category | Tests |
 | --- | --- |
-| implementation-gap | 1422 |
+| implementation-gap | 1396 |
 | unsupported-module | 737 |
 | requires-v8-flags | 239 |
 | requires-exec-path | 200 |
@@ -70,7 +70,7 @@ description: Node.js v22 test/parallel/ conformance results for the secure-exec
 | constants | 1 | 0 | 1 | 0 | 0.0% |
 | corepack | 1 | 0 | 1 | 0 | 0.0% |
 | coverage | 1 | 0 | 1 | 0 | 0.0% |
-| crypto | 99 | 16 (13 vacuous) | 83 | 0 | 16.2% |
+| crypto | 99 | 42 (13 vacuous) | 57 | 0 | 42.4% |
 | cwd | 3 | 0 | 3 | 0 | 0.0% |
 | data | 1 | 0 | 1 | 0 | 0.0% |
 | datetime | 1 | 0 | 1 | 0 | 0.0% |
@@ -245,11 +245,11 @@ description: Node.js v22 test/parallel/ conformance results for the secure-exec
 | wrap | 4 | 0 | 4 | 0 | 0.0% |
 | x509 | 1 | 0 | 1 | 0 | 0.0% |
 | zlib | 53 | 17 | 33 | 3 | 34.0% |
-| **Total** | **3532** | **738** | **2723** | **71** | **21.3%** |
+| **Total** | **3532** | **764** | **2697** | **71** | **22.1%** |
 
 ## Expectations Detail
 
-### implementation-gap (741 entries)
+### implementation-gap (715 entries)
 
 **Glob patterns:**
 
@@ -260,7 +260,7 @@ description: Node.js v22 test/parallel/ conformance results for the secure-exec
 - `test-https-*.js` — https depends on tls — most tests fail on missing TLS fixture files or crypto API gaps
 - `test-http2-*.js` — http2 module bridged via kernel — most tests fail on API gaps, missing fixtures, or protocol handling
 
-*735 individual tests — see expectations.json for full list.*
+*709 individual tests — see expectations.json for full list.*
 
 ### unsupported-module (190 entries)