startup_diagnostics

Diagnosis order:
1. Read the development extension host's `remoteexthost.log`; find `ExtensionService#_doActivateExtension reqlan.reqlan-extension`.
2. Distinguish code-loading time, activate-call time, and activate-resolved time.
3. If activation failed, use the first Reqlan stack frame rather than inferring a CPU hang.
4. If manifest UI exists but every command is missing, investigate module load / activation before indexing or webview data.
5. If the extension-owned " Loading Reqlan … " shell appears, provider resolution succeeded; subsequent delays belong to webview bootstrap or index readiness.
6. Confirm `out/extension/main.cjs` is newer than changed source and includes lazy `import("./vendor/sql-asm.cjs")`.
CPU-idle profiles do not disprove activation failure: once `require()` throws, the host can remain healthy and mostly idle while Reqlan stays unregistered.

Interactive page: startup_diagnostics