feat(vedic): render the modern planets as their own row group, label the B.V. Raman frame, and bind the ayanamsa labels to the spec

Author: ph33nx

bun.lock

@@ -45,7 +45,7 @@
 		"@hey-api/openapi-ts": "0.99.0",
 		"@lit-labs/rollup-plugin-minify-html-literals": "^0.2.0",
 		"@playwright/test": "^1.61.1",
-		"@roxyapi/sdk": "^1.2.53",
+		"@roxyapi/sdk": "^1.2.57",
 		"@types/bun": "^1.3.14",
 		"@types/node": "^26.1.1",
 		"@types/react": "^19.2.17",

package.json

@@ -6,7 +6,7 @@ import { RoxyDataElement } from '../utils/base-element.js';
 import { baseStyles } from '../utils/base-styles.js';
 import { formatSignPosition } from '../utils/degree.js';
 import { chevron, disclosureStyles } from '../utils/disclosure.js';
-import { formatNumber } from '../utils/format.js';
+import { formatNumber, formatWithSanskrit } from '../utils/format.js';
 import { capitalize } from '../utils/string.js';
 
 /**
@@ -108,6 +108,12 @@ export class RoxyVedicPlanetsTable extends RoxyDataElement<BirthChartResponse> {
 			tbody tr.lagna {
 				background: color-mix(in srgb, var(--roxy-accent, #f59e0b) 10%, transparent);
 			}
+			/* The moderns are separated from the nine grahas by a RULE, never a tint. A tint
+			   would read as emphasis the tradition does not give them, and a tinted row is
+			   exactly where this library has measured muted text below the AA floor before. */
+			tbody tr.modern-first {
+				border-top-width: 2px;
+			}
 			td.graha {
 				font-weight: var(--roxy-weight-bold, 600);
 				color: var(--roxy-fg, #0a0a0a);
@@ -268,7 +274,8 @@ export class RoxyVedicPlanetsTable extends RoxyDataElement<BirthChartResponse> {
 					nakshatra lord, house, its state in all three avastha systems, and retrograde
 					state. Jagradadi and Deeptadi are read from sign dignity, which the nodes and
 					the Lagna do not have, so those two cells are blank on the Rahu, Ketu and
-					Lagna rows.
+					Lagna rows. Uranus, Neptune and Pluto appear only when asked for and rule no
+					sign, so every avastha and house cell is blank on their rows too.
 				</caption>
 				<thead>
 					<tr>
@@ -322,6 +329,7 @@ export class RoxyVedicPlanetsTable extends RoxyDataElement<BirthChartResponse> {
 							<td>${p.isRetrograde ? html`<span class="retro">R</span>` : nothing}</td>
 						</tr>`;
 					})}
+					${this.renderModernRows()}
 				</tbody>
 			</table>
 			</div>
@@ -333,6 +341,39 @@ export class RoxyVedicPlanetsTable extends RoxyDataElement<BirthChartResponse> {
 		</div>`;
 	}
 
+	/**
+	 * Uranus, Neptune and Pluto, present only when the caller sent `modernPlanets: true`.
+	 *
+	 * @remarks
+	 * They arrive in their OWN array rather than inside `meta`, which is deliberate on the API side and load-bearing here: a component iterating `meta` must not pick them up by accident, because classical Jyotish is defined over nine grahas. The moderns rule no sign, so they have no dignity and therefore no Baladi, Jagradadi or Deeptadi state and no house lordship.
+	 *
+	 * Those cells are left BLANK rather than filled with a zero or a dash, matching what the nodes and the Lagna already do two columns over. A zero would read as a measured state of zero strength, which is a different and false claim from "this system does not apply here".
+	 */
+	private renderModernRows() {
+		const moderns = this.data?.modernPlanets ?? [];
+		if (moderns.length === 0) return nothing;
+		return moderns.map((m, i) => {
+			const signGlyph = SIGN_GLYPH[capitalize(m.rashi ?? '')] ?? '';
+			return html`<tr class="modern ${i === 0 ? 'modern-first' : ''}">
+				<td class="graha">${formatWithSanskrit(m.planet, m.sanskritName)}</td>
+				<td>
+					${signGlyph ? html`<span class="glyph">${signGlyph}</span>` : nothing}${m.rashi ?? ''}
+				</td>
+				<td class="num">
+					${typeof m.longitude === 'number' ? formatSignPosition(m.longitude) : ''}
+				</td>
+				<td>${m.nakshatra?.name ?? ''}</td>
+				<td class="num">${m.nakshatra?.pada ?? ''}</td>
+				<td>${m.nakshatra?.lord ?? ''}</td>
+				<td></td>
+				<td></td>
+				<td></td>
+				<td></td>
+				<td>${m.isRetrograde ? html`<span class="retro">R</span>` : nothing}</td>
+			</tr>`;
+		});
+	}
+
 	private renderCombustion() {
 		const combust = this.data?.combustion ?? [];
 		if (combust.length === 0) return nothing;

packages/ui/src/components/vedic-planets-table.ts

@@ -144,12 +144,15 @@ export function formatAspectName(a: { type?: string }): string {
 /**
  * Display label for an ayanamsa identifier. `kp-newcomb` -> `KP Newcomb`.
  *
- * The raw values are API enums. KP is an initialism and must stay uppercase, which {@link humanize} alone cannot know, so the three known frames are mapped explicitly and anything else degrades to a humanized slug rather than rendering the enum.
+ * The raw values are API enums, and every one of them needs a human form that {@link humanize} cannot derive: KP is an initialism that must stay uppercase, and `raman` is a person, B.V. Raman, not a word. Anything unmapped degrades to a humanized slug rather than rendering the enum, which is a safe fallback and NOT a licence to skip the map: `raman` shipped as a frame months after this map was written and read as a bare "Raman" until 2026-08-03. `format.test.ts` now fails if the committed spec gains a frame this map lacks.
  */
-const AYANAMSA_LABEL: Record<string, string> = {
+export const AYANAMSA_LABEL: Record<string, string> = {
 	'kp-newcomb': 'KP Newcomb',
 	'kp-old': 'KP Old',
 	lahiri: 'Lahiri',
+	raman: 'B.V. Raman',
+
+	custom: 'Custom',
 };
 
 export function formatAyanamsa(type: unknown, degrees?: unknown): string {

packages/ui/src/utils/format.ts

@@ -19,6 +19,7 @@ import {
 	polarToCartesian,
 } from '../src/utils/degree.js';
 import {
+	AYANAMSA_LABEL,
 	distinctSanskrit,
 	formatAspectName,
 	formatAyanamsa,
@@ -553,12 +554,25 @@ describe('shared display formatters', () => {
 		expect(formatDateRange(undefined, undefined)).toBe('');
 	});
 
+	test('every ayanamsa the spec accepts has a human label', async () => {
+		// The map is hand-written because no humanizer can know that KP is an initialism or
+		// that Raman is a person. That is exactly why it goes stale: `raman` shipped months
+		// after the map and rendered as a bare "Raman" until someone read the output. Bind it
+		// to the committed spec so the next frame cannot arrive unlabelled.
+		const spec = await Bun.file('specs/openapi.json').json();
+		const frames: string[] =
+			spec.components.schemas.BirthChartRequest.properties.ayanamsa.enum;
+		expect(frames.length).toBeGreaterThan(3);
+		expect(frames.filter((f) => !AYANAMSA_LABEL[f])).toEqual([]);
+	});
+
 	test('formatAyanamsa keeps KP uppercase and degrades unknown frames', () => {
 		expect(formatAyanamsa('kp-newcomb', 23.6214)).toBe(
 			'KP Newcomb (23.62\u00b0)',
 		);
 		expect(formatAyanamsa('lahiri', 23.72)).toBe('Lahiri (23.72\u00b0)');
 		expect(formatAyanamsa('lahiri')).toBe('Lahiri');
+		expect(formatAyanamsa('raman', 22.5)).toBe('B.V. Raman (22.5\u00b0)');
 		expect(formatAyanamsa('raman-something')).toBe('Raman something');
 	});
 

packages/ui/tests/utils.test.ts

@@ -161,6 +161,10 @@ async function main() {
 				},
 			}),
 		),
+		// `modernPlanets` and `avasthaInfo` default to FALSE on the API, and the planets
+		// table renders a row group and three columns that exist only when they are sent.
+		// A sample that omits them leaves those renderers permanently unaudited, since the
+		// audit can only see what the fixture contains.
 		run('vedic-planets', () =>
 			roxy.vedicAstrology.generateBirthChart({
 				body: {
@@ -169,6 +173,8 @@ async function main() {
 					latitude: PERSON1.latitude,
 					longitude: PERSON1.longitude,
 					timezone: PERSON1.timezone,
+					modernPlanets: true,
+					avasthaInfo: true,
 				},
 			}),
 		),