[777genius]

Why

Kiro project installation needs to configure the selected repository while preserving the detected user profile, foreign settings and other project state.

Changes

Add the explicit .kiro project lane using the existing exact JSONC/skill transaction engine. Validate scoped binding/receipt/path authority and managed-stdio package/data/cwd bindings, including read-only active-projection consistency. Preserve user behavior and report file configuration as prepared/installed; workspace trust, custom-agent selection and ACP/runtime discovery are not synthesized.

Research and validation

The client plan completed two independent review/fix rounds before code. Official pinned Kiro CLI 2.33.1 archive integrity and the complete distribution were verified; eight genuine version/help probes succeeded in a fresh networkless profile. This does not qualify project discovery or MCP runtime.

Author tests pass: client/provider scoped receipt, rollback and stdio contracts, public SDK lifecycle, compatibility goldens, and a production public-CLI Git/ZIP journey with project/user isolation, stable reconciliation, repair, update, cold transfer and exact removal. The public test name is included by the cross-platform project-contract selector. Changed-code and whole-file size/architecture lint report zero issues.

Two independent implementation reviews are now running against production checkpoint 9eeadc1a; findings will be fixed in this same PR. This checkpoint is published immediately for parallel CI.

Stack

Client-specific draft for #472. The temporary base contains the already independently reviewed client composition because this leaf uses that assembled checkpoint; it has no separate feature PR. Retarget to the project feature after its parent client PRs land, and merge only there after review/fixes and applicable CI. No main merge or release.

Delivered in #499

Delivered by #499, merged into main as 3b93148c. The integrated source 3386c72a91e7e9b3574f12ce0613b399227a1ada passed all 74 check runs and 24 PR workflows; the actual merge tree is identical to that validated source.

This PR's reviewed head f1d374b4900dcfd7ea148db4eb27f9572761983f is preserved by ancestry in the integrated source and the main merge. Closing as incorporated; no separate merge into the earlier stacked base is needed.

[coderabbitai]

Important

Draft PR not reviewed

Draft PRs are not automatically reviewed by default.

• Trigger a manual review

To automatically review draft PRs, update your CodeRabbit configuration:

reviews:
  auto_review:
    drafts: true

• Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}