fix(i18n): translate the sidereal frame caption, and read copy passed to a helper

Author: ph33nx

AGENTS.md

@@ -530,7 +530,7 @@ The language comes from `lang` on the element, else the nearest ancestor carryin
 
 English is the default and needs no catalogue. Load only the languages your site serves; one catalogue covers every Roxy component on the page.
 
-A catalogue ships for every language the API serves: `de`, `es`, `fr`, `hi`, `pt`, `ru`, `tr`. Each covers `<roxy-natal-chart>`, `<roxy-transit-wheel>`, `<roxy-ephemeris-table>`, `<roxy-data>`, `<roxy-bodygraph>`, `<roxy-hd-type-card>`, `<roxy-hd-variables>`, `<roxy-reference-card>` and the shared labels every component inherits; the remaining components write English labels until their entries land. Every term is sourced from named astrology references in that language rather than translated word for word. **The values the API returns are never rewritten**: a planet, sign, aspect or house-system name renders exactly as the response carries it, so the words on the chart and the words in the response can never disagree. Ask for a language and the response carries the reader-facing name beside the English one, so the chart prints the translated name while the English one stays available to compare against in your own code.
+A catalogue ships for every language the API serves: `de`, `es`, `fr`, `hi`, `pt`, `ru`, `tr`. Coverage grows card by card, and a card is either translated or it is not, so a component reads its own labels in your language or writes them in English, never a mixture. Every term is sourced from named astrology references in that language rather than translated word for word. **The values the API returns are never rewritten**: a planet, sign, aspect or house-system name renders exactly as the response carries it, so the words on the chart and the words in the response can never disagree. Ask for a language and the response carries the reader-facing name beside the English one, so the chart prints the translated name while the English one stays available to compare against in your own code.
 
 Dates, times and numbers need no catalogue at all. They follow the same page language and are written the way that language writes them, hour cycle included, so a German page reads `15. Jan. 1990, 14:30` and an Argentine one `15 de ene de 1990, 2:30 p. m.`.
 

README.md

@@ -820,7 +820,7 @@ Two things are separate on purpose. The catalogue is the wording this library wr
 
 Dates, times and numbers follow the page as well, in the conventions that language actually uses: a Spanish page reads `15 ene 1990`, an Argentine one `15 de ene de 1990`, a German one `15. Jan. 1990, 14:30`. The hour cycle comes from the language, not from us, so nobody gets a 12-hour clock on a page that writes 24. This needs no catalogue and no attribute: it follows the same `lang` your page already declares.
 
-A catalogue ships for every language the API serves: `de`, `es`, `fr`, `hi`, `pt`, `ru`, `tr`. Each covers `<roxy-natal-chart>`, `<roxy-transit-wheel>`, `<roxy-ephemeris-table>`, `<roxy-data>`, `<roxy-bodygraph>`, `<roxy-hd-type-card>`, `<roxy-hd-variables>`, `<roxy-reference-card>` and the shared chrome every component inherits; the remaining components render English labels until their catalogue entries land. Every term in every catalogue is sourced from named astrology references in that language rather than translated word for word, because the words a practitioner reads are the product.
+A catalogue ships for every language the API serves: `de`, `es`, `fr`, `hi`, `pt`, `ru`, `tr`. Coverage grows card by card, and a card is either translated or it is not, so a component reads its own labels in your language or renders them in English, never a mixture. Every term in every catalogue is sourced from named astrology references in that language rather than translated word for word, because the words a practitioner reads are the product.
 
 ## Reliability
 

packages/ui/src/components/arudha-padas.ts

@@ -148,7 +148,7 @@ export class RoxyArudhaPadas extends RoxyDataElement<ArudhaResponse> {
 		return html`<div class="wrap" part="card" aria-label="Arudha padas">
 			<header class="head" part="header">
 				<h2 class="title">Arudha padas</h2>
-				${renderFrameCaption(this.effectiveLang(), d.frame)}
+				${renderFrameCaption(this.effectiveLang(), d.frame, this.translator)}
 			</header>
 			<div class="leads" part="details">
 				<div class="lead"><span>Lagna</span><strong>${d.lagnaRashi ?? ''}</strong></div>

packages/ui/src/components/ashtakavarga-grid.ts

@@ -234,7 +234,7 @@ export class RoxyAshtakavargaGrid extends RoxyDataElement<AshtakavargaResponse>
 						? html`<p class="subtitle">${signs.length} signs</p>`
 						: nothing
 				}
-				${renderFrameCaption(this.effectiveLang(), d.frame)}
+				${renderFrameCaption(this.effectiveLang(), d.frame, this.translator)}
 			</div>
 
 			${renderTablist({

packages/ui/src/components/bhav-chalit-table.ts

@@ -148,7 +148,7 @@ export class RoxyBhavChalitTable extends RoxyDataElement<BhavChalitResponse> {
 								house between the Rashi chart and the unequal Sripati cusps.`
 					}
 				</p>
-				${renderFrameCaption(this.effectiveLang(), d.frame)}
+				${renderFrameCaption(this.effectiveLang(), d.frame, this.translator)}
 			</header>
 
 			${

packages/ui/src/components/bhava-bala-table.ts

@@ -158,7 +158,7 @@ export class RoxyBhavaBalaTable extends RoxyDataElement<BhavaBalaResponse> {
 						d.houseSystem ? html` on the ${d.houseSystem} frame` : nothing
 					}
 				</p>
-				${renderFrameCaption(this.effectiveLang(), d.frame)}
+				${renderFrameCaption(this.effectiveLang(), d.frame, this.translator)}
 			</header>
 
 			<div class="rows" part="table" role="list">

packages/ui/src/components/chara-karakas.ts

@@ -175,7 +175,7 @@ export class RoxyCharaKarakas extends RoxyDataElement<CharaKarakaResponse> {
 					<span class="scheme-chip">${d.scheme ?? ''}</span>
 					${d.scheme ? (SCHEMES[d.scheme] ?? '') : ''}
 				</p>
-				${renderFrameCaption(this.effectiveLang(), d.frame)}
+				${renderFrameCaption(this.effectiveLang(), d.frame, this.translator)}
 			</header>
 			<div class="leads" part="details">
 				<div class="lead"><span>Atmakaraka</span><strong>${d.atmakaraka ?? ''}</strong></div>

packages/ui/src/components/divisional-chart.ts

@@ -107,7 +107,7 @@ export class RoxyDivisionalChart extends RoxyDataElement<DivisionalChartResponse
 							? html`<p class="significance">${division.significance}</p>`
 							: nothing
 					}
-					${renderFrameCaption(this.effectiveLang(), d.frame)}
+					${renderFrameCaption(this.effectiveLang(), d.frame, this.translator)}
 				</div>
 				${renderKundliStyleTablist(this.chartStyle, this.setStyle)}
 			</div>

packages/ui/src/components/dosha-card.ts

@@ -171,7 +171,7 @@ export class RoxyDoshaCard extends RoxyDataElement<DoshaData> {
 				<span class=${`badge ${present ? 'present' : 'absent'}`}>
 					${present ? 'Present' : 'Absent'}
 				</span>
-				${renderFrameCaption(this.effectiveLang(), d.frame)}
+				${renderFrameCaption(this.effectiveLang(), d.frame, this.translator)}
 			</header>
 			${
 				'type' in d && d.type

packages/ui/src/components/guna-milan.ts

@@ -373,7 +373,7 @@ export class RoxyGunaMilan extends RoxyDataElement<CompatibilityResponse> {
 					</div>`
 					: nothing
 			}
-			${renderFrameCaption(this.effectiveLang(), d.frame)}
+			${renderFrameCaption(this.effectiveLang(), d.frame, this.translator)}
 		</article>`;
 	}
 }