v2.7.0

Highlights

• @byline/core — Added an optional i18n.content.localeDefinitions field to the site config's i18n.content block, alongside the existing defaultLocale and locales. It carries author-controlled display names for the content locales a document can be published in — e.g. { code: 'fr', nativeName: 'Français' }. Byline itself doesn't render these (the content-locale set has no admin switcher); they exist purely so a public frontend can label its content-language affordances — hreflang clusters, "read this in…" links, sitemap alternates — with hand-authored names read straight off getServerConfig().i18n.content.localeDefinitions, rather than maintaining a parallel label map or accepting the lowercase forms (français) that CLDR's Intl.DisplayNames returns for romance languages. The field is fully optional and backward-compatible: hosts that omit it resolve labels per-code via Intl.DisplayNames as before; hosts that supply it for only some codes still fall back for the rest, and entries for codes outside locales are silently ignored. The byline and byline-examples CLI templates were updated to demonstrate the new field.

All other @byline/* packages bumped to 2.7.0 in lockstep with no behavioural changes this cycle.