Add Kiro to databricks aitools install

[antonyprasad-db]

Summary

Adds Kiro to the agent registry so databricks aitools install treats it like any other skills-only agent. Follows the same shape as Goose (#6214), Gemini CLI (#6204) and Pi (#6199).

Why

Kiro reads agent skills from ~/.kiro/skills (user-level) and <workspace>/.kiro/skills (workspace-level), each skill a directory containing SKILL.md — exactly the layout this repo already emits. Today Kiro users have to fall back to databricks aitools install --path ~/.kiro/skills, which works but records no state, so aitools update and aitools uninstall never see those skills and aitools list reports every one of them as not installed.

Verification

Tested on macOS with Kiro 1.0.182.

Kiro's loader (NodeProgressiveContextSource) rejects a skill when frontmatter is missing, when name or description is empty, when name is outside 1–64 characters, when description exceeds 1024, or when name does not equal the directory name. Everything this repo emits satisfies that.

With 29 stable skills installed into ~/.kiro/skills, Kiro accepted all 29. The only rejections in that directory were two deliberately malformed probe skills added to confirm the loader was really scanning, plus two unrelated pre-existing skills whose frontmatter name disagrees with their directory:

skill.frontmatter.missing   zz-probe-no-frontmatter      (deliberate probe)
skill.fields.missing        zz-probe-no-description      (deliberate probe)
skill.name.mismatch         analyze-mlflow-trace         (pre-existing, unrelated)
skill.name.mismatch         analyze-mlflow-chat-session  (pre-existing, unrelated)

Worth knowing for anyone testing this: Kiro resolves skills lazily when a chat session starts, not when the IDE launches. Installing and then looking at an already-open Kiro shows nothing until a new session begins.

Notes on the registry entry

• SkillsSubdir is left empty because Kiro's directory is literally skills, so the default applies.
• SupportsProjectScope: true — Kiro's own picker text documents both scopes.
• Binary: "kiro" is set, but Kiro is IDE-first so the binary is frequently absent from PATH. Detection then falls back to ConfigDir and reports files-only, which is the correct state for a skills-only agent (Plugin nil).

Telemetry

Also adds AitoolsAgentTypeKiro and the matching agentType case, so Kiro installs are not logged as TYPE_UNSPECIFIED and TestAgentTypeCoversRegistry stays green.

The Universe half is already merged, so nothing is owed on the proto side. That guard's failure message notes the enum lives in enum.proto (Universe) as well as aitools_install.go (CLI). KIRO = 10 was added to AitoolsAgentType.Type and merged to master on 2026-09-01 (universe 2524420), with Protobuf-Linter-Pr and OpenAPICompatibility-Pr both green — the latter being the machine check that the additive enum value is backward compatible. The two changes are order-independent: the enum addition is additive, and the CLI only emits "KIRO" once this PR merges. So this is the complete change and needs a review rather than any follow-up work.

Tests

go test ./cmd/aitools/... ./libs/aitools/... ./libs/telemetry/...

ok  github.com/databricks/cli/cmd/aitools              2.027s
ok  github.com/databricks/cli/libs/aitools/agents
ok  github.com/databricks/cli/libs/aitools/installer
ok  github.com/databricks/cli/libs/telemetry           4.959s
ok  github.com/databricks/cli/libs/telemetry/protos    0.826s

Test coverage added alongside the existing Goose cases: registry paths and project detection in libs/aitools/agents/registry_test.go, the skills-only assertion in agents_test.go, and the project-scope declaration in libs/aitools/installer/installer_test.go.

[github-actions]

Approval status: pending

/cmd/aitools/ - needs approval

Files: cmd/aitools/telemetry.go
Suggested: @lennartkats-db
Also eligible: @simonfaltum, @parthban-db, @fjakobs, @Shridhad, @atilafassina, @keugenek, @igrekun, @pkosiec, @MarioCadenas, @pffigueiredo, @ditadi, @calvarjorge, @renaudhartert-db, @hectorcast-db, @tanmay-db, @Divyansh-db, @tejaskochar-db, @mihaimitrea-db, @chrisst, @rauchy

/libs/aitools/ - needs approval

4 files changed
Suggested: @lennartkats-db
Also eligible: @simonfaltum, @parthban-db, @fjakobs, @Shridhad, @atilafassina, @keugenek, @igrekun, @pkosiec, @MarioCadenas, @pffigueiredo, @ditadi, @calvarjorge, @renaudhartert-db, @hectorcast-db, @tanmay-db, @Divyansh-db, @tejaskochar-db, @mihaimitrea-db, @chrisst, @rauchy

/libs/telemetry/ - needs approval

Files: libs/telemetry/protos/aitools_install.go
Suggested: @simonfaltum
Also eligible: @parthban-db, @renaudhartert-db, @hectorcast-db, @tanmay-db, @Divyansh-db, @tejaskochar-db, @mihaimitrea-db, @chrisst, @rauchy

_{Any maintainer (@andrewnester, @anton-107, @denik, @pietern, @shreyas-goenka, @simonfaltum, @renaudhartert-db, @janniklasrose, @lennartkats-db, @rugpanov, @rclarey) can approve all areas.
See OWNERS for ownership rules.}

[github-actions]

An authorized user can trigger integration tests manually by following the instructions below:

Trigger:
go/deco-tests-run/cli

Inputs:

• PR number: 6436
• Commit SHA: 136fa64efba03f151c8db2ca704db8dc826cd941

Checks will be approved automatically on success.

[antonyprasad-db]

Update on the one maintainer TODO in the description — the enum.proto side is now handled.

I've submitted that change internally: KIRO = 10 appended to AitoolsAgentType.Type after GOOSE = 9. It's in review with the log-schema owners. That path needs UI Platform review plus a Trust and Safety approver, which is why it's a separate change rather than something a maintainer here has to shepherd.

Two things I confirmed while doing it:

• AitoolsAgentType is referenced in exactly two places internally — the enum and the agents field declaration. There's no mapping table, allow-list, or consumer switch that also needs the new value, so that one-line addition is the whole server-side change.
• It's additive at the next free number, so the two PRs can land in either order. The CLI only emits "KIRO" once this one merges, and the enum value is harmless before that.

No changes to this PR as a result — just closing the loop so the proto side isn't left as an open question.

[antonyprasad-db]

Closing the loop on my previous comment: the enum.proto change is merged, not just submitted.

KIRO = 10 is on AitoolsAgentType.Type in master as of 2026-09-01. Protobuf-Linter-Pr and OpenAPICompatibility-Pr both passed, the latter being the machine confirmation that the additive enum value is backward compatible rather than just my assertion.

So both halves are done and this PR is the complete change. I've updated the description, which still carried the original "a maintainer will need to do" caveat and read as though something was outstanding.

Two things I can't do from outside the org, in case either is what's holding this up:

• I can't request a reviewer. @lennartkats-db — the approval bot suggests you for cmd/aitools/, matching the Goose (Add Goose to databricks aitools install #6214), Gemini (Add Gemini CLI to databricks aitools install #6204) and Pi (Add Pi to databricks aitools install #6199) entries this follows.
• I can't trigger the integration tests, which the bot notes need an authorized user.

Happy to rebase or split this if either would help.