refactor: drop 12 runtimes, keep Claude, Codex, OpenCode, Cursor, ZCode, Antigravity
Removes kilo, kimi, kimi-code, copilot, windsurf, augment, trae, qwen, hermes, cline, codebuddy and pi end to end: capability descriptors, installer branches and converters (bin/install.js 14.9k -> 11.2k lines), TypeScript converters, hook surfaces and runtime homes, review lanes qwen/kimi-code, the two pi migrations, Kimi payload normalization in the hook guards, dead hostBehaviors vocabulary, launcher home probes, fixtures, runtime-specific tests and the prose that presented them as supported. Installer output for the six kept runtimes is byte-identical to before the prune. The Kimi tool-vocabulary tests in workflow-guard, read-guard and read-injection-scanner are left in place pending a decision.
This commit is contained in:
@@ -81,7 +81,7 @@ two adapter shapes it uses, set by the `embeddingMode` axis.
|
||||
dispatch directly at invocation time (`embeddingMode: imperative`). The host
|
||||
hands control to MSD's runtime launcher and MSD does the rest, live, on every
|
||||
invocation. Most CLI-style and IDE-embedded hosts work this way — OpenCode,
|
||||
Cursor, Cline, Hermes, Qwen, Kilo, Trae, Kimi, Antigravity, and Augment are
|
||||
Cursor, and Antigravity are
|
||||
all imperative integrations.
|
||||
|
||||
**Declarative** hosts cannot run arbitrary code at dispatch time. They
|
||||
@@ -113,8 +113,8 @@ scale in the same cycle. Fourteen runtimes moved onto the public interface via a
|
||||
(#2087–#2100) — existing bespoke integrations were rewritten to express
|
||||
themselves as EoS descriptors rather than as ad hoc code.
|
||||
|
||||
Three new hosts joined over the same window, each exercising a different
|
||||
part of the interface: ZCode (#1925), pi (#2102), and a VS Code extension
|
||||
Two new hosts joined over the same window, each exercising a different
|
||||
part of the interface: ZCode (#1925) and a VS Code extension
|
||||
driven entirely through the adapter layer (#2103). Gemini CLI was retired in
|
||||
favor of its successor, Antigravity, which shares its underlying
|
||||
infrastructure (#1928).
|
||||
|
||||
Reference in New Issue
Block a user