Standardize glossary defaults and source glossary from JSON

[zz-plant]

Motivation

• Make glossary entries carry explicit, reviewable defaults (scope, operational tests, genealogy, references) instead of relying on runtime fallbacks so content is consistent across pages and APIs.
• Centralize the canonical glossary data in the JSON file so the TypeScript module and site consumers use the same source of truth.
• Fix validation noise and ensure validate-glossary passes by normalizing entry shape and fields.

Description

• Added explicit scope, operationalTests, genealogy, and references (or empty arrays) to glossary entries in src/content/glossary.json so every entry includes the same structured metadata.
• Simplified src/content/glossary.ts to import the JSON (import glossaryData from "./glossary.json") and assign export const glossaryContent = glossaryData[0] as GlossaryContent; instead of embedding a large inline object.
• Ran formatting on the changed files with bunx prettier --write to match repo style.

Testing

• Ran the repo checks with bun run check, which includes lint, unit tests, typecheck, Astro checks, validate:json, and validate:glossary, and all checks passed.

---

Codex Task

[cloudflare-workers-and-pages]

Deploying with    Cloudflare Workers

The latest updates on your project. Learn more about integrating Git with Workers.

Status	Name	Latest Commit	Preview URL	Updated (UTC)
✅ Deployment successful! View logs	et3	24cef1c	Commit Preview URL Branch Preview URL	Jan 15 2026, 09:55 PM

[gemini-code-assist]

Note

Gemini is unable to generate a summary for this pull request due to the file types involved not being currently supported.