Generate definitions for remaining ~12.4k concepts (follow-up to #2426)

[jung-thomas]

Background

Follow-up to #2426. The concept-definition generator (scripts/seed-concept-definitions.cjs, job srv/jobs/generate-concept-definitions-job.js, guardrails from #2431) was run on PROD with --budget 500, producing 500 grounded definitions (0 errors, 0 terminology violations, 0 grounding skips), all subsequently approved.

That covers only 500 of ~12,878 PROD concepts. The remaining ~12,378 concepts still have no description (blank on-page below the tiles — the "hyperlink hell" #2426 flagged persists for every un-defined concept).

Goal

Generate grounded DRAFT definitions for the remaining PROD concepts, in budgeted batches, and get them reviewed/approved.

Approach

• Re-run in batches: cds bind --exec -- node scripts/seed-concept-definitions.cjs --commit --budget <N> against PROD.
  • Each run: ~500 concepts ≈ 35 min wall-clock, ~502k prompt + ~85k completion tokens (AI Core). Budget total cost/time accordingly (~25 batches for full coverage).
  • Skips concepts with no groundable linked docs (skippedNoGrounding) — those need curated doc links first (same mechanism as the feat(concepts): ABAP Keyword Documentation links (#2426) #2432 keyword-docu seeds) before they can be defined.
• Every definition lands descriptionStatus='DRAFT'; review + approve via /admin-ui/ → Concepts → filter Definition Status = DRAFT before it renders. Do NOT bulk-approve unreviewed (the Topics and Concepts #2426 500-run was an explicit one-off maintainer decision).
• Republish after each approval wave: gh workflow run rebuild-content.yml -f environment=prod -f mode=full (or slug-targeted for a small wave).

Open questions

• Batch cadence / total AI Core budget to allocate.
• Prioritization: define high-traffic / top-linked concepts first vs. straight FIFO.
• How many skippedNoGrounding concepts exist, and whether to curate doc links for them (ties into feat(concepts): ABAP Keyword Documentation links (#2426) #2432's approach).

Definition of done

• All PROD concepts either have an APPROVED definition or are explicitly excluded (no grounding, out of scope).
• Coverage tracked (count APPROVED vs total) — consider an admin dashboard tile.

Refs: #2426, #2431 (generator + guardrails), #2432 (doc-link grounding).