feat!: 1.0.0 — so a caret range can finally do its job

[catomean]

Eleven repos depend on this package and sit on five different versions, from 0.6.2 to 0.15.0, while the registry serves 0.16.0 to none of them.

That is not neglect, and the automation is not broken.

The cause

A caret range on a pre-1.0 version does not cross a minor. ^0.13.0 means at least 0.13.0 and below 0.14.0, because semver treats a 0.x minor as a breaking change.

^0.6.2   → satisfies 0.16.0?  false      ^1.6.2   → satisfies 1.16.0?  true
^0.13.0  → satisfies 0.16.0?  false      ^1.13.0  → satisfies 1.16.0?  true
^0.15.0  → satisfies 0.16.0?  false      ^1.15.0  → satisfies 1.16.0?  true

Dependabot runs weekly in all ten consuming repos. It correctly classifies each 0.x minor as breaking, and correctly routes it to its own PR for a human to read — the right policy for a breaking change, and the wrong outcome for a package whose minors have been additive in practice. The version numbering defeated the process.

Repo	Range	Resolves to
fleetcrown · aoz-housing	^0.6.2	0.6.x
surf-your-life	^0.8.0	0.8.x
revamp-info	^0.12.0	0.12.x
orangecat · evig · truthseeker	^0.13.0	0.13.x
botsmann · hirnli · vitareba	^0.15.0	0.15.x

What this changes

1.0.0 ends it by construction. Afterwards ^1.x admits every later minor, Dependabot groups them with the routine bumps, and CI is the gate that makes taking them safe rather than brave.

No code changes. The surface is byte-identical to 0.16.0. This release exists to change what a range means, and bundling behaviour into it would make the one upgrade everybody has to eyeball harder to eyeball.

The cost, stated plainly

The upgrade to 1.0.0 is a real one for old consumers: coming from 0.6.x crosses ten minors of a package that was permitted to break at each. Every repo runs its own suite on the way. That cost is paid once, and it is the last time.

Also

The README gains a Versioning section stating the promise from here — minors additive, majors carry a migration note — and the rule that keeps drift uninteresting:

Model ids rot on a timescale of weeks. Anything on that clock does not belong in a release, because shipping it means a version bump per rot and one upgrade per consumer to deliver a fact that was true yesterday.

So the package ships the logic and keeps perishable data in the environment and in live catalogue fetches. That is what makes being a version behind uninteresting, which is a better property than being always current.

Verify green locally: lint, typecheck, build, 162 tests.

🤖 Generated with Claude Code

https://claude.ai/code/session_01CAfKwM1oUSA9tU9fgdhfdf