Add git.mleku.dev remote push to release process (v0.40.1)

- Update release command to push to git.mleku.dev using gitmlekudev SSH key
- Add release process documentation to README.md

Files modified:
- .claude/commands/release.md: Add GIT_SSH_COMMAND push to git.mleku.dev
- README.md: Document release process and SSH key configuration
- pkg/version/version: Bump to v0.40.1

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>

.claude/commands/release.md

@@ -42,10 +42,11 @@ If no argument provided, default to `patch`.
 
 9. **Create a git tag** with the new version (e.g., `v0.36.0`)
 
-10. **Push to remotes** (origin and gitea) with tags:
+10. **Push to remotes** (origin, gitea, and git.mleku.dev) with tags:
     ```
     git push origin main --tags
     git push gitea main --tags
+    GIT_SSH_COMMAND="ssh -i ~/.ssh/gitmlekudev" git push ssh://mleku@git.mleku.dev:2222/mleku/next.orly.dev.git main --tags
     ```
 
 11. **Deploy to VPS** by running:

README.md

@@ -618,3 +618,18 @@ pt, err := hex.Dec(string(pTag.ValueHex()))
 // WRONG: Value() may return binary bytes, not hex
 pt, err := hex.Dec(string(pTag.Value()))  // Will fail for binary-encoded tags!
 ```
+
+### Release Process
+
+The `/release` command pushes to multiple git remotes. To push to git.mleku.dev with the dedicated SSH key, ensure the `gitmlekudev` key is configured:
+
+```bash
+# SSH key should be at ~/.ssh/gitmlekudev
+# The release command uses GIT_SSH_COMMAND to specify this key:
+GIT_SSH_COMMAND="ssh -i ~/.ssh/gitmlekudev" git push ssh://mleku@git.mleku.dev:2222/mleku/next.orly.dev.git main --tags
+```
+
+Remotes pushed during release:
+- `origin` - Primary remote
+- `gitea` - Gitea mirror
+- `git.mleku.dev` - Using `gitmlekudev` SSH key

pkg/version/version

@@ -1 +1 @@
-v0.40.0
+v0.40.1