Fix typo, gitignore DS_Store and .op, remove accidentally tracked files

- Fix "opevators" → "operators"
- Add .DS_Store and .op/ to .gitignore
- Remove accidentally committed macOS metadata and 1Password plugin files

Assisted-by: Claude Sonnet 4.6 <noreply@anthropic.com>
Signed-off-by: Sam Barker <sam@quadrocket.co.uk>

Author: SamBarker

.DS_Store

@@ -7,4 +7,6 @@ vendor
 *.iml
 */bootstrap/
 _config-overrides.yml
-.ruby-version
+.ruby-version
+.DS_Store
+.op/

.gitignore

@@ -9,7 +9,7 @@ categories: benchmarking performance
 
 Every good benchmarking story starts with a hunch. Mine was that Kroxylicious is cheap to run — I'd stake my career on it, in fact — but it turns out that "trust me, I wrote it" is not a widely accepted unit of measurement. People want proof. Sensibly.
 
-There's a practical question underneath the hunch too. The most common thing opevators ask us is some variation of: "How many cores does the proxy need?" Which is really just "is this thing going to slow down my Kafka?" in a polite engineering hat. We'd been giving the classic answer: "it depends on your workload and traffic patterns, so you'll need to test in your environment." Which is true. And also deeply unsatisfying for everyone involved, including us.
+There's a practical question underneath the hunch too. The most common thing operators ask us is some variation of: "How many cores does the proxy need?" Which is really just "is this thing going to slow down my Kafka?" in a polite engineering hat. We'd been giving the classic answer: "it depends on your workload and traffic patterns, so you'll need to test in your environment." Which is true. And also deeply unsatisfying for everyone involved, including us.
 
 So we stopped saying "it depends", and got off the fence: we built something you can run **yourselves** on your own infrastructure with your own workload, and measured it. Here are some representative numbers from ours.