[SaKaNa-Y]

Summary

Plugin authors who copy the Kit guides can subscribe to lifecycle events that never fire, register a JSON dock that fails to render, or construct a remote URL that the parser does not recognize.

Correct the guides, skill references and JSON renderer comments to match the current API. Clarify that host lifecycle events run in the Node process.

- command:registered / message:added / terminal:session:updated
+ commands:registered / messages:added / terminals:session:updated
- docks.register({ ..., ui })
+ docks.register({ ..., view: ui.view })
- #vite-devtools-kit-connection=...
+ #devframe-remote-connection=...

Evidence

• Before: Old event names received no notifications. The old JSON registration failed type checking and browser rendering. Remote URLs with the old key parsed as null.
  After: All documented event families received notifications. Corrected event and JSON examples passed type checking. The real JSON renderer displayed the corrected view in a browser fixture with controlled shared state. Both fragment and query descriptors parsed with the corrected key.
• pnpm lint, pnpm test --run (400 passed, 2 skipped), pnpm typecheck, pnpm build and the documentation site build passed.

Merge Danger

Door: two-way

Blast Radius: documentation

The changes cover guides, skill references and source comments. Runtime behavior is unchanged.

[pkg-pr-new]

Open in StackBlitz

@vitejs/devtools

npm i https://pkg.pr.new/@vitejs/devtools@625

@vitejs/devtools-kit

npm i https://pkg.pr.new/@vitejs/devtools-kit@625

@vitejs/devtools-oxc

npm i https://pkg.pr.new/@vitejs/devtools-oxc@625

@vitejs/devtools-rolldown

npm i https://pkg.pr.new/@vitejs/devtools-rolldown@625

@vitejs/devtools-vite

npm i https://pkg.pr.new/@vitejs/devtools-vite@625

@vitejs/devtools-vitest

npm i https://pkg.pr.new/@vitejs/devtools-vitest@625

commit: 4d765dd