Enforce Echo design vocabulary

[flyingrobots]

Migrated from Method backlog

This issue was created from a legacy filesystem backlog card. GitHub Issues are now the live work tracker; repository docs remain Method evidence.

Source backlog: docs/method/backlog/cool-ideas/DOCS_glossary-enforcement.md
Original lane: cool-ideas
Original legend: DOCS

Original backlog card

Enforce Echo design vocabulary

Status: active cool idea. Echo has docs/guide/course/glossary.md and docs
linting, but no glossary/terminology enforcement gate. Keep this as a bounded
docs-tooling task, not as a new vocabulary source of truth.

Echo uses WARP terms informally across docs and code comments. A glossary test
would catch terminology drift in teaching docs, specs, and comments. The
authoritative vocabulary should remain in the live docs it checks, starting with
docs/guide/course/glossary.md.

[coderabbitai]

🔗 Related PRs

#385 - docs(backlog): two follow-ups from the 2026-05-30 merge session [merged]

---

📝 Issue Planner

_{Check the box below or use the @coderabbitai plan command to generate an implementation plan and prompts that you can use with your favorite coding assistant.}

• Create Plan

---

🧪 Issue enrichment is currently in open beta.

You can configure auto-planning by selecting labels in the issue_enrichment configuration.

To disable automatic issue enrichment, add the following to your .coderabbit.yaml:

issue_enrichment:
  auto_enrich:
    enabled: false

💬 Have feedback or questions? Drop into our discord!