[mhodzic93]

Doc-only, mirrors web-client#331. Keeps the four copies byte-identical.

Adds the spaced-en-dash carve-out for ranges whose endpoints contain spaces, and replaces the known-gap section with a coverage section now that web-client is swept end to end.

🤖 Generated with Claude Code

[buildpulse-v2]

Agent code review

Walkthrough

This is a pure documentation update to EXTERNAL-VOICE.md (1 file changed, 18 insertions, 8 deletions). It makes two targeted improvements: (1) adds a paragraph clarifying that a spaced en-dash in a date range (e.g., Aug 7 – Sep 7, 2026) is intentionally correct typography even though the guard flags it — advising developers to pin the line rather than mangle the date; and (2) replaces the "Known gap" section with a "Coverage" section that updates the status of web-client (now swept end to end, including the previously-unswept in-product dashboard copy) and shifts the known outstanding gap to blog post bodies stored in blog_posts (~750 em-dashes in 88 pre-rule posts, with a note that backfill was deliberately declined).

Findings

No issues found.

Verdict

Clean documentation-only PR. The title accurately describes the change, the new text is internally consistent, and it reflects the completion of work called out explicitly in PR #13 (the in-product dashboard sweep). The known-gap acknowledgment for legacy blog posts is well-reasoned and appropriately noted as a decision rather than an oversight. All pre-APPROVE checklist items pass.

Confidence

HIGH — single documentation file, diff is unambiguous, no code or logic changes.

💡 Tips for working with the BuildPulse reviewer

• Re-review on demand — comment @buildpulse review on the PR (/buildpulse review also works). The fresh review bills the requester's seat.
• Teach it by replying to a finding — reply to any inline comment: "we never do X here" becomes a standing rule for this repository (acknowledged in-thread, not raised again); "not in this PR" mutes the topic for this PR only. Replies are free. Org admins can view or remove learned rules on the AI Features page.
• Every push is re-reviewed automatically — smaller PRs get a fresh full review, larger ones get a delta review of what changed since the last look; an "Update branch" merge with an unchanged diff carries the previous verdict forward without a new billed review.
• Draft PRs are skipped until marked ready for review (repositories can opt in to draft reviews on the AI Features page).