docs: remove prose em dashes from evi and skills surfaces (U-14)

[evlogai]

What

Removes every prose em dash from the surfaces the daily content pass cannot reach, and aligns the self-review contract check with the tiered integration contract EVL-361 landed in the content doctrine.

Why

U-14 (no em dashes, no en dashes in prose, on any surface) applies everywhere, but the content-lint corpus only walks apps/docs/content, skills/, .agents/skills/, and AGENTS.md files; apps/evi/docs/ and apps/evi/agent/skills/ are never scanned, so drift there survives. A hand scan found prose dashes in all of those unscanned trees, plus one U-14 candidate on a scanned docs page (5.use-cases/5.eve.md).

Files (18)

• apps/evi/docs/ (observability, authorization, notes, vision, capability-placement): headings like ### evlog/eve — let ... become ### evlog/eve: let ..., appositives become commas or parentheses, sentence joins become periods or colons.
• apps/evi/agent/skills/ (before-after, daily-digest, cost-watchdog, linear-maintenance, self-review, upstream-sync): prose and frontmatter descriptions; the Daily digest — YYYY-MM-DD document-title templates become Daily digest: YYYY-MM-DD.
• skills/ (review-logging-patterns, build-audit-logs): table glosses become colons or commas. The en-dash numeric ranges (1 – 7 years, 30 – 90 days) stay: U-14 exempts ranges between two numbers.
• .agents/skills/ (create-map-rule, create-framework-integration, create-enricher): prose, frontmatter templates, and table cells.
• apps/docs/content/5.use-cases/5.eve.md: the one scanned page still carrying prose dashes.
• apps/evi/agent/skills/self-review/SKILL.md: the integration contract check now says "every first-class framework integration", and names the guide-level tier, matching the doctrine correction in EVL-361.

What stays

Dashes inside code blocks and verbatim templates stay (U-14 exempts them): the AGENTS.md tree diagram, code comments in skill templates, and the ### {title} — {question} heading format in create-map-rule, which prescribes the format the docs rules pages actually use.

Checks

• pnpm run lint: 22/22 tasks successful.
• pnpm content:lint on all 129 pages: zero U-14 candidates remaining; the self-review skill's T-15 critical was also resolved by the contract rewrite (the old row's evlog/shared literal tripped the retired-entrypoint rule).

No changeset: apps/* and skills prose only, no package consumer impact.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated
evi	Error		Sep 16, 2026 9:11am UTC
evlog-docs	Ready	Preview, v0	Sep 16, 2026 9:11am UTC
evlog-render-lab	Ready	Preview	Sep 16, 2026 9:11am UTC
evlog-telemetry	Ready	Preview	Sep 16, 2026 9:11am UTC
just-use-evlog	Ready	Preview	Sep 16, 2026 9:11am UTC

[coderabbitai]

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Advanced

Run ID: e65ea503-9b80-4f3d-bab8-011149479721

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

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

[pkg-pr-new]

npm i https://pkg.pr.new/@evlog/cli@703

npm i https://pkg.pr.new/evlog@703

npm i https://pkg.pr.new/@evlog/nuxthub@703

npm i https://pkg.pr.new/@evlog/telemetry@703

commit: 3b002c5

[github-actions]

Thank you for following the naming conventions! 🙏