PR #68324: fix(plugins): enable native jiti for doctor-contract loader to cut status cold-start ~13s

• Repository: openclaw/openclaw
• Author: hclsys
• State: open | merged: False
• Link: https://github.com/openclaw/openclaw/pull/68324

Description (problem / solution / changelog)

Summary

Fixes #68282 — `openclaw status` (and `--json`, `--deep`, `--usage`) pays a ~15s first-call penalty on every fresh process, dominated by doctor-contract loading through the default jiti path. The reporter measured the contract-api artifact in isolation at 15.7s default vs 2.1s with `tryNative: true`, and `listPluginDoctorLegacyConfigRules` ate 21.8s of the total 17s config-validation wall time.

Root cause

`src/plugins/doctor-contract-registry.ts:46-52` built the loader via:

```ts function getJiti(modulePath: string) { return getCachedPluginJitiLoader({ cache: jitiLoaders, modulePath, importerUrl: import.meta.url, }); } ```

Without `tryNative` explicit, `getCachedPluginJitiLoader` defers to `resolvePluginLoaderJitiTryNative` in `src/plugins/sdk-alias.ts`. That function has an unconditional guard that returns `false` whenever `modulePath` matches `/dist/extensions/` — which is exactly where contract artifacts live in shipped builds (`dist/extensions/telegram/contract-api.js` etc.). So every doctor contract load took the slow transpile-and-cache path on cold start.

Fix

Pass `tryNative: process.platform !== "win32"` explicitly from the doctor registry:

```ts function getJiti(modulePath: string) { return getCachedPluginJitiLoader({ cache: jitiLoaders, modulePath, importerUrl: import.meta.url, tryNative: process.platform !== "win32", }); } ```

Jiti keeps its transpile path as a fallback on native-import failure, so aliased `openclaw/plugin-sdk/*` imports inside contract modules still resolve via the existing alias-map flow. Windows is left on the pre-existing slower path because `supportsNativeJitiRuntime` in `sdk-alias.ts` disables native jiti for that platform anyway.

Test plan

• Added a regression test `enables native jiti loading on Linux for contract-api modules (#68282)` in `src/plugins/doctor-contract-registry.test.ts`, mirroring the existing `disables native jiti loading on Windows for contract-api modules` case. Asserts `createJiti` is invoked with `tryNative: true` when `process.platform` returns `linux`.
• Existing Windows test (`disables native jiti loading on Windows`) still passes because the new pass-through evaluates to `false` on Windows.
• `NODE_OPTIONS=--max-old-space-size=8192 npx tsc --noEmit` — 245 baseline on main, 245 on branch (no delta).
• `pnpm exec oxlint` on both touched files — 0 warnings, 0 errors.

Local full vitest is blocked by pre-existing `test/non-isolated-runner.ts` drift (reproduces on `main`); CI exercises the new case normally.

Risk

• Contract artifacts in `dist/extensions/<plugin>/` are built JS bundles — native import is the fast and correct path for them. The transpile fallback remains active if a native-load edge case (e.g. a contract module that imports a TS source path directly) fails.
• Windows path is unchanged because `supportsNativeJitiRuntime` already disables native jiti there.
• No API surface changes; doctor-rule loading emits the same `PluginDoctorContractEntry` values, just faster on first call.

Measurement (from issue body)

This PR puts the doctor registry on the 2.1s path.

Changed files

• src/plugins/doctor-contract-registry.test.ts (modified, +31/-0)
• src/plugins/doctor-contract-registry.ts (modified, +12/-0)

PR #68348: fix: use native loading for doctor contract API to speed up status command

• Repository: openclaw/openclaw
• Author: nightq
• State: open | merged: False
• Link: https://github.com/openclaw/openclaw/pull/68348

Description (problem / solution / changelog)

Summary

Fixes openclaw#68282

The openclaw status and related status commands are slow on a fresh process because doctor contract loading uses the slow jiti path instead of native loading for built artifacts.

Root Cause

The getJiti function in doctor-contract-registry.ts was not passing tryNative flag to getCachedPluginJitiLoader, causing built artifacts to be loaded through the slow jiti path instead of native loading.

Fix

• Import shouldPreferNativeJiti from sdk-alias.js
• Pass tryNative: shouldPreferNativeJiti(modulePath) to getCachedPluginJitiLoader

This matches the pattern used in other loader functions (e.g., loader.ts line 443, bundled-capability-runtime.ts line 206, runtime-plugin-boundary.ts line 118')

Test Plan

• Relevant unit tests pass (src/plugins/doctor-contract-registry.test.ts - 4 tests passed)
• Follows existing code style

Closes openclaw#68282

Changed files

• src/plugins/doctor-contract-registry.ts (modified, +2/-0)