docs: ban machine-writing tells in the writing standard

[strawgate]

Adds a short "Machine-writing tells" subsection to the docs writing standard in CLAUDE.md (which AGENTS.md symlinks to): no em-dashes, no doubled words/typos, no filler or hype, no throat-clearing intros, no decorative emoji.

Also removes the em-dashes from CLAUDE.md itself so the file follows its own rule (en-dash numeric ranges kept).

[coderabbitai]

Warning

Review limit reached

@strawgate, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 12 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: b047e4e9-0c16-47ba-91fb-8aab90e8596b

📥 Commits

Reviewing files that changed from the base of the PR and between 1994ca6 and 6163bf0.

📒 Files selected for processing (1)

• CLAUDE.md

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch claude/agents-md-writing-tells

---

_{Comment @coderabbitai help to get the list of available commands.}

[cubic-dev-ai]

No issues found across 1 file

Confidence score: 5/5

• Automated review surfaced no issues in the provided summaries.
• No files require special attention.

_{Re-trigger cubic}

[strawgate]

Closing as superseded. Everything this PR proposed has since merged into the documentation style guide:

• The machine-writing tells (no em-dashes, no hype/filler like seamless/robust/leverage, no throat-clearing, no decorative emoji) are already in dev-docs/documentation-style-guide.md §4 ("Ban the README dialect") and §5, via docs: add the documentation style guide #2067 and docs: de-em-dash the style guide and add the no-em-dash rule #2069.
• The em-dash removal this PR made in CLAUDE.md is moot: docs: quality pass across the integration guides #2068 moved that detailed prose out of CLAUDE.md into the style guide (which is already de-em-dashed), leaving a compact pointer.
• The only nuance not spelled out verbatim (no doubled words / the the) is covered by the guide's pre-publish "Spell/typo check".

So the rules live in the guide now; nothing here to merge on top of that.