Resolve per-language {title, description} for an article
rendered by the aggregator pipeline. The resolver follows a strict
priority ladder that prefers real editorial highlights over boring,
repeated templates — satisfying the core SEO requirement that every
published article carry a unique, content-reflective headline and
description in every language variant.
Manifest override — manifest.title / manifest.description on
the analysis-run manifest, either as a plain string (applied to every
language) or a LanguageMap<string> object for explicit per-language
values.
Localized executive brief — for non-English <lang>, the
translated sibling executive-brief_<lang>.md (or
extended/executive-brief_<lang>.md) under the run directory.
Resolved via editorial-brief-resolver.ts. This is the authoritative
localized source produced by the news-translate workflow.
English executive brief, verbatim — the English brief
(executive-brief.md / extended/executive-brief.md) used as a
fall-through when a locale has no translated brief yet.
Artefact editorial H1 — first # … heading from the first
substantive artefact under the run directory.
Aggregated-markdown H1 — the first # … heading in the aggregator
output, accepted under the same non-generic rule.
First strong prose paragraph — the first line of the aggregated
Markdown that survives shouldSkipDescriptionLine.
Localized template — the per-article-type *_TITLES generator
from src/constants/language-articles.ts. Last resort.
--- IMPLEMENTATION NOTE ---
Following Refactor 6/8 (issue #2034) this file holds the resolver
orchestrator (resolveArticleMetadata) plus per-language dispatch
(resolveOneLanguage, resolvePerLanguageEditorial) that depend on
resolveLocalizedBriefHighlight from editorial-brief-resolver.ts.
Pure leaf helpers live in src/aggregator/metadata/:
Description
Resolve per-language
{title, description}for an article rendered by the aggregator pipeline. The resolver follows a strict priority ladder that prefers real editorial highlights over boring, repeated templates — satisfying the core SEO requirement that every published article carry a unique, content-reflective headline and description in every language variant.Priority ladder (per language, highest wins) — matches the editorial contract documented in
.github/prompts/04-article-generation.md§ 6.2:manifest.title/manifest.descriptionon the analysis-run manifest, either as a plain string (applied to every language) or aLanguageMap<string>object for explicit per-language values.<lang>, the translated siblingexecutive-brief_<lang>.md(orextended/executive-brief_<lang>.md) under the run directory. Resolved viaeditorial-brief-resolver.ts. This is the authoritative localized source produced by thenews-translateworkflow.executive-brief.md/extended/executive-brief.md) used as a fall-through when a locale has no translated brief yet.# …heading from the first substantive artefact under the run directory.# …heading in the aggregator output, accepted under the same non-generic rule.*_TITLESgenerator fromsrc/constants/language-articles.ts. Last resort.--- IMPLEMENTATION NOTE ---
Following Refactor 6/8 (issue #2034) this file holds the resolver orchestrator (
resolveArticleMetadata) plus per-language dispatch (resolveOneLanguage,resolvePerLanguageEditorial) that depend onresolveLocalizedBriefHighlightfromeditorial-brief-resolver.ts. Pure leaf helpers live insrc/aggregator/metadata/:metadata/types.ts—ResolvedMetadata{Entry},MetadataManifest,ResolveMetadataOptions.metadata/h1-extractor.ts— first-H1 extraction.metadata/lede-extractor.ts— strong-prose + lede-after-heading.metadata/heading-rules.ts— generic/category/lede heading rules.metadata/slug.ts—humanizeSlug.metadata/artifact-highlight.ts— editorial-artefact highlight ladder + priority-finding extractor.metadata/template-fallback.ts—buildTemplateFallback+SEO_CONTEXT_LABELS.metadata/text-utils.ts— truncation + skip filters.metadata/date-labels.ts— week/month/quarter/year/term labels.metadata/resolve-helpers.ts— pure resolver helpers (manifest override, editorial-content, contextual title/description, SEO keywords).New code should import directly from the leaf modules. This barrel is preserved for backward compatibility with existing call sites.