@roxyapi/ui 0.25.0 → 0.26.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (78) hide show
  1. package/AGENTS.md +3 -1
  2. package/README.md +9 -1
  3. package/components-catalog.json +125 -125
  4. package/dist/cdn/components/endpoint-form.js +1 -1
  5. package/dist/cdn/components/endpoint-form.js.map +1 -1
  6. package/dist/cdn/components/natal-chart.js.map +2 -2
  7. package/dist/cdn/components/relocation-wheel.js.map +2 -2
  8. package/dist/cdn/components/transit-wheel.js +12 -12
  9. package/dist/cdn/components/transit-wheel.js.map +3 -3
  10. package/dist/cdn/locales/de.js +1 -1
  11. package/dist/cdn/locales/de.js.map +2 -2
  12. package/dist/cdn/locales/es.js +1 -1
  13. package/dist/cdn/locales/es.js.map +2 -2
  14. package/dist/cdn/locales/fr.js +1 -1
  15. package/dist/cdn/locales/fr.js.map +2 -2
  16. package/dist/cdn/locales/hi.js +1 -1
  17. package/dist/cdn/locales/hi.js.map +2 -2
  18. package/dist/cdn/locales/pt.js +1 -1
  19. package/dist/cdn/locales/pt.js.map +2 -2
  20. package/dist/cdn/locales/ru.js +1 -1
  21. package/dist/cdn/locales/ru.js.map +2 -2
  22. package/dist/cdn/locales/tr.js +1 -1
  23. package/dist/cdn/locales/tr.js.map +2 -2
  24. package/dist/cdn/roxy-ui.js +17 -17
  25. package/dist/cdn/roxy-ui.js.map +3 -3
  26. package/dist/components/endpoint-form.js +1 -1
  27. package/dist/components/endpoint-form.js.map +1 -1
  28. package/dist/components/natal-chart.d.ts +4 -0
  29. package/dist/components/natal-chart.d.ts.map +1 -1
  30. package/dist/components/natal-chart.js.map +2 -2
  31. package/dist/components/relocation-wheel.js.map +2 -2
  32. package/dist/components/transit-wheel.d.ts +79 -37
  33. package/dist/components/transit-wheel.d.ts.map +1 -1
  34. package/dist/components/transit-wheel.js +11 -11
  35. package/dist/components/transit-wheel.js.map +3 -3
  36. package/dist/i18n/chrome-strings.d.ts +1 -1
  37. package/dist/i18n/chrome-strings.d.ts.map +1 -1
  38. package/dist/index.cjs +5 -5
  39. package/dist/index.cjs.map +3 -3
  40. package/dist/index.js +5 -5
  41. package/dist/index.js.map +3 -3
  42. package/dist/locales/de.d.ts.map +1 -1
  43. package/dist/locales/de.js +1 -1
  44. package/dist/locales/de.js.map +2 -2
  45. package/dist/locales/es.d.ts.map +1 -1
  46. package/dist/locales/es.js +1 -1
  47. package/dist/locales/es.js.map +2 -2
  48. package/dist/locales/fr.d.ts.map +1 -1
  49. package/dist/locales/fr.js +1 -1
  50. package/dist/locales/fr.js.map +2 -2
  51. package/dist/locales/hi.d.ts.map +1 -1
  52. package/dist/locales/hi.js +1 -1
  53. package/dist/locales/hi.js.map +2 -2
  54. package/dist/locales/pt.d.ts.map +1 -1
  55. package/dist/locales/pt.js +1 -1
  56. package/dist/locales/pt.js.map +2 -2
  57. package/dist/locales/ru.d.ts.map +1 -1
  58. package/dist/locales/ru.js +1 -1
  59. package/dist/locales/ru.js.map +2 -2
  60. package/dist/locales/tr.d.ts.map +1 -1
  61. package/dist/locales/tr.js +1 -1
  62. package/dist/locales/tr.js.map +2 -2
  63. package/dist/types/types.gen.d.ts +46 -0
  64. package/dist/types/types.gen.d.ts.map +1 -1
  65. package/dist/version.d.ts +1 -1
  66. package/package.json +1 -1
  67. package/src/components/natal-chart.ts +11 -1
  68. package/src/components/transit-wheel.ts +115 -49
  69. package/src/i18n/chrome-strings.ts +1 -0
  70. package/src/locales/de.ts +1 -0
  71. package/src/locales/es.ts +2 -0
  72. package/src/locales/fr.ts +1 -0
  73. package/src/locales/hi.ts +1 -0
  74. package/src/locales/pt.ts +1 -0
  75. package/src/locales/ru.ts +1 -0
  76. package/src/locales/tr.ts +1 -0
  77. package/src/types/types.gen.ts +46 -0
  78. package/src/version.ts +1 -1
package/dist/version.d.ts CHANGED
@@ -1,2 +1,2 @@
1
- export declare const ROXY_UI_VERSION = "0.25.0";
1
+ export declare const ROXY_UI_VERSION = "0.26.0";
2
2
  //# sourceMappingURL=version.d.ts.map
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@roxyapi/ui",
3
- "version": "0.25.0",
3
+ "version": "0.26.0",
4
4
  "description": "Web components for the RoxyAPI catalog. Drop-in charts, tables, cards, forms for astrology, tarot, numerology, biorhythm, I Ching, crystals, dreams, angel numbers, and more. One key, beautiful in 30 minutes.",
5
5
  "type": "module",
6
6
  "main": "./dist/index.cjs",
@@ -591,7 +591,13 @@ export class RoxyNatalChart extends RoxyDataElement<WheelChart> {
591
591
  }
592
592
  </div>
593
593
  ${this.renderDetails()}
594
- ${this.renderPatterns()}
594
+ ${
595
+ // Ungated on purpose. The figures are chart geometry, not a reading, and
596
+ // only the paragraph inside each card answers to hide-readings. Do NOT
597
+ // wrap this call in the flag: the reasoning, and the escape hatch for a
598
+ // page that wants the block gone anyway, are on renderPatterns.
599
+ this.renderPatterns()
600
+ }
595
601
  ${this.renderInterpretations()}
596
602
  </div>`;
597
603
  }
@@ -1073,6 +1079,10 @@ export class RoxyNatalChart extends RoxyDataElement<WheelChart> {
1073
1079
  *
1074
1080
  * @remarks
1075
1081
  * A pattern carries no localized partner for its `name`, `element`, `modality` or its `planets` list, so all four render English on every page. Do NOT translate the chips by looking each body up in `planets[].nameLocalized`: the response is the authority for its own vocabulary, and a second translation of the same fact assembled here is exactly what can end up disagreeing with the wheel beside it.
1082
+ *
1083
+ * **This block is DATA, so `hide-readings` thins it rather than removing it, and that split is deliberate.** A T-Square is a geometric fact about where the bodies sit, exactly like the aspect rows and the house cusps: the figure, its element and modality, its tightness and its planets are all measurements, and the only reading in the card is the paragraph, which {@link RoxyNatalChart.renderPattern} already drops. The line is the one the library states everywhere else and the one the docs promise: "wheels, maps, tables, grids, legends, badges and every number stay, the interpretive prose goes". `<roxy-aspects-table>` renders this identical `patterns` payload and makes the identical cut, so gating the whole block here would make the same figure appear and disappear depending on which component a page reached for.
1084
+ *
1085
+ * **A page that wants the block gone entirely has a lever, and it is not this flag.** The section carries `part="section patterns"`, so `roxy-natal-chart::part(patterns) { display: none }` removes it. That is the documented answer for dropping a block of DATA, the same way `::part(readings)` styles the interpretation; `hide-readings` is the answer for prose, and stretching it to cover measurements would leave a practitioner with no way to publish the figures without the words.
1076
1086
  */
1077
1087
  private renderPatterns() {
1078
1088
  const patterns = this.data?.patterns ?? [];
@@ -35,6 +35,20 @@ type Body = CalculateTransitAspectsResponse['transitPlanets'][number];
35
35
  type TransitAspect = CalculateTransitAspectsResponse['aspects'][number];
36
36
  type TransitSummary = CalculateTransitAspectsResponse['summary'];
37
37
 
38
+ /**
39
+ * The transit-aspects response plus the natal frame it now carries.
40
+ *
41
+ * @remarks
42
+ * `/astrology/transit-aspects` returns `houses` and `ascendant` field for field identical to the
43
+ * natal-chart ones, which is what lets the prop and the payload share one code path below. They are
44
+ * declared here as OPTIONAL rather than read straight off the generated response type because
45
+ * `specs/openapi.json` is refreshed from live only after the API deploys, so the type does not name
46
+ * them yet and this component must compile against both the old spec and the new one. Once the spec
47
+ * refresh lands the intersection is a no-op and this alias can go.
48
+ */
49
+ type TransitAspectsPayload = CalculateTransitAspectsResponse &
50
+ Partial<Pick<NatalChartResponse, 'houses' | 'ascendant'>>;
51
+
38
52
  /**
39
53
  * Radii, outermost first. Every one is explicit rather than derived from its
40
54
  * neighbour, because the two rings of glyphs and their two bands of degree
@@ -61,7 +75,7 @@ const TRANSIT_LINE_R = 112;
61
75
  const NATAL_LINE_R = 104;
62
76
  /** Innermost circle, closing the wheel under the natal degree labels. */
63
77
  const HUB_R = 70;
64
- /** House sector numbers, inside the hub: the only band on this wheel with nothing else in it. Drawn ONLY from cusps the page supplied. */
78
+ /** House sector numbers, inside the hub: the only band on this wheel with nothing else in it. Drawn ONLY from real cusps, the response ones or a page override. */
65
79
  const HOUSE_NUM_R = 58;
66
80
  /**
67
81
  * Widths a fanned cluster has to clear. The glyph is the wider mark but sits on
@@ -128,17 +142,23 @@ const byName = (list: Body[]): Map<string, Body> => {
128
142
  * missing House column for months. The numbers are rendered, in their own
129
143
  * columns, labelled with the system the response names.
130
144
  *
131
- * **What is still absent is the GEOMETRY, and that is why the default wheel has
132
- * no house ring.** The response carries no ascendant and no cusp longitudes, so a
133
- * house number is a placement with no sector to draw it in. Equal sectors derived
134
- * from {@link RoxyTransitWheel.ascendant} and labelled with a quadrant system
135
- * would replace one false statement with a worse one, so the default wheel fixes
136
- * 0 degrees Aries on the left horizon, says so in the legend and in the SVG
137
- * description rather than leaving a reader to discover it, and draws no house
138
- * divisions at all. A host that holds the real cusps (from /astrology/natal-chart,
139
- * which returns all twelve) passes {@link RoxyTransitWheel.houses} and gets the
140
- * sector ring. Both props are supplied data placed on a circle, never a cusp this
141
- * component worked out.
145
+ * **The GEOMETRY arrived next, and the wheel now draws itself.** The response also
146
+ * carries the twelve natal cusps as `houses` and the natal `ascendant`, the same
147
+ * twelve the house numbers above were read against, so the sector ring and the
148
+ * real horizon come out of the one call the page already made. That closed the
149
+ * house-less bi-wheel every embed drew through WordPress, /embed and the CDN
150
+ * widgets, none of which can compose a second call. {@link RoxyTransitWheel.houses}
151
+ * and {@link RoxyTransitWheel.ascendant} remain as OVERRIDES and keep winning
152
+ * where a page sets them, which is what a stored response predating the fields,
153
+ * or a trimming proxy, needs.
154
+ *
155
+ * **Nothing is ever derived, whichever source it came from.** A payload with
156
+ * neither field still fixes 0 degrees Aries on the left horizon, says so in the
157
+ * legend and in the SVG description rather than leaving a reader to discover it,
158
+ * and draws no house divisions at all. Equal sectors derived from an Ascendant
159
+ * and labelled with a quadrant system would replace one false statement with a
160
+ * worse one. Every cusp on this wheel is a longitude some source stated, placed
161
+ * on a circle, never one this component worked out.
142
162
  */
143
163
  @customElement('roxy-transit-wheel')
144
164
  export class RoxyTransitWheel extends RoxyDataElement<CalculateTransitAspectsResponse> {
@@ -460,31 +480,37 @@ export class RoxyTransitWheel extends RoxyDataElement<CalculateTransitAspectsRes
460
480
  heading = 'Transits';
461
481
 
462
482
  /**
463
- * Natal Ascendant as an ecliptic longitude in degrees (0-360), supplied by the
464
- * page from a chart endpoint that returns one.
483
+ * Natal Ascendant as an ecliptic longitude in degrees (0-360), to override the
484
+ * one the response carries.
465
485
  *
466
486
  * @remarks
467
- * /astrology/transit-aspects returns no ascendant, so this is the only way the
468
- * wheel can sit on a real horizon. Setting it ROTATES the wheel so the given
469
- * longitude falls on the left horizon and draws the ASC/DSC axis. It draws no
470
- * house divisions, because a rotation is not a cusp; that is what
471
- * {@link RoxyTransitWheel.houses} is for. Leave both unset for the honest
472
- * default: 0 degrees Aries on the left.
487
+ * Leave it unset on a live /astrology/transit-aspects response: that endpoint
488
+ * returns the natal `ascendant` and the wheel reads it, so the horizon is
489
+ * right with no page wiring at all. Set it only to orient the wheel on a
490
+ * DIFFERENT horizon than the response describes, or to give one to a payload
491
+ * that carries none. Either way it ROTATES the wheel so the given longitude
492
+ * falls on the left horizon and draws the ASC/DSC axis. It draws no house
493
+ * divisions, because a rotation is not a cusp; that is what
494
+ * {@link RoxyTransitWheel.houses} is for. With neither the prop nor a payload
495
+ * ascendant the wheel falls back to the honest default: 0 degrees Aries on
496
+ * the left.
473
497
  */
474
498
  @property({ type: Number })
475
499
  ascendant?: number;
476
500
 
477
501
  /**
478
- * The twelve natal house cusps, supplied by the page. Takes the
479
- * /astrology/natal-chart `houses` array verbatim, or twelve bare cusp
480
- * longitudes in house order.
502
+ * The twelve natal house cusps, to override the ones the response carries.
503
+ * Takes the /astrology/natal-chart `houses` array verbatim, or twelve bare
504
+ * cusp longitudes in house order.
481
505
  *
482
506
  * @remarks
483
- * /astrology/transit-aspects numbers every body by house but returns no cusp
484
- * longitudes, so this is the only way the wheel can draw the sectors those
485
- * numbers refer to. Supplying it draws the twelve cusp lines and their numbers
486
- * and, unless {@link RoxyTransitWheel.ascendant} also arrives, rotates the
487
- * first cusp onto the left horizon.
507
+ * Leave it unset on a live /astrology/transit-aspects response: that endpoint
508
+ * returns the same twelve natal cusps its house numbers are read against, so
509
+ * the sector ring draws itself. Set it to draw a different cusp set than the
510
+ * response carries, or to give one to a payload that carries none (a stored
511
+ * response predating the field, or a proxy that trims it). Supplying either
512
+ * source draws the twelve cusp lines and their numbers and, unless an
513
+ * ascendant is also available, rotates the first cusp onto the left horizon.
488
514
  *
489
515
  * Both accepted shapes exist because the natural source is a natal-chart
490
516
  * response a host already holds, and passing `chart.houses` straight through
@@ -497,25 +523,54 @@ export class RoxyTransitWheel extends RoxyDataElement<CalculateTransitAspectsRes
497
523
  @property({ type: Array })
498
524
  houses?: NatalChartResponse['houses'] | number[];
499
525
 
500
- /** True when the page supplied a usable ascendant, so the ASC/DSC axis is a value the host gave rather than one derived from a cusp. */
526
+ /** The response widened to the natal frame it carries. One cast, so nothing below repeats it. */
527
+ private get payload(): TransitAspectsPayload | undefined {
528
+ return this.data as TransitAspectsPayload | undefined;
529
+ }
530
+
531
+ /**
532
+ * The Ascendant longitude the wheel orients on, or undefined.
533
+ *
534
+ * @remarks
535
+ * The PROP wins over the payload wherever both exist: a page that passes one
536
+ * has said something the response cannot know, and silently preferring the
537
+ * response would make the prop dead on exactly the responses that carry the
538
+ * field.
539
+ */
540
+ private get effectiveAscendant(): number | undefined {
541
+ for (const value of [this.ascendant, this.payload?.ascendant?.longitude]) {
542
+ if (typeof value === 'number' && Number.isFinite(value)) return value;
543
+ }
544
+ return undefined;
545
+ }
546
+
547
+ /** True when an ascendant is available at all, so the ASC/DSC axis is a real horizon rather than one derived from a cusp. */
501
548
  private get ascendantGiven(): boolean {
502
- return (
503
- typeof this.ascendant === 'number' && Number.isFinite(this.ascendant)
504
- );
549
+ return this.effectiveAscendant !== undefined;
550
+ }
551
+
552
+ /** True when the sector ring came from the page rather than from the response, so the legend can say which. */
553
+ private get cuspsFromPage(): boolean {
554
+ return Array.isArray(this.houses);
505
555
  }
506
556
 
507
557
  /**
508
- * The supplied cusps, normalized to houses 1 to 12 in order, or null.
558
+ * The cusps to draw, normalized to houses 1 to 12 in order, or null. The prop
559
+ * first, then the ones the response carries, on the same precedence rule as
560
+ * {@link RoxyTransitWheel.effectiveAscendant}.
509
561
  *
510
562
  * @remarks
511
563
  * Sorted by house number rather than trusted in array order, and rejected
512
564
  * whole unless the twelve numbers are exactly 1 to 12 with finite longitudes.
513
565
  * A cusp set that fails either check is not a house division, and drawing part
514
566
  * of one would put a sector boundary where the host never claimed there was
515
- * one.
567
+ * one. A malformed PROP is rejected outright rather than falling through to
568
+ * the payload: the page overrode the response on purpose, and quietly drawing
569
+ * the response cusps under a bad override would be a different chart than
570
+ * either source asked for.
516
571
  */
517
572
  private get cusps(): Array<{ number: number; longitude: number }> | null {
518
- const raw = this.houses;
573
+ const raw = this.houses ?? this.payload?.houses;
519
574
  if (!Array.isArray(raw) || raw.length !== 12) return null;
520
575
  const out = raw
521
576
  .map((h, i) =>
@@ -542,9 +597,7 @@ export class RoxyTransitWheel extends RoxyDataElement<CalculateTransitAspectsRes
542
597
  * most of a sign away from the Ascendant itself.
543
598
  */
544
599
  private toAngle(longitude: number): number {
545
- const origin = this.ascendantGiven
546
- ? (this.ascendant as number)
547
- : (this.cusps?.[0]?.longitude ?? 0);
600
+ const origin = this.effectiveAscendant ?? this.cusps?.[0]?.longitude ?? 0;
548
601
  return 180 + origin - longitude;
549
602
  }
550
603
 
@@ -601,11 +654,21 @@ export class RoxyTransitWheel extends RoxyDataElement<CalculateTransitAspectsRes
601
654
  return this.t('Sign wheel, 0° Aries on the left');
602
655
  }
603
656
 
604
- /** Whether the twelve sectors on the wheel are real cusps, in words. Same dual use as {@link RoxyTransitWheel.orientationCaption}. */
657
+ /**
658
+ * Whether the twelve sectors on the wheel are real cusps, in words, and where
659
+ * they came from. Same dual use as {@link RoxyTransitWheel.orientationCaption}.
660
+ *
661
+ * @remarks
662
+ * The source is named because the caption is provenance: a reader
663
+ * reconciling this wheel against another calculator needs to know whether the
664
+ * cusps are the ones the endpoint computed the house numbers against, or a set
665
+ * the page substituted for them.
666
+ */
605
667
  private get cuspCaption(): string {
606
- return this.cusps
668
+ if (!this.cusps) return this.t('No house cusps');
669
+ return this.cuspsFromPage
607
670
  ? this.t('House cusps supplied by the page')
608
- : this.t('No house cusps');
671
+ : this.t('House cusps from the response');
609
672
  }
610
673
 
611
674
  private renderWheel(
@@ -657,7 +720,7 @@ export class RoxyTransitWheel extends RoxyDataElement<CalculateTransitAspectsRes
657
720
  return ticks;
658
721
  }
659
722
 
660
- /** Twelve sign boundaries, drawn from the inner ring outward. Solid, and always exactly 30 degrees apart: house cusps are the dashed lines from {@link RoxyTransitWheel.renderHouses} and only exist when the page supplied them. */
723
+ /** Twelve sign boundaries, drawn from the inner ring outward. Solid, and always exactly 30 degrees apart: house cusps are the dashed lines from {@link RoxyTransitWheel.renderHouses} and only exist when a cusp set is available. */
661
724
  private renderSpokes() {
662
725
  return SIGNS_ORDER.map((_, i) => {
663
726
  const angle = this.toAngle(i * 30);
@@ -668,7 +731,8 @@ export class RoxyTransitWheel extends RoxyDataElement<CalculateTransitAspectsRes
668
731
  }
669
732
 
670
733
  /**
671
- * The twelve house sectors, drawn ONLY from cusps the page supplied.
734
+ * The twelve house sectors, drawn ONLY from cusps some source stated: the ones
735
+ * the response carries, or the {@link RoxyTransitWheel.houses} override.
672
736
  *
673
737
  * @remarks
674
738
  * Dashed and inset to the sign band, because the solid spokes beside them are
@@ -677,7 +741,7 @@ export class RoxyTransitWheel extends RoxyDataElement<CalculateTransitAspectsRes
677
741
  * of its own sector, so an unequal house carries its label inside itself; the
678
742
  * hub is the one band on this wheel with nothing else in it.
679
743
  *
680
- * Nothing here is derived. With no cusps supplied this renders nothing at all
744
+ * Nothing here is derived. With no cusps available this renders nothing at all
681
745
  * rather than twelve equal sectors from the Ascendant, which would be a
682
746
  * different chart wearing the same label.
683
747
  *
@@ -832,16 +896,18 @@ export class RoxyTransitWheel extends RoxyDataElement<CalculateTransitAspectsRes
832
896
  }
833
897
 
834
898
  /**
835
- * ASC and DSC ticks, drawn ONLY when the page supplied an ascendant. Nothing
836
- * is derived: the descendant is the exact opposite point of the value given.
899
+ * ASC and DSC ticks, drawn ONLY when an ascendant is available, from the prop
900
+ * or from the response. Nothing is derived: the descendant is the exact
901
+ * opposite point of that value.
837
902
  *
838
903
  * Gated on the ascendant alone, never on the cusps. Under whole-sign the first
839
904
  * cusp is 0 degrees of the rising sign rather than the Ascendant, so labelling
840
905
  * it ASC would be wrong on exactly the charts a traditional reader casts.
841
906
  */
842
907
  private renderAxis() {
843
- if (!this.ascendantGiven) return nothing;
844
- const asc = normalizeLongitude(this.ascendant as number);
908
+ const given = this.effectiveAscendant;
909
+ if (given === undefined) return nothing;
910
+ const asc = normalizeLongitude(given);
845
911
  return [asc, oppositePoint(asc)].map((lon, i) => {
846
912
  const angle = this.toAngle(lon);
847
913
  const inner = polarToCartesian(CENTER, CENTER, OUTER_R, angle);
@@ -926,7 +992,7 @@ export class RoxyTransitWheel extends RoxyDataElement<CalculateTransitAspectsRes
926
992
  *
927
993
  * @remarks
928
994
  * The House columns are where the response's house numbers land, because the
929
- * wheel has no sectors to put them in unless the page supplied cusps. Both
995
+ * wheel has no sectors to put them in unless a cusp set is available. Both
930
996
  * columns are read against the NATAL cusps: the transiting one is the natal
931
997
  * house that body is currently passing through, which is the whole point of a
932
998
  * transit report and is why the two are not the same fact under one heading.
@@ -107,6 +107,7 @@ export const CHROME_STRINGS = [
107
107
  'First house cusp on the left horizon',
108
108
  'Sign wheel, 0° Aries on the left',
109
109
  'House cusps supplied by the page',
110
+ 'House cusps from the response',
110
111
  'No house cusps',
111
112
 
112
113
  // Transit bi-wheel: summary and the tightest contact. `Natal` and
package/src/locales/de.ts CHANGED
@@ -139,6 +139,7 @@ export const de: Record<ChromeString, string> = {
139
139
  'Spitze des ersten Hauses am linken Horizont',
140
140
  'Sign wheel, 0° Aries on the left': 'Tierkreis, 0° Widder links',
141
141
  'House cusps supplied by the page': 'Von der Seite übergebene Häuserspitzen',
142
+ 'House cusps from the response': 'Aus der Antwort übernommene Häuserspitzen',
142
143
  'No house cusps': 'Keine Häuserspitzen',
143
144
 
144
145
  'Transit aspect summary': 'Übersicht der Transitaspekte',
package/src/locales/es.ts CHANGED
@@ -139,6 +139,8 @@ export const es: Record<ChromeString, string> = {
139
139
  'Rueda de signos, 0° Aries a la izquierda',
140
140
  'House cusps supplied by the page':
141
141
  'Cúspides de casas proporcionadas por la página',
142
+ 'House cusps from the response':
143
+ 'Cúspides de casas incluidas en la respuesta',
142
144
  'No house cusps': 'Sin cúspides de casas',
143
145
 
144
146
  'Transit aspect summary': 'Resumen de aspectos de tránsito',
package/src/locales/fr.ts CHANGED
@@ -122,6 +122,7 @@ export const fr: Record<ChromeString, string> = {
122
122
  'First house cusp on the left horizon': 'Cuspide de la maison 1 à gauche',
123
123
  'Sign wheel, 0° Aries on the left': 'Roue des signes, 0° Bélier à gauche',
124
124
  'House cusps supplied by the page': 'Cuspides de maison fournies par la page',
125
+ 'House cusps from the response': 'Cuspides de maison issues de la réponse',
125
126
  'No house cusps': 'Aucune cuspide de maison',
126
127
 
127
128
  'Transit aspect summary': 'Résumé des aspects de transits',
package/src/locales/hi.ts CHANGED
@@ -144,6 +144,7 @@ export const hi: Record<ChromeString, string> = {
144
144
  'First house cusp on the left horizon': 'बाएँ क्षितिज पर प्रथम भाव की संधि',
145
145
  'Sign wheel, 0° Aries on the left': 'राशि चक्र, बाईं ओर 0° मेष',
146
146
  'House cusps supplied by the page': 'पृष्ठ से मिली भाव संधियाँ',
147
+ 'House cusps from the response': 'उत्तर से मिली भाव संधियाँ',
147
148
  'No house cusps': 'कोई भाव संधि नहीं',
148
149
 
149
150
  'Transit aspect summary': 'गोचर दृष्टि सारांश',
package/src/locales/pt.ts CHANGED
@@ -118,6 +118,7 @@ export const pt: Record<ChromeString, string> = {
118
118
  'Sign wheel, 0° Aries on the left': 'Roda zodiacal, 0° de Áries à esquerda',
119
119
  'House cusps supplied by the page':
120
120
  'Cúspides das casas fornecidas pela página',
121
+ 'House cusps from the response': 'Cúspides das casas incluídas na resposta',
121
122
  'No house cusps': 'Sem cúspides de casas',
122
123
 
123
124
  'Transit aspect summary': 'Resumo dos aspectos de trânsito',
package/src/locales/ru.ts CHANGED
@@ -122,6 +122,7 @@ export const ru: Record<ChromeString, string> = {
122
122
  'Куспид первого дома слева на горизонте',
123
123
  'Sign wheel, 0° Aries on the left': 'Зодиакальный круг, 0° Овна слева',
124
124
  'House cusps supplied by the page': 'Куспиды домов заданы страницей',
125
+ 'House cusps from the response': 'Куспиды домов из ответа',
125
126
  'No house cusps': 'Без куспидов домов',
126
127
 
127
128
  'Transit aspect summary': 'Сводка транзитных аспектов',
package/src/locales/tr.ts CHANGED
@@ -129,6 +129,7 @@ export const tr: Record<ChromeString, string> = {
129
129
  'First house cusp on the left horizon': '1. ev başlangıcı sol ufukta',
130
130
  'Sign wheel, 0° Aries on the left': 'Burç çemberi, 0° Koç solda',
131
131
  'House cusps supplied by the page': 'Sayfadan gelen ev başlangıçları',
132
+ 'House cusps from the response': 'Yanıttan gelen ev başlangıçları',
132
133
  'No house cusps': 'Ev başlangıcı yok',
133
134
 
134
135
  'Transit aspect summary': 'Transit açıları özeti',
@@ -10398,6 +10398,52 @@ export type CalculateTransitAspectsResponses = {
10398
10398
  * House system actually used for the natal cusps behind every house number in this response. Differs from the requested system only above the polar circle, where quadrant systems fall back to Whole Sign.
10399
10399
  */
10400
10400
  houseSystem: 'placidus' | 'whole-sign' | 'equal' | 'koch';
10401
+ /**
10402
+ * The twelve NATAL house cusps that every house number in this response is read against, in the house system named by houseSystem. Same shape as the natal-chart houses array, so a bi-wheel can be drawn with real house sectors from this one response instead of pairing it with a second call.
10403
+ */
10404
+ houses: Array<{
10405
+ /**
10406
+ * House number (1-12). Each house governs specific life themes in Western astrology.
10407
+ */
10408
+ number: number;
10409
+ /**
10410
+ * Ecliptic longitude of this house cusp in degrees (0-360).
10411
+ */
10412
+ longitude: number;
10413
+ /**
10414
+ * Zodiac sign on this house cusp. Colors the themes of this life area.
10415
+ */
10416
+ sign: string;
10417
+ /**
10418
+ * Degree within the zodiac sign on this cusp (0-29.999).
10419
+ */
10420
+ degree: number;
10421
+ /**
10422
+ * Zodiac sign name on this cusp in the requested language, for display only. Present only when lang is set to a language other than English, since in English it would repeat its canonical partner field exactly. Never compare against this value, compare against the canonical field beside it.
10423
+ */
10424
+ signLocalized?: string;
10425
+ }>;
10426
+ /**
10427
+ * The natal Ascendant (rising sign): the eastern horizon at birth, and the left-hand horizon a chart wheel is oriented to. Reported alongside the cusps because the two are not the same longitude in every house system: Whole Sign puts the first cusp at 0 degrees of the rising sign, which can sit most of a sign away from the Ascendant itself.
10428
+ */
10429
+ ascendant: {
10430
+ /**
10431
+ * Tropical zodiac sign on the natal Ascendant. Always English, whatever the lang parameter says. Use signLocalized for anything a reader sees.
10432
+ */
10433
+ sign: string;
10434
+ /**
10435
+ * Ascendant sign name in the requested language, for display only. Present only when lang is set to a language other than English, since in English it would repeat its canonical partner field exactly. Never compare against this value, compare against the canonical field beside it.
10436
+ */
10437
+ signLocalized?: string;
10438
+ /**
10439
+ * Degree within the Ascendant sign (0-29.999).
10440
+ */
10441
+ degree: number;
10442
+ /**
10443
+ * Absolute ecliptic longitude of the natal Ascendant in degrees (0-360).
10444
+ */
10445
+ longitude: number;
10446
+ };
10401
10447
  /**
10402
10448
  * Current transiting positions in the tropical zodiac, each placed in the natal house it is passing through. All 14 celestial bodies: the 10 classical planets (Sun through Pluto), the lunar nodes, Chiron, and Black Moon Lilith.
10403
10449
  */
package/src/version.ts CHANGED
@@ -1,2 +1,2 @@
1
1
  // Generated by scripts/sync-version.ts. Do not edit.
2
- export const ROXY_UI_VERSION = '0.25.0';
2
+ export const ROXY_UI_VERSION = '0.26.0';