chore: bump gui-chat-protocol to ^2.0.0 and plugin to 2.0.0

[isamu]

Summary

Bumps gui-chat-protocol to ^2.0.0 and this plugin to 2.0.0 (from 1.5.0).

This plugin only uses gui-chat-protocol's types (ToolResult, ToolPlugin, …) — it calls none of the four APIs whose signatures changed in 2.0.0, so no source change was needed.

Items to Confirm / Review

• Version-only change. Confirm the major bump is the intended signal for the protocol's 1.x → 2.x shift.

User Prompt

https://www.npmjs.com/package/gui-chat-protocol 2.0.0 になった。
一部 breaking change があるので、
https://github.com/receptron/gui-chat-protocol/releases
をよくよんで、このdir以下で gui-chat-protocol を使っているものは全部あげていく。
npm があるものは全部 publish する。そのときに major のバージョンを上げる。
同時に型問題とかで refactor できるものはしておいてね。

Breaking changes in gui-chat-protocol 2.0.0

Four public signatures stopped accepting a caller-named type parameter and now take a reader instead — dispatch, subscribe, getConfig, publish ("a type parameter appearing only in return position is a type assertion with nicer syntax"). No plugin in this family calls any of them, so that half of the migration is a no-op here.

What does reach the plugins is the same rule applied to ToolContextApp:

-export interface ToolContextApp extends Record<string, (...args: any[]) => any> {
-    getConfig: <T = unknown>(key: string) => T | undefined;
+export interface ToolContextApp extends Record<string, (...args: any[]) => unknown> {
+    getConfig: {
+        (key: string): unknown;
+        <T>(key: string, parse: (raw: unknown) => T): T | undefined;
+    };

Verification

Run locally on this branch: yarn typecheck, yarn lint, yarn build — all green.

[socket-security]

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	gui-chat-protocol@​1.2.0 ⏵ 2.0.0	+1		+1	+1

View full report