docs(glossary): add scorer, grader, judge synonyms to Evaluator

[Lotte-Verheyden]

Adds Scorer, Grader, and Judge as synonyms on the Evaluator glossary entry (lib/glossary-data.js), replacing the inaccurate Observation Type synonym.

"Observation Type" is the category the term belongs to, not a synonym, and the definition already states "An observation type...". The three added terms are genuine synonyms readers use, so searches for scorer, grader, or judge now surface the Evaluator entry. They also render beside the term in the UI and as "Also known as:" in the Markdown/PDF output.

---

Note

Low Risk
Documentation-only glossary metadata with no runtime or API behavior changes.

Overview
Updates the Evaluator glossary entry so its synonyms list uses Scorer, Grader, and Judge instead of Observation Type.

That swap improves glossary search and the “Also known as” UI/export for terms readers actually use, without changing definitions or other entries.

^{Reviewed by Cursor Bugbot for commit cf6767c. Bugbot is set up for automated code reviews on this repo. Configure here.}

Greptile Summary

Updates the Evaluator glossary entry to use accurate synonyms so users searching for scorer, grader, or judge can discover it.

• Replaces the inaccurate “Observation Type” synonym with “Scorer,” “Grader,” and “Judge.”
• Updates synonym text rendered in the glossary UI and Markdown/PDF output.

Confidence Score: 5/5

The PR appears safe to merge with no actionable issues identified.

The new synonym strings match the existing glossary data shape, are handled correctly by search and output rendering, and do not collide with other glossary terms or synonyms.

_{Reviews (1): Last reviewed commit: "docs(glossary): add scorer, grader, judg..." | Re-trigger Greptile}

Context used:

• Knowledge Base — Product Documentation Content (content/docs, content/guides, content/faq)

[vercel]

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

Project	Deployment	Actions	Updated (UTC)
langfuse-docs	Ready	Preview	Aug 7, 2026 5:52pm

[github-actions]

@claude review

[claude]

LGTM — accurate, low-risk glossary metadata fix.

Extended reasoning...

Overview

Single-line change to lib/glossary-data.js: the Evaluator glossary entry's synonyms array is changed from ["Observation Type"] to ["Scorer", "Grader", "Judge"]. No other entries, definitions, or code paths are touched.

Security risks

None. This is static glossary metadata rendered client-side (used for search matching and an "Also known as:" display); there is no user input, auth, or data flow involved.

Level of scrutiny

Minimal scrutiny is appropriate here — this is a content-only data correction. The rationale is sound: "Observation Type" was the entry's category, not a synonym (and is already stated in the definition text: "An observation type..."), so it was a genuine inaccuracy. "Scorer", "Grader", and "Judge" are legitimate synonyms readers commonly search for. I checked TERMS for duplicate id/term collisions and confirmed no other entry uses these three synonyms, so there is no ambiguity introduced in glossary search/lookup.

Other factors

The change is mechanical, self-contained, and matches the pattern used elsewhere in the file (e.g. RBAC → Role-Based Access Control, SDK → Software Development Kit). No markdown override or generated file needs updating since this only affects a JS data module consumed by the Glossary component. No tests exist for this data file and none are warranted for a content tweak.