v0.10.7 — why this one, answered on npm too

The comparison against the tools that came before Kiro-Kit was only on the repository README. Someone deciding on npm never sees that page, so the package page now carries it too: what starter templates, settings managers, config generators, and steering collections each do, where each stops, and where Kiro-Kit is the wrong choice.

First release cut by CI

This version was published by the workflow, not by a person. Authentication is an OIDC identity GitHub mints for the publish job and npm accepts as a trusted publisher — there is no token in the repository to leak, and none to rotate when it expires.

The release path is now: bump the version, merge, push a tag. The workflow refuses to publish if the tag disagrees with package.json, and skips instead of failing if the version is already on npm.

Published with provenance — the package is cryptographically linked to the commit and workflow that built it.

npx kiro-kit@0.10.7 init