feat(yoke): add Kiro CLI as a first-class agent runtime via ACP

[hmkim]

Summary

Adds AWS Kiro CLI as a first-class agent runtime in Clay, alongside Claude Code and Codex, through the YOKE adapter layer. Users pick the vendor, create a session, chat, approve tools, and switch models — with no user-visible difference between runtimes.

Kiro exposes the Agent Client Protocol (ACP) via kiro-cli acp — standard JSON-RPC 2.0 over stdio, the same editor-agnostic protocol used by Zed. This mirrors the transport strategy already used for codex app-server.

Clay session (vendor=kiro)
  -> YOKE Kiro Adapter   (lib/yoke/adapters/kiro.js)
  -> KiroAcpServer       (lib/yoke/kiro-acp-server.js)  spawn `kiro-cli acp`
  -> kiro-cli binary     (JSON-RPC 2.0 over stdio)

What's included

New files

• lib/yoke/kiro-acp-server.js — child-process JSON-RPC transport
• lib/yoke/adapters/kiro.js — YOKE adapter (dynamic model catalog, session lifecycle, session/update event flattening, permission routing, resume, abort)
• lib/kiro-defaults.js — single source of truth for Kiro defaults
• lib/public/kiro-avatar.svg — branded avatar
• docs/guides/KIRO-INTEGRATION.md + EN/KO summaries

Wiring (mirrors every codex touch-point)

• yoke/index.js — factory switch, auth (kiro-cli whoami), install detection, createAdapters
• sdk-bridge.js — detectInstalledVendors, login command, KIRO adapterOptions, neutral interrupt message
• sdk-message-processor.js, project-notifications.js — auth titles
• project-sessions.js — GUI-only session mode for kiro
• client UI: vendor toggle, new-session buttons (install-gated), effort levels, avatar/name maps

Key design decisions

• Dynamic model catalog (like Claude, unlike Codex's hardcoded list): init() runs kiro-cli chat --list-models --format json, filtering out [Internal]/[Deprecated] entries; default is the auto router.
• Permission name recovery: session/request_permission carries only { toolCallId, title }, so the adapter caches kind + rawInput from the preceding tool_call notification to pass a canonical tool name (Bash, Edit, ...) to canUseTool. Without this, Clay's permission whitelist matching would break.
• Split tool output (fix commit): Kiro emits tool output across two tool_call_update events (interim content, then status: completed with the output in rawOutput). The adapter accumulates content per toolCallId and falls back to rawOutput so tool_result is never empty.
• GUI-only sessions, same as Codex; per-project adapter scoped to a cwd/slug.

Testing

Verified end-to-end against the live kiro-cli 2.7.0 binary, and on a real device (iPhone via Tailscale):

• Init discovers 15 curated models; default auto
• Text streams in real time; result emitted with usage
• Model switching works (session/set_model; confirmed opus-4.8 / haiku-4.5 on device)
• Tool approval routes through canUseTool with canonical name Bash + {command}; approve and deny paths verified
• tool_result shows real command output (echo hello-kiro-42)
• Abort interrupts the turn cleanly
• Registers alongside claude/codex in the daemon adapter path

Commits

• feat(yoke): add Kiro CLI adapter via Agent Client Protocol
• fix(yoke): populate Kiro tool_result content from split ACP updates

[amazon-q-developer]

This PR successfully integrates Kiro CLI as a first-class agent runtime via the Agent Client Protocol (ACP). The implementation follows good patterns mirroring existing Claude and Codex adapters, includes comprehensive error handling, and maintains security best practices through tool whitelisting and permission controls.

Key Changes:

• New KiroAcpServer transport layer for JSON-RPC 2.0 communication
• KiroAdapter implementing the YOKE interface with dynamic model catalog, session lifecycle management, and permission routing
• Integration wiring throughout the codebase (auth, vendor detection, UI controls)
• Comprehensive documentation

Findings:

• 1 logic error identified in binary path resolution

The changes are well-tested according to the PR description, with verification against kiro-cli 2.7.0 including model discovery, streaming, tool approval, and session management.

---

You can now have the agent implement changes and create commits directly on your pull request's source branch. Simply comment with /q followed by your request in natural language to ask the agent to make changes.

[amazon-q-developer]

🛑 Logic Error: The where command on Windows receives binName as argument but which on Unix receives hardcoded "kiro-cli" string. This inconsistency causes the Windows binary name (possibly "kiro-cli.exe") to be ignored on Unix systems, preventing discovery of the correct binary when binName is set to a different value than "kiro-cli".

Suggested change

	: execFileSync("which", ["kiro-cli"], { timeout: 3000, encoding: "utf8", stdio: ["pipe", "pipe", "pipe"] });
	: execFileSync("which", [binName], { timeout: 3000, encoding: "utf8", stdio: ["pipe", "pipe", "pipe"] });

[hmkim]

Superseded by the upstream PR chadbyte#385 (rebased on latest main). Closing to avoid confusion — the work continues there.