agent-context: bump Kiro manifest version automatically on sync

[ethanpalm]

Summary

The Kiro power manifest has stayed at 1.0.0 since #6916, even though about 15 skill updates changed its content. The README asked for a manual bump on every Kiro-affecting change, and nothing enforced it.

Changes

• scripts/lib.mjs: during sync, compare the generated skill, MCP config, and manifest (ignoring version) against the target repo. If they differ, bump the target's patch version. A higher version in targets/kiro.json wins, for deliberate minor or major releases.
• targets/kiro.json: set 1.0.1 so existing installs pick up everything merged since 1.0.0.
• README.md: describe the automatic bump. Also corrects "no package dependencies" (the project uses ajv).
• New test covering: first sync, no-op resync, a content change bumping the version, and the idempotent resync after it.

Why sync time, not a CI check

A CI check would fail every docs-bot skill PR that forgot to bump, and open PRs would conflict on the version line. The sync workflow always rebuilds its branch from the target's main, so it bumps exactly once per merged sync PR.

Validation

• npm test (6/6), npm run check pass.
• Dry-run sync-target.mjs kiro against a fresh clone of kiro-power (current as of today's sync merge): no content diff, version unchanged, as expected.

Unverified

I haven't confirmed how Kiro itself uses the manifest version for updates. This relies on the README's existing claim that it does.

🤖 Generated with Claude Code

---

Note

Medium Risk
Changes how Kiro release versions are computed during sync, which affects update detection for installs; logic is covered by tests but depends on Kiro honoring manifest version as documented.

Overview
Kiro’s plugin.json version no longer has to be bumped by hand on every skill or MCP change. Sync now decides the manifest version when writing into the target repo instead of copying the built artifact verbatim.

On sync, the tool compares a snapshot of the generated skill tree, MCP config, and manifest fields (excluding version) against what’s already in the destination. If nothing changed, the version stays put; if released content differs, it increments the patch from the destination’s current version. A higher pluginManifest.version in targets/kiro.json still wins for intentional minor or major releases. The written manifest is validated with ajv before save.

targets/kiro.json is set to 1.0.1 so the next sync signals updates for everything since 1.0.0. The README now documents this behavior and notes the ajv dependency (replacing the incorrect “no package dependencies” line). A new test covers first sync, idempotent re-sync, patch bump after content drift, and stability after that.

^{Reviewed by Cursor Bugbot for commit ca9f9a9. Bugbot is set up for automated code reviews on this repo. Configure here.}

[mintlify]

Preview deployment for your docs. Learn more about Mintlify Previews.

Project	Status	Preview	Updated
mintlify	🟢 Ready	View Preview	Sep 23, 2026, 5:59 PM