Files
Jakub Zych 6cfa0c55d2 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.
2026-10-06 20:02:40 +02:00

4.4 KiB

Feature PR

Using the wrong template? — Bug fix: use fix.md — Enhancement to existing behavior: use enhancement.md


Linked Issue

Required. This PR will be auto-closed if no valid issue link is found. The linked issue must have the approved-feature label. If it does not, this PR will be closed without review — no exceptions.

Closes #

⛔ No approved-feature label on the issue = immediate close. Do not open this PR if a maintainer has not yet approved the feature spec. Do not open this PR if you wrote code before the issue was approved.


Feature summary

What changed

New files

File Purpose

Modified files

File What changed

Implementation notes

Spec compliance

Testing

Test coverage

Platforms tested

  • macOS
  • Windows (including backslash path handling)
  • Linux

Runtimes tested

  • Claude Code
  • Antigravity
  • OpenCode
  • Codex
  • Other: ___
  • N/A — specify which runtimes are supported and why others are excluded

Scope confirmation

  • The implementation matches the scope approved in the linked issue exactly
  • No additional features, commands, or behaviors were added beyond what was approved
  • If scope changed during implementation, I updated the issue spec and received re-approval

Documentation

CI enforces this — lint:docs fails any PR with an Added / Changed / Deprecated / Removed changeset fragment that does not also touch at least one file under docs/. Features almost always trigger Added. See CONTRIBUTING.md → Documentation Updates.

  • Updated the relevant file(s) under docs/ to reflect this feature
    • New command or flag → docs/COMMANDS.md and docs/FEATURES.md
    • New workflow or behavior → docs/USER-GUIDE.md
    • Configuration / schema change → docs/CONFIGURATION.md
    • Architectural change → docs/ARCHITECTURE.md and/or docs/adr/
    • Agent or skill change → docs/AGENTS.md
  • All docs/ content added in this PR is written in English (translated READMEs README.pt-BR.md / README.zh-CN.md / README.ja-JP.md / README.ko-KR.md are community-maintained and do not need to be updated in this PR)
  • If genuinely no user-facing docs impact (rare for features — explain in PR), apply the no-docs label or add <!-- docs-exempt: <reason> --> inside each triggering changeset fragment.

Checklist

  • Issue linked above with Closes #NNN — PR will be auto-closed if missing
  • Linked issue has the approved-feature label — PR will be closed if missing
  • All acceptance criteria from the issue are met (listed above)
  • Implementation scope matches the approved spec exactly
  • All existing tests pass (npm test)
  • New tests cover the happy path, error cases, and edge cases
  • .changeset/ fragment added with a user-facing description of the feature (npm run changeset -- --type Added --pr <NNN> --body "...")
  • No unnecessary external dependencies added
  • Works on Windows (backslash paths handled)

Breaking changes

None

Screenshots / recordings