chore: add Claude settings, ship/release commands, reviewer agents, changelog

- /ship now commits and pushes with a branch guard and no longer tags;
  /release tags vMAJOR.MINOR.PATCH and confirms before pushing
- operator-reviewer and go-operator-reviewer agents from egress-proxies-operator
- committed permission allowlist; settings.local.json ignored

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

.claude/commands/release.md

@@ -0,0 +1,18 @@
+---
+description: Tag a release and push it after confirmation
+---
+
+Commit all staged and unstaged changes into git, assign the next release tag, then
+ask for confirmation before pushing.
+
+Before committing, check the current branch (`git branch --show-current`). Releases
+are cut from `main`; on any other branch, stop and ask.
+
+Tags are semver `vMAJOR.MINOR.PATCH` (see CLAUDE.md, "Git Commits, Pushes and Tags").
+Find the latest with `git tag --list 'v*' --sort=-v:refname | head -1`; if there is
+none, start at `v0.1.0`. The old `0.01`–`0.07` tags are not part of the sequence.
+Default to a patch bump for fixes and a minor bump for features; state the tag you
+picked and why when asking for confirmation.
+
+Pushing the tag triggers `.gitea/workflows/build.yaml`, which builds and pushes the
+image and moves `:latest`.

.claude/commands/ship.md

@@ -1 +1,22 @@
-Commit all staged and unstaged changes into git, assign the next tag in sequence, then ask for confirmation before pushing.
+---
+description: Commit current changes and push to the remote
+---
+
+Commit the current working-tree changes and push them.
+
+1. Run `git status` and `git diff` to see what will be committed.
+2. Check the current branch (`git branch --show-current`). If it's `main` and the
+   change looks feature-sized (not one of CLAUDE.md's "commit straight to main"
+   exceptions: small fixes, typos/formatting, or the user explicitly said `main`),
+   stop and tell the user to branch first — don't push a feature to `main`.
+3. Stage the changed files (`git add -A` is fine here).
+4. Create a commit with a short message describing the changes (infer it from the
+   diff), including a `Co-Authored-By:` trailer for Claude.
+   Pass the message via a HEREDOC.
+5. Push with `git push`. If the current branch has no upstream, use `git push -u origin HEAD`.
+6. If the branch isn't `main`, remind the user to open an MR with `tea pr create`
+   (see CLAUDE.md's Branching & Merge Requests section) rather than opening one
+   automatically.
+7. Report the commit hash and push result.
+
+If there are no changes, stop and say so — do not create an empty commit.