matrix: add opencode and kilo_code rows (A1, vendor-docs, unadapted)

[jothimani-rajendran]

What this changes

Batch A1 of org-plan plan/one-oh-gaps.md at 5be6e1d. It adds opencode and kilo_code to the matrix as unadapted rows. Neither agent gets a vendor config entry, because neither documents a command-hook surface. Each agent's only interception surface is an in-process JS/TS plugin API (tool.execute.before). No family in data/vendors/ can speak that dialect, and the org keeps in-process plugin APIs on watch. So both rows say exactly that. Neither row invents a surface.

Derived by agentseam tier-table (tiers are not written by hand):

Agent	Tier	Grade	Fail mode	Basis	Recorded
kilo_code	unadapted	none	n/a	vendor-docs	2026-10-11
opencode	unadapted	none	n/a	vendor-docs	2026-10-11

unadapted, not none: both agents do have a hook surface. The gap is that we have no adapter for it, which is a claim about us (ARCHITECTURE.md).

Evidence (all read 2026-10-11)

opencode. Versions: opencode-ai 1.18.35 (v1) and @opencode/cli 2.0.26 (v2), the npm latest of each.

• v1 plugin API: https://opencode.ai/docs/plugins/ documents a tool.execute.before hook that can throw to block. Plugins load from .opencode/plugins/.
• v2 plugin API: https://opencode.ai/v2/docs/plugins and https://opencode.ai/v2/docs/build/plugins document ctx.tool.hook("execute.before").
• Config: https://opencode.ai/v2/docs/config, and the schema at https://opencode.ai/config.json. The top-level Config is additionalProperties: false and has no hook key.
• Instructions: AGENTS.md, per the v2 config page.

kilo_code. Version: @kilocode/cli 7.8.8, the npm latest. The docs page says it applies to the current VS Code extension and the CLI.

• Plugin API: https://kilo.ai/docs/automate/extending/plugins documents the same in-process plugin API, "identical to OpenCode". Plugins load from .kilo/plugin/.
• Migration guide: https://kilo.ai/articles/claude-code-to-kilo-code-migration-guide maps PreToolUse to tool.execute.before.
• Config schema: https://app.kilo.ai/config.json has no hook key.
• Upstream request: Feature request: PreToolUse hooks for tool call interception Kilo-Org/kilocode#7859 asked for command hooks. It was closed in a bulk close of legacy-extension issues, with no statement about command hooks.
• Instructions: AGENTS.md, per https://kilo.ai/docs/customize/custom-instructions.

Files

• data/matrix.json: two rows, each with a verified record (version, date, method) and a note. Each note links its evidence-wanted issue.
• data/vendor-releases.json: npm sources @opencode/cli and @kilocode/cli for tools/watch_versions.py. Each note gives the date and version it resolved to.
• instructions.py: both agents read the shared AGENTS.md. This is required by test_every_matrix_agent_is_reachable_by_instructions.
• packaging-limits.json and permissions-unrecorded.json: an honest unrecorded reason for each agent. This is required by the every_matrix_agent_is_accounted_for tests.
• docs/figures and docs/assets: the generator's 16-agent layout pin is moved to 18. The figures are regenerated with make_*.py, and the social preview with gen_brand_assets.py.
• tests/test_instructions.py: the agent count is pinned at 18. Files written stays at 9.

Evidence-wanted issues

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

Claim check

• No capability claim is widened without a mechanism behind it (both rows have events: {} and grade none)
• Any new/changed MATRIX row carries a verified record (version, date, method)
• Primary sources are linked above. There are no payload shapes, because there is no command hook.

Checks

• pytest -q passes locally: 1896 passed, 4 skipped
• ruff check . and ruff format --check . pass
• The runtime path is still stdlib-only (tests/check_stdlib_only.py OK)
• Commits are signed off

Notes for the reviewer

• README lags. README.md still says "16 agents", "16 agents reached with 9 files written" and "8 of them read AGENTS.md". The real numbers are now 18, 9 and 10. There is no README generator, and README is not hand-edited per OPERATING.md, so it is left for the orchestrator or owner to decide.
• Missing label. evidence wanted does not exist in this repo, so it was not created. help wanted exists, and both issues carry it.

🤖 Generated with Claude Code