kiro: Add version 0.10.32

[zeldrisho]

Closes #17316

Relates to #17296

• I have read the Contributing Guide

Summary by CodeRabbit

• New Features
  • Kiro is now available via the Scoop package manager for Windows (x64) as an installable package (initial release v0.10.32).
  • Installer provides a desktop/Start shortcut and command shim, and supports automatic update checks for future releases.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 8e8751c and d73c619.

📒 Files selected for processing (1)

• bucket/kiro.json

🚧 Files skipped from review as they are similar to previous changes (1)

• bucket/kiro.json

---

Walkthrough

Adds a new Scoop manifest bucket/kiro.json for Kiro (Windows x64) version 0.10.32, including metadata, download URL and SHA256, bin and shortcut mappings, a checkver JSONPath, and autoupdate URL templating for 64-bit builds.

Changes

Cohort / File(s)	Summary
Kiro Scoop Manifest bucket/kiro.json	Added new Scoop manifest with package metadata (version 0.10.32), download URL and SHA256 for win32-x64, bin and shortcuts entries, checkver pointing to metadata-win32-x64-user-stable.json ($.currentRelease), and autoupdate URL template for 64-bit builds.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Poem

🐰✨ I added a manifest small and neat,
Kiro's installer ready, checksum complete.
Version pinned, updates set to play,
Windows x64 will dance today. 🥕🚀

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 inconclusive)

Check name	Status	Explanation	Resolution
Description check	❓ Inconclusive	The PR description is missing the conventional PR title format specified in the template. The actual PR title is 'kiro: Add version 0.10.32', which uses the correct manifest format, but the checkbox for 'Use conventional PR title' is unchecked.	Update the description to check the conventional PR title checkbox and ensure full compliance with template requirements.

✅ Passed checks (4 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title directly and specifically summarizes the main change: adding a new kiro package manifest for version 0.10.32.
Linked Issues check	✅ Passed	The PR successfully implements all requirements from issue #17316: adds kiro package v0.10.32 with correct description, homepage, download URL, architecture, and all expected manifest structure.
Out of Scope Changes check	✅ Passed	All changes are within scope; the PR only adds bucket/kiro.json manifest file as required by issue #17316 with no unrelated modifications.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment

---

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 and usage tips.}

[github-actions]

All changes look good.

Wait for review from human collaborators.

kiro

• Lint
• Description
• License
• Hashes
• Checkver
• Autoupdate

Check the full log for details.

[coderabbitai]

🧹 Nitpick comments (1)

bucket/kiro.json (1)

3-3: Consider a more specific project description for discoverability.

Current text is generic. A description like “Agentic IDE by AWS” is clearer and aligns better with package intent.

Based on learnings: In ScoopInstaller/Extras manifests, the description field may describe the project’s overall capabilities (including cross‑platform support) and should communicate the full scope of the software.

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@bucket/kiro.json` at line 3, The description field in kiro.json is too
generic; update the "description" value (currently "AI IDE for prototype to
production") to a more specific, discoverable phrase that summarizes the product
and scope (e.g., include agentic/IDE, vendor or platform, and cross-platform
capability). Edit the "description" property in kiro.json to something like
"Agentic IDE for building and deploying applications (cross‑platform,
AWS‑integrated)" or another concise, specific description that reflects the
package intent.

🤖 Prompt for all review comments with AI agents

Verify each finding against the current code and only fix it if needed.

Nitpick comments:
In `@bucket/kiro.json`:
- Line 3: The description field in kiro.json is too generic; update the
"description" value (currently "AI IDE for prototype to production") to a more
specific, discoverable phrase that summarizes the product and scope (e.g.,
include agentic/IDE, vendor or platform, and cross-platform capability). Edit
the "description" property in kiro.json to something like "Agentic IDE for
building and deploying applications (cross‑platform, AWS‑integrated)" or another
concise, specific description that reflects the package intent.

---

ℹ️ Review info

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 13fc8e2 and 8e8751c.

📒 Files selected for processing (1)

• bucket/kiro.json

[z-Fng]

/verify

[github-actions]

All changes look good.

Wait for review from human collaborators.

kiro

• Lint
• Description
• License
• Hashes
• Checkver
• Autoupdate

Check the full log for details.

[z-Fng]

Thanks for your contribution!