No documented upgrade path for OpenClaw version on button-deployed Moltworker instances

The Dockerfile pins OpenClaw to a specific version (openclaw@2026.2.3 currently). In-place npm install -g updates files on disk but these are overwritten on container restart since the version is baked into the container image.

For users who deployed via the "Deploy to Cloudflare" button, there is no documented way to upgrade the OpenClaw version short of forking the repo and editing the Dockerfile manually.
Request: Either bump the pinned version regularly as part of Moltworker releases, support a OPENCLAW_VERSION environment variable that overrides the baked version at container startup, or document the fork-and-edit Dockerfile path explicitly.

This is a legitimate gap that affects every button-deployed user who wants to stay current on security patches. Given that OpenClaw had 90+ security fixes across three releases in the past week alone, the inability to upgrade easily is a real security concern worth raising publicly. Other users are almost certainly hitting the same wall.