Add Kiro CLI agent support

[hengliu0919]

Description

Adds first-class Kiro CLI support across Warp's CLI-agent surfaces:

• Detects kiro-cli and its launcher aliases as Kiro sessions.
• Adds Kiro branding, telemetry, and Kiro skill-provider integration.
• Enables the CLI-agent footer and Rich Input submission path for Kiro.
• Adds focused unit coverage and real-display integration screenshots for Kiro Rich Input and vertical tabs.

This draft also adds the required product and technical specifications:

• specs/GH9066/product.md
• specs/GH9066/tech.md

Please review the specifications before the implementation. They update the scope from closed spec PR #12387 and leave unsupported plugin status integration out of this change.

Linked Issue

Closes #9066

• The linked issue is labeled ready-to-spec or ready-to-implement.
• Where appropriate, screenshots or a short video of the implementation are included below (especially for user-visible or UI changes).

Testing

• ./script/format --check
• cargo clippy --workspace --exclude warp_completer --all-targets --tests -- -D warnings
• cargo clippy -p warp --all-targets --tests -- -D warnings
• cargo clippy -p warp_completer --all-targets --tests -- -D warnings
• cargo +stable test -p warp test_kiro_variant_properties --lib
• cargo +stable test -p warp cli_agent_rich_input_hint_text_mentions_active_cli_agent --lib
• DISPLAY=:99 LIBCLANG_PATH=/usr/lib64 WARPUI_USE_REAL_DISPLAY_IN_INTEGRATION_TESTS=1 cargo +stable run -p integration --bin integration -- test_kiro_cli_rich_input_shows_kiro_branding

The real-display e2e test passed and verified the active Kiro session, open Rich Input state, configured placeholder, Kiro icon, Enter prompt for Kiro... UI, and rendered vertical-tabs panel.

• I have manually tested my changes locally with ./script/run

Screenshots / Videos

Rich Input

Vertical Tabs

Agent Mode

• Warp Agent Mode - This PR was created via Warp's AI Agent Mode

CHANGELOG-IMPROVEMENT: Add Kiro CLI detection, branding, skill integration, and Rich Input support.

[cla-bot]

Thank you for your pull request and welcome to our community. We require contributors to sign our Contributor License Agreement, and we don't seem to have the users @hengliu0919 on file. In order for us to review and merge your code, each contributor must visit https://cla.warp.dev to read and agree to our CLA. Once you have done so, please comment @cla-bot check to trigger another check.

[cla-bot]

Thank you for your pull request and welcome to our community. We require contributors to sign our Contributor License Agreement, and we don't seem to have the users @hengliu0919 on file. In order for us to review and merge your code, each contributor must visit https://cla.warp.dev to read and agree to our CLA. Once you have done so, please comment @cla-bot check to trigger another check.

[hengliu0919]

@cla-bot check

[cla-bot]

The cla-bot has been summoned, and re-checked this pull request!

[oz-for-oss]

@hengliu0919

Every PR must be linked to a same-repo issue before Oz can review it.

This PR is linked to #9066, but no linked issue is marked ready-to-implement yet. Only repository maintainers apply that label, so please wait for a maintainer to mark the issue. Once it is marked, push a new commit or comment /oz-review to re-trigger review.

See the contribution guidelines for the full readiness model.

Powered by Oz

[oz-for-oss]

@hengliu0919

Every PR must be linked to a same-repo issue before Oz can review it.

This PR is linked to #9066, but no linked issue is marked ready-to-implement yet. Only repository maintainers apply that label, so please wait for a maintainer to mark the issue. Once it is marked, push a new commit or comment /oz-review to re-trigger review.

See the contribution guidelines for the full readiness model.

Powered by Oz