Evidence wanted: kilo_code adapter (vendor-docs) #175

The kilo_code row in src/agentseam/data/matrix.json (added in #173) rests on vendor documentation only (basis: vendor-docs). Nobody has tested it against a running Kilo Code. This issue asks for evidence that confirms the row or proves it wrong.

What the row claims

How to test it

1. Install the CLI with npm install -g @kilocode/cli, or the VS Code extension kilocode.kilo-code. Record kilo --version, or the extension version.
2. Command hooks. Check whether this release accepts a command hook. Add a hook-like key to kilo.jsonc and start kilo.
   • The row holds if the key is rejected, or if the command never runs.
   • The row is disproved if any documented key makes Kilo run an external command with a JSON payload before a tool call.
3. In-process plugin. Put this file at .kilo/plugin/block.ts:

   import type { Plugin } from "@kilocode/plugin"
   const block: Plugin = async () => ({ "tool.execute.before": async (input) => { if (input.tool === "bash") throw new Error("blocked") } })
   export default { id: "block", server: block }

   Ask the agent to run echo hi.
   • The row's description of the surface holds if the bash call is refused with "blocked".
   • If the call runs, the plugin surface is not what the row says.
4. Instructions. Put a distinctive line in AGENTS.md and ask the agent to repeat its instructions. The line should come back.

How to submit evidence

Comment here, or use the evidence-report issue form, with:

• the Kilo client version (CLI or extension) and your OS;
• a transcript or screen recording of steps 2–4;
• the src/agentseam/data/vendor-releases.json entry tools/watch_versions.py should track, if @kilocode/cli is the wrong feed.

A row moves from vendor-docs to tested or witnessed only through evidence like this, never by editing its basis by hand.

If a claim is wrong, a fix PR is welcome. It should change the row's verified record and notes, and link this issue.