fix: release the toolkit as 0.1.0 rather than 1.0.0

[ShocOne]

release-please succeeded for the first time and opened #47 — for 1.0.0.

Why it chose 1.0.0

Not a breaking change being detected. The history rewrite removed the only feat!: subject and BREAKING CHANGE: trailer, and main now carries neither (verified: both counts are 0).

It is the initial-release default. strategies/base.js:464:

if (this.initialVersion) {
    return Version.parse(this.initialVersion);
}
return Version.parse('1.0.0');

No tag exists, so release-please took that path rather than bumping the manifest's 0.0.0. Worth noting the bump rule itself would have given 0.1.0 — versioning-strategies/default.js returns a MinorVersionUpdate for features with no breaking change, and only diverts to a patch when bump-patch-for-minor-pre-major is set. So bump-minor-pre-major was the wrong lever; initial-version is the right one.

Why 0.1.0 is also the right number

1.0.0 claims an API somebody can depend on. The blueprint format is at version 3, having moved three times in this phase alone, and two roadmap phases are still outstanding. This matches the stated intent for the release.

Effect

Once merged, release-please updates #47 in place to chore(main): release 0.1.0 and tags v0.1.0 when that is merged.

🤖 Generated with Claude Code