@roxyapi/ui-vue 0.40.0 → 0.41.0

package/dist/types/types.gen.d.ts

@@ -4846,7 +4846,7 @@ export type KpChartResponse = {
                 planets: Array<string>;
             }>;
             /**
-             * All significators in order of strength
+             * The four levels flattened, strongest first, repeats included: a planet that reaches the house at two levels appears once per level, so the length counts level hits. The levels beside it are the per-level view.
              */
             all: Array<string>;
         }>;
@@ -4866,7 +4866,7 @@ export type KpChartResponse = {
                 houses: Array<number>;
             }>;
             /**
-             * All houses signified in order of strength
+             * The four levels flattened, strongest first, repeats included: a house appears once per level the planet reaches it at, so the length counts level hits. The levels beside it are the per-level view.
              */
             allHouses: Array<number>;
         }>;
@@ -5215,7 +5215,7 @@ export type KpSublordChangesResponse = {
      */
     endDate: string;
     /**
-     * Total Krishnamurti sublord transitions detected. Moon crosses ~14 sublords per day due to its fast motion.
+     * Total Krishnamurti sublord transitions detected. The Moon, the fastest body, crosses about 9 sublords a day.
      */
     totalChanges: number;
     /**
@@ -5227,7 +5227,7 @@ export type KpSublordChangesResponse = {
          */
         date: string;
         /**
-         * Precise sublord transition time (HH:MM, 24-hour). Refined via binary search to ~1 minute accuracy. Adjusted to requested timezone.
+         * Sublord transition time (HH:MM, 24-hour): the instant is found to the second and shown to the minute it falls in. Adjusted to requested timezone.
          */
         time: string;
         /**
@@ -5264,17 +5264,17 @@ export type KpSublordChangesRequest = {
     /**
      * Planet to track (case-insensitive). Valid values: Sun, Moon, Mars, Mercury, Jupiter, Venus, Saturn
      */
-    planet: string;
+    planet: 'Sun' | 'Moon' | 'Mars' | 'Mercury' | 'Jupiter' | 'Venus' | 'Saturn';
     /**
-     * Start date for sublord change search (YYYY-MM-DD format)
+     * First day of the search (YYYY-MM-DD), a calendar day in `timezone`.
      */
     startDate: string;
     /**
-     * End date for sublord change search (YYYY-MM-DD format)
+     * Last day of the search, inclusive (YYYY-MM-DD), a calendar day in `timezone`. Not before startDate, at most 365 days after it.
      */
     endDate: string;
     /**
-     * IANA name (e.g. "America/New_York", "Europe/London") OR decimal hours from UTC. IANA resolved to the DST-correct offset for startDate. Output times are converted to this timezone. Defaults to 0 (UTC).
+     * IANA name (e.g. "America/New_York", "Europe/London"), a fixed offset like "+05:30", OR decimal hours from UTC. One offset is taken from startDate (DST-correct for that date) and used for the whole range, so a window crossing a daylight-saving change is read on the earlier offset throughout; send a fixed offset if you need that explicit. The two dates are read as calendar days in this timezone and output times are converted to it, so one date with 5.5 is that whole Indian day. Defaults to 0 (UTC).
      */
     timezone?: number | string;
     /**
@@ -5312,7 +5312,7 @@ export type KpRasiChangesResponse = {
          */
         date: string;
         /**
-         * Precise ingress time (HH:MM, 24-hour). Calculated via binary search refinement to ~1 minute accuracy. Adjusted to requested timezone.
+         * Ingress time (HH:MM, 24-hour): the instant is found to the second and shown to the minute it falls in. Adjusted to requested timezone.
          */
         time: string;
         /**
@@ -5341,17 +5341,17 @@ export type KpRasiChangesRequest = {
     /**
      * Planet to track (case-insensitive). Valid values: Sun, Moon, Mars, Mercury, Jupiter, Venus, Saturn
      */
-    planet: string;
+    planet: 'Sun' | 'Moon' | 'Mars' | 'Mercury' | 'Jupiter' | 'Venus' | 'Saturn';
     /**
-     * Start date for sign ingress search (YYYY-MM-DD format)
+     * First day of the search (YYYY-MM-DD), a calendar day in `timezone`.
      */
     startDate: string;
     /**
-     * End date for sign ingress search (YYYY-MM-DD format)
+     * Last day of the search, inclusive (YYYY-MM-DD), a calendar day in `timezone`. Not before startDate, at most 365 days after it.
      */
     endDate: string;
     /**
-     * IANA name (e.g. "America/New_York", "Europe/London") OR decimal hours from UTC. IANA resolved to the DST-correct offset for startDate. Output times are converted to this timezone. Defaults to 0 (UTC).
+     * IANA name (e.g. "America/New_York", "Europe/London"), a fixed offset like "+05:30", OR decimal hours from UTC. One offset is taken from startDate (DST-correct for that date) and used for the whole range, so a window crossing a daylight-saving change is read on the earlier offset throughout; send a fixed offset if you need that explicit. The two dates are read as calendar days in this timezone and output times are converted to it, so one date with 5.5 is that whole Indian day. Defaults to 0 (UTC).
      */
     timezone?: number | string;
     /**
@@ -5695,7 +5695,7 @@ export type KpHoraryResponse = {
                 planets: Array<string>;
             }>;
             /**
-             * All significators in order of strength
+             * The four levels flattened, strongest first, repeats included: a planet that reaches the house at two levels appears once per level, so the length counts level hits. The levels beside it are the per-level view.
              */
             all: Array<string>;
         }>;
@@ -5715,7 +5715,7 @@ export type KpHoraryResponse = {
                 houses: Array<number>;
             }>;
             /**
-             * All houses signified in order of strength
+             * The four levels flattened, strongest first, repeats included: a house appears once per level the planet reaches it at, so the length counts level hits. The levels beside it are the per-level view.
              */
             allHouses: Array<number>;
         }>;
@@ -10274,7 +10274,7 @@ export type GetMonthlyTropicalAspectsResponses = {
              */
             aspectLocalized?: string;
             /**
-             * Whether the aspect is harmonious, challenging or neutral. Canonical English, so a calendar can colour or filter on it directly. natureLocalized carries the reader-facing form.
+             * Whether the aspect is harmonious, challenging or neutral. Canonical English, so a calendar can color or filter on it directly. natureLocalized carries the reader-facing form.
              */
             nature: string;
             /**
@@ -13505,31 +13505,31 @@ export type GetDailyHoroscopeResponses = {
          */
         date: string;
         /**
-         * General daily overview based on Moon house activation and planetary transits. Unique per sign based on whole-sign house positions.
+         * The single most relevant event of the period, whichever life area it touches, read into the whole-sign houses of this sign. The same event that leads column, at lede length rather than developed into a full movement, and checkable against the events array. Typically 30 to 60 words. Join it with love, career, health and finance for a general reading built from the six sections. Deterministic: the same sign and period always returns the same text.
          */
         overview: string;
         /**
-         * Love and relationship forecast. Based on Venus house position relative to this sign, providing unique guidance per sign.
+         * Love and relationship forecast, read into the whole-sign houses of this sign. The same ranked events that drive column, filtered to romance and partnership, plus the standing placements that reach it. Every event named here is in the events array, so a piece can be fact-checked before it runs; this section reads an event through whichever of its houses carries romance and partnership, which for an aspect between two houses can be the other one from the house the events array leads with, and both are whole-sign houses of the bodies involved counted from this sign. Typically 50 to 90 words. Render it alone for a single-topic page, or alongside the other five sections for a general reading; column is the same material woven into one piece instead of split by topic. Deterministic: the same sign and period always returns the same text.
          */
         love: string;
         /**
-         * Career and professional outlook. Based on Mars house position relative to this sign, with Saturn and Jupiter influences.
+         * Career and professional outlook, read into the whole-sign houses of this sign. The same ranked events that drive column, filtered to career, work and reputation, plus the standing placements that reach it. Every event named here is in the events array, so a piece can be fact-checked before it runs; this section reads an event through whichever of its houses carries career, work and reputation, which for an aspect between two houses can be the other one from the house the events array leads with, and both are whole-sign houses of the bodies involved counted from this sign. Typically 50 to 90 words. Render it alone for a single-topic page, or alongside the other five sections for a general reading; column is the same material woven into one piece instead of split by topic. Deterministic: the same sign and period always returns the same text.
          */
         career: string;
         /**
-         * Health, energy, and wellness guidance for the day.
+         * Health, energy, and wellness guidance, read into the whole-sign houses of this sign. The same ranked events that drive column, filtered to health, plus the standing placements that reach it. Every event named here is in the events array, so a piece can be fact-checked before it runs; this section reads an event through whichever of its houses carries health, which for an aspect between two houses can be the other one from the house the events array leads with, and both are whole-sign houses of the bodies involved counted from this sign. Typically 50 to 90 words. Render it alone for a single-topic page, or alongside the other five sections for a general reading; column is the same material woven into one piece instead of split by topic. Deterministic: the same sign and period always returns the same text.
          */
         health: string;
         /**
-         * Financial outlook and money-related guidance.
+         * Financial outlook and money-related guidance, read into the whole-sign houses of this sign. The same ranked events that drive column, filtered to finance, plus the standing placements that reach it. Every event named here is in the events array, so a piece can be fact-checked before it runs; this section reads an event through whichever of its houses carries finance, which for an aspect between two houses can be the other one from the house the events array leads with, and both are whole-sign houses of the bodies involved counted from this sign. Typically 50 to 90 words. Render it alone for a single-topic page, or alongside the other five sections for a general reading; column is the same material woven into one piece instead of split by topic. Deterministic: the same sign and period always returns the same text.
          */
         finance: string;
         /**
-         * Actionable daily advice based on the dominant transit energy.
+         * The single actionable takeaway from the leading event of the period, read into the whole-sign houses of this sign and checkable against the events array. Drawn from the same event as overview, kept to a short, actionable pair of sentences rather than grown to match the other sections. Deterministic: the same sign and period always returns the same text.
          */
         advice: string;
         /**
-         * The full column for this period, ready to run as one piece, with paragraphs separated by a blank line. Names the events driving it and the dates they fall on, read into the whole-sign houses of this sign. Typically 120 to 180 words. The six section fields are the same reading split by topic, so render either shape and never both. Deterministic: the same sign and period always returns the same column.
+         * The full column for this period, ready to run as one piece, with paragraphs separated by a blank line. Names the events driving it and the dates they fall on, read into the whole-sign houses of this sign. Typically 120 to 180 words. The six section fields read the same ranked events filtered to their own life area, each composed as a column of its own rather than an excerpt of this one, so render either shape and never both. Deterministic: the same sign and period always returns the same column.
          */
         column: string;
         /**
@@ -13578,7 +13578,7 @@ export type GetDailyHoroscopeResponses = {
          */
         compatibleSigns: Array<string>;
         /**
-         * Active planetary transits affecting this sign today, with house activations. Each transit shows the planet, its current sign, and which house it activates for the queried sign.
+         * Active planetary transits affecting this sign today, with house activations. Each transit shows the planet, its current sign, and which house it activates for the queried sign. The sign and the house phrase translate with the lang parameter; the planet name stays canonical English so a caller can match on it whatever the language.
          */
         activeTransits: Array<string>;
         /**
@@ -13736,31 +13736,31 @@ export type GetWeeklyHoroscopeResponses = {
          */
         week: string;
         /**
-         * Weekly overview highlighting the dominant planetary transits through the sign.
+         * The single most relevant event of the period, whichever life area it touches, read into the whole-sign houses of this sign. The same event that leads column, at lede length rather than developed into a full movement, and checkable against the events array. Typically 40 to 80 words. Join it with love, career, health and finance for a general reading built from the six sections. Deterministic: the same sign and period always returns the same text.
          */
         overview: string;
         /**
-         * Weekly love and relationship forecast.
+         * Weekly love and relationship forecast, read into the whole-sign houses of this sign. The same ranked events that drive column, filtered to romance and partnership, plus the standing placements that reach it. Every event named here is in the events array, so a piece can be fact-checked before it runs; this section reads an event through whichever of its houses carries romance and partnership, which for an aspect between two houses can be the other one from the house the events array leads with, and both are whole-sign houses of the bodies involved counted from this sign. Typically 80 to 120 words. Render it alone for a single-topic page, or alongside the other five sections for a general reading; column is the same material woven into one piece instead of split by topic. Deterministic: the same sign and period always returns the same text.
          */
         love: string;
         /**
-         * Weekly career and professional outlook.
+         * Weekly career and professional outlook, read into the whole-sign houses of this sign. The same ranked events that drive column, filtered to career, work and reputation, plus the standing placements that reach it. Every event named here is in the events array, so a piece can be fact-checked before it runs; this section reads an event through whichever of its houses carries career, work and reputation, which for an aspect between two houses can be the other one from the house the events array leads with, and both are whole-sign houses of the bodies involved counted from this sign. Typically 80 to 120 words. Render it alone for a single-topic page, or alongside the other five sections for a general reading; column is the same material woven into one piece instead of split by topic. Deterministic: the same sign and period always returns the same text.
          */
         career: string;
         /**
-         * Weekly health, energy, and wellness guidance.
+         * Weekly health, energy, and wellness guidance, read into the whole-sign houses of this sign. The same ranked events that drive column, filtered to health, plus the standing placements that reach it. Every event named here is in the events array, so a piece can be fact-checked before it runs; this section reads an event through whichever of its houses carries health, which for an aspect between two houses can be the other one from the house the events array leads with, and both are whole-sign houses of the bodies involved counted from this sign. Typically 80 to 120 words. Render it alone for a single-topic page, or alongside the other five sections for a general reading; column is the same material woven into one piece instead of split by topic. Deterministic: the same sign and period always returns the same text.
          */
         health: string;
         /**
-         * Weekly financial outlook.
+         * Weekly financial outlook, read into the whole-sign houses of this sign. The same ranked events that drive column, filtered to finance, plus the standing placements that reach it. Every event named here is in the events array, so a piece can be fact-checked before it runs; this section reads an event through whichever of its houses carries finance, which for an aspect between two houses can be the other one from the house the events array leads with, and both are whole-sign houses of the bodies involved counted from this sign. Typically 80 to 120 words. Render it alone for a single-topic page, or alongside the other five sections for a general reading; column is the same material woven into one piece instead of split by topic. Deterministic: the same sign and period always returns the same text.
          */
         finance: string;
         /**
-         * Actionable weekly guidance based on transit patterns.
+         * The single actionable takeaway from the leading event of the period, read into the whole-sign houses of this sign and checkable against the events array. Drawn from the same event as overview, kept to a short, actionable pair of sentences rather than grown to match the other sections. Deterministic: the same sign and period always returns the same text.
          */
         advice: string;
         /**
-         * The full column for this period, ready to run as one piece, with paragraphs separated by a blank line. Names the events driving it and the dates they fall on, read into the whole-sign houses of this sign. Typically 250 to 450 words. The six section fields are the same reading split by topic, so render either shape and never both. Deterministic: the same sign and period always returns the same column.
+         * The full column for this period, ready to run as one piece, with paragraphs separated by a blank line. Names the events driving it and the dates they fall on, read into the whole-sign houses of this sign. Typically 250 to 450 words. The six section fields read the same ranked events filtered to their own life area, each composed as a column of its own rather than an excerpt of this one, so render either shape and never both. Deterministic: the same sign and period always returns the same column.
          */
         column: string;
         /**
@@ -13951,31 +13951,31 @@ export type GetMonthlyHoroscopeResponses = {
          */
         month: string;
         /**
-         * Monthly overview covering the major planetary transits and their impact on the sign.
+         * The single most relevant event of the period, whichever life area it touches, read into the whole-sign houses of this sign. The same event that leads column, at lede length rather than developed into a full movement, and checkable against the events array. Typically 55 to 100 words. Join it with love, career, health and finance for a general reading built from the six sections. Deterministic: the same sign and period always returns the same text.
          */
         overview: string;
         /**
-         * Monthly love and relationship forecast.
+         * Monthly love and relationship forecast, read into the whole-sign houses of this sign. The same ranked events that drive column, filtered to romance and partnership, plus the standing placements that reach it. Every event named here is in the events array, so a piece can be fact-checked before it runs; this section reads an event through whichever of its houses carries romance and partnership, which for an aspect between two houses can be the other one from the house the events array leads with, and both are whole-sign houses of the bodies involved counted from this sign. Typically 120 to 200 words. Render it alone for a single-topic page, or alongside the other five sections for a general reading; column is the same material woven into one piece instead of split by topic. Deterministic: the same sign and period always returns the same text.
          */
         love: string;
         /**
-         * Monthly career and professional outlook.
+         * Monthly career and professional outlook, read into the whole-sign houses of this sign. The same ranked events that drive column, filtered to career, work and reputation, plus the standing placements that reach it. Every event named here is in the events array, so a piece can be fact-checked before it runs; this section reads an event through whichever of its houses carries career, work and reputation, which for an aspect between two houses can be the other one from the house the events array leads with, and both are whole-sign houses of the bodies involved counted from this sign. Typically 120 to 200 words. Render it alone for a single-topic page, or alongside the other five sections for a general reading; column is the same material woven into one piece instead of split by topic. Deterministic: the same sign and period always returns the same text.
          */
         career: string;
         /**
-         * Monthly health and wellness guidance.
+         * Monthly health and wellness guidance, read into the whole-sign houses of this sign. The same ranked events that drive column, filtered to health, plus the standing placements that reach it. Every event named here is in the events array, so a piece can be fact-checked before it runs; this section reads an event through whichever of its houses carries health, which for an aspect between two houses can be the other one from the house the events array leads with, and both are whole-sign houses of the bodies involved counted from this sign. Typically 120 to 200 words. Render it alone for a single-topic page, or alongside the other five sections for a general reading; column is the same material woven into one piece instead of split by topic. Deterministic: the same sign and period always returns the same text.
          */
         health: string;
         /**
-         * Monthly financial outlook and guidance.
+         * Monthly financial outlook and guidance, read into the whole-sign houses of this sign. The same ranked events that drive column, filtered to finance, plus the standing placements that reach it. Every event named here is in the events array, so a piece can be fact-checked before it runs; this section reads an event through whichever of its houses carries finance, which for an aspect between two houses can be the other one from the house the events array leads with, and both are whole-sign houses of the bodies involved counted from this sign. Typically 120 to 200 words. Render it alone for a single-topic page, or alongside the other five sections for a general reading; column is the same material woven into one piece instead of split by topic. Deterministic: the same sign and period always returns the same text.
          */
         finance: string;
         /**
-         * Actionable guidance for the month as a whole, derived from the Mercury house activation for this sign. Distinct from the per-week advice inside weekByWeek: this is the single takeaway for the month.
+         * The single actionable takeaway from the leading event of the period, read into the whole-sign houses of this sign and checkable against the events array. Drawn from the same event as overview, kept to a short, actionable pair of sentences rather than grown to match the other sections. Deterministic: the same sign and period always returns the same text.
          */
         advice: string;
         /**
-         * The full column for this period, ready to run as one piece, with paragraphs separated by a blank line. Names the events driving it and the dates they fall on, read into the whole-sign houses of this sign. Typically 400 to 700 words. The six section fields are the same reading split by topic, so render either shape and never both. Deterministic: the same sign and period always returns the same column.
+         * The full column for this period, ready to run as one piece, with paragraphs separated by a blank line. Names the events driving it and the dates they fall on, read into the whole-sign houses of this sign. Typically 400 to 700 words. The six section fields read the same ranked events filtered to their own life area, each composed as a column of its own rather than an excerpt of this one, so render either shape and never both. Deterministic: the same sign and period always returns the same column.
          */
         column: string;
         /**
@@ -14012,32 +14012,32 @@ export type GetMonthlyHoroscopeResponses = {
             through?: string;
         }>;
         /**
-         * Week-by-week breakdown with sign-specific focus areas based on transit house positions.
+         * The month read one calendar week at a time, off the same ranked events as column and events[]: the life area each week turns on, and the one thing that area asks for. Two weeks may land in the same area, because two events of a month often do; the sentence beside it is always different. Use it for the week strip of a monthly page.
          */
         weekByWeek: Array<{
             /**
-             * Week number within the month (1-4).
+             * Position of the week inside the month, 1 first. The rows are calendar weeks, Monday to Sunday, clipped to the month at each end, so a month carries four, five or six of them. Row N is therefore the same week the weekly forecast covers, which is what lets a monthly page link straight into it.
              */
             week: number;
             /**
-             * Primary focus area for this week, derived from planetary house activations for this sign.
+             * The life area the week turns on, in the requested language: the theme of the whole-sign house holding the strongest event the reading names inside that week, or of the strongest standing placement where the week holds no dated event. Same values as the life areas of the yearly key periods.
              */
             focus: string;
             /**
-             * Specific guidance for this week.
+             * What that house asks for, as one sentence in the requested language. No two weeks of one month repeat a sentence.
              */
             advice: string;
         }>;
         /**
-         * Key astrological dates this month with actual New Moon, Full Moon, and retrograde dates calculated from ephemeris data.
+         * The dates to circle this month, earliest first: every lunation and eclipse of the month, plus the headline movements the reading is built on, which are the sign changes of the slower planets and every station with the direction it turns. Each is placed in the whole-sign house it reaches for this sign. Every row is an instant the ephemeris gives, checkable against NASA JPL Horizons or the US Naval Observatory, and every row that is not a lunation or an eclipse is also a row of events[], so the list cannot contradict the reading beside it.
          */
         keyDates: Array<{
             /**
-             * Date of the astrological event (YYYY-MM-DD).
+             * UTC date of the event (YYYY-MM-DD). The exact instant, to the second, is on the matching row of events[].
              */
             date: string;
             /**
-             * Astrological event active on this date (lunar phases, retrogrades, sign ingresses).
+             * The event as one sentence in the requested language, placed in the whole-sign house it reaches for this sign.
              */
             event: string;
         }>;
@@ -14196,31 +14196,31 @@ export type GetYearlyHoroscopeResponses = {
          */
         year: number;
         /**
-         * Yearly overview, led by the single event with the most weight for this sign across the whole year.
+         * The single most relevant event of the period, whichever life area it touches, read into the whole-sign houses of this sign. The same event that leads column, at lede length rather than developed into a full movement, and checkable against the events array. Typically 70 to 120 words. Join it with love, career, health and finance for a general reading built from the six sections. Deterministic: the same sign and period always returns the same text.
          */
         overview: string;
         /**
-         * Yearly love and relationship outlook.
+         * Yearly love and relationship outlook, read into the whole-sign houses of this sign. The same ranked events that drive column, filtered to romance and partnership, plus the standing placements that reach it. Every event named here is in the events array, so a piece can be fact-checked before it runs; this section reads an event through whichever of its houses carries romance and partnership, which for an aspect between two houses can be the other one from the house the events array leads with, and both are whole-sign houses of the bodies involved counted from this sign. Typically 150 to 260 words. Render it alone for a single-topic page, or alongside the other five sections for a general reading; column is the same material woven into one piece instead of split by topic. Deterministic: the same sign and period always returns the same text.
          */
         love: string;
         /**
-         * Yearly career and professional outlook.
+         * Yearly career and professional outlook, read into the whole-sign houses of this sign. The same ranked events that drive column, filtered to career, work and reputation, plus the standing placements that reach it. Every event named here is in the events array, so a piece can be fact-checked before it runs; this section reads an event through whichever of its houses carries career, work and reputation, which for an aspect between two houses can be the other one from the house the events array leads with, and both are whole-sign houses of the bodies involved counted from this sign. Typically 150 to 260 words. Render it alone for a single-topic page, or alongside the other five sections for a general reading; column is the same material woven into one piece instead of split by topic. Deterministic: the same sign and period always returns the same text.
          */
         career: string;
         /**
-         * Yearly health, energy, and wellness outlook.
+         * Yearly health, energy, and wellness outlook, read into the whole-sign houses of this sign. The same ranked events that drive column, filtered to health, plus the standing placements that reach it. Every event named here is in the events array, so a piece can be fact-checked before it runs; this section reads an event through whichever of its houses carries health, which for an aspect between two houses can be the other one from the house the events array leads with, and both are whole-sign houses of the bodies involved counted from this sign. Typically 150 to 260 words. Render it alone for a single-topic page, or alongside the other five sections for a general reading; column is the same material woven into one piece instead of split by topic. Deterministic: the same sign and period always returns the same text.
          */
         health: string;
         /**
-         * Yearly financial outlook.
+         * Yearly financial outlook, read into the whole-sign houses of this sign. The same ranked events that drive column, filtered to finance, plus the standing placements that reach it. Every event named here is in the events array, so a piece can be fact-checked before it runs; this section reads an event through whichever of its houses carries finance, which for an aspect between two houses can be the other one from the house the events array leads with, and both are whole-sign houses of the bodies involved counted from this sign. Typically 150 to 260 words. Render it alone for a single-topic page, or alongside the other five sections for a general reading; column is the same material woven into one piece instead of split by topic. Deterministic: the same sign and period always returns the same text.
          */
         finance: string;
         /**
-         * The single takeaway for the year, drawn from the event that leads it rather than stated in general terms.
+         * The single actionable takeaway from the leading event of the period, read into the whole-sign houses of this sign and checkable against the events array. Drawn from the same event as overview, kept to a short, actionable pair of sentences rather than grown to match the other sections. Deterministic: the same sign and period always returns the same text.
          */
         advice: string;
         /**
-         * The full column for this period, ready to run as one piece, with paragraphs separated by a blank line. Names the events driving it and the dates they fall on, read into the whole-sign houses of this sign. Typically 600 to 900 words. The six section fields are the same reading split by topic, so render either shape and never both. Deterministic: the same sign and period always returns the same column.
+         * The full column for this period, ready to run as one piece, with paragraphs separated by a blank line. Names the events driving it and the dates they fall on, read into the whole-sign houses of this sign. Typically 600 to 900 words. The six section fields read the same ranked events filtered to their own life area, each composed as a column of its own rather than an excerpt of this one, so render either shape and never both. Deterministic: the same sign and period always returns the same column.
          */
         column: string;
         /**
@@ -16945,6 +16945,10 @@ export type GetCurrentDashaData = {
          * Lunar node type for Rahu and Ketu, used ONLY when "significators" is true. Dasha dates themselves come from the Moon and never move with this field. "mean" uses the smooth mean node (traditional default). "true" uses the osculating node, which swings up to 1.5 degrees either side of mean over a 173-day cycle and can therefore change which house or star a node falls in. Defaults to "mean".
          */
         nodeType?: 'mean' | 'true';
+        /**
+         * ISO 8601 datetime (YYYY-MM-DDTHH:MM:SS) to read the running periods at, for a reading prepared for a future day, a backtest, or a chart cast for a past moment. Defaults to the current instant. Interpreted as local time in the request timezone (a trailing Z is accepted but ignored); with timezone 0 it is UTC.
+         */
+        datetime?: string;
     };
     path?: never;
     query?: {
@@ -20225,7 +20229,7 @@ export type GetVedicDailyReadingResponses = {
          */
         areas: {
             /**
-             * The finance area: the positive house group 2, 5, 11 netted against the negative group 6, 8, 12, read off the lords of the running dasha, bhukti and antara, because that is the KP rule for when a matter fructifies, plus the natal basis the day is read against. ALWAYS AN OBJECT. Above latitude 66.56 the six netted members are null, because the Placidus cusps behind the significators have no solution there, while natal is still populated because it is a property of the birth chart and needs no cusps; the reading also still carries its gochara, panchanga and dasha and names the omission in degraded. The two house groups are Krishnamurti Paddhati practice, but the NET is a KP practitioner convention rather than a classical operation: the KP sources that carry these groups use them as a promise test and an avoidance test, never as arithmetic. The groups also vary by author, and TWO houses are live disagreements rather than one. The 6th: some KP authors place it on the POSITIVE side as service income and salary, the exact opposite of the assignment used here. The 5th: it is named as a speculative GAIN house in the same KP sources that elsewhere call it a negation house, reading it as the 12th from the 6th and therefore loss of earning capacity, and both readings appear in one publication. The 1st is treated as a negation house by some authors on the same logic, as the 12th from the 2nd, and is not on either side here. This is a six house net and it is NOT the focus=finance lens, which re-reads all twelve bhavas in money vocabulary and moves no number. The two are orthogonal and both ship.
+             * The finance area: the positive house group 2, 5, 11 netted against the negative group 6, 8, 12, read off the lords of the running dasha, bhukti and antara, because that is the KP rule for when a matter fructifies, plus the natal basis the day is read against. ALWAYS AN OBJECT. Above latitude 66.56 the seven netted members are null, because the Placidus cusps behind the significators have no solution there, while natal is still populated because it is a property of the birth chart and needs no cusps; the reading also still carries its gochara, panchanga and dasha and names the omission in degraded. The two house groups are Krishnamurti Paddhati practice, but the NET is a KP practitioner convention rather than a classical operation: the KP sources that carry these groups use them as a promise test and an avoidance test, never as arithmetic. The groups also vary by author, and TWO houses are live disagreements rather than one. The 6th: some KP authors place it on the POSITIVE side as service income and salary, the exact opposite of the assignment used here. The 5th: it is named as a speculative GAIN house in the same KP sources that elsewhere call it a negation house, reading it as the 12th from the 6th and therefore loss of earning capacity, and both readings appear in one publication. The 1st is treated as a negation house by some authors on the same logic, as the 12th from the 2nd, and is not on either side here. This is a six house net and it is NOT the focus=finance lens, which re-reads all twelve bhavas in money vocabulary and moves no number. The two are orthogonal and both ship.
              */
             finance: {
                 /**
@@ -20295,7 +20299,37 @@ export type GetVedicDailyReadingResponses = {
                     dashaLevels: Array<'mahadasha' | 'antardasha' | 'pratyantardasha'>;
                 }> | null;
                 /**
-                 * The natal basis of this area: whether the chart is wealthy AT ALL, as the four classical wealth and poverty verdicts dhana, daridra, lakshmi, dhanamalika, each with the evidence that decided it. A PROPERTY OF THE BIRTH CHART AND NOT OF THE DAY, so it is the same block on every date this native is ever read for, which is exactly why it is CONTEXT rather than a term: it deliberately does not enter score, verdict, tally or evaluated, above or here. Folding a constant into a per-day number would shift every day by the identical amount, carrying no information into the only comparison those numbers support, and it would break the published closed form that makes the top-level score reproducible by hand from grahas alone. Read it as the standing question the day is being read against. The verdicts are the same ones POST /yoga/detect and POST /birth-chart return for this chart, computed in the Lahiri natal frame rather than in the KP-Newcomb frame the significators above use. PRESENT AT EVERY LATITUDE, including above the polar circle: these verdicts need only whole-sign houses from the Lagna, so nothing about them depends on the cusps the KP members above lose there.
+                 * The equal-weight mean of the three day-level layer scores printed beside it, recomputable as round((day + finance + natal) / 3). WHICH LAYER IS WHICH: "day" is the top-level score of this reading, "finance" is areas.finance.score above, and "natal" is the share of the natal wealth yoga rows that speak for the native, positive yogas present plus negative yogas absent over the rows evaluated, so it is 0, 25, 50, 75 or 100. Equal weights are a RoxyAPI convention: no classical authority weights the natal chart, the running dasha and the transiting sky against each other, so the three are averaged as they are and printed beside the result, and the band uses the same ladder as verdict. The composite measures how much of this reading backs the native on this day and never the outcome of any matter: read it as support, not as a prediction. NULL IN TWO CASES, and neither is a low score. Null when the running lords reach none of the six houses, because an absence of connection is not a verdict and must not be averaged as one. Null above latitude 66.56, where the Placidus cusps the KP significators are read from have no solution: the question does not apply there rather than the answer being no, so never render it as zero or as a weak verdict. The natal block beside it is unaffected and still ships, and degraded names areas.finance.score.
+                 */
+                composite: {
+                    /**
+                     * The mean itself, 0 to 100, rounded. Every term is printed in the layers below, so the division can be redone rather than trusted.
+                     */
+                    score: number;
+                    /**
+                     * The band the composite falls in, on the same ladder the top-level verdict uses: "very-strong" at 75 and above, "strong" at 50 and above, "moderate" at 25 and above, "weak" below 25.
+                     */
+                    band: 'very-strong' | 'strong' | 'moderate' | 'weak';
+                    /**
+                     * The three terms of the mean, always in the order day, finance, natal. Published so a caller who wants different weights can apply them to these same three numbers instead of asking for a second reading.
+                     */
+                    layers: Array<{
+                        /**
+                         * Which term this row carries: "day" the top-level score of this reading, "finance" the KP net score in this area, "natal" the natal wealth count. Canonical English machine value, so it stays safe to switch on in code.
+                         */
+                        layer: 'day' | 'finance' | 'natal';
+                        /**
+                         * The term that went into the mean, 0 to 100. Each one is either printed elsewhere in this response or counted off a block that is, so no number enters the average unseen.
+                         */
+                        score: number;
+                        /**
+                         * Where that one term lands on its own, on the same ladder as the composite band above: "very-strong" at 75 and above, "strong" at 50 and above, "moderate" at 25 and above, "weak" below 25.
+                         */
+                        band: 'very-strong' | 'strong' | 'moderate' | 'weak';
+                    }>;
+                } | null;
+                /**
+                 * The natal basis of this area: whether the chart is wealthy AT ALL, as the four classical wealth and poverty verdicts dhana, daridra, lakshmi, dhanamalika, each with the evidence that decided it. A PROPERTY OF THE BIRTH CHART AND NOT OF THE DAY, so it is the same block on every date this native is ever read for, which is exactly why it is CONTEXT rather than a term: it deliberately does not enter score, verdict, tally or evaluated, above or here, and the one number it does enter is the composite beside it, where it is printed as its own layer rather than folded in. Folding a constant into a per-day number would shift every day by the identical amount, carrying no information into the only comparison those numbers support, and it would break the published closed form that makes the top-level score reproducible by hand from grahas alone. Read it as the standing question the day is being read against. The verdicts are the same ones POST /yoga/detect and POST /birth-chart return for this chart, computed in the Lahiri natal frame rather than in the KP-Newcomb frame the significators above use. PRESENT AT EVERY LATITUDE, including above the polar circle: these verdicts need only whole-sign houses from the Lagna, so nothing about them depends on the cusps the KP members above lose there.
                  */
                 natal: Array<{
                     /**
@@ -20351,7 +20385,7 @@ export type GetVedicDailyReadingResponses = {
          */
         degraded: Array<{
             /**
-             * Which part of the reading this location or date could not supply. "areas.finance.score" names the KP net by the member it is read through: the finance area itself always ships and its natal block is always populated, and it is the six netted members that are null.
+             * Which part of the reading this location or date could not supply. "areas.finance.score" names the KP net by the member it is read through: the finance area itself always ships and its natal block is always populated, and it is the seven netted members that are null.
              */
             component: 'dayStart' | 'dayEnd' | 'areas.finance.score';
             /**
@@ -21221,7 +21255,7 @@ export type GetDetailedPanchangResponses = {
             endsAt: string | null;
         };
         /**
-         * Panchang element transition times. exact timing of when each element (tithi, yoga, karana, nakshatra, Moon sign) changes. Calculated using binary search for ~1 minute precision. Essential for precise muhurta determination and panchang calendars.
+         * Panchang element transition times: when each element (tithi, yoga, karana, nakshatra, Moon sign) changes, found to the second. Essential for precise muhurta determination and panchang calendars.
          */
         transitions: {
             /**
@@ -22248,19 +22282,6 @@ export type GetYogaErrors = {
          */
         code: string;
     };
-    /**
-     * Yoga not found
-     */
-    404: {
-        /**
-         * Human-readable error message. The wording may change, so do not parse it programmatically. Switch on the stable code instead.
-         */
-        error: string;
-        /**
-         * Machine-readable error code. Stable identifier for programmatic error handling.
-         */
-        code: string;
-    };
     /**
      * Method not allowed. The path exists but only responds to the methods listed in `allow[]` and the `Allow` response header.
      */
@@ -25608,19 +25629,6 @@ export type GetRashiErrors = {
          */
         code: string;
     };
-    /**
-     * Rashi not found
-     */
-    404: {
-        /**
-         * Human-readable error message. The wording may change, so do not parse it programmatically. Switch on the stable code instead.
-         */
-        error: string;
-        /**
-         * Machine-readable error code. Stable identifier for programmatic error handling.
-         */
-        code: string;
-    };
     /**
      * Method not allowed. The path exists but only responds to the methods listed in `allow[]` and the `Allow` response header.
      */
@@ -25866,19 +25874,6 @@ export type GetNakshatraErrors = {
          */
         code: string;
     };
-    /**
-     * Nakshatra not found
-     */
-    404: {
-        /**
-         * Human-readable error message. The wording may change, so do not parse it programmatically. Switch on the stable code instead.
-         */
-        error: string;
-        /**
-         * Machine-readable error code. Stable identifier for programmatic error handling.
-         */
-        code: string;
-    };
     /**
      * Method not allowed. The path exists but only responds to the methods listed in `allow[]` and the `Allow` response header.
      */
@@ -26499,19 +26494,6 @@ export type GetAvasthaErrors = {
          */
         code: string;
     };
-    /**
-     * No avastha state matches that slug.
-     */
-    404: {
-        /**
-         * Human-readable error message. The wording may change, so do not parse it programmatically. Switch on the stable code instead.
-         */
-        error: string;
-        /**
-         * Machine-readable error code. Stable identifier for programmatic error handling.
-         */
-        code: string;
-    };
     /**
      * Method not allowed. The path exists but only responds to the methods listed in `allow[]` and the `Allow` response header.
      */
@@ -43730,7 +43712,7 @@ export type CalculateEntrancePadaResponses = {
              */
             id: string;
             /**
-             * Display name of the devata, with the diacritics the transliteration carries.
+             * Display name of the devata. A Sanskrit proper noun: romanised with the diacritics the transliteration carries in every language, and written in Devanagari as the Sanskrit text prints it when lang is hi. Compare on id, never on this.
              */
             name: string;
             /**
@@ -43981,7 +43963,7 @@ export type GenerateMandalaResponses = {
              */
             devata?: string;
             /**
-             * Display name of that devata, with the diacritics the transliteration carries. Present only on the 81 pada grid.
+             * Display name of that devata. A Sanskrit proper noun: romanised with the diacritics the transliteration carries in every language, and written in Devanagari as the Sanskrit text prints it when lang is hi. Present only on the 81 pada grid.
              */
             devataName?: string;
             /**
@@ -45324,9 +45306,9 @@ export type CalculateRoomComplianceResponses = {
              */
             reading: string;
             /**
-             * What to do when the room is not where it belongs. Original prose, translated in place when lang is set.
+             * What to do when the room is not where it belongs. Present when the verdict is acceptable or avoid, and absent on an ideal placement, which has nothing to fix. Original prose, translated in place when lang is set.
              */
-            remedy: string;
+            remedy?: string;
             /**
              * Where a verdict comes from: a chapter and verse of a named public-domain edition, or the literal convention with the practice it rests on. Every verdict in this domain carries one.
              */
@@ -45934,7 +45916,7 @@ export type ListDikpalaDirectionsResponses = {
              */
             id: string;
             /**
-             * The lord of this quarter of the horizon, per Brihat Samhita 54.3. Always English transliteration, safe to compare against. These are NOT the 45 mandala devatas and the two sets must not be merged: Agni is the north-east mandala square and the south-east dikpala.
+             * The lord of this quarter of the horizon, per Brihat Samhita 54.3. A Sanskrit proper noun: romanised with the diacritics the transliteration carries in every language, and written in Devanagari as the Sanskrit text prints it when lang is hi. Compare on id, never on this. These are NOT the 45 mandala devatas and the two sets must not be merged: Agni is the north-east mandala square and the south-east dikpala.
              */
             dikpala: string;
             /**
@@ -45962,7 +45944,7 @@ export type ListDikpalaDirectionsResponses = {
                  */
                 id: string;
                 /**
-                 * Display name of the devata, with the diacritics the transliteration carries.
+                 * Display name of the devata. A Sanskrit proper noun: romanised with the diacritics the transliteration carries in every language, and written in Devanagari as the Sanskrit text prints it when lang is hi.
                  */
                 name: string;
             }>;
@@ -46095,19 +46077,6 @@ export type GetDikpalaDirectionErrors = {
          */
         code: string;
     };
-    /**
-     * No direction with that id
-     */
-    404: {
-        /**
-         * Human-readable error message. The wording may change, so do not parse it programmatically. Switch on the stable code instead.
-         */
-        error: string;
-        /**
-         * Machine-readable error code. Stable identifier for programmatic error handling.
-         */
-        code: string;
-    };
     /**
      * Method not allowed. The path exists but only responds to the methods listed in `allow[]` and the `Allow` response header.
      */
@@ -46161,7 +46130,7 @@ export type GetDikpalaDirectionResponses = {
          */
         id: string;
         /**
-         * The lord of this quarter of the horizon, per Brihat Samhita 54.3. Always English transliteration, safe to compare against. These are NOT the 45 mandala devatas and the two sets must not be merged: Agni is the north-east mandala square and the south-east dikpala.
+         * The lord of this quarter of the horizon, per Brihat Samhita 54.3. A Sanskrit proper noun: romanised with the diacritics the transliteration carries in every language, and written in Devanagari as the Sanskrit text prints it when lang is hi. Compare on id, never on this. These are NOT the 45 mandala devatas and the two sets must not be merged: Agni is the north-east mandala square and the south-east dikpala.
          */
         dikpala: string;
         /**
@@ -46189,7 +46158,7 @@ export type GetDikpalaDirectionResponses = {
              */
             id: string;
             /**
-             * Display name of the devata, with the diacritics the transliteration carries.
+             * Display name of the devata. A Sanskrit proper noun: romanised with the diacritics the transliteration carries in every language, and written in Devanagari as the Sanskrit text prints it when lang is hi.
              */
             name: string;
         }>;
@@ -46393,7 +46362,7 @@ export type ListDevatasResponses = {
              */
             id: string;
             /**
-             * Display name of the devata, with the diacritics the transliteration carries. A Sanskrit proper noun, so it stays as it is in every language.
+             * Display name of the devata. A Sanskrit proper noun: romanised with the diacritics the transliteration carries in every language, and written in Devanagari as the Sanskrit text prints it when lang is hi. Compare on id, never on this.
              */
             name: string;
             /**
@@ -46561,19 +46530,6 @@ export type GetDevataErrors = {
          */
         code: string;
     };
-    /**
-     * No devata with that id
-     */
-    404: {
-        /**
-         * Human-readable error message. The wording may change, so do not parse it programmatically. Switch on the stable code instead.
-         */
-        error: string;
-        /**
-         * Machine-readable error code. Stable identifier for programmatic error handling.
-         */
-        code: string;
-    };
     /**
      * Method not allowed. The path exists but only responds to the methods listed in `allow[]` and the `Allow` response header.
      */
@@ -46627,7 +46583,7 @@ export type GetDevataResponses = {
          */
         id: string;
         /**
-         * Display name of the devata, with the diacritics the transliteration carries. A Sanskrit proper noun, so it stays as it is in every language.
+         * Display name of the devata. A Sanskrit proper noun: romanised with the diacritics the transliteration carries in every language, and written in Devanagari as the Sanskrit text prints it when lang is hi. Compare on id, never on this.
          */
         name: string;
         /**
@@ -53429,19 +53385,6 @@ export type GetSephirahErrors = {
          */
         code: string;
     };
-    /**
-     * No sephirah carries that identifier.
-     */
-    404: {
-        /**
-         * Human-readable error message. The wording may change, so do not parse it programmatically. Switch on the stable code instead.
-         */
-        error: string;
-        /**
-         * Machine-readable error code. Stable identifier for programmatic error handling.
-         */
-        code: string;
-    };
     /**
      * Method not allowed. The path exists but only responds to the methods listed in `allow[]` and the `Allow` response header.
      */
@@ -53898,19 +53841,6 @@ export type GetHebrewLetterErrors = {
          */
         code: string;
     };
-    /**
-     * No letter carries that identifier.
-     */
-    404: {
-        /**
-         * Human-readable error message. The wording may change, so do not parse it programmatically. Switch on the stable code instead.
-         */
-        error: string;
-        /**
-         * Machine-readable error code. Stable identifier for programmatic error handling.
-         */
-        code: string;
-    };
     /**
      * Method not allowed. The path exists but only responds to the methods listed in `allow[]` and the `Allow` response header.
      */