feat(ephemeris-table,i18n): the monthly ephemeris rendered as a collapsed 31 Rows disclosure, because no component was bound to it

A site owner who placed the monthly ephemeris got Year, Month and a
disclosure reading 31 Rows. The operation was not in the component map, so
it fell through to the generic renderer, which cannot present days[].positions[].
The API was never the problem: it already returns planetLocalized and
signLocalized, so the reading was there and nothing drew it.

<roxy-ephemeris-table> is bound to both monthly operations, which return an
identical shape (14 tropical bodies, 9 Navagraha sidereal). Layout follows
published ephemerides rather than developer instinct: days down the rows,
bodies across glyph-headed columns, positions as 9 Leo 16 rather than a
decimal longitude, retrograde marked in the cell, and sign changes and
retrograde windows listed above the grid the way a printed ephemeris lists
ingresses and stations beside it. Every ingress reconciles against an
independently computed calendar once the noon UTC sampling is accounted for.

Translated in all seven locales from named astrology references in each
language, with rejected candidates recorded. Two traps closed: the German
article is dropped so a weak-noun sign stays uninflected, and the Turkish
dative lands on burc rather than the sign name, so both placeholders
substitute bare and correct. Empty states and captions are marked composed,
because no astrology site publishes either.

Also fixes a stale e2e fixture: transit-aspects now returns houses and
ascendant, so four specs asserted a no-cusps state the live response no
longer produces. They now assert the drawn ring and reach the degraded
branch by stripping the fields from the real payload.

Author: ph33nx

AGENTS.md

@@ -66,6 +66,7 @@ Use the table below for the formal endpoint to component mapping.
 | `<roxy-local-space-compass>` | Western | POST /astrology/local-space | Compass dial of planetary azimuth lines from the birthplace, dimmed below the horizon |
 | `<roxy-relocation-wheel>` | Western | POST /astrology/relocation-chart | Relocated chart wheel plus the move geometry, angular planets, and planets that change house |
 | `<roxy-positions-table>` | Western | POST /astrology/asteroids, /astrology/lilith, /astrology/progressions, /astrology/solar-arc, /astrology/arabic-lots | Body, sign, degree, and per-shape columns (house, motion, formula, or natal arc) plus each reading |
+| `<roxy-ephemeris-table>` | Cross | POST /astrology/planets/monthly, /vedic-astrology/planetary-positions/monthly | Per-body sign changes and retrograde windows for the month, over the full daily position grid |
 | `<roxy-fixed-stars>` | Western | POST /astrology/fixed-stars | Star to natal point conjunctions with readings, plus a catalog of position, magnitude, nature, and keywords |
 | `<roxy-profection-card>` | Western | POST /astrology/profections | Profected house and sign for the year, the lord of the year, its natal placement, and the reading |
 | `<roxy-compatibility-card>` | Cross | POST /astrology/compatibility-score, /numerology/compatibility, /biorhythm/compatibility | Score card with category breakdown |
@@ -555,7 +556,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-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`. 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.
 
 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

@@ -635,6 +635,7 @@ The self-fetch form renders spec-driven inputs (a zodiac tile picker, a boolean
 | `<roxy-local-space-compass>` | Western | POST /astrology/local-space | Compass dial of planetary azimuth lines from the birthplace, dimmed below the horizon |
 | `<roxy-relocation-wheel>` | Western | POST /astrology/relocation-chart | Relocated chart wheel plus the move geometry, angular planets, and planets that change house |
 | `<roxy-positions-table>` | Western | POST /astrology/asteroids, /astrology/lilith, /astrology/progressions, /astrology/solar-arc, /astrology/arabic-lots | Body, sign, degree, and per-shape columns (house, motion, formula, or natal arc) plus each reading |
+| `<roxy-ephemeris-table>` | Cross | POST /astrology/planets/monthly, /vedic-astrology/planetary-positions/monthly | Per-body sign changes and retrograde windows for the month, over the full daily position grid |
 | `<roxy-fixed-stars>` | Western | POST /astrology/fixed-stars | Star to natal point conjunctions with readings, plus a catalog of position, magnitude, nature, and keywords |
 | `<roxy-profection-card>` | Western | POST /astrology/profections | Profected house and sign for the year, the lord of the year, its natal placement, and the reading |
 | `<roxy-compatibility-card>` | Cross | POST /astrology/compatibility-score, /numerology/compatibility, /biorhythm/compatibility | Score card with category breakdown |
@@ -796,7 +797,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-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`. 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.
 
 ## Reliability
 

apps/docs/components-manifest.js

@@ -34,6 +34,16 @@ const DASHA_BODY = {
 	significators: true,
 };
 
+/**
+ * The month both ephemeris cards request. Fixed rather than "the month in progress"
+ * (which the API defaults to when year and month are omitted) so the demo, the
+ * captured sample and the preview image all describe the same 31 days: this month
+ * carries a solar ingress, two Mercury ingresses, a mid-month Chiron station and
+ * four bodies retrograde throughout, so every render branch on the card has data.
+ * Keep in sync with scripts/refresh-samples.ts.
+ */
+const EPHEMERIS_MONTH = { year: 2026, month: 8 };
+
 const REGISTRY_BASE = 'https://cdn.jsdelivr.net/gh/RoxyAPI/ui@main/registry';
 const UI_CDN = 'https://cdn.jsdelivr.net/npm/@roxyapi/ui@latest/dist/cdn';
 // Must match PK_PLACEHOLDER in scripts/widget-snippets.ts, which produces the snippets.
@@ -261,6 +271,29 @@ window.ROXY_UI_DEMOS = [
 		seoLine: 'The seven Hermetic lots with their sect-aware formulas',
 		sdkCall: `  const { data } = await roxy.astrology.calculateArabicLots({
     body: ${JSON.stringify(PERSON1, null, 2).replace(/\n/g, '\n    ')},
+  });`,
+	}),
+	entry({
+		id: 'ephemeris',
+		tag: 'roxy-ephemeris-table',
+		heading: 'Ephemeris',
+		topic: 'Astrology',
+		seoLine: 'Monthly ephemeris: daily tropical positions with sign changes and retrogrades',
+		sdkCall: `  const { data } = await roxy.astrology.getMonthlyTropicalEphemeris({
+    body: ${JSON.stringify(EPHEMERIS_MONTH, null, 2).replace(/\n/g, '\n    ')},
+  });`,
+	}),
+	// The second shape the one table renders: nine Navagraha instead of fourteen
+	// Western bodies, Rahu and Ketu instead of the lunar nodes. Without this card
+	// the sidereal roster is never rendered on the showcase or walked by the audit.
+	entry({
+		id: 'ephemeris-vedic',
+		tag: 'roxy-ephemeris-table',
+		heading: 'Ephemeris (Navagraha)',
+		topic: 'Astrology',
+		seoLine: 'Monthly Navagraha ephemeris: daily sidereal positions with sign changes and retrogrades',
+		sdkCall: `  const { data } = await roxy.vedicAstrology.getMonthlyEphemeris({
+    body: ${JSON.stringify(EPHEMERIS_MONTH, null, 2).replace(/\n/g, '\n    ')},
   });`,
 	}),
 	entry({