🔖 chore: number the standard-decorator line 0.2.0, not 2.0.0

Nothing has been published to npm, so 2.0.0 claimed a 1.0.0 predecessor that no
one could install. Staying on 0.x states what is true — the API may still move —
and under semver a breaking change is then a minor bump, which is precisely the
relationship between the two lines: 0.1.x keeps legacy experimentalDecorators,
0.2.x moves to TC39 standard decorators.

The break itself is unchanged and still documented; only the number and the
references to the other line moved.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01SAcqrz3FcadkYr3xG32CjK

CHANGELOG.md

@@ -5,7 +5,11 @@ All notable changes to this project are documented in this file.
 The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.1.0/),
 and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
 
-## [2.0.0] - 2026-08-04
+## [0.2.0] - 2026-08-04
+
+> The project stays on 0.x while nothing has been published: under semver that signals the
+> API may still move, which is honest for software with no real-world users. A breaking
+> change is therefore a minor bump, which is why this is 0.2.0 rather than 2.0.0.
 
 **Breaking.** Cereale moves to TC39 standard decorators, which is what makes validation rules
 type-checked against the fields they are attached to.
@@ -67,9 +71,9 @@ sync API — is unchanged.
 Standard decorators are transformed by `tsc` and by esbuild; **oxc does not implement them
 yet**. The library builds with `tsc` and consumers bundling with esbuild or Vite are fine, but
 the test runner (Vitest 4, which uses oxc) needs an esbuild transform plugin — see
-`vitest.config.ts`. Projects on an oxc-based toolchain should stay on 1.x for now.
+`vitest.config.ts`. Projects on an oxc-based toolchain should stay on 0.1.x for now.
 
-## [Unreleased] (released as 1.0.0)
+## [0.1.0] - 2026-08-05
 
 ### Added