CLAUDE.md: the wrapper-chart one-time step is done, not still pending

Stale since this repo's actual first release (v0.1.1, 2026-10-01) already
did it -- Ryuvia/charts/terdut-operator already exists and already pins
v0.1.1. Caught while about to repeat the same wrong assumption for this
release.

CLAUDE.md

@@ -36,11 +36,9 @@ charts --force` after `config/` changes, then re-review — `--force` does not t
 importantly the optional `terdutServer` block, DESIGN.md §10). It installs the operator +
 CRDs + RBAC, and optionally one `TerdutServer` CR (`terdutServer.enabled`, off by default).
 
-**One manual step the release skill's own automation does not cover**: `release-preflight`
+That one-time manual step — hand-creating the initial `terdut-operator/` wrapper entry
-expects an existing `terdut-operator/` entry under `Ryuvia/charts` to bump on release
+under `Ryuvia/charts`, since `chart-bump` only ever bumps an existing one — is done. It
-(steps 8-10 of the skill). There is no such entry yet — this repo's first-ever release
+happened during this repo's actual first release (v0.1.1, 2026-10-01; v0.1.0 published but
-can publish its own image and chart (the `test`/`image`/`chart`/`scan-image` jobs), but
+never deployed anywhere, after its own `scan-image` found a CVE in the grpc version it had
-the wrapper-chart bump and PR will fail until someone creates that initial wrapper entry
+just bumped to). Every release since bumps that wrapper entry like any other onboarded
-in `Ryuvia/charts` by hand, the same one-time step every other onboarded repo already had
+repo's.
-done for it before its own first release. That's a deliberate decision to deploy this
-operator for real, not something to do as a side effect of finishing this stage.