Walkthrough: Using custom commands to enforce a strict style guide.

Custom commands? Another feature to add more complexity and break the pipeline. Because what we really need is another layer of YAML to manage.

You're telling me to wrap my entire team's writing process in a brittle bot that will choke the second someone uses an Oxford comma it wasn't trained on. Here's what that "enforcement" looks like in practice.

```yaml
# contentbot-config.yaml
commands:
- name: "enforce_style"
trigger: "apply_style_guide"
action:
type: "rewrite"
parameters:
style: "apache"
rules:
- "no_passive_voice"
- "max_sentence_length: 25"
- "heading_format: title_case"
failure: "reject"
```

So now my pull request fails because ContentBot decided a sentence was 26 words. Great. Instead of a human review, we get a cryptic error from a black box. I'll stick with a linting script in the CI that we can actually debug. At least when it breaks, I can `tail -f` a log and fix it.