feat(synastry,samples): drop the natal-merge workaround now that the endpoint returns positions

The synastry wheel needed per-person planet longitudes the response did not
carry, so the capture script made an extra natal call and merged the arrays in
by hand. The fixture that produced was not a response any caller could get: it
showed natal-shaped planets carrying interpretation prose, which synastry has
never returned. The endpoint returns the plotting subset as of today, so the
extra call, the merge and the SynastryWithPlanets intersection type are all
gone and the demo now renders from one real response.

Adds a monthly horoscope demo card. The card already rendered an advice block
for any period that carried the field, and monthly is the one that did not, so
that branch had nothing exercising it. A branch with no demo card is a branch
the audit never walks.

Raises the e2e timeout to 90s. The axe passes take 10-12s alone and roughly
triple under the three browser matrix; one was already running at 29.1s against
the 30s default, and the extra demo card tipped addStyleTag in the practitioner
spec past it. That surfaces as a timeout inside a THEMING test and reads as a
theming bug, which is the expensive part.

Author: ph33nx

apps/docs/components-manifest.js

@@ -295,6 +295,15 @@ window.ROXY_UI_DEMOS = [
 		attrs: ' period="daily"',
 		sdkCall: `  const { data } = await roxy.astrology.getDailyHoroscope({ path: { sign: 'aries' } });`,
 	}),
+	entry({
+		id: 'horoscope-monthly',
+		tag: 'roxy-horoscope-card',
+		heading: 'Monthly horoscope',
+		seoLine:
+			'Month-level horoscope with a week-by-week breakdown, key lunar dates and one takeaway for the month',
+		attrs: ' period="monthly"',
+		sdkCall: `  const { data } = await roxy.astrology.getMonthlyHoroscope({ path: { sign: 'aries' } });`,
+	}),
 	entry({
 		id: 'compat',
 		tag: 'roxy-compatibility-card',