@roxyapi/ui 0.38.0 → 0.39.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.
- package/AGENTS.md +4 -4
- package/README.md +4 -4
- package/components-catalog.json +207 -153
- package/dist/cdn/components/endpoint-form.js +1 -1
- package/dist/cdn/components/endpoint-form.js.map +1 -1
- package/dist/cdn/components/hexagram.js +2 -2
- package/dist/cdn/components/hexagram.js.map +2 -2
- package/dist/cdn/components/vastu-mandala.js +5 -5
- package/dist/cdn/components/vastu-mandala.js.map +3 -3
- package/dist/cdn/roxy-ui.js +19 -19
- package/dist/cdn/roxy-ui.js.map +3 -3
- package/dist/components/endpoint-form.js +1 -1
- package/dist/components/endpoint-form.js.map +1 -1
- package/dist/components/hexagram.d.ts +5 -4
- package/dist/components/hexagram.d.ts.map +1 -1
- package/dist/components/hexagram.js +1 -1
- package/dist/components/hexagram.js.map +2 -2
- package/dist/components/vastu-mandala.d.ts +13 -0
- package/dist/components/vastu-mandala.d.ts.map +1 -1
- package/dist/components/vastu-mandala.js +4 -4
- package/dist/components/vastu-mandala.js.map +3 -3
- package/dist/generated/endpoint-bindings.d.ts.map +1 -1
- package/dist/generated/tool-components.d.ts.map +1 -1
- package/dist/index.cjs +16 -16
- package/dist/index.cjs.map +3 -3
- package/dist/index.js +19 -19
- package/dist/index.js.map +3 -3
- package/dist/schemas/get--feng-shui-bagua.json +1 -1
- package/dist/schemas/get--feng-shui-flying-stars-stars.json +1 -1
- package/dist/schemas/post--vastu-entrance.json +1 -1
- package/dist/styles/themes/practitioner.css +5 -5
- package/dist/types/types.gen.d.ts +182 -62
- package/dist/types/types.gen.d.ts.map +1 -1
- package/dist/version.d.ts +1 -1
- package/package.json +1 -1
- package/src/components/hexagram.ts +29 -24
- package/src/components/vastu-mandala.ts +38 -5
- package/src/generated/endpoint-bindings.ts +54 -0
- package/src/generated/tool-components.ts +45 -0
- package/src/manifest.ts +4 -4
- package/src/styles/themes/practitioner.css +5 -5
- package/src/types/types.gen.ts +182 -62
- package/src/version.ts +1 -1
|
@@ -1,7 +1,7 @@
|
|
|
1
1
|
{
|
|
2
2
|
"version": 3,
|
|
3
3
|
"sources": ["../../src/components/hexagram.ts", "../../src/utils/string.ts", "../../src/tokens/index.ts", "../../src/utils/base-element.ts", "../../src/i18n/localized-element.ts", "../../src/i18n/lang.ts", "../../src/i18n/registry.ts", "../../src/i18n/locale-controller.ts", "../../src/utils/base-styles.ts", "../../src/utils/compact.ts", "../../src/utils/key-guard.ts", "../../src/utils/fetch-controller.ts", "../../src/utils/interp-accordion.ts", "../../src/utils/disclosure.ts", "../../src/utils/markup-data.ts"],
|
|
4
|
-
"sourcesContent": ["import { css, html, nothing, svg } from 'lit';\nimport { customElement } from 'lit/decorators.js';\nimport { trigramGlyph } from '../tokens/index.js';\nimport type {\n\tCastReadingResponse,\n\tGetDailyHexagramResponse,\n\tGetHexagramResponse,\n\tGetRandomHexagramResponse,\n\tHexagram,\n\tLookupHexagramResponse,\n} from '../types/index.js';\nimport { RoxyDataElement } from '../utils/base-element.js';\nimport { baseStyles } from '../utils/base-styles.js';\nimport { disclosureStyles } from '../utils/disclosure.js';\nimport {\n\ttype InterpSection,\n\tinterpAccordionStyles,\n} from '../utils/interp-accordion.js';\n\ntype HexagramData =\n\t| GetHexagramResponse\n\t| GetRandomHexagramResponse\n\t| LookupHexagramResponse\n\t| GetDailyHexagramResponse\n\t| CastReadingResponse;\n\n/**\n * I Ching hexagram card. Renders /iching/hexagrams/{number}, /iching/cast,\n * /iching/daily, /iching/daily/cast.\n *\n * @remarks\n * **There is deliberately no `mode` input.** Which of the four shapes arrived is\n * shape-detected from the payload in {@link RoxyHexagram.resolveHexagram}, which\n * is the rule for every multi-endpoint component here: an attribute and a\n * response can disagree, and only one of them is the reading. A `mode` property\n * shipped anyway, reflected and typed into both framework wrappers, and nothing\n * ever read it.\n */\n@customElement('roxy-hexagram')\nexport class RoxyHexagram extends RoxyDataElement<HexagramData> {\n\tstatic styles = [\n\t\tbaseStyles,\n\t\tdisclosureStyles,\n\t\tinterpAccordionStyles,\n\t\tcss`.card{background:var(--roxy-surface,#fff);border:1px solid var(--roxy-border,#e4e4e7);border-radius:var(--roxy-radius-md,8px);padding:var(--roxy-space-lg,1.5rem);box-shadow:var(--roxy-shadow-sm);gap:var(--roxy-space-lg,1.5rem);grid-template-columns:6rem 1fr;display:grid}@container (width<=480px){.card{grid-template-columns:1fr}}.glyphs{gap:var(--roxy-space-md,1rem);align-content:start;align-self:start;justify-items:center;display:grid}.symbol{color:var(--roxy-accent-ink,#b45309);font-size:3rem;line-height:1}.lines{gap:4px;width:4rem;display:grid}.line{justify-content:center;align-items:center;gap:4px;height:8px;display:flex}.seg{background:var(--roxy-fg,#0a0a0a);border-radius:1px;height:6px;display:block}.line.broken .seg{width:1.4rem}.line.solid .seg{width:3rem}.line.changing .seg{background:var(--roxy-accent,#f59e0b)}.title{font-size:var(--roxy-text-xl,1.5rem);font-weight:var(--roxy-weight-bold,600);letter-spacing:var(--roxy-tracking-tight);margin:0}.subtitle{color:var(--roxy-muted,#71717a);font-size:var(--roxy-text-sm,.875rem);margin:0 0 var(--roxy-space-sm,.5rem)}.trigrams{gap:var(--roxy-space-md,1rem);margin-bottom:var(--roxy-space-sm,.5rem);color:var(--roxy-secondary,#475569);font-size:var(--roxy-text-xs,.75rem);text-transform:uppercase;letter-spacing:.06em;display:flex}.tri-glyph{font-size:var(--roxy-text-xl,1.5rem);color:var(--roxy-accent-ink,#b45309);vertical-align:middle;margin-right:4px}.judgment,.image,.message{margin:0 0 var(--roxy-space-sm,.5rem);font-size:var(--roxy-text-sm,.875rem);color:var(--roxy-fg,#0a0a0a)}.judgment:before{content:\"Judgment. \";font-weight:var(--roxy-weight-bold,600);color:var(--roxy-secondary,#475569)}.image:before{content:\"Image. \";font-weight:var(--roxy-weight-bold,600);color:var(--roxy-secondary,#475569)}.line-meaning{padding-left:var(--roxy-space-sm,.5rem);border-left:2px solid var(--roxy-border,#e4e4e7);color:var(--roxy-muted,#71717a);margin:0}.changing{margin-top:var(--roxy-space-md,1rem);padding-top:var(--roxy-space-md,1rem);border-top:1px solid var(--roxy-border,#e4e4e7);color:var(--roxy-accent-ink,#b45309);font-size:var(--roxy-text-sm,.875rem)}`,\n\t];\n\n\tprivate resolveHexagram(): {\n\t\thex: Hexagram;\n\t\tlines?: number[];\n\t\tchangingLinePositions?: number[];\n\t\tdailyMessage?: string;\n\t\tresultingHexagram?: Hexagram;\n\t} | null {\n\t\tconst d = this.data;\n\t\tif (!d) return null;\n\t\tif ('hexagram' in d && d.hexagram) {\n\t\t\tif ('lines' in d) {\n\t\t\t\tconst cast = d as CastReadingResponse;\n\t\t\t\treturn {\n\t\t\t\t\thex: cast.hexagram as Hexagram,\n\t\t\t\t\tlines: cast.lines,\n\t\t\t\t\tchangingLinePositions: cast.changingLinePositions,\n\t\t\t\t\tresultingHexagram: cast.resultingHexagram as Hexagram | undefined,\n\t\t\t\t};\n\t\t\t}\n\t\t\tconst daily = d as GetDailyHexagramResponse;\n\t\t\treturn {\n\t\t\t\thex: daily.hexagram as Hexagram,\n\t\t\t\tdailyMessage: daily.dailyMessage,\n\t\t\t};\n\t\t}\n\t\treturn { hex: d as Hexagram };\n\t}\n\n\tprotected renderData() {\n\t\tconst resolved = this.resolveHexagram();\n\t\tif (!resolved) return this.renderEmpty();\n\n\t\tconst {\n\t\t\thex: h,\n\t\t\tlines: castLines,\n\t\t\tchangingLinePositions,\n\t\t\tdailyMessage,\n\t\t\tresultingHexagram,\n\t\t} = resolved;\n\t\tconst lines = castLines ?? this.derivedLines(h);\n\t\tconst changing = new Set(changingLinePositions ?? []);\n\n\t\tconst readings = !this.hideReadings;\n\n\t\treturn html`<article class=\"card\" part=\"card\" aria-label=\"${this.t('I Ching hexagram')}\"><div class=\"glyphs\" part=\"chart\">${h.symbol ? html`<div class=\"symbol\">${h.symbol}</div>` : nothing}<div class=\"lines\" aria-hidden=\"true\">${lines\n\t\t\t\t\t\t.slice()\n\t\t\t\t\t\t.reverse()\n\t\t\t\t\t\t.map((l, idx) => {\n\t\t\t\t\t\t\t// reverse so visual top is line 6\n\t\t\t\t\t\t\tconst realIdx = lines.length - 1 - idx + 1;\n\t\t\t\t\t\t\tconst isChanging = changing.has(realIdx);\n\t\t\t\t\t\t\tconst broken = l === 6 || l === 8;\n\t\t\t\t\t\t\tconst cls = `${broken ? 'broken' : 'solid'}${isChanging ? ' changing' : ''}`;\n\t\t\t\t\t\t\treturn html`<div class=\"line ${cls}\">${\n\t\t\t\t\t\t\t\t\tbroken\n\t\t\t\t\t\t\t\t\t\t? svg`<span class=\"seg\"></span><span class=\"seg\"></span>`\n\t\t\t\t\t\t\t\t\t\t: svg`<span class=\"seg\"></span>`\n\t\t\t\t\t\t\t\t}</div>`;\n\t\t\t\t\t\t})}</div></div><div part=\"header\"><h2 class=\"title\">${\n\t\t\t\t\t\t// One text node, not two. The markup minifier collapses the space\n\t\t\t\t\t\t// between adjacent template expressions, which rendered the title as\n\t\t\t\t\t\t// \"30.The Clinging\" with the separator eaten. Join in JS instead.\n\t\t\t\t\t\t[\n\t\t\t\t\t\t\th.number != null ? `${h.number}.` : '',\n\t\t\t\t\t\t\th.english ?? h.chinese ?? 'Hexagram',\n\t\t\t\t\t\t]\n\t\t\t\t\t\t\t.filter(Boolean)\n\t\t\t\t\t\t\t.join(' ')\n\t\t\t\t\t}</h2><p class=\"subtitle\">${h.chinese ? html`${h.chinese}` : nothing} ${h.pinyin ? html`· ${h.pinyin}` : nothing}</p><div class=\"trigrams\" part=\"details\">${\n\t\t\t\t\t\th.upperTrigram\n\t\t\t\t\t\t\t? html`<div>${this.t('Upper')} <span class=\"tri-glyph\">${trigramGlyph(h.upperTrigram) ?? ''}</span>${h.upperTrigram}</div>`\n\t\t\t\t\t\t\t: nothing\n\t\t\t\t\t} ${\n\t\t\t\t\t\th.lowerTrigram\n\t\t\t\t\t\t\t? html`<div>${this.t('Lower')} <span class=\"tri-glyph\">${trigramGlyph(h.lowerTrigram) ?? ''}</span>${h.lowerTrigram}</div>`\n\t\t\t\t\t\t\t: nothing\n\t\t\t\t\t}</div>${\n\t\t\t\t\t// The Judgment and the Image are the written oracle of the figure, so\n\t\t\t\t\t// they go with the readings; the figure, the trigrams and which lines\n\t\t\t\t\t// are moving are what stays.\n\t\t\t\t\th.judgment && readings\n\t\t\t\t\t\t? html`<p class=\"judgment\">${h.judgment}</p>`\n\t\t\t\t\t\t: nothing\n\t\t\t\t} ${h.image && readings ? html`<p class=\"image\">${h.image}</p>` : nothing} ${dailyMessage && readings ? html`<p class=\"message\">${dailyMessage}</p>` : nothing} ${\n\t\t\t\t\th.interpretation?.general && readings\n\t\t\t\t\t\t? html`<p>${h.interpretation.general}</p>`\n\t\t\t\t\t\t: nothing\n\t\t\t\t} ${\n\t\t\t\t\tchanging.size > 0\n\t\t\t\t\t\t? html`<div class=\"changing\" part=\"section changing-lines\">${this.t('Changing lines: {{lines}}.', {\n\t\t\t\t\t\t\t\tlines: Array.from(changing)\n\t\t\t\t\t\t\t\t\t.sort((a, b) => a - b)\n\t\t\t\t\t\t\t\t\t.join(', '),\n\t\t\t\t\t\t\t})} ${\n\t\t\t\t\t\t\t\tresultingHexagram?.english\n\t\t\t\t\t\t\t\t\t? html`${this.t('Becomes hexagram {{number}} {{name}}.', {\n\t\t\t\t\t\t\t\t\t\t\tnumber: resultingHexagram.number,\n\t\t\t\t\t\t\t\t\t\t\tname: resultingHexagram.english,\n\t\t\t\t\t\t\t\t\t\t})}`\n\t\t\t\t\t\t\t\t\t: nothing\n\t\t\t\t\t\t\t}</div>`\n\t\t\t\t\t\t: nothing\n\t\t\t\t} ${this.renderLines(h, changing)}</div></article>`;\n\t}\n\n\t/**\n\t * The line readings. Each line carries its oracle statement and, since the 2026-07 API rewrite, a written meaning. Both are rendered: a bare \"Changing lines: 3\" leaves a reader no way to know what line 3 is telling them.\n\t *\n\t * @remarks\n\t * When lines are moving, only those lines are shown: a cast turns on the moving lines, and listing the other five buries the answer. With no lines moving (a lookup, a random draw, the daily hexagram) all six are shown, because there the hexagram is being read as a reference rather than as an answer to a question.\n\t */\n\tprivate renderLines(h: Hexagram, changing: Set<number>) {\n\t\tconst all = h.changingLines ?? [];\n\t\tif (all.length === 0) return nothing;\n\n\t\tconst isCast = changing.size > 0;\n\t\tconst shown = isCast ? all.filter((l) => changing.has(l.position)) : all;\n\t\tif (shown.length === 0) return nothing;\n\n\t\tconst sections: InterpSection[] = shown.map((l) => ({\n\t\t\tlabel: `Line ${l.position}`,\n\t\t\tbody: l.text ?? '',\n\t\t\textra: l.meaning\n\t\t\t\t? html`<p class=\"line-meaning\">${l.meaning}</p>`\n\t\t\t\t: nothing,\n\t\t}));\n\n\t\treturn this.renderInterpretation(\n\t\t\tsections,\n\t\t\t'hexagram-lines',\n\t\t\tisCast ? 'Changing lines' : 'Lines',\n\t\t);\n\t}\n\n\t/**\n\t * Lines for a static hexagram (lookup/random/daily, which carry no cast `lines` array): read the `binary` pattern. 6 digits BOTTOM to top, so index 0 is line 1, the bottom line, exactly like the cast `lines` array. 1 = yang (solid, 7), 0 = yin (broken, 8). Falls back to all-yang only if `binary` is malformed. The Unicode `symbol` block (U+4DC0) is in King Wen order, NOT line order, so it must never be used to derive the lines.\n\t *\n\t * @remarks\n\t * This used to `.reverse()`, because the API served `binary` top-to-bottom while documenting it bottom-to-top, and reversing was the only way to render the figure the right way up. The API fixed the data in 2026-07 (the same inversion was making `/cast` return the vertically MIRRORED hexagram for 56 of the 64 figures), so `binary` and `lines` now point the same way and the reverse would flip every asymmetric hexagram upside down. Do not put it back.\n\t */\n\tprivate derivedLines(h: Hexagram): number[] {\n\t\tconst binary = h.binary ?? '';\n\t\tif (/^[01]{6}$/.test(binary)) {\n\t\t\treturn Array.from(binary, (c) => (c === '1' ? 7 : 8));\n\t\t}\n\t\treturn Array.from({ length: 6 }, () => 7);\n\t}\n}\n\ndeclare global {\n\tinterface HTMLElementTagNameMap {\n\t\t'roxy-hexagram': RoxyHexagram;\n\t}\n}\n", "/**\n * Shared string helpers used across components. Single source of truth so the\n * same formatting rules apply to every key/label/title that surfaces in the\n * shadow tree.\n *\n * - `lookupKey`: the ONE normalizer every lookup table in this library is keyed\n * and read by (`tokens/index.ts` glyphs and abbreviations, `i18n/` chrome\n * strings).\n * - `capitalize`: title-cases the first character, lowercases the rest. A\n * DISPLAY helper only; it is not a lookup key (see `lookupKey`).\n * - `humanize`: turns an API key (`birth_date`, `birthDate`, `mahadasha-end`)\n * into a label suitable for display (\"Birth date\", \"Mahadasha end\").\n */\n\n/**\n * Fold a name to the canonical key its lookup table is stored under: lower case, every run of spaces, underscores and hyphens collapsed to one space, trimmed.\n *\n * @remarks\n * This exists because a GUESSED key spelling is a defect class this repo has now shipped twice. The glyph tables were keyed off whatever {@link capitalize} happened to produce (`North node`), while the API returns `North Node`, so every call site that reached the table without first calling `capitalize` missed and fell through to a fabricated abbreviation. Aspects hit the same wall from the other side: `/aspects` returns `SEMI SEXTILE` where synastry returns `SEMI_SEXTILE`.\n *\n * One normalizer, applied when a table is DEFINED and again when it is READ, removes the whole class: no call site has to remember a convention, and no table has to guess a spelling. Use it for every new table keyed by an API-supplied name.\n *\n * @example\n * ```ts\n * lookupKey('North Node'); // 'north node'\n * lookupKey('SEMI_SEXTILE'); // 'semi sextile'\n * lookupKey('semi-sextile'); // 'semi sextile'\n * ```\n */\nexport function lookupKey(s: string): string {\n\treturn s\n\t\t.toLowerCase()\n\t\t.replace(/[\\s_-]+/g, ' ')\n\t\t.trim();\n}\n\nexport function capitalize(s: string): string {\n\tif (!s) return '';\n\treturn s.charAt(0).toUpperCase() + s.slice(1).toLowerCase();\n}\n\nexport function humanize(s: string): string {\n\treturn (\n\t\ts\n\t\t\t.replace(/[_-]+/g, ' ')\n\t\t\t.replace(/([a-z])([A-Z])/g, '$1 $2')\n\t\t\t// Split a trailing/embedded digit off a word so \"person1\" reads \"Person 1\"\n\t\t\t// and every group legend and field label spaces its ordinal.\n\t\t\t.replace(/([a-z])([0-9])/g, '$1 $2')\n\t\t\t.replace(/^\\w/, (c) => c.toUpperCase())\n\t);\n}\n", "/**\n * Symbol constants used across components. Single source of truth so chart\n * wheels, card headers, hexagram displays, and panchang tables stay visually\n * consistent.\n *\n * @remarks\n * **Every table here is keyed by {@link lookupKey} and read ONLY through the accessor beside it.** The raw records are deliberately not exported: a component that indexes a record directly has to guess the key convention, and a guessed spelling renders `No North Node R`, `So South Node R` and `Bl Black Moon Lilith` on a live chart. The API returns `North Node` with a space, while {@link capitalize} produces `North node`, so a call site that indexes without normalising misses the table.\n *\n * **A miss returns `undefined`, never a manufactured abbreviation.** A `?? name.slice(0, 2)` fallback renders a failed lookup as a plausible two-letter code that reads exactly like an intentional abbreviation, so nothing about the output says it is broken. A caller that can omit the glyph should omit it (`?? ''`); a caller that must show something falls back to the FULL name, which is visibly wrong at the size these slots are drawn.\n *\n * `tests/tokens.test.ts` resolves every body, sign and aspect name the committed spec can emit against these tables, so a vocabulary the API gains cannot ship unglyphed.\n */\n\nimport { lookupKey } from '../utils/string.js';\n\n/** Look one name up in a normalized table. The single read path for every map in this file. */\nconst resolve = (\n\ttable: Record<string, string>,\n\tname: string | undefined | null,\n): string | undefined => (name ? table[lookupKey(name)] : undefined);\n\nconst PLANET_GLYPH: Record<string, string> = {\n\tsun: '☉',\n\tmoon: '☽',\n\tmercury: '☿',\n\tvenus: '♀',\n\tearth: '♁',\n\tmars: '♂',\n\tjupiter: '♃',\n\tsaturn: '♄',\n\turanus: '♅',\n\tneptune: '♆',\n\tpluto: '♇',\n\trahu: '☊',\n\tketu: '☋',\n\tascendant: 'Asc',\n\tlagna: 'La',\n\t'north node': '☊',\n\t'south node': '☋',\n\tchiron: '⚷',\n\tlilith: '⚸',\n\t'black moon lilith': '⚸',\n};\n\n/** Astrological glyph for a planet or point, or `undefined` when the library has none for it. */\nexport const planetGlyph = (\n\tname: string | undefined | null,\n): string | undefined => resolve(PLANET_GLYPH, name);\n\nconst PLANET_ABBR: Record<string, string> = {\n\tsun: 'Su',\n\tmoon: 'Mo',\n\tmercury: 'Me',\n\tvenus: 'Ve',\n\tmars: 'Ma',\n\tjupiter: 'Ju',\n\tsaturn: 'Sa',\n\turanus: 'Ur',\n\tneptune: 'Ne',\n\tpluto: 'Pl',\n\trahu: 'Ra',\n\tketu: 'Ke',\n\tascendant: 'Asc',\n\tlagna: 'La',\n};\n\n/** Two-letter graha code for the tight cells of a North/South Indian kundli, or `undefined`. */\nexport const planetAbbr = (\n\tname: string | undefined | null,\n): string | undefined => resolve(PLANET_ABBR, name);\n\nconst SIGN_GLYPH: Record<string, string> = {\n\taries: '♈',\n\ttaurus: '♉',\n\tgemini: '♊',\n\tcancer: '♋',\n\tleo: '♌',\n\tvirgo: '♍',\n\tlibra: '♎',\n\tscorpio: '♏',\n\tsagittarius: '♐',\n\tcapricorn: '♑',\n\taquarius: '♒',\n\tpisces: '♓',\n};\n\n/** Zodiac glyph for a sign name in any case, or `undefined`. */\nexport const signGlyph = (\n\tname: string | undefined | null,\n): string | undefined => resolve(SIGN_GLYPH, name);\n\nconst SIGN_ABBR: Record<string, string> = {\n\taries: 'Ar',\n\ttaurus: 'Ta',\n\tgemini: 'Ge',\n\tcancer: 'Cn',\n\tleo: 'Le',\n\tvirgo: 'Vi',\n\tlibra: 'Li',\n\tscorpio: 'Sc',\n\tsagittarius: 'Sg',\n\tcapricorn: 'Cp',\n\taquarius: 'Aq',\n\tpisces: 'Pi',\n};\n\n/** Two-letter rashi code for kundli cells and grid headers, or `undefined`. */\nexport const signAbbr = (name: string | undefined | null): string | undefined =>\n\tresolve(SIGN_ABBR, name);\n\n/** The twelve signs in zodiacal order. Display values, not lookup keys: read them through {@link signGlyph} / {@link signAbbr}. */\nexport const SIGNS_ORDER = [\n\t'Aries',\n\t'Taurus',\n\t'Gemini',\n\t'Cancer',\n\t'Leo',\n\t'Virgo',\n\t'Libra',\n\t'Scorpio',\n\t'Sagittarius',\n\t'Capricorn',\n\t'Aquarius',\n\t'Pisces',\n] as const;\n\n/**\n * Glyph per aspect. Used by the natal, transit and synastry aspect tables.\n *\n * @remarks\n * These are the nine aspects Unicode itself defines as a set, in its Miscellaneous Symbols block note: `260C, 26BA, 2220, 26B9, 25A1, 25B3, 26BC, 26BB, 260D` for 0, 30, 45, 60, 90, 120, 135, 150 and 180 degrees. That is exactly the vocabulary the API returns, so every aspect resolves to a real glyph and none falls through to a truncated slug.\n *\n * Do not substitute the visually similar maths operators. Unicode lists `⊻` XOR and `⊼` NAND as cross-references FROM the real quincunx and semisextile glyphs, so they look like safe stand-ins and are easy to pair the wrong way round, which renders a 150 degree quincunx with the 30 degree semisextile symbol. An astrologer reads the glyph, not the tooltip.\n */\nconst ASPECT_SYMBOL: Record<string, string> = {\n\tconjunction: '☌',\n\tsemisextile: '⚺',\n\t'semi sextile': '⚺',\n\tsemisquare: '∠',\n\t'semi square': '∠',\n\tsextile: '⚹',\n\tsquare: '□',\n\ttrine: '△',\n\tsesquiquadrate: '⚼',\n\tquincunx: '⚻',\n\topposition: '☍',\n};\n\n/** Aspect glyph for any of the separator forms the endpoints use (`SEMI_SEXTILE`, `SEMI SEXTILE`, `semi-sextile`), or `undefined`. */\nexport const aspectSymbol = (\n\tname: string | undefined | null,\n): string | undefined => resolve(ASPECT_SYMBOL, name);\n\n/** Trigrams used by I Ching hexagrams. Eight trigrams compose 64 hexagrams. */\nconst TRIGRAM_GLYPH: Record<string, string> = {\n\theaven: '☰',\n\tlake: '☱',\n\tfire: '☲',\n\tthunder: '☳',\n\twind: '☴',\n\twater: '☵',\n\tmountain: '☶',\n\tearth: '☷',\n};\n\n/** Trigram glyph for a trigram name in any case, or `undefined`. */\nexport const trigramGlyph = (\n\tname: string | undefined | null,\n): string | undefined => resolve(TRIGRAM_GLYPH, name);\n\n/** Moon phase emoji set. Used by the moon phase card. */\nconst MOON_PHASE_EMOJI: Record<string, string> = {\n\t'new moon': '🌑',\n\t'waxing crescent': '🌒',\n\t'first quarter': '🌓',\n\t'waxing gibbous': '🌔',\n\t'full moon': '🌕',\n\t'waning gibbous': '🌖',\n\t'last quarter': '🌗',\n\t'waning crescent': '🌘',\n};\n\n/**\n * Emoji for a lunar phase, or `undefined`.\n *\n * @remarks\n * The live API suffixes most phase names (`Waxing Gibbous Moon`) and calls the third quarter `Third Quarter Moon`, while only new and full moon carry the suffix in the table. Both reconciliations live here rather than in the card, so any component reading a phase name resolves the same eight phases from the same four spellings.\n */\nexport const moonPhaseEmoji = (\n\tname: string | undefined | null,\n): string | undefined => {\n\tif (!name) return undefined;\n\tconst key = lookupKey(name);\n\tconst bare = key.replace(/ moon$/, '');\n\tconst alias = bare === 'third quarter' ? 'last quarter' : bare;\n\treturn MOON_PHASE_EMOJI[key] ?? MOON_PHASE_EMOJI[alias];\n};\n", "import {\n\ttype ComplexAttributeConverter,\n\ttype CSSResultGroup,\n\thtml,\n\tnothing,\n\ttype PropertyValues,\n} from 'lit';\nimport { property, state } from 'lit/decorators.js';\nimport { ifDefined } from 'lit/directives/if-defined.js';\nimport type { ChromeString } from '../i18n/chrome-strings.js';\nimport { RoxyLocalizedElement } from '../i18n/localized-element.js';\nimport { baseStyles } from './base-styles.js';\nimport { expandCompact } from './compact.js';\nimport { buildRequest, FetchController } from './fetch-controller.js';\nimport {\n\ttype InterpSection,\n\trenderInterpAccordion,\n} from './interp-accordion.js';\nimport { MarkupDataController } from './markup-data.js';\n\n/**\n * Read the `submit-context` attribute into the object a proxied submit carries.\n *\n * @remarks\n * Hand-written rather than `type: Object`, which resolves malformed JSON to `null` in silence: a page whose context never left has nothing to look at, and the route it was meant for reports only that the value it expected is not there. One warning covers both refusals (unparseable, or parsed to something that is not an object) because both leave the request without a context, which is the fact worth reading.\n */\nconst submitContextConverter: ComplexAttributeConverter<\n\tRecord<string, unknown> | undefined\n> = {\n\tfromAttribute: (value) => {\n\t\tif (value == null) return undefined;\n\t\ttry {\n\t\t\tconst parsed: unknown = JSON.parse(value);\n\t\t\tif (parsed && typeof parsed === 'object' && !Array.isArray(parsed)) {\n\t\t\t\treturn parsed as Record<string, unknown>;\n\t\t\t}\n\t\t} catch {\n\t\t\t// Both refusals share the warning below.\n\t\t}\n\t\tconsole.warn(\n\t\t\t'[roxy-ui] submit-context must be a JSON object; sending the request without it.',\n\t\t);\n\t\treturn undefined;\n\t},\n};\n\n/**\n * Shared base for every data-driven Roxy component. Consolidates the things every component used to repeat by hand and adds the self-contained, drop-in behavior: controlled-mode hydration, an opt-in self-fetch (form, request, loading, error, empty), the typed `data` slot, and the render switch. A subclass implements one method, {@link RoxyDataElement.renderData}.\n *\n * @remarks\n * Two render modes, one component, which is the whole drop-in contract:\n *\n * - Controlled: a server (WordPress, JSX SSR, static HTML) fetches the response and injects it as a direct-child `<script type=\"application/json\" class=\"roxy-data\">`. {@link MarkupDataController} hydrates `data` from it on connect. No key reaches the browser. This is the path the WordPress plugin drives, and it is unchanged by the base class.\n * - Uncontrolled: no data is injected, but a `data-endpoint` and a `pk_` `publishable-key` are set. The component renders its own `<roxy-endpoint-form>` (an internal detail, never placed by the consumer), and on submit fetches through {@link FetchController}, which refuses any non-publishable key. The result populates `data` and the component renders it.\n *\n * The JavaScript `data` property always wins over markup, so a host that assigns `el.data = …` after upgrade is authoritative.\n *\n * Self-fetch needs `<roxy-endpoint-form>` (and `<roxy-location-search>`) registered. The CDN bundle and the full `@roxyapi/ui` entry register everything; per-component ESM consumers that want self-fetch import the form component too.\n *\n * Two things every subclass inherits for the host page to shape the render from outside the shadow root, with no JavaScript: the `hide-readings` attribute ({@link RoxyDataElement.hideReadings}), and the `part` names on the base's own branches (`form`, `loading`, `error`, `empty`, `edit-bar`, `attribution`). A component adds `part` to its own structural blocks, drawn from the published part vocabulary.\n *\n * Translation is inherited rather than defined here: `t()`, `translator` and `effectiveLang()` live on {@link RoxyLocalizedElement}, which the two declared widgets extend as well, so the form a visitor fills and the card it produces read the same catalogue.\n *\n * @example\n * ```ts\n * @customElement('roxy-dream-card')\n * export class RoxyDreamCard extends RoxyDataElement<GetDreamSymbolResponse> {\n * static styles = [baseStyles, css`.card { … }`];\n * protected renderData(d: GetDreamSymbolResponse) {\n * return html`<article class=\"card\">…</article>`;\n * }\n * }\n * ```\n */\nexport abstract class RoxyDataElement<\n\tT = unknown,\n> extends RoxyLocalizedElement {\n\tstatic styles: CSSResultGroup = [baseStyles];\n\n\t/** Typed RoxyAPI response. Assigned in JavaScript, hydrated from the roxy-data island, or set by a self-fetch. */\n\t@property({ attribute: false })\n\tdata: T | null = null;\n\n\t/** Endpoint path for self-fetch, e.g. \"astrology/natal-chart\" or \"dreams/symbols/{id}\". Empty disables self-fetch (controlled mode only). */\n\t@property({ type: String, attribute: 'data-endpoint' })\n\tendpoint = '';\n\n\t/** HTTP method for self-fetch. */\n\t@property({ type: String })\n\tmethod: 'GET' | 'POST' = 'POST';\n\n\t/** Browser-safe publishable key (pk_) for self-fetch. A secret key is refused client-side. */\n\t@property({ type: String, attribute: 'publishable-key' })\n\tpublishableKey?: string;\n\n\t/** Override the API origin for self-hosted or proxied deployments. Absolute, or relative to the page for a same-origin route. */\n\t@property({ type: String, attribute: 'base-url' })\n\tbaseUrl?: string;\n\n\t/** Override the OpenAPI spec URL the self-fetch form introspects. */\n\t@property({ type: String, attribute: 'spec-url' })\n\tspecUrl?: string;\n\n\t/** Consumer backend route that proxies the request (holds the secret key). When set, self-fetch POSTs the request here instead of calling RoxyAPI directly, so no key reaches the browser. The server-rendered (WordPress) path. */\n\t@property({ type: String, attribute: 'submit-url' })\n\tsubmitUrl?: string;\n\n\t/**\n\t * Data the host page chooses, as a JSON object, sent to the {@link RoxyDataElement.submitUrl} route as `context` beside the request. The place a page attaches its own verification data to a proxied submission.\n\t *\n\t * @remarks\n\t * Shapeless by design and never read here: the component parses the attribute, hands the object to the request, and leaves every key of it to the page and the route that answers it. Nothing is sent when it is unset, when the JSON does not parse, and when it parses to anything but an object, so a route written before this existed goes on receiving exactly the request it always did.\n\t *\n\t * It rides the proxy path only. A direct call with a `publishable-key` sends what the endpoint declares, so setting this without a `submit-url` does nothing.\n\t *\n\t * @example\n\t * ```html\n\t * <roxy-natal-chart\n\t * data-endpoint=\"astrology/natal-chart\"\n\t * submit-url=\"/api/roxy/proxy\"\n\t * submit-context='{\"token\":\"...\"}'\n\t * ></roxy-natal-chart>\n\t * ```\n\t */\n\t@property({ attribute: 'submit-context', converter: submitContextConverter })\n\tsubmitContext?: Record<string, unknown>;\n\n\t/**\n\t * Where the self-fetch form's city search sends its request, absolute or relative to the page.\n\t *\n\t * @remarks\n\t * The companion of {@link RoxyDataElement.submitUrl}, and it is separate because the two requests have different shapes: the proxy route takes one POSTed `{ path, method, body, query }`, while the city search is a GET the search issues on its own while a visitor types. A birth-data form makes both, so a page that routes its API traffic through its own server names that route here as well. It is forwarded to the internal form, which forwards it to the search; unset, the search keeps its own default.\n\t */\n\t@property({ type: String, attribute: 'location-url' })\n\tlocationUrl?: string;\n\n\t/** Persist the last self-fetch form values in sessionStorage (keyed by endpoint) and prefill the form on reload. */\n\t@property({ type: Boolean })\n\tremember = false;\n\n\t/**\n\t * Render the chart and the data, and omit the written interpretation. Off by default, so a component that does not set it is byte-identical to before.\n\t *\n\t * @remarks\n\t * The suppressed content is the prose an endpoint returns ABOUT the result: the interpretation accordion, the interpretive paragraphs, and the keyword chips that belong to them. Everything a practitioner reads the numbers off stays: wheels, tables, grids, legends, pills, counts and dates. The reading is dropped from the DOM rather than hidden with CSS, so a page that publishes the chart alone never ships the prose it is not showing.\n\t *\n\t * Set it when the page supplies its own words, which is the common case for a practitioner site that wants the graphic under its own writing.\n\t */\n\t@property({ type: Boolean, attribute: 'hide-readings', reflect: true })\n\thideReadings = false;\n\n\t/**\n\t * Remove named structural blocks from this component, as a comma-separated list of `part` names.\n\t *\n\t * @remarks\n\t * The sibling of {@link RoxyDataElement.hideReadings} and deliberately a different tool. `hide-readings` drops the PROSE an endpoint returns about a result; this drops a whole block whatever it contains, which is what a page wants when the block is measurement rather than writing. Hiding the chart-pattern list on a teaching page is the case it exists for: a T-square is data, so `hide-readings` leaves it standing on purpose.\n\t *\n\t * Any name in `components-catalog.json` works, on any component that publishes it, because the rule is generated from the name rather than from a list of components that opted in. A name no block carries costs nothing and hides nothing.\n\t *\n\t * **This hides with CSS, it does not remove from the DOM, and the difference is the reason both exist.** A part name is a rendering concern the base can act on generically; whether a block is prose is a question only the component can answer. So a page that must not SHIP the words uses `hide-readings`, and a page that just should not SHOW a block uses this.\n\t *\n\t * @example\n\t * ```html\n\t * <roxy-natal-chart hide-sections=\"patterns\"></roxy-natal-chart>\n\t * <roxy-natal-chart hide-sections=\"patterns, aspects\"></roxy-natal-chart>\n\t * ```\n\t */\n\t@property({ type: String, attribute: 'hide-sections', reflect: true })\n\thideSections = '';\n\n\t/** Override the self-fetch form's submit-button label. Empty derives one from the endpoint. */\n\t@property({ type: String, attribute: 'submit-label' })\n\tsubmitLabel?: string;\n\n\t/** Render a small \"Spiritual data by RoxyAPI\" credit under a self-fetch or auto-mount result. Off by default; any value except \"off\"/\"false\" enables it. The one-tag widgets script turns it on unless data-attribution=\"off\". Never shown in controlled mode. */\n\t@property({ type: String })\n\tattribution?: string;\n\n\t/** True while an uncontrolled self-fetch is in flight. Public so {@link FetchController} can drive it. */\n\t@state()\n\tloading = false;\n\n\t/** Message from a failed self-fetch, or null. Public so {@link FetchController} can drive it. */\n\t@state()\n\terror: string | null = null;\n\n\t/**\n\t * True once a self-fetch (not a consumer-assigned or island-hydrated `data`) produced the current result. It gates the interactive result affordances, so controlled mode never shows an Edit control or a sticky picker.\n\t */\n\t@state()\n\tprivate selfFetched = false;\n\n\t/** True when the visitor asked to edit a self-fetch result, so the form is restored over the result. */\n\t@state()\n\tprivate editing = false;\n\n\t/** True when the last self-fetch form was a single-enum picker, so it stays visible above the result and a change refetches. */\n\t@state()\n\tprivate sticky = false;\n\n\t/** Last submitted form values (nested per group), kept in memory to restore the form on Edit and to prefill the sticky picker. */\n\tprivate lastValues?: Record<string, unknown>;\n\n\tprivate fetcher: FetchController<T>;\n\n\tconstructor() {\n\t\tsuper();\n\t\t// Controlled mode: hydrate `data` from a direct-child roxy-data island when\n\t\t// no JS property was assigned. Keyless; the server already fetched.\n\t\tnew MarkupDataController<T>(this);\n\t\tthis.fetcher = new FetchController<T>(this);\n\t}\n\n\tprotected willUpdate(changed: PropertyValues): void {\n\t\t// A result asked for in compact form arrives with its same-shaped arrays\n\t\t// columnar, so it is decoded once here and every component goes on\n\t\t// rendering the plain shape. `expandCompact` hands back the same object\n\t\t// when nothing is encoded, so an ordinary response is neither copied nor\n\t\t// re-rendered, and Lit records a property set here inside the update in\n\t\t// progress rather than scheduling another one.\n\t\tif (changed.has('data') && this.data != null) {\n\t\t\tconst expanded = expandCompact(this.data);\n\t\t\tif (expanded !== this.data) this.data = expanded;\n\t\t}\n\t\tif (changed.has('publishableKey')) {\n\t\t\tthis.fetcher.publishableKey = this.publishableKey;\n\t\t}\n\t\tif (changed.has('baseUrl') && this.baseUrl) {\n\t\t\tthis.fetcher.baseUrl = this.baseUrl;\n\t\t}\n\t\tif (changed.has('submitUrl')) {\n\t\t\tthis.fetcher.submitUrl = this.submitUrl;\n\t\t}\n\t\tif (changed.has('submitContext')) {\n\t\t\tthis.fetcher.submitContext = this.submitContext;\n\t\t}\n\t}\n\n\trender(): unknown {\n\t\treturn html`${this.hiddenSectionsStyle()}${this.renderState()}`;\n\t}\n\n\t/**\n\t * The one rule set that acts on {@link RoxyDataElement.hideSections}, generated from the names rather than from a list of components.\n\t *\n\t * @remarks\n\t * `[part~=\"name\"]` is the selector because `part` is a space-separated list: the natal chart's aspect grid carries `section aspects table aspect-grid`, so a `~=` match reaches it by any one of its names while `=` would reach it by none. It is emitted INSIDE the shadow root, which is the only place a rule can see a `part` attribute on the element that declares it.\n\t *\n\t * Names are filtered to the same `[a-z][a-z0-9-]*` shape the catalog and the WordPress setting both use, so nothing a page passes can close the rule or inject a second one. An unknown name compiles to a selector that matches nothing, which is why there is no validation error and no list of legal names to keep in sync.\n\t *\n\t * A `<style>` element in the template rather than a static stylesheet, because static styles are evaluated once and shared across every instance, so two charts on one page could not hide different blocks. Lit supports per-instance style elements; the documented cost is a re-parse when the expression changes, which is irrelevant here because the value is set once from a page attribute and effectively never changes after that.\n\t *\n\t * **`!important` is load-bearing and is not a shortcut around specificity.** Lit puts static `styles` in `adoptedStyleSheets`, and the scoping spec applies those AFTER any `<style>` element inside the same shadow root, so an in-tree rule loses to the component's own stylesheet at equal specificity no matter how it is written. Measured: `patterns` is a bare `section` with no declared display and hid correctly without it, while `legend` carries `display:flex` from the static sheet and stayed visible. The WordPress site-wide rule needs no `!important` for the opposite reason, that an outer-tree `::part()` rule already outranks anything inside.\n\t */\n\tprivate hiddenSectionsStyle(): unknown {\n\t\tconst names = this.hideSections\n\t\t\t.split(',')\n\t\t\t.map((n) => n.trim().toLowerCase())\n\t\t\t.filter((n) => /^[a-z][a-z0-9-]*$/.test(n));\n\t\tif (names.length === 0) return nothing;\n\t\tconst rules = names\n\t\t\t.map((n) => `[part~=\"${n}\"]{display:none!important}`)\n\t\t\t.join('');\n\t\treturn html`<style>${rules}</style>`;\n\t}\n\n\t/** The state machine every render goes through, split out so {@link render} can pair it with the per-instance rules above. */\n\tprivate renderState(): unknown {\n\t\tif (this.loading) return this.renderLoading();\n\t\tif (this.error != null) return this.renderError(this.error);\n\t\tif (this.data != null) {\n\t\t\t// Controlled mode (consumer-assigned or island-hydrated data) renders the\n\t\t\t// result alone, byte-identical to before: no picker, no Edit. The one\n\t\t\t// exception is the widgets auto-mount attrs-complete path, which assigns\n\t\t\t// data directly AND sets `attribution`; a real controlled consumer never\n\t\t\t// sets the attribute, so this stays byte-identical for them.\n\t\t\tif (!this.selfFetched) {\n\t\t\t\treturn this.showAttribution()\n\t\t\t\t\t? html`${this.renderData(this.data)}${this.renderAttribution()}`\n\t\t\t\t\t: this.renderData(this.data);\n\t\t\t}\n\t\t\tif (this.editing) return this.renderForm();\n\t\t\treturn this.renderResult(this.data);\n\t\t}\n\t\treturn this.renderNoData();\n\t}\n\n\t/** Render the populated response. The single method every component implements. */\n\tprotected abstract renderData(data: T): unknown;\n\n\t/**\n\t * The interpretation accordion, gated by {@link RoxyDataElement.hideReadings}. Every component that shows a written reading routes through here instead of calling {@link renderInterpAccordion} directly.\n\t *\n\t * @remarks\n\t * The gate lives on the base rather than in each component because the property does, and a plain render function cannot read component state. One call site per accordion, one place that decides whether prose renders, and the section it emits carries the same `readings` part in every component.\n\t *\n\t * Prose that is NOT in an accordion (a summary paragraph, a per-item interpretation) is still the component's own to gate, since only the component knows which of its blocks are readings.\n\t *\n\t * @param heading - English source copy, translated here. Typed as {@link ChromeString} so the compiler, not a reviewer, rejects a heading no catalogue carries.\n\t */\n\tprotected renderInterpretation(\n\t\tsections: InterpSection[],\n\t\tname: string,\n\t\theading?: ChromeString,\n\t): unknown {\n\t\tif (this.hideReadings) return nothing;\n\t\t// Localized HERE rather than in the accordion: that is a plain render\n\t\t// function with no host, so it cannot read a language, and this is the one\n\t\t// call site every component routes through.\n\t\treturn renderInterpAccordion(sections, name, this.t(heading ?? 'Reading'));\n\t}\n\n\t/**\n\t * A self-fetch result plus its re-query affordance. A single-enum form keeps its picker above the result so a new selection refetches (a sign switch is a new reading); any other form gets a compact Edit control that restores the form with the previous values.\n\t */\n\tprotected renderResult(data: T): unknown {\n\t\tconst body = this.sticky\n\t\t\t? html`${this.renderForm()}${this.renderData(data)}`\n\t\t\t: html`<div class=\"roxy-edit-bar\" part=\"edit-bar\"><button type=\"button\" class=\"roxy-edit\" @click=\"${this.onEdit}\">${this.t('Edit query')}</button></div>${this.renderData(data)}`;\n\t\treturn this.showAttribution()\n\t\t\t? html`${body}${this.renderAttribution()}`\n\t\t\t: body;\n\t}\n\n\tprivate onEdit = () => {\n\t\tthis.editing = true;\n\t};\n\n\t/** True when the attribution credit renders: the attribute is present and not explicitly disabled. */\n\tprivate showAttribution(): boolean {\n\t\treturn (\n\t\t\tthis.attribution != null &&\n\t\t\tthis.attribution !== 'off' &&\n\t\t\tthis.attribution !== 'false'\n\t\t);\n\t}\n\n\t/** Small muted credit under a self-fetch or auto-mount result. Reached only from the result path, so controlled mode never renders it. */\n\tprotected renderAttribution(): unknown {\n\t\treturn html`<div class=\"roxy-attribution\" part=\"attribution\"><a href=\"https://roxyapi.com/?utm_source=widget&utm_medium=embed\" target=\"_blank\" rel=\"noopener\">${this.t('Spiritual data by RoxyAPI')}</a></div>`;\n\t}\n\n\t/** The data-absent branch: the self-fetch form when an endpoint is set, otherwise the empty state. */\n\tprotected renderNoData(): unknown {\n\t\treturn this.endpoint ? this.renderForm() : this.renderEmpty();\n\t}\n\n\t/** Internal self-fetch form. Reuses the introspecting `<roxy-endpoint-form>`; the consumer never places it. */\n\tprotected renderForm(): unknown {\n\t\treturn html`<roxy-endpoint-form part=\"form\" data-endpoint=\"${this.endpoint}\" method=\"${this.method}\" spec-url=\"${ifDefined(this.specUrl)}\" publishable-key=\"${ifDefined(this.publishableKey)}\" location-url=\"${ifDefined(this.locationUrl)}\" submit-label=\"${ifDefined(this.submitLabel)}\" lang=\"${ifDefined(this.effectiveLang())}\" .initialValues=\"${this.formInitialValues()}\" @roxy-submit=\"${this.onFormSubmit}\"></roxy-endpoint-form>`;\n\t}\n\n\t/** Prefill source for the form: the last submission (Edit / sticky refetch) wins over remembered storage. */\n\tprivate formInitialValues(): Record<string, unknown> | undefined {\n\t\treturn (\n\t\t\tthis.lastValues ?? (this.remember ? this.readRemembered() : undefined)\n\t\t);\n\t}\n\n\tprivate onFormSubmit = (e: Event) => {\n\t\tconst detail = (e as CustomEvent).detail as {\n\t\t\tvalues: Record<string, unknown>;\n\t\t\tqueryKeys?: string[];\n\t\t\tsticky?: boolean;\n\t\t};\n\t\tthis.lastValues = detail.values;\n\t\tthis.sticky = !!detail.sticky;\n\t\tthis.selfFetched = true;\n\t\tthis.editing = false;\n\t\tif (this.remember) this.writeRemembered(detail.values);\n\t\tvoid this.fetcher.run(\n\t\t\tbuildRequest(\n\t\t\t\tthis.endpoint,\n\t\t\t\tthis.method,\n\t\t\t\tdetail.values,\n\t\t\t\tdetail.queryKeys ?? [],\n\t\t\t),\n\t\t);\n\t};\n\n\t/** sessionStorage key for this component's remembered form values, scoped by endpoint. */\n\tprivate rememberKey(): string {\n\t\treturn `roxy-ui:form:${this.endpoint}`;\n\t}\n\n\tprivate readRemembered(): Record<string, unknown> | undefined {\n\t\ttry {\n\t\t\tconst raw = sessionStorage.getItem(this.rememberKey());\n\t\t\treturn raw ? (JSON.parse(raw) as Record<string, unknown>) : undefined;\n\t\t} catch {\n\t\t\treturn undefined;\n\t\t}\n\t}\n\n\tprivate writeRemembered(values: Record<string, unknown>): void {\n\t\ttry {\n\t\t\tsessionStorage.setItem(this.rememberKey(), JSON.stringify(values));\n\t\t} catch {\n\t\t\t// Private mode / disabled storage: remembering is best-effort, never fatal.\n\t\t}\n\t}\n\n\t/** Terminal empty state: one translated message for every component, addressable as `::part(empty)`. Override only where an empty state must DO something a message cannot. */\n\tprotected renderEmpty(): unknown {\n\t\treturn html`<div class=\"roxy-empty\" role=\"status\" part=\"empty\">${this.t('No data')}</div>`;\n\t}\n\n\t/** Loading placeholder shown during a self-fetch. */\n\tprotected renderLoading(): unknown {\n\t\treturn html`<div class=\"roxy-skeleton\" style=\"height:8rem\" role=\"status\" aria-label=\"${this.t('Loading')}\" part=\"loading\"></div>`;\n\t}\n\n\t/**\n\t * Error state shown when a self-fetch fails. Keeps the form in view so the request can be retried.\n\t *\n\t * The message goes through `t()` because ONE of the messages that reaches here is ours: `KEY_REFUSED_MESSAGE` (`utils/key-guard.ts`), which {@link FetchController} assigns when a site owner pastes a secret key into a browser page, and which `<roxy-location-search>` renders in its own shadow root from the same constant. Translating it in one place and not the other would put two languages on one page. Everything else that lands here is a wire fact (an HTTP status, a browser network error), misses the catalogue and renders unchanged.\n\t */\n\tprotected renderError(message: string): unknown {\n\t\tconst banner = html`<div class=\"roxy-error\" role=\"alert\" part=\"error\">${this.t(message)}</div>`;\n\t\treturn this.endpoint ? html`${banner}${this.renderForm()}` : banner;\n\t}\n}\n", "import { LitElement } from 'lit';\nimport { resolveLang } from './lang.js';\nimport { LocaleController } from './locale-controller.js';\nimport { translate } from './registry.js';\n\n/**\n * The base every element that writes WORDS extends: it resolves the page language and translates its own chrome.\n *\n * @remarks\n * This is deliberately smaller than {@link RoxyDataElement}, and the split is what makes the widgets translatable at all. `<roxy-endpoint-form>` and `<roxy-location-search>` are the two declared widgets: they fetch, they hold state, and they are NOT data components, so they cannot inherit the data base without dragging its controlled-mode hydration, its self-fetch controller and its own form rendering (which renders the form, so the form inheriting it would compose itself). They extended `LitElement` directly instead, which meant they had no `t()` and no {@link LocaleController}, so a Spanish page rendered a Spanish result card over an English form and neither widget re-rendered when a deferred locale payload landed.\n *\n * So the mechanism lives here ONCE and all three inherit it. There is no second translator, no second registry and no second way to resolve a language: adding one is how a catalogue entry and a call site drift apart.\n *\n * Two costs are why this is its own module rather than a second export of `utils/base-element.ts`. Every `dist/cdn/components/*.js` is a self-contained IIFE, so importing the data base into the city search would compile `FetchController`, `MarkupDataController` and the interpretation accordion into a bundle that uses none of them. And `utils/base-element.ts` imports THIS file, so putting the class there would close a cycle the moment a widget imported it.\n */\nexport abstract class RoxyLocalizedElement extends LitElement {\n\tconstructor() {\n\t\tsuper();\n\t\t// Re-render if a chrome-string catalogue lands after this element upgraded.\n\t\t// A host page loads the payload as its own script tag, so it can arrive\n\t\t// after first paint and there is nothing the site owner could do about it.\n\t\tnew LocaleController(this);\n\t}\n\n\t/**\n\t * The chrome string for this element's language, keyed by its own English source text.\n\t *\n\t * @remarks\n\t * Pass the English copy, never a key. With no catalogue registered the source string is returned unchanged, so an English page pays nothing and a language we do not ship degrades to English rather than to a visible key.\n\t *\n\t * Chrome only. A value the API returned (a planet, a sign, an aspect, a house system) is NOT translated here: it is rendered as the response carries it, so the words on the chart and the words in the response can never disagree. The same holds for a label derived from a spec field NAME through `humanize()`: a catalogue keyed on English source text cannot reach a string computed per response. A derived name is catalogued only where the set it comes from is CLOSED and small enough to enumerate against the spec, which is true of the nine form group names and of nothing else so far.\n\t *\n\t * @example\n\t * ```ts\n\t * this.t('Aspect grid'); // 'Cuadricula de aspectos' under lang=\"es\"\n\t * this.t('{{count}} planets', { count: 12 }); // '12 planetas'\n\t * ```\n\t */\n\tprotected t(source: string, vars?: Record<string, string | number>): string {\n\t\treturn translate(this.effectiveLang(), source, vars);\n\t}\n\n\t/** {@link RoxyLocalizedElement.t} as a value, bound once, for a shared render helper that has no host of its own and therefore cannot resolve a page language (`utils/hd-reading.ts`). Named `translator` and not `translate` because `HTMLElement.translate` is a real DOM property and shadowing it with a protected member makes every `@customElement` decorator in the library fail to typecheck. */\n\tprotected readonly translator = (\n\t\tsource: string,\n\t\tvars?: Record<string, string | number>,\n\t): string => this.t(source, vars);\n\n\t/**\n\t * Site-owner language for this element: the `lang` attribute, the nearest ancestor carrying one, or the document. Protected so a component that composes another can forward it (a child inside this shadow root cannot reach the host page on its own).\n\t *\n\t * Full tag, region included. The truncation to what `?lang=` accepts happens where the request is built, in `<roxy-endpoint-form>`.\n\t */\n\tprotected effectiveLang(): string | undefined {\n\t\treturn resolveLang(this);\n\t}\n}\n", "/**\n * Where a component's language comes from, and what is safe to send to the API.\n *\n * @remarks\n * Two different answers, and conflating them is the whole reason this file is separate from the catalogue:\n *\n * - {@link resolveLang} answers \"what language is this PAGE in\", and keeps the full tag, because `es-AR` is a legitimate thing for a catalogue to want to differ on.\n * - {@link apiLang} answers \"what may go on the query string\", which is a narrower question with a hard edge: `?lang=es-AR` is a 400, `?lang=es` is a 200.\n *\n * The full tag is not a nicety the catalogue happens to tolerate: `utils/format.ts` hands it to `Intl`, which reads the region and writes `15 de ene de 1990` for `es-AR` where it writes `15 ene 1990` for `es`. Passing the API answer to a formatter demotes every regional visitor to the base language and nothing fails, so the two values are never interchangeable.\n */\n\nimport { API_LANGUAGES } from '../generated/api-languages.js';\n\n/**\n * The site-owner language for an element, resolved through the four-link chain the revamp design specifies.\n *\n * @remarks\n * 1. the element's own `lang` attribute (the explicit per-embed override),\n * 2. the nearest ancestor carrying `lang`, so one wrapper localizes a whole section,\n * 3. `document.documentElement.lang`, which is what makes this work on a real CMS with no markup change at all: WordPress emits `<html lang=\"es-AR\">` on every page of a Spanish site,\n * 4. nothing, which the callers read as English.\n *\n * All four links matter: with only the first, a component on a fully Spanish page renders English chrome and the only remedy is hand-editing every embed.\n *\n * `navigator.language` is deliberately NOT in the chain. It is the VISITOR's preference, not the site's: it fragments the API cache across every locale a visitor might carry and silently serves two people different content from the same URL.\n *\n * Link 2 uses `closest`, which stops at a shadow boundary. A component composed INSIDE another component's shadow root therefore cannot see the host page, which is why every composing component forwards `lang` to its children explicitly.\n */\nexport function resolveLang(el: HTMLElement): string | undefined {\n\t// Native accessor, never a Lit @property: declaring one would shadow\n\t// HTMLElement.lang and break the platform attribute for every consumer.\n\tif (el.lang) return el.lang;\n\tif (typeof document === 'undefined') return undefined;\n\tconst inherited = el.closest?.('[lang]')?.getAttribute('lang');\n\tif (inherited) return inherited;\n\treturn document.documentElement.lang || undefined;\n}\n\n/**\n * Which script a Chinese page is written in, read off the region it names.\n *\n * @remarks\n * Chinese is the one language the API keys by SCRIPT rather than by language alone, because `zh`\n * on its own does not say which of the two a reader can actually read. Real pages almost never\n * write the script: a Taiwanese site writes `zh-TW` and a mainland site writes `zh-CN`, which is\n * what the region-to-script correspondence every internationalisation library ships is for.\n * Without this step both of those degrade to English, which takes the whole Chinese audience off\n * the domains the API answers in Chinese at all.\n *\n * A bare `zh` with neither region nor script resolves to nothing on purpose: guessing a script for\n * a reader who did not name one picks characters half of them cannot read.\n */\nconst ZH_SCRIPT_BY_REGION: Readonly<Record<string, string>> = {\n\ttw: 'hant',\n\thk: 'hant',\n\tmo: 'hant',\n\tcn: 'hans',\n\tsg: 'hans',\n\tmy: 'hans',\n};\n\n/** The API's own spelling of a tag, matched case-insensitively, or undefined when it serves no such language. */\nfunction asApiLang(tag: string): string | undefined {\n\tconst wanted = tag.toLowerCase();\n\treturn API_LANGUAGES.find((l) => l.toLowerCase() === wanted);\n}\n\n/**\n * The value safe to put on `?lang=`, or `undefined` to leave the request on the API default.\n *\n * @remarks\n * Three steps, and the order is load-bearing the moment {@link resolveLang} starts reading `<html lang>`:\n *\n * - **A tag the API serves goes as it is**, matched without regard to case, so `zh-Hant` and `ZH-HANT` both send the spelling the API declares. This comes first because the next step would throw away the very subtag those tags are identified by.\n * - **Chinese resolves its script**, from an explicit script subtag or from the region ({@link ZH_SCRIPT_BY_REGION}), because that is where the language actually lives.\n * - **Everything else drops its region.** A regional tag is a 400, so a Spanish WordPress site would go from English-but-working to broken the day the language chain was completed. `es-AR`, `es-419` and `ES` all send `es`.\n *\n * **An unsupported language is omitted, not sent.** The chain surfaces whatever the host page carries, including languages the API does not translate, and an unlisted tag is the same 400. Omitting it degrades to English, which is the behaviour those pages already had.\n */\nexport function apiLang(el: HTMLElement): string | undefined {\n\tconst tag = resolveLang(el);\n\tif (!tag) return undefined;\n\tconst exact = asApiLang(tag);\n\tif (exact) return exact;\n\tconst parts = tag.toLowerCase().split('-');\n\tconst base = parts[0] as string;\n\tif (base === 'zh') {\n\t\tconst script =\n\t\t\tparts.find((p) => p === 'hans' || p === 'hant') ??\n\t\t\tZH_SCRIPT_BY_REGION[parts[1] ?? ''];\n\t\treturn script ? asApiLang(`zh-${script}`) : undefined;\n\t}\n\treturn asApiLang(base);\n}\n", "/**\n * The chrome-string catalogue: one resolver reading one registry, so a translation can arrive from anywhere without a component changing.\n *\n * @remarks\n * **The key IS the canonical English string**, folded through {@link lookupKey}. There is no invented key vocabulary to keep in sync with the copy, which is the same rule the glyph tables in `tokens/index.ts` follow (they key off the exact value the API returns). Two consequences that are the whole point:\n *\n * - **English costs zero bytes.** A miss returns the source string, so the English build ships no catalogue at all, and a site that never loads a locale payload is byte-identical to one built before this file existed.\n * - **A missing translation degrades to English, never to a key.** The failure mode of a keyed catalogue is a raw `natal.tabs.wheel` on the page; here the worst case is the English word.\n *\n * **The registry lives on `globalThis`, not in module scope, because it has to.** Every `dist/cdn/components/*.js` is a self-contained IIFE with its own copy of this module, so a `Map` here would be invisible to the second component on the page. One global object, written by the locale payload and read by every bundle, is what makes `dist/cdn/locales/es.js` a single download that translates all of them.\n *\n * Load order is not guaranteed on a real host (WordPress enqueues scripts in an order the plugin does not fully control, and a payload may be deferred), so {@link onLocaleChange} lets an element that has already rendered in English re-render when its catalogue lands.\n */\n\nimport { lookupKey } from '../utils/string.js';\n\n/** Shared mutable state, addressed by a name rather than a module binding so every bundle on the page reaches the same object. */\ninterface LocaleRegistry {\n\t/** Language tag (lower case) to catalogue, keyed by {@link lookupKey} of the English source string. */\n\tcatalogs: Record<string, Record<string, string>>;\n\t/**\n\t * Language tag (lower case) to the API's field-label map: `fields` keyed by wire name,\n\t * `enums` keyed `{fieldName}.{value}`.\n\t *\n\t * A SEPARATE key space from `catalogs` on purpose. A chrome string is keyed by the English\n\t * text a component writes, which is a constant in our source; a field label is keyed by a\n\t * name that only the OpenAPI spec knows, computed per operation, so no catalogue keyed on\n\t * English source text can ever reach it. Same registry because the delivery problem is\n\t * identical (a payload that may land after first paint), so it reuses one global object and\n\t * one listener set rather than growing a second of each.\n\t */\n\tfieldLabels: Record<string, FieldLabels>;\n\t/** Language tags whose fetch is in flight or done, so N forms on a page cost ONE request. */\n\trequested: Set<string>;\n\t/** Elements waiting to re-render when a catalogue arrives. */\n\tlisteners: Set<() => void>;\n}\n\n/** The `/languages/field-labels` payload, minus the echoed `lang`. */\nexport interface FieldLabels {\n\tfields: Record<string, string>;\n\tenums: Record<string, string>;\n}\n\nconst GLOBAL_KEY = '__ROXY_UI_I18N__';\n\nfunction registry(): LocaleRegistry {\n\tconst holder = globalThis as unknown as Record<string, LocaleRegistry>;\n\tconst existing = holder[GLOBAL_KEY];\n\tif (existing) return existing;\n\tconst created: LocaleRegistry = {\n\t\tcatalogs: {},\n\t\tfieldLabels: {},\n\t\trequested: new Set(),\n\t\tlisteners: new Set(),\n\t};\n\tholder[GLOBAL_KEY] = created;\n\treturn created;\n}\n\n/**\n * Publish a catalogue for a language tag and wake every mounted element.\n *\n * @remarks\n * The catalogue is authored keyed by the English source string, exactly as it appears at the call site, and normalized here. That keeps the source file readable and diffable against the component that renders it, while the runtime lookup stays a single property read.\n *\n * This is the ONLY way into the registry, so a catalogue can later come from a static file, a server response, or a host page inlining a script tag, without a component knowing the difference.\n */\nexport function registerLocale(\n\tlang: string,\n\tcatalog: Record<string, string>,\n): void {\n\tconst reg = registry();\n\tconst normalized: Record<string, string> = {};\n\tfor (const [source, translated] of Object.entries(catalog)) {\n\t\tnormalized[lookupKey(source)] = translated;\n\t}\n\treg.catalogs[lang.toLowerCase()] = normalized;\n\tfor (const listener of reg.listeners) listener();\n}\n\n/**\n * Replace `{{name}}` placeholders. Copied from the API-side translator so both sides of the product interpolate identically; an unknown placeholder is left verbatim rather than blanked, so a typo in a catalogue is visible instead of silently eating the value.\n */\nexport function interpolate(\n\ttemplate: string,\n\tvars?: Record<string, string | number>,\n): string {\n\tif (!vars) return template;\n\treturn template.replace(/\\{\\{(\\w+)\\}\\}/g, (match, key: string) =>\n\t\tkey in vars ? String(vars[key] ?? '') : match,\n\t);\n}\n\n/**\n * The chrome string for `lang`, falling back to the English `source` it is keyed by.\n *\n * @remarks\n * A regional tag resolves against its base language, so `es-AR` and `es-419` both read the `es` catalogue and a site does not have to know which tags we happen to ship. An exact regional catalogue still wins if one is ever registered.\n */\nexport function translate(\n\tlang: string | undefined,\n\tsource: string,\n\tvars?: Record<string, string | number>,\n): string {\n\tif (!lang) return interpolate(source, vars);\n\tconst { catalogs } = registry();\n\tconst tag = lang.toLowerCase();\n\tconst catalog = catalogs[tag] ?? catalogs[tag.split('-')[0] as string];\n\treturn interpolate(catalog?.[lookupKey(source)] ?? source, vars);\n}\n\n/**\n * Publish a field-label map for a language tag and wake every mounted element.\n *\n * @remarks\n * Exported so a host that already has the payload (a server-rendered page, a test, a WordPress\n * plugin inlining it) can supply it without a network call, exactly as {@link registerLocale}\n * allows for chrome strings.\n */\nexport function registerFieldLabels(lang: string, labels: FieldLabels): void {\n\tconst reg = registry();\n\treg.fieldLabels[lang.toLowerCase()] = labels;\n\tfor (const listener of reg.listeners) listener();\n}\n\n/** The field-label map for `lang`, resolving a regional tag against its base language. */\nfunction labelsFor(lang: string | undefined): FieldLabels | undefined {\n\tif (!lang) return undefined;\n\tconst { fieldLabels } = registry();\n\tconst tag = lang.toLowerCase();\n\treturn fieldLabels[tag] ?? fieldLabels[tag.split('-')[0] as string];\n}\n\n/**\n * The label for a request field name, or `undefined` when nothing has been published.\n *\n * @remarks\n * Returning `undefined` rather than the name is deliberate: the caller owns the fallback, which is\n * `humanize()`, and that keeps this resolver honest about what it actually knows. A form renders\n * identically to before until a payload arrives.\n */\nexport function fieldLabel(\n\tlang: string | undefined,\n\tname: string,\n): string | undefined {\n\treturn labelsFor(lang)?.fields[name];\n}\n\n/** The label for one selectable option, keyed `{fieldName}.{value}` as the API publishes it. */\nexport function optionLabel(\n\tlang: string | undefined,\n\tfield: string,\n\tvalue: string,\n): string | undefined {\n\treturn labelsFor(lang)?.enums[`${field}.${value}`];\n}\n\n/** Subscribe to catalogue arrivals. Returns the unsubscribe, so an element can drop it on disconnect. */\nexport function onLocaleChange(listener: () => void): () => void {\n\tconst { listeners } = registry();\n\tlisteners.add(listener);\n\treturn () => {\n\t\tlisteners.delete(listener);\n\t};\n}\n", "import type { ReactiveController, ReactiveControllerHost } from 'lit';\nimport { onLocaleChange } from './registry.js';\n\n/**\n * Re-renders its host when a chrome-string catalogue arrives.\n *\n * @remarks\n * Without this the catalogue would have to be on the page BEFORE the elements upgrade, which is not something a component can require of a real host. WordPress orders enqueued scripts by dependency and a site owner can add `defer` to any of them; a CDN embed is two independent `<script src>` tags. Any of those can land the locale payload after the first paint, and the visible result would be a chart that renders in English on a Spanish page for no reason the site owner can see or fix.\n *\n * Mirrors `MarkupDataController`: constructed in {@link RoxyDataElement}'s constructor, subscribes on connect, drops the subscription on disconnect. Registration is idempotent and a re-register of the same language simply re-renders, so a payload loaded twice is harmless.\n */\nexport class LocaleController implements ReactiveController {\n\tprivate readonly host: ReactiveControllerHost;\n\tprivate unsubscribe?: () => void;\n\n\tconstructor(host: ReactiveControllerHost) {\n\t\tthis.host = host;\n\t\thost.addController(this);\n\t}\n\n\thostConnected(): void {\n\t\tthis.unsubscribe = onLocaleChange(() => this.host.requestUpdate());\n\t}\n\n\thostDisconnected(): void {\n\t\tthis.unsubscribe?.();\n\t\tthis.unsubscribe = undefined;\n\t}\n}\n", "import { css } from 'lit';\n\n/**\n * Shared host styles every component pulls in. Sets default font, color,\n * container query support, and the entry fade-in.\n */\nexport const baseStyles = css`:host{--roxy-label-col:minmax(0, 25%);font-family:var(--roxy-font-sans,system-ui, -apple-system, BlinkMacSystemFont, \"Segoe UI\", Roboto, sans-serif);color:var(--roxy-fg,#0a0a0a);font-size:var(--roxy-text-base,1rem);line-height:var(--roxy-leading-normal,1.5);animation:roxy-fade-in var(--roxy-motion-duration,.2s) var(--roxy-motion-easing,cubic-bezier(.4, 0, .2, 1)) both;background:0 0;display:block;container-type:inline-size}:host([bare]){--roxy-surface:transparent;--roxy-shadow-sm:none;--roxy-shadow-md:none}*,:before,:after{box-sizing:border-box}h1,h2,h3,h4{font-family:var(--roxy-font-display,var(--roxy-font-sans,system-ui, -apple-system, BlinkMacSystemFont, \"Segoe UI\", Roboto, sans-serif))}@keyframes roxy-fade-in{0%{opacity:0;transform:translateY(2px)}to{opacity:1;transform:translateY(0)}}@media (prefers-reduced-motion:reduce){:host{animation:none}}.roxy-skeleton{background:linear-gradient(90deg, var(--roxy-border,#e4e4e7) 0%, color-mix(in srgb, var(--roxy-border,#e4e4e7) 60%, transparent) 50%, var(--roxy-border,#e4e4e7) 100%);border-radius:var(--roxy-radius-md,8px);background-size:200% 100%;animation:1.4s ease-in-out infinite roxy-shimmer}@keyframes roxy-shimmer{0%{background-position:200% 0}to{background-position:-200% 0}}@media (prefers-reduced-motion:reduce){.roxy-skeleton{animation:none}}.roxy-sr-only{clip-path:inset(50%);white-space:nowrap;border:0;width:1px;height:1px;margin:0;padding:0;position:absolute;overflow:hidden}.roxy-empty{padding:var(--roxy-space-lg,1.5rem);color:var(--roxy-muted,#71717a);text-align:center;font-size:var(--roxy-text-sm,.875rem)}.roxy-error{gap:var(--roxy-space-sm,.5rem);padding:var(--roxy-space-lg,1.5rem);background:var(--roxy-surface,#fff);border:1px solid var(--roxy-danger,#dc2626);border-radius:var(--roxy-radius-md,8px);color:var(--roxy-danger-fg,#991b1b);font-size:var(--roxy-text-sm,.875rem);justify-items:start;display:grid}:host(:focus-within) .roxy-card{outline:2px solid var(--roxy-ring,#f59e0b66);outline-offset:2px}.roxy-attribution{margin-top:var(--roxy-space-sm,.5rem);font-size:var(--roxy-text-xs,.75rem);color:var(--roxy-muted,#71717a);text-align:right}.roxy-attribution a{color:inherit;text-decoration:none}.roxy-attribution a:hover{color:var(--roxy-accent-ink,#b45309);text-decoration:underline}.roxy-attribution a:focus-visible{outline:2px solid var(--roxy-ring,#f59e0b66);outline-offset:2px}.roxy-edit-bar{margin-bottom:var(--roxy-space-sm,.5rem);justify-content:flex-end;display:flex}.roxy-edit{padding:var(--roxy-space-xs,.25rem) var(--roxy-space-md,1rem);border:1px solid var(--roxy-border,#e4e4e7);border-radius:var(--roxy-radius-md,8px);color:var(--roxy-fg,#0a0a0a);font-family:inherit;font-size:var(--roxy-text-sm,.875rem);cursor:pointer;background:0 0}.roxy-edit:hover{border-color:var(--roxy-accent,#f59e0b);color:var(--roxy-accent-ink,#b45309)}.roxy-edit:focus-visible{outline:2px solid var(--roxy-ring,#f59e0b66);outline-offset:2px}:host{font-variant-emoji:text}`;\n", "const COLS = '__cols';\nconst ROWS = '__rows';\n\nfunction isPlainObject(value: unknown): value is Record<string, unknown> {\n\treturn typeof value === 'object' && value !== null && !Array.isArray(value);\n}\n\n/**\n * Walk a value, rebuilding only the branches that actually hold an encoded array.\n *\n * @remarks\n * The identity return is the contract, not an optimisation: a response with nothing encoded in it comes back as the same object, so every render path that existed before this decoder sees the exact bytes it always saw.\n */\nfunction decode(value: unknown): unknown {\n\tif (Array.isArray(value)) {\n\t\tlet rebuilt = false;\n\t\tconst out = value.map((item) => {\n\t\t\tconst next = decode(item);\n\t\t\tif (next !== item) rebuilt = true;\n\t\t\treturn next;\n\t\t});\n\t\treturn rebuilt ? out : value;\n\t}\n\tif (!isPlainObject(value)) return value;\n\n\tconst cols = value[COLS];\n\tconst rows = value[ROWS];\n\t// Exactly the two keys and nothing else: a real payload that happens to carry\n\t// a field of either name is left alone.\n\tif (\n\t\tArray.isArray(cols) &&\n\t\tArray.isArray(rows) &&\n\t\tObject.keys(value).length === 2\n\t) {\n\t\treturn rows.map((row) => {\n\t\t\tconst item: Record<string, unknown> = {};\n\t\t\t(cols as string[]).forEach((col, i) => {\n\t\t\t\titem[col] = decode((row as unknown[])[i]);\n\t\t\t});\n\t\t\treturn item;\n\t\t});\n\t}\n\n\tlet rebuilt = false;\n\tconst out: Record<string, unknown> = {};\n\tfor (const [key, item] of Object.entries(value)) {\n\t\tconst next = decode(item);\n\t\tif (next !== item) rebuilt = true;\n\t\tout[key] = next;\n\t}\n\treturn rebuilt ? out : value;\n}\n\n/**\n * Turn a compact API response back into the plain shape the components render.\n *\n * @remarks\n * Asking a Remote MCP tool for a compact result trades repeated field names for a header: an array of same-shaped objects arrives as `{ __cols: [names], __rows: [[values]] }`, which costs an agent far fewer tokens to read and carries exactly the same data. This is the decoder, applied at every depth, so a compact result renders in a component with nothing else to do.\n *\n * Every data component runs it on the way in, so a page that sets `data` from a tool result needs no call of its own. It is exported for the paths that hold the JSON before an element does.\n *\n * A value with nothing encoded in it is returned unchanged, by reference.\n *\n * @example\n * ```ts\n * expandCompact({ aspects: { __cols: ['a', 'b'], __rows: [['sun', 'moon'], ['sun', 'mars'], ['moon', 'mars']] } });\n * // { aspects: [{ a: 'sun', b: 'moon' }, { a: 'sun', b: 'mars' }, { a: 'moon', b: 'mars' }] }\n * ```\n */\nexport function expandCompact<T>(value: T): T {\n\treturn decode(value) as T;\n}\n", "/**\n * The one place the \"publishable key only\" rule lives. Every client-side fetch boundary ({@link ../components/location-search.ts}, {@link ./fetch-controller.ts}) calls through here so a secret or legacy unprefixed key is refused identically: no network call, the same visible message, the same `roxy-validation-error` event. Centralising it is what stops the two paths drifting, which is exactly how `<roxy-location-search>` used to warn-then-fetch a secret key while the controller fail-closed.\n */\n\n/** Canonical refusal message. Both fetch boundaries surface this exact wording. */\nexport const KEY_REFUSED_MESSAGE =\n\t'Client-side components accept a pk_ publishable key only. Use a publishable key with an origin allowlist, or render server-side.';\n\n/** True when the key is a browser-safe `pk_` publishable key. */\nexport function isPublishableKey(key: string | undefined | null): boolean {\n\treturn !!key && key.startsWith('pk_');\n}\n\n/**\n * The fail-closed condition: a key is PRESENT and is NOT a `pk_` key. An absent key is not refused, so a keyless public call (a form-slotted city search with no key set) still proceeds; only a real secret/legacy token in the browser is stopped.\n */\nexport function keyIsRefused(key: string | undefined | null): boolean {\n\treturn !!key && !key.startsWith('pk_');\n}\n\n/**\n * Announce a refused key: dispatch the shared `roxy-validation-error` (bubbling, composed) and, when `warn` is set, log it once for the developer. The caller sets its own visible error state and skips the fetch; this only handles the parts both boundaries share.\n */\nexport function dispatchKeyRefusal(\n\thost: EventTarget,\n\topts: { warn?: boolean } = {},\n): void {\n\tif (opts.warn) console.warn(KEY_REFUSED_MESSAGE);\n\thost.dispatchEvent(\n\t\tnew CustomEvent('roxy-validation-error', {\n\t\t\tdetail: { reason: 'possible-secret-key', message: KEY_REFUSED_MESSAGE },\n\t\t\tbubbles: true,\n\t\t\tcomposed: true,\n\t\t}),\n\t);\n}\n", "import type { ReactiveController, ReactiveControllerHost } from 'lit';\nimport {\n\tdispatchKeyRefusal,\n\tKEY_REFUSED_MESSAGE,\n\tkeyIsRefused,\n} from './key-guard.js';\n\n/**\n * Host slots the controller drives. {@link RoxyDataElement} satisfies this, so the form mixin can attach a controller without the component wiring state by hand.\n *\n * @remarks\n * Intersected with `HTMLElement` because the controller dispatches events on the host. Lit's `ReactiveControllerHost` is the update-lifecycle contract only (`addController`, `requestUpdate`, `updateComplete`) and carries no DOM surface, even though every real host is a `LitElement` and therefore an `HTMLElement`. Declaring the DOM half is what the controller actually needs; it used to reach it through a `this.host as unknown as EventTarget` double cast instead, which asserted a capability the type never promised.\n */\ntype FetchHost<T> = ReactiveControllerHost &\n\tHTMLElement & {\n\t\tdata: T | null;\n\t\tloading: boolean;\n\t\terror: string | null;\n\t};\n\n/** Default RoxyAPI v2 origin. A component overrides it per instance via its `base-url` attribute. */\n/** The public API root. Exported so anything else that must reach the API (the field-label\n * fetch in `endpoint-form`) uses the SAME origin as every data request instead of a second copy. */\nexport const DEFAULT_BASE_URL = 'https://roxyapi.com/api/v2';\n\n/**\n * Turn a failed `Response` into the message to show: the API's own `{ error }` string when the body carries one, else the status line.\n *\n * @remarks\n * Exported so every client-side fetch boundary renders the same words for the same failure, the way {@link keyIsRefused} centralizes the key refusal. A boundary that discards the response body cannot tell a rejected request from an empty result, and renders the two identically.\n */\nexport async function readApiError(res: Response): Promise<string> {\n\ttry {\n\t\tconst body = (await res.json()) as { error?: string };\n\t\tif (body?.error) return body.error;\n\t} catch {\n\t\t// Non-JSON error body: fall through to the status line.\n\t}\n\treturn `Request failed (${res.status})`;\n}\n\n/** A single request the controller issues on the component's behalf. */\nexport interface RoxyRequest {\n\t/** Path under the API base, e.g. \"/dreams/symbols/water\" or \"/astrology/natal-chart\". */\n\tpath: string;\n\tmethod?: 'GET' | 'POST';\n\t/** JSON body for POST endpoints. */\n\tbody?: unknown;\n\t/** Query string parameters; nullish values are dropped. */\n\tquery?: Record<string, string | number | undefined>;\n}\n\n/**\n * Client-side fetch for uncontrolled (self-fetching) components: drives `host.data` / `host.loading` / `host.error` and cancels a stale request when a newer one starts or the host disconnects.\n *\n * @remarks\n * Security boundary. The only credential this ever sends is a `pk_` publishable key, which carries a server-side origin allowlist. A secret (`sk_`) or legacy unprefixed key is refused before any network call and surfaced as an error, so a server secret cannot leak into a browser request. This centralizes the guard that originated in `<roxy-location-search>` so every self-fetching component enforces it identically.\n *\n * Controlled-mode components never construct this. When a server injects the response as a `<script class=\"roxy-data\">` island, there is no key and no fetch, which is the path server-rendered consumers (WordPress, JSX SSR, static HTML) rely on.\n */\nexport class FetchController<T = unknown> implements ReactiveController {\n\tprivate readonly host: FetchHost<T>;\n\tprivate abort?: AbortController;\n\n\t/** Browser-safe publishable key. Set by the host from its `publishable-key` attribute. */\n\tpublishableKey?: string;\n\t/** API origin, overridable for self-hosted or proxied deployments. */\n\tbaseUrl = DEFAULT_BASE_URL;\n\t/**\n\t * Consumer backend route that holds the secret key. When set, the request is POSTed here as `{ path, method, body, query }` instead of called against RoxyAPI directly, so no key (publishable or secret) is sent from the browser. This is the canonical path for server-rendered hosts (WordPress); the backend proxies the request with its own `sk_` key and returns the JSON response.\n\t */\n\tsubmitUrl?: string;\n\t/**\n\t * Object the host page attaches to the proxied request, carried beside it as `context`. Set by the host from its `submit-context` attribute, and shapeless on purpose: this passes it through and reads no key of it, so what it holds is for the page and its own route to agree on.\n\t *\n\t * @remarks\n\t * Only the {@link FetchController.submitUrl} path can carry it, because that is the only body this code writes. A direct call sends the request the endpoint declares and nothing beside it.\n\t */\n\tsubmitContext?: Record<string, unknown>;\n\n\tconstructor(host: FetchHost<T>) {\n\t\tthis.host = host;\n\t\thost.addController(this);\n\t}\n\n\thostDisconnected() {\n\t\tthis.abort?.abort();\n\t\tthis.abort = undefined;\n\t}\n\n\t/**\n\t * Issue the request and resolve once `host.data` (success) or `host.error`\n\t * (failure) is set. A no-op return when a non-publishable key is present:\n\t * the error is already surfaced and nothing is sent.\n\t */\n\tasync run(req: RoxyRequest): Promise<void> {\n\t\t// submit-url proxy: no key leaves the browser; the consumer's backend holds it.\n\t\tif (!this.submitUrl && this.secretKeyRefused()) return;\n\t\tthis.abort?.abort();\n\t\tconst controller = new AbortController();\n\t\tthis.abort = controller;\n\t\tthis.host.loading = true;\n\t\tthis.host.error = null;\n\t\ttry {\n\t\t\tconst res = this.submitUrl\n\t\t\t\t? await fetch(this.submitUrl, {\n\t\t\t\t\t\tmethod: 'POST',\n\t\t\t\t\t\theaders: {\n\t\t\t\t\t\t\tAccept: 'application/json',\n\t\t\t\t\t\t\t'Content-Type': 'application/json',\n\t\t\t\t\t\t},\n\t\t\t\t\t\tbody: this.proxyBody(req),\n\t\t\t\t\t\tsignal: controller.signal,\n\t\t\t\t\t})\n\t\t\t\t: await this.callApi(req, controller.signal);\n\t\t\tif (!res.ok) throw new Error(await readApiError(res));\n\t\t\tconst json = (await res.json()) as T;\n\t\t\tif (controller.signal.aborted) return;\n\t\t\tthis.host.data = json;\n\t\t} catch (err) {\n\t\t\tif ((err as { name?: string })?.name === 'AbortError') return;\n\t\t\tthis.host.error = err instanceof Error ? err.message : String(err);\n\t\t} finally {\n\t\t\tif (this.abort === controller) this.abort = undefined;\n\t\t\tif (!controller.signal.aborted) this.host.loading = false;\n\t\t}\n\t}\n\n\t/**\n\t * The body of a proxied POST: the request, plus {@link FetchController.submitContext} under `context` when the host set one.\n\t *\n\t * @remarks\n\t * The context is appended rather than declared on {@link RoxyRequest}, so with none set the payload is the request object itself and every route already written against it keeps receiving the same four keys in the same order. A `null` or an empty object would be a fifth key such a route never agreed to read.\n\t */\n\tprivate proxyBody(req: RoxyRequest): string {\n\t\treturn JSON.stringify(\n\t\t\tthis.submitContext ? { ...req, context: this.submitContext } : req,\n\t\t);\n\t}\n\n\t/** Direct call against RoxyAPI with the publishable key (the no-backend path). */\n\tprivate callApi(req: RoxyRequest, signal: AbortSignal): Promise<Response> {\n\t\t// Resolved against the page, so a same-origin base (\"/api/roxy\") is as valid as an\n\t\t// absolute one. Every route a host page can name resolves the same way, and a bare\n\t\t// `new URL()` would reject the relative shape with an opaque \"Invalid URL\".\n\t\tconst url = new URL(`${this.baseUrl}${req.path}`, document.baseURI);\n\t\tfor (const [k, v] of Object.entries(req.query ?? {})) {\n\t\t\tif (v != null) url.searchParams.set(k, String(v));\n\t\t}\n\t\tconst headers: Record<string, string> = { Accept: 'application/json' };\n\t\tif (this.publishableKey) headers['X-API-Key'] = this.publishableKey;\n\t\tif (req.body != null) headers['Content-Type'] = 'application/json';\n\t\treturn fetch(url, {\n\t\t\tmethod: req.method ?? 'GET',\n\t\t\theaders,\n\t\t\tbody: req.body != null ? JSON.stringify(req.body) : undefined,\n\t\t\tsignal,\n\t\t});\n\t}\n\n\t/** True when a key is set and it is not a browser-safe `pk_` publishable key. Surfaces the error and refuses to send, via the shared {@link keyIsRefused} guard so every fetch boundary fail-closes identically. */\n\tprivate secretKeyRefused(): boolean {\n\t\tif (!keyIsRefused(this.publishableKey)) return false;\n\t\tthis.host.error = KEY_REFUSED_MESSAGE;\n\t\tdispatchKeyRefusal(this.host);\n\t\treturn true;\n\t}\n}\n\n/**\n * Translate flat form values into a {@link RoxyRequest} for an endpoint. The `{name}` segments in the endpoint template are substituted from the values and removed; the rest become the JSON body for POST or query parameters for GET. This is the spec-light request builder the base element uses to turn a `<roxy-endpoint-form>` submission into a self-fetch, so a component needs no per-endpoint glue.\n *\n * @param queryKeys - Names the spec declares as `in: query` for this operation, which `<roxy-endpoint-form>` reports on its `roxy-submit` event. A POST operation can still take query parameters (every localized endpoint takes `?lang=`), and sending one in the JSON body silently drops it, so those names are routed to the query string on POST as well as GET.\n */\nexport function buildRequest(\n\tendpoint: string,\n\tmethod: 'GET' | 'POST',\n\tvalues: Record<string, unknown>,\n\tqueryKeys: readonly string[] = [],\n): RoxyRequest {\n\tconst rest: Record<string, unknown> = { ...values };\n\tconst path = `/${endpoint.replace(/^\\//, '')}`.replace(\n\t\t/\\{([^}]+)\\}/g,\n\t\t(_match, name: string) => {\n\t\t\tconst v = rest[name];\n\t\t\tdelete rest[name];\n\t\t\treturn encodeURIComponent(String(v ?? ''));\n\t\t},\n\t);\n\tconst inQuery = new Set(queryKeys);\n\tconst query: Record<string, string | number | undefined> = {};\n\tconst body: Record<string, unknown> = {};\n\tfor (const [k, v] of Object.entries(rest)) {\n\t\tif (v === undefined || v === '') continue;\n\t\tif (method === 'GET' || inQuery.has(k)) query[k] = v as string | number;\n\t\telse body[k] = v;\n\t}\n\treturn { path, method, query, body: method === 'POST' ? body : undefined };\n}\n", "/**\n * The interpretation accordion: the one way this library shows a label, a short value, and a body of prose behind a disclosure.\n *\n * @remarks\n * Exclusive by construction (`<details name>`), so a card grows by at most one open section and never becomes a wall of text. Callers pass their own group `name` so two accordions on one page do not fight over which section is open.\n *\n * This lives here rather than in a component because the same accordion is the right shape wherever an endpoint returns a labelled reading: the Human Design bodygraph and type card use it for strategy, authority, and aura; `roxy-hexagram` uses it for the changing lines. A card that draws its own disclosure, because its summary carries more than a label and an aside, still renders the shared body and imports {@link readingDetailStyles} for it rather than restating those rules.\n *\n * **Call it through `RoxyDataElement.renderInterpretation`, never directly.** That method is where `hide-readings` is honoured, so a direct call renders prose a host asked to be left out. The section it emits carries `part=\"section readings\"` and each row `part=\"reading\"`, which is what makes the readings of EVERY component addressable under one name from outside the shadow root.\n */\n\nimport { css, html, nothing } from 'lit';\nimport type { ChromeString } from '../i18n/chrome-strings.js';\nimport { chevron } from './disclosure.js';\nimport type { Translate } from './hd-reading.js';\n\n/** One row: the label, the short value shown as the aside, and the interpretation body. `extra` renders under the body for a section that carries more than prose. */\nexport interface InterpSection {\n\tlabel: string;\n\taside?: string;\n\tbody: string;\n\textra?: unknown;\n}\n\n/**\n * Styles for the markup {@link renderReadingDetail} emits. Import this wherever that helper is called; {@link interpAccordionStyles} already embeds it, so an accordion caller needs only the one.\n *\n * @remarks\n * Separate from the accordion shell because the two are needed independently: a card can draw its own disclosure and still render the shared reading body, and hand-copying these rules is how the chip colour and spacing drifted apart across five components.\n *\n * No margin-top on the chip row. The body above already spaces its children, so a margin here would set the chips twice as far out as every other row.\n */\nexport const readingDetailStyles = css`.interp-keywords{flex-wrap:wrap;gap:.25rem;display:flex}.interp-keywords .kw{border-radius:var(--roxy-radius-full,9999px);background:color-mix(in srgb, var(--roxy-accent,#f59e0b) 14%, transparent);color:var(--roxy-fg,#0a0a0a);font-size:var(--roxy-text-xs,.75rem);padding:1px 8px}`;\n\nexport const interpAccordionStyles = css`.block{border-top:1px solid var(--roxy-border,#e4e4e7);padding-top:var(--roxy-space-md,1rem)}.block h3{margin:0 0 var(--roxy-space-sm,.5rem);font-size:var(--roxy-text-sm,.875rem);font-weight:var(--roxy-weight-bold,600);color:var(--roxy-muted,#71717a);text-transform:uppercase;letter-spacing:.06em}.interp-card{border:1px solid var(--roxy-border,#e4e4e7);border-radius:var(--roxy-radius-md,8px);padding:var(--roxy-space-sm,.5rem) var(--roxy-space-md,1rem);margin-bottom:var(--roxy-space-xs,.25rem)}.interp-card summary{cursor:pointer;color:var(--roxy-fg,#0a0a0a);align-items:center;gap:var(--roxy-space-sm,.5rem);font-weight:500;font-size:var(--roxy-text-sm,.875rem);display:flex}.interp-card summary:focus-visible{outline:2px solid var(--roxy-ring,#f59e0b66);outline-offset:2px;border-radius:var(--roxy-radius-sm,4px)}.interp-lead{flex-wrap:wrap;flex:auto;order:1;align-items:baseline;gap:.4rem;min-width:0;display:inline-flex}.interp-aside{flex-shrink:0;order:2;align-items:center;gap:.5rem;display:inline-flex}.roxy-chevron{order:3}.interp-aside small{color:var(--roxy-muted,#71717a);white-space:nowrap;font-weight:400}@container (width<=26rem){.interp-card summary{flex-wrap:wrap}.roxy-chevron{order:2}.interp-aside{flex-basis:100%;order:3;justify-content:flex-end}}.interp-body{margin-top:var(--roxy-space-sm,.5rem);gap:var(--roxy-space-sm,.5rem);color:var(--roxy-fg,#0a0a0a);font-size:var(--roxy-text-sm,.875rem);overflow-wrap:anywhere;line-height:1.6;display:grid}.interp-body p{margin:0}${readingDetailStyles}`;\n\n/** The keyword chips a reading carries, or nothing. One renderer because four components drew the identical row, and the markup has to match {@link readingDetailStyles}, which is the pairing that drifts when it is copied. */\nexport function renderKeywordChips(keywords: readonly string[] | undefined) {\n\tif (!keywords?.length) return nothing;\n\treturn html`<div class=\"interp-keywords\">${keywords.map((k) => html`<span class=\"kw\">${k}</span>`)}</div>`;\n}\n\n/** The prose an endpoint returns ABOUT one contact: a summary, up to three labelled lines, and the keyword chips under them. Every field is optional, so a narrower response renders fewer rows rather than empty ones. */\nexport interface ReadingDetail {\n\tsummary?: string;\n\timpact?: string;\n\ttiming?: string;\n\tguidance?: string;\n\tkeywords?: readonly string[];\n}\n\n/** Render one {@link ReadingDetail}. The three labels are copy, so this takes the translator, and they are typed {@link ChromeString} because the lookup is one indirection from the call: a scan of `t(...)` sites cannot follow that, and the compiler can. */\nexport function renderReadingDetail(\n\td: ReadingDetail | undefined,\n\tt: Translate,\n) {\n\tif (!d) return nothing;\n\tconst line = (label: ChromeString, value: string | undefined) =>\n\t\tvalue ? html`<p><strong>${t(label)}</strong> ${value}</p>` : nothing;\n\treturn html`${d.summary ? html`<p>${d.summary}</p>` : nothing} ${line('Impact:', d.impact)}${line('Timing:', d.timing)}${line('Guidance:', d.guidance)} ${renderKeywordChips(d.keywords)}`;\n}\n\n/**\n * Render the accordion. Sections with no body are dropped, so a caller can pass the full set and let a narrower response render only what it carries. `name` groups the `<details>` exclusively, so opening one closes the last.\n */\nexport function renderInterpAccordion(\n\tsections: InterpSection[],\n\tname: string,\n\theading: string,\n) {\n\tconst shown = sections.filter((s) => Boolean(s.body));\n\tif (shown.length === 0) return nothing;\n\n\treturn html`<section class=\"block\" part=\"section readings\"><h3>${heading}</h3>${shown.map(\n\t\t\t(\n\t\t\t\ts,\n\t\t\t\ti,\n\t\t\t) => html`<details class=\"interp-card\" part=\"reading\" name=\"${name}\" ?open=\"${i === 0}\"><summary><span class=\"interp-lead\">${s.label}</span> ${chevron()} ${s.aside ? html`<span class=\"interp-aside\"><small>${s.aside}</small></span>` : nothing}</summary><div class=\"interp-body\"><p>${s.body}</p>${s.extra ?? nothing}</div></details>`,\n\t\t)}</section>`;\n}\n", "import type { TemplateResult } from 'lit';\nimport { css, html } from 'lit';\n\n/**\n * Disclosure chevron for `<details>`/`<summary>` accordions. Replaces the\n * browser default triangle with a thin chevron that rotates when the host\n * `<details>` opens. Render it inside the `<summary>` and pair with\n * {@link disclosureStyles}.\n */\nexport function chevron(): TemplateResult {\n\treturn html`<svg class=\"roxy-chevron\" viewBox=\"0 0 16 16\" width=\"14\" height=\"14\" aria-hidden=\"true\"><path d=\"M4 6l4 4 4-4\" fill=\"none\" stroke=\"currentColor\" stroke-width=\"1.5\" stroke-linecap=\"round\" stroke-linejoin=\"round\"/></svg>`;\n}\n\n/**\n * Shared `<details>` accordion styling: hides the native disclosure triangle\n * and rotates the {@link chevron} 180 degrees when the accordion is open.\n * Import into any component that renders disclosure accordions so the chevron\n * looks and behaves identically.\n */\nexport const disclosureStyles = css`summary{list-style:none}summary::-webkit-details-marker{display:none}.roxy-chevron{aspect-ratio:auto;width:14px;height:14px;color:var(--roxy-muted,#71717a);transition:transform var(--roxy-motion-duration,.2s) var(--roxy-motion-easing,ease);flex-shrink:0}details[open]>summary .roxy-chevron{transform:rotate(180deg)}@media (prefers-reduced-motion:reduce){.roxy-chevron{transition:none}}`;\n", "import type { ReactiveController, ReactiveControllerHost } from 'lit';\n\n/**\n * Marker class on the inline JSON script a server emits inside a component.\n *\n * @example\n * ```html\n * <roxy-natal-chart>\n * <script type=\"application/json\" class=\"roxy-data\">{ ...response... }</script>\n * </roxy-natal-chart>\n * ```\n */\nconst ROXY_DATA_CLASS = 'roxy-data';\n\n/**\n * Serialize a RoxyAPI response for embedding inside an inline `<script type=\"application/json\" class=\"roxy-data\">`. This is the safe writer counterpart to {@link MarkupDataController}, the reader: server-rendered and cached consumers (WordPress, JSX SSR, static HTML) emit the script with this, and the component hydrates `data` from it on connect.\n *\n * @remarks\n * Use this instead of a bare `JSON.stringify`. A raw stringify of a response that contains the literal text `</script>` (common in long interpretation prose) closes the script element early, corrupting the page and creating an HTML-injection vector. This escapes the script-unsafe characters to their `\\uXXXX` JSON escapes, which `JSON.parse` restores to the original characters, so the value the component receives is identical to the response you passed.\n *\n * `<` is the load-bearing escape (it defeats `</script>` and `<!--`). `>` and `&` are escaped for defence in depth, and U+2028 / U+2029 because they are valid in JSON yet are line terminators in a `<script>` context and break some parsers. The escapes introduce only `\\uXXXX` sequences, so the replacements never feed each other and order is irrelevant.\n *\n * Pass the unwrapped RoxyAPI response, the same shape you would assign to `element.data`. Do not pass the SDK envelope (`{ data, error, request, response }`).\n *\n * @example\n * ```ts\n * import { serializeRoxyData } from '@roxyapi/ui';\n *\n * const { data } = await roxy.dreams.getDreamSymbol({ path: { id: 'water' } });\n * const html = `<roxy-dream-card><script type=\"application/json\" class=\"roxy-data\">${serializeRoxyData(data)}</script></roxy-dream-card>`;\n * ```\n */\nexport function serializeRoxyData(data: unknown): string {\n\treturn JSON.stringify(data)\n\t\t.replace(/</g, '\\\\u003c')\n\t\t.replace(/>/g, '\\\\u003e')\n\t\t.replace(/&/g, '\\\\u0026')\n\t\t.replace(/\\u2028/g, '\\\\u2028')\n\t\t.replace(/\\u2029/g, '\\\\u2029');\n}\n\n/**\n * Build the complete `<script type=\"application/json\" class=\"roxy-data\">…</script>` element a server nests inside a `roxy-*` component for the no-JavaScript hydration path. The payload is escaped via {@link serializeRoxyData}, so it is safe to drop straight into HTML output.\n *\n * @remarks\n * The element carries both `type=\"application/json\"` and `class=\"roxy-data\"` because {@link MarkupDataController} reads only a direct-child script that has both. Emit one of these inside the target component; the JavaScript `data` property still wins if it is later assigned.\n *\n * @example\n * ```ts\n * import { roxyDataScript } from '@roxyapi/ui';\n *\n * const { data } = await roxy.crystals.getCrystal({ path: { id: 'amethyst' } });\n * const html = `<roxy-crystal-grid>${roxyDataScript(data)}</roxy-crystal-grid>`;\n * ```\n */\nexport function roxyDataScript(data: unknown): string {\n\treturn `<script type=\"application/json\" class=\"${ROXY_DATA_CLASS}\">${serializeRoxyData(data)}</script>`;\n}\n\n/**\n * True when the element is a `<script type=\"application/json\">`. Uses tag name and attribute rather than `instanceof HTMLScriptElement` so the check holds in every DOM implementation, including server-rendered and hydration runtimes where the constructor global may be absent.\n */\nfunction isJsonScript(el: Element): boolean {\n\treturn (\n\t\tel.nodeName === 'SCRIPT' && el.getAttribute('type') === 'application/json'\n\t);\n}\n\n/**\n * Host shape the controller drives: any reactive element that exposes a public `data` slot. The controller only writes `data` when the host left it unset, so the JavaScript property path always wins.\n */\ninterface DataHost extends ReactiveControllerHost, HTMLElement {\n\tdata?: unknown;\n}\n\n/**\n * Reactive controller that lets a component hydrate its `data` from embedded markup when no `data` property was assigned in JavaScript.\n *\n * @remarks\n * The server-side and cached-render model: a backend renders the RoxyAPI response into a direct-child `<script type=\"application/json\" class=\"roxy-data\">` element, ships static HTML, and never runs per-element JavaScript to assign a property. On connect this controller reads that script, parses it, and feeds the result to the host. The JavaScript property path is untouched and authoritative: if `host.data` already holds a value when the host connects, the controller does nothing and the markup is ignored.\n *\n * Source resolution order on connect, first hit wins:\n *\n * 1. `host.data` already set in JavaScript -> leave it, read nothing.\n * 2. A direct-child `<script type=\"application/json\" class=\"roxy-data\">` -> parse and use. Direct-child only, so a nested component's own script is never read by an ancestor.\n *\n * Fetching from a URL is intentionally unsupported: that would require a browser-visible key and breaks the server-rendered, cached model these consumers rely on.\n *\n * Timing: {@link hostConnected} runs inside the host `connectedCallback`. For an element parsed from server HTML, its direct children are present by the time the custom element upgrades and connects, so the script is readable here. For an element created with `document.createElement` and connected before any child is appended, there is nothing to read and the property path is the only source, which is exactly the existing behavior.\n *\n * Failure is safe: malformed JSON or a missing script leaves `host.data` untouched, so the host renders its normal empty state.\n *\n * Reading the script never mutates it, and only the marked script is touched, so any sibling fallback markup a server nested inside the element (for no-JavaScript, AMP, or crawler rendering) is left in place.\n *\n * @example\n * ```ts\n * import { MarkupDataController } from '../utils/markup-data.js';\n *\n * export class RoxyExample extends LitElement {\n * constructor() {\n * super();\n * new MarkupDataController(this);\n * }\n *\n * @property({ attribute: false })\n * data: ExampleResponse | null = null;\n * }\n * ```\n */\nexport class MarkupDataController<T = unknown> implements ReactiveController {\n\tprivate readonly host: DataHost;\n\n\tconstructor(host: DataHost) {\n\t\tthis.host = host;\n\t\thost.addController(this);\n\t}\n\n\thostConnected() {\n\t\t// Property path wins. If the consumer (React, vanilla `.data =`, the\n\t\t// widgets script, an MCP agent) already set data, never look at markup.\n\t\tif (this.host.data != null) return;\n\n\t\tconst parsed = this.read();\n\t\tif (parsed === undefined) return;\n\n\t\tthis.host.data = parsed as T;\n\t\tthis.host.requestUpdate();\n\t}\n\n\t/**\n\t * Resolve the embedded payload. Returns `undefined` when there is nothing valid to read so the caller can leave `host.data` untouched.\n\t */\n\tprivate read(): T | undefined {\n\t\tconst inline = this.findInlineScript();\n\t\treturn inline ? this.parse(inline.textContent) : undefined;\n\t}\n\n\t/**\n\t * Direct-child `<script type=\"application/json\" class=\"roxy-data\">`. Scoped to immediate children so a nested data-driven component never has its script read by an ancestor, and so sibling fallback markup is ignored.\n\t */\n\tprivate findInlineScript(): Element | null {\n\t\tfor (const child of Array.from(this.host.children)) {\n\t\t\tif (isJsonScript(child) && child.classList.contains(ROXY_DATA_CLASS)) {\n\t\t\t\treturn child;\n\t\t\t}\n\t\t}\n\t\treturn null;\n\t}\n\n\tprivate parse(text: string | null): T | undefined {\n\t\tif (!text?.trim()) return undefined;\n\t\ttry {\n\t\t\treturn JSON.parse(text) as T;\n\t\t} catch {\n\t\t\t// Malformed embedded JSON: fail safe, leave the host empty state in\n\t\t\t// place rather than throwing during connect.\n\t\t\treturn undefined;\n\t\t}\n\t}\n}\n"],
|
|
5
|
-
"mappings": "wMAAA,OAAS,OAAAA,GAAK,QAAAC,EAAM,WAAAC,EAAS,OAAAC,MAAW,MACxC,OAAS,iBAAAC,OAAqB,oBC4BvB,SAASC,EAAUC,EAAmB,CAC5C,OAAOA,EACL,YAAY,EACZ,QAAQ,WAAY,GAAG,EACvB,KAAK,CACR,CClBA,IAAMC,GAAU,CACfC,EACAC,IACyBA,EAAOD,EAAME,EAAUD,CAAI,CAAC,EAAI,OAuI1D,IAAME,GAAwC,CAC7C,OAAQ,IACR,KAAM,IACN,KAAM,IACN,QAAS,IACT,KAAM,IACN,MAAO,IACP,SAAU,IACV,MAAO,GACR,EAGaC,EACZC,GACwBC,GAAQH,GAAeE,CAAI,ECxKpD,OAGC,QAAAE,EACA,WAAAC,MAEM,MACP,OAAS,YAAAC,EAAU,SAAAC,MAAa,oBAChC,OAAS,aAAAC,MAAiB,+BCR1B,OAAS,cAAAC,OAAkB,MC6BpB,SAASC,EAAYC,EAAqC,CAGhE,GAAIA,EAAG,KAAM,OAAOA,EAAG,KACvB,GAAI,OAAO,SAAa,IAAa,OACrC,IAAMC,EAAYD,EAAG,UAAU,QAAQ,GAAG,aAAa,MAAM,EAC7D,OAAIC,GACG,SAAS,gBAAgB,MAAQ,MACzC,CCOA,IAAMC,EAAa,mBAEnB,SAASC,GAA2B,CACnC,IAAMC,EAAS,WACTC,EAAWD,EAAOF,CAAU,EAClC,GAAIG,EAAU,OAAOA,EACrB,IAAMC,EAA0B,CAC/B,SAAU,CAAC,EACX,YAAa,CAAC,EACd,UAAW,IAAI,IACf,UAAW,IAAI,GAChB,EACA,OAAAF,EAAOF,CAAU,EAAII,EACdA,CACR,CA0BO,SAASC,EACfC,EACAC,EACS,CACT,OAAKA,EACED,EAAS,QAAQ,iBAAkB,CAACE,EAAOC,IACjDA,KAAOF,EAAO,OAAOA,EAAKE,CAAG,GAAK,EAAE,EAAID,CACzC,EAHkBF,CAInB,CAQO,SAASI,EACfC,EACAC,EACAL,EACS,CACT,GAAI,CAACI,EAAM,OAAON,EAAYO,EAAQL,CAAI,EAC1C,GAAM,CAAE,SAAAM,CAAS,EAAIC,EAAS,EACxBC,EAAMJ,EAAK,YAAY,EACvBK,EAAUH,EAASE,CAAG,GAAKF,EAASE,EAAI,MAAM,GAAG,EAAE,CAAC,CAAW,EACrE,OAAOV,EAAYW,IAAUC,EAAUL,CAAM,CAAC,GAAKA,EAAQL,CAAI,CAChE,CAiDO,SAASW,EAAeC,EAAkC,CAChE,GAAM,CAAE,UAAAC,CAAU,EAAIC,EAAS,EAC/B,OAAAD,EAAU,IAAID,CAAQ,EACf,IAAM,CACZC,EAAU,OAAOD,CAAQ,CAC1B,CACD,CC1JO,IAAMG,EAAN,KAAqD,CAI3D,YAAYC,EAA8B,CACzC,KAAK,KAAOA,EACZA,EAAK,cAAc,IAAI,CACxB,CAEA,eAAsB,CACrB,KAAK,YAAcC,EAAe,IAAM,KAAK,KAAK,cAAc,CAAC,CAClE,CAEA,kBAAyB,CACxB,KAAK,cAAc,EACnB,KAAK,YAAc,MACpB,CACD,EHbO,IAAeC,EAAf,cAA4CC,EAAW,CAC7D,aAAc,CACb,MAAM,EA0BP,KAAmB,WAAa,CAC/BC,EACAC,IACY,KAAK,EAAED,EAAQC,CAAI,EAzB/B,IAAIC,EAAiB,IAAI,CAC1B,CAgBU,EAAEF,EAAgBC,EAAgD,CAC3E,OAAOE,EAAU,KAAK,cAAc,EAAGH,EAAQC,CAAI,CACpD,CAaU,eAAoC,CAC7C,OAAOG,EAAY,IAAI,CACxB,CACD,EIxDA,OAAS,OAAAC,OAAW,MAMb,IAAMC,EAAaD,+4FCN1B,IAAME,GAAO,SACPC,GAAO,SAEb,SAASC,GAAcC,EAAkD,CACxE,OAAO,OAAOA,GAAU,UAAYA,IAAU,MAAQ,CAAC,MAAM,QAAQA,CAAK,CAC3E,CAQA,SAASC,EAAOD,EAAyB,CACxC,GAAI,MAAM,QAAQA,CAAK,EAAG,CACzB,IAAIE,EAAU,GACRC,EAAMH,EAAM,IAAKI,GAAS,CAC/B,IAAMC,EAAOJ,EAAOG,CAAI,EACxB,OAAIC,IAASD,IAAMF,EAAU,IACtBG,CACR,CAAC,EACD,OAAOH,EAAUC,EAAMH,CACxB,CACA,GAAI,CAACD,GAAcC,CAAK,EAAG,OAAOA,EAElC,IAAMM,EAAON,EAAMH,EAAI,EACjBU,EAAOP,EAAMF,EAAI,EAGvB,GACC,MAAM,QAAQQ,CAAI,GAClB,MAAM,QAAQC,CAAI,GAClB,OAAO,KAAKP,CAAK,EAAE,SAAW,EAE9B,OAAOO,EAAK,IAAKC,GAAQ,CACxB,IAAMJ,EAAgC,CAAC,EACvC,OAACE,EAAkB,QAAQ,CAACG,EAAKC,IAAM,CACtCN,EAAKK,CAAG,EAAIR,EAAQO,EAAkBE,CAAC,CAAC,CACzC,CAAC,EACMN,CACR,CAAC,EAGF,IAAIF,EAAU,GACRC,EAA+B,CAAC,EACtC,OAAW,CAACQ,EAAKP,CAAI,IAAK,OAAO,QAAQJ,CAAK,EAAG,CAChD,IAAMK,EAAOJ,EAAOG,CAAI,EACpBC,IAASD,IAAMF,EAAU,IAC7BC,EAAIQ,CAAG,EAAIN,CACZ,CACA,OAAOH,EAAUC,EAAMH,CACxB,CAkBO,SAASY,EAAiBZ,EAAa,CAC7C,OAAOC,EAAOD,CAAK,CACpB,CClEO,IAAMa,EACZ,mIAUM,SAASC,EAAaC,EAAyC,CACrE,MAAO,CAAC,CAACA,GAAO,CAACA,EAAI,WAAW,KAAK,CACtC,CAKO,SAASC,EACfC,EACAC,EAA2B,CAAC,EACrB,CACHA,EAAK,MAAM,QAAQ,KAAKC,CAAmB,EAC/CF,EAAK,cACJ,IAAI,YAAY,wBAAyB,CACxC,OAAQ,CAAE,OAAQ,sBAAuB,QAASE,CAAoB,EACtE,QAAS,GACT,SAAU,EACX,CAAC,CACF,CACD,CCZO,IAAMC,GAAmB,6BAQhC,eAAsBC,GAAaC,EAAgC,CAClE,GAAI,CACH,IAAMC,EAAQ,MAAMD,EAAI,KAAK,EAC7B,GAAIC,GAAM,MAAO,OAAOA,EAAK,KAC9B,MAAQ,CAER,CACA,MAAO,mBAAmBD,EAAI,MAAM,GACrC,CAqBO,IAAME,EAAN,KAAiE,CAoBvE,YAAYC,EAAoB,CAbhC,aAAUL,GAcT,KAAK,KAAOK,EACZA,EAAK,cAAc,IAAI,CACxB,CAEA,kBAAmB,CAClB,KAAK,OAAO,MAAM,EAClB,KAAK,MAAQ,MACd,CAOA,MAAM,IAAIC,EAAiC,CAE1C,GAAI,CAAC,KAAK,WAAa,KAAK,iBAAiB,EAAG,OAChD,KAAK,OAAO,MAAM,EAClB,IAAMC,EAAa,IAAI,gBACvB,KAAK,MAAQA,EACb,KAAK,KAAK,QAAU,GACpB,KAAK,KAAK,MAAQ,KAClB,GAAI,CACH,IAAML,EAAM,KAAK,UACd,MAAM,MAAM,KAAK,UAAW,CAC5B,OAAQ,OACR,QAAS,CACR,OAAQ,mBACR,eAAgB,kBACjB,EACA,KAAM,KAAK,UAAUI,CAAG,EACxB,OAAQC,EAAW,MACpB,CAAC,EACA,MAAM,KAAK,QAAQD,EAAKC,EAAW,MAAM,EAC5C,GAAI,CAACL,EAAI,GAAI,MAAM,IAAI,MAAM,MAAMD,GAAaC,CAAG,CAAC,EACpD,IAAMM,EAAQ,MAAMN,EAAI,KAAK,EAC7B,GAAIK,EAAW,OAAO,QAAS,OAC/B,KAAK,KAAK,KAAOC,CAClB,OAASC,EAAK,CACb,GAAKA,GAA2B,OAAS,aAAc,OACvD,KAAK,KAAK,MAAQA,aAAe,MAAQA,EAAI,QAAU,OAAOA,CAAG,CAClE,QAAE,CACG,KAAK,QAAUF,IAAY,KAAK,MAAQ,QACvCA,EAAW,OAAO,UAAS,KAAK,KAAK,QAAU,GACrD,CACD,CAQQ,UAAUD,EAA0B,CAC3C,OAAO,KAAK,UACX,KAAK,cAAgB,CAAE,GAAGA,EAAK,QAAS,KAAK,aAAc,EAAIA,CAChE,CACD,CAGQ,QAAQA,EAAkBI,EAAwC,CAIzE,IAAMC,EAAM,IAAI,IAAI,GAAG,KAAK,OAAO,GAAGL,EAAI,IAAI,GAAI,SAAS,OAAO,EAClE,OAAW,CAACM,EAAGC,CAAC,IAAK,OAAO,QAAQP,EAAI,OAAS,CAAC,CAAC,EAC9CO,GAAK,MAAMF,EAAI,aAAa,IAAIC,EAAG,OAAOC,CAAC,CAAC,EAEjD,IAAMC,EAAkC,CAAE,OAAQ,kBAAmB,EACrE,OAAI,KAAK,iBAAgBA,EAAQ,WAAW,EAAI,KAAK,gBACjDR,EAAI,MAAQ,OAAMQ,EAAQ,cAAc,EAAI,oBACzC,MAAMH,EAAK,CACjB,OAAQL,EAAI,QAAU,MACtB,QAAAQ,EACA,KAAMR,EAAI,MAAQ,KAAO,KAAK,UAAUA,EAAI,IAAI,EAAI,OACpD,OAAAI,CACD,CAAC,CACF,CAGQ,kBAA4B,CACnC,OAAKK,EAAa,KAAK,cAAc,GACrC,KAAK,KAAK,MAAQC,EAClBC,EAAmB,KAAK,IAAI,EACrB,IAHwC,EAIhD,CACD,EAOO,SAASC,EACfC,EACAC,EACAC,EACAC,EAA+B,CAAC,EAClB,CACd,IAAMC,EAAgC,CAAE,GAAGF,CAAO,EAC5CG,EAAO,IAAIL,EAAS,QAAQ,MAAO,EAAE,CAAC,GAAG,QAC9C,eACA,CAACM,EAAQC,IAAiB,CACzB,IAAMb,EAAIU,EAAKG,CAAI,EACnB,cAAOH,EAAKG,CAAI,EACT,mBAAmB,OAAOb,GAAK,EAAE,CAAC,CAC1C,CACD,EACMc,EAAU,IAAI,IAAIL,CAAS,EAC3BM,EAAqD,CAAC,EACtDzB,EAAgC,CAAC,EACvC,OAAW,CAACS,EAAGC,CAAC,IAAK,OAAO,QAAQU,CAAI,EACnCV,IAAM,QAAaA,IAAM,KACzBO,IAAW,OAASO,EAAQ,IAAIf,CAAC,EAAGgB,EAAMhB,CAAC,EAAIC,EAC9CV,EAAKS,CAAC,EAAIC,GAEhB,MAAO,CAAE,KAAAW,EAAM,OAAAJ,EAAQ,MAAAQ,EAAO,KAAMR,IAAW,OAASjB,EAAO,MAAU,CAC1E,CC3LA,OAAS,OAAA0B,EAAK,QAAAC,EAAM,WAAAC,MAAe,MCVnC,OAAS,OAAAC,GAAK,QAAAC,OAAY,MAQnB,SAASC,GAA0B,CACzC,OAAOD,8NACR,CAQO,IAAME,EAAmBH,sYDazB,IAAMI,GAAsBC,2RAEtBC,EAAwBD,09CAA49CD,EAAmB,GA+B7gD,SAASG,EACfC,EACAC,EACAC,EACC,CACD,IAAMC,EAAQH,EAAS,OAAQI,GAAM,EAAQA,EAAE,IAAK,EACpD,OAAID,EAAM,SAAW,EAAUE,EAExBC,uDAA0DJ,CAAO,QAAQC,EAAM,IACpF,CACCC,EACAG,IACID,sDAAyDL,CAAI,YAAYM,IAAM,CAAC,wCAAwCH,EAAE,KAAK,WAAWI,EAAQ,CAAC,IAAIJ,EAAE,MAAQE,sCAAyCF,EAAE,KAAK,kBAAoBC,CAAO,yCAAyCD,EAAE,IAAI,OAAOA,EAAE,OAASC,CAAO,kBAC1T,CAAC,YACH,CEnEA,IAAMI,GAAkB,YAkDxB,SAASC,GAAaC,EAAsB,CAC3C,OACCA,EAAG,WAAa,UAAYA,EAAG,aAAa,MAAM,IAAM,kBAE1D,CA2CO,IAAMC,EAAN,KAAsE,CAG5E,YAAYC,EAAgB,CAC3B,KAAK,KAAOA,EACZA,EAAK,cAAc,IAAI,CACxB,CAEA,eAAgB,CAGf,GAAI,KAAK,KAAK,MAAQ,KAAM,OAE5B,IAAMC,EAAS,KAAK,KAAK,EACrBA,IAAW,SAEf,KAAK,KAAK,KAAOA,EACjB,KAAK,KAAK,cAAc,EACzB,CAKQ,MAAsB,CAC7B,IAAMC,EAAS,KAAK,iBAAiB,EACrC,OAAOA,EAAS,KAAK,MAAMA,EAAO,WAAW,EAAI,MAClD,CAKQ,kBAAmC,CAC1C,QAAWC,KAAS,MAAM,KAAK,KAAK,KAAK,QAAQ,EAChD,GAAIN,GAAaM,CAAK,GAAKA,EAAM,UAAU,SAASC,EAAe,EAClE,OAAOD,EAGT,OAAO,IACR,CAEQ,MAAME,EAAoC,CACjD,GAAKA,GAAM,KAAK,EAChB,GAAI,CACH,OAAO,KAAK,MAAMA,CAAI,CACvB,MAAQ,CAGP,MACD,CACD,CACD,EXrIA,IAAMC,GAEF,CACH,cAAgBC,GAAU,CACzB,GAAIA,GAAS,KACb,IAAI,CACH,IAAMC,EAAkB,KAAK,MAAMD,CAAK,EACxC,GAAIC,GAAU,OAAOA,GAAW,UAAY,CAAC,MAAM,QAAQA,CAAM,EAChE,OAAOA,CAET,MAAQ,CAER,CACA,QAAQ,KACP,iFACD,EAED,CACD,EA8BsBC,EAAf,cAEGC,CAAqB,CAiI9B,aAAc,CACb,MAAM,EA7HP,UAAiB,KAIjB,cAAW,GAIX,YAAyB,OAiDzB,cAAW,GAWX,kBAAe,GAmBf,kBAAe,GAYf,aAAU,GAIV,WAAuB,KAMvB,KAAQ,YAAc,GAItB,KAAQ,QAAU,GAIlB,KAAQ,OAAS,GA8HjB,KAAQ,OAAS,IAAM,CACtB,KAAK,QAAU,EAChB,EAiCA,KAAQ,aAAgBC,GAAa,CACpC,IAAMC,EAAUD,EAAkB,OAKlC,KAAK,WAAaC,EAAO,OACzB,KAAK,OAAS,CAAC,CAACA,EAAO,OACvB,KAAK,YAAc,GACnB,KAAK,QAAU,GACX,KAAK,UAAU,KAAK,gBAAgBA,EAAO,MAAM,EAChD,KAAK,QAAQ,IACjBC,EACC,KAAK,SACL,KAAK,OACLD,EAAO,OACPA,EAAO,WAAa,CAAC,CACtB,CACD,CACD,EAzKC,IAAIE,EAAwB,IAAI,EAChC,KAAK,QAAU,IAAIC,EAAmB,IAAI,CAC3C,CAtIA,YAAO,OAAyB,CAACC,CAAU,EAwIjC,WAAWC,EAA+B,CAOnD,GAAIA,EAAQ,IAAI,MAAM,GAAK,KAAK,MAAQ,KAAM,CAC7C,IAAMC,EAAWC,EAAc,KAAK,IAAI,EACpCD,IAAa,KAAK,OAAM,KAAK,KAAOA,EACzC,CACID,EAAQ,IAAI,gBAAgB,IAC/B,KAAK,QAAQ,eAAiB,KAAK,gBAEhCA,EAAQ,IAAI,SAAS,GAAK,KAAK,UAClC,KAAK,QAAQ,QAAU,KAAK,SAEzBA,EAAQ,IAAI,WAAW,IAC1B,KAAK,QAAQ,UAAY,KAAK,WAE3BA,EAAQ,IAAI,eAAe,IAC9B,KAAK,QAAQ,cAAgB,KAAK,cAEpC,CAEA,QAAkB,CACjB,OAAOG,IAAO,KAAK,oBAAoB,CAAC,GAAG,KAAK,YAAY,CAAC,EAC9D,CAcQ,qBAA+B,CACtC,IAAMC,EAAQ,KAAK,aACjB,MAAM,GAAG,EACT,IAAKC,GAAMA,EAAE,KAAK,EAAE,YAAY,CAAC,EACjC,OAAQA,GAAM,oBAAoB,KAAKA,CAAC,CAAC,EAC3C,GAAID,EAAM,SAAW,EAAG,OAAOE,EAC/B,IAAMC,EAAQH,EACZ,IAAKC,GAAM,WAAWA,CAAC,4BAA4B,EACnD,KAAK,EAAE,EACT,OAAOF,WAAcI,CAAK,UAC3B,CAGQ,aAAuB,CAC9B,OAAI,KAAK,QAAgB,KAAK,cAAc,EACxC,KAAK,OAAS,KAAa,KAAK,YAAY,KAAK,KAAK,EACtD,KAAK,MAAQ,KAMX,KAAK,YAKN,KAAK,QAAgB,KAAK,WAAW,EAClC,KAAK,aAAa,KAAK,IAAI,EAL1B,KAAK,gBAAgB,EACzBJ,IAAO,KAAK,WAAW,KAAK,IAAI,CAAC,GAAG,KAAK,kBAAkB,CAAC,GAC5D,KAAK,WAAW,KAAK,IAAI,EAKvB,KAAK,aAAa,CAC1B,CAeU,qBACTK,EACAC,EACAC,EACU,CACV,OAAI,KAAK,aAAqBJ,EAIvBK,EAAsBH,EAAUC,EAAM,KAAK,EAAEC,GAAW,SAAS,CAAC,CAC1E,CAKU,aAAaE,EAAkB,CACxC,IAAMC,EAAO,KAAK,OACfV,IAAO,KAAK,WAAW,CAAC,GAAG,KAAK,WAAWS,CAAI,CAAC,GAChDT,+FAAkG,KAAK,MAAM,KAAK,KAAK,EAAE,YAAY,CAAC,kBAAkB,KAAK,WAAWS,CAAI,CAAC,GAChL,OAAO,KAAK,gBAAgB,EACzBT,IAAOU,CAAI,GAAG,KAAK,kBAAkB,CAAC,GACtCA,CACJ,CAOQ,iBAA2B,CAClC,OACC,KAAK,aAAe,MACpB,KAAK,cAAgB,OACrB,KAAK,cAAgB,OAEvB,CAGU,mBAA6B,CACtC,OAAOV,sJAAyJ,KAAK,EAAE,2BAA2B,CAAC,YACpM,CAGU,cAAwB,CACjC,OAAO,KAAK,SAAW,KAAK,WAAW,EAAI,KAAK,YAAY,CAC7D,CAGU,YAAsB,CAC/B,OAAOA,mDAAsD,KAAK,QAAQ,aAAa,KAAK,MAAM,eAAeW,EAAU,KAAK,OAAO,CAAC,sBAAsBA,EAAU,KAAK,cAAc,CAAC,mBAAmBA,EAAU,KAAK,WAAW,CAAC,mBAAmBA,EAAU,KAAK,WAAW,CAAC,WAAWA,EAAU,KAAK,cAAc,CAAC,CAAC,qBAAqB,KAAK,kBAAkB,CAAC,mBAAmB,KAAK,YAAY,yBACpZ,CAGQ,mBAAyD,CAChE,OACC,KAAK,aAAe,KAAK,SAAW,KAAK,eAAe,EAAI,OAE9D,CAwBQ,aAAsB,CAC7B,MAAO,gBAAgB,KAAK,QAAQ,EACrC,CAEQ,gBAAsD,CAC7D,GAAI,CACH,IAAMC,EAAM,eAAe,QAAQ,KAAK,YAAY,CAAC,EACrD,OAAOA,EAAO,KAAK,MAAMA,CAAG,EAAgC,MAC7D,MAAQ,CACP,MACD,CACD,CAEQ,gBAAgBC,EAAuC,CAC9D,GAAI,CACH,eAAe,QAAQ,KAAK,YAAY,EAAG,KAAK,UAAUA,CAAM,CAAC,CAClE,MAAQ,CAER,CACD,CAGU,aAAuB,CAChC,OAAOb,uDAA0D,KAAK,EAAE,SAAS,CAAC,QACnF,CAGU,eAAyB,CAClC,OAAOA,6EAAgF,KAAK,EAAE,SAAS,CAAC,yBACzG,CAOU,YAAYc,EAA0B,CAC/C,IAAMC,EAASf,sDAAyD,KAAK,EAAEc,CAAO,CAAC,SACvF,OAAO,KAAK,SAAWd,IAAOe,CAAM,GAAG,KAAK,WAAW,CAAC,GAAKA,CAC9D,CACD,EApVCC,EAAA,CADCC,EAAS,CAAE,UAAW,EAAM,CAAC,GANT5B,EAOrB,oBAIA2B,EAAA,CADCC,EAAS,CAAE,KAAM,OAAQ,UAAW,eAAgB,CAAC,GAVjC5B,EAWrB,wBAIA2B,EAAA,CADCC,EAAS,CAAE,KAAM,MAAO,CAAC,GAdL5B,EAerB,sBAIA2B,EAAA,CADCC,EAAS,CAAE,KAAM,OAAQ,UAAW,iBAAkB,CAAC,GAlBnC5B,EAmBrB,8BAIA2B,EAAA,CADCC,EAAS,CAAE,KAAM,OAAQ,UAAW,UAAW,CAAC,GAtB5B5B,EAuBrB,uBAIA2B,EAAA,CADCC,EAAS,CAAE,KAAM,OAAQ,UAAW,UAAW,CAAC,GA1B5B5B,EA2BrB,uBAIA2B,EAAA,CADCC,EAAS,CAAE,KAAM,OAAQ,UAAW,YAAa,CAAC,GA9B9B5B,EA+BrB,yBAoBA2B,EAAA,CADCC,EAAS,CAAE,UAAW,iBAAkB,UAAW/B,EAAuB,CAAC,GAlDvDG,EAmDrB,6BASA2B,EAAA,CADCC,EAAS,CAAE,KAAM,OAAQ,UAAW,cAAe,CAAC,GA3DhC5B,EA4DrB,2BAIA2B,EAAA,CADCC,EAAS,CAAE,KAAM,OAAQ,CAAC,GA/DN5B,EAgErB,wBAWA2B,EAAA,CADCC,EAAS,CAAE,KAAM,QAAS,UAAW,gBAAiB,QAAS,EAAK,CAAC,GA1EjD5B,EA2ErB,4BAmBA2B,EAAA,CADCC,EAAS,CAAE,KAAM,OAAQ,UAAW,gBAAiB,QAAS,EAAK,CAAC,GA7FhD5B,EA8FrB,4BAIA2B,EAAA,CADCC,EAAS,CAAE,KAAM,OAAQ,UAAW,cAAe,CAAC,GAjGhC5B,EAkGrB,2BAIA2B,EAAA,CADCC,EAAS,CAAE,KAAM,MAAO,CAAC,GArGL5B,EAsGrB,2BAIA2B,EAAA,CADCE,EAAM,GAzGc7B,EA0GrB,uBAIA2B,EAAA,CADCE,EAAM,GA7Gc7B,EA8GrB,qBAMQ2B,EAAA,CADPE,EAAM,GAnHc7B,EAoHb,2BAIA2B,EAAA,CADPE,EAAM,GAvHc7B,EAwHb,uBAIA2B,EAAA,CADPE,EAAM,GA3Hc7B,EA4Hb,sBH/JF,IAAM8B,EAAN,cAA2BC,CAA8B,CAQvD,iBAMC,CACR,IAAMC,EAAI,KAAK,KACf,GAAI,CAACA,EAAG,OAAO,KACf,GAAI,aAAcA,GAAKA,EAAE,SAAU,CAClC,GAAI,UAAWA,EAAG,CACjB,IAAMC,EAAOD,EACb,MAAO,CACN,IAAKC,EAAK,SACV,MAAOA,EAAK,MACZ,sBAAuBA,EAAK,sBAC5B,kBAAmBA,EAAK,iBACzB,CACD,CACA,IAAMC,EAAQF,EACd,MAAO,CACN,IAAKE,EAAM,SACX,aAAcA,EAAM,YACrB,CACD,CACA,MAAO,CAAE,IAAKF,CAAc,CAC7B,CAEU,YAAa,CACtB,IAAMG,EAAW,KAAK,gBAAgB,EACtC,GAAI,CAACA,EAAU,OAAO,KAAK,YAAY,EAEvC,GAAM,CACL,IAAKC,EACL,MAAOC,EACP,sBAAAC,EACA,aAAAC,EACA,kBAAAC,CACD,EAAIL,EACEM,EAAQJ,GAAa,KAAK,aAAaD,CAAC,EACxCM,EAAW,IAAI,IAAIJ,GAAyB,CAAC,CAAC,EAE9CK,EAAW,CAAC,KAAK,aAEvB,OAAOC,kDAAqD,KAAK,EAAE,kBAAkB,CAAC,sCAAsCR,EAAE,OAASQ,wBAA2BR,EAAE,MAAM,SAAWS,CAAO,yCAAyCJ,EAChO,MAAM,EACN,QAAQ,EACR,IAAI,CAACK,EAAGC,IAAQ,CAEhB,IAAMC,EAAUP,EAAM,OAAS,EAAIM,EAAM,EACnCE,EAAaP,EAAS,IAAIM,CAAO,EACjCE,EAASJ,IAAM,GAAKA,IAAM,EAEhC,OAAOF,qBADK,GAAGM,EAAS,SAAW,OAAO,GAAGD,EAAa,YAAc,EAAE,EACxC,KAChCC,EACGC,sDACAA,4BACJ,QACF,CAAC,CAAC,oDAIF,CACCf,EAAE,QAAU,KAAO,GAAGA,EAAE,MAAM,IAAM,GACpCA,EAAE,SAAWA,EAAE,SAAW,UAC3B,EACE,OAAO,OAAO,EACd,KAAK,GAAG,CACX,4BAA4BA,EAAE,QAAUQ,IAAOR,EAAE,OAAO,GAAKS,CAAO,IAAIT,EAAE,OAASQ,MAASR,EAAE,MAAM,GAAKS,CAAO,4CAC/GT,EAAE,aACCQ,SAAY,KAAK,EAAE,OAAO,CAAC,4BAA4BQ,EAAahB,EAAE,YAAY,GAAK,EAAE,UAAUA,EAAE,YAAY,SACjHS,CACJ,IACCT,EAAE,aACCQ,SAAY,KAAK,EAAE,OAAO,CAAC,4BAA4BQ,EAAahB,EAAE,YAAY,GAAK,EAAE,UAAUA,EAAE,YAAY,SACjHS,CACJ,SAIAT,EAAE,UAAYO,EACXC,wBAA2BR,EAAE,QAAQ,OACrCS,CACJ,IAAIT,EAAE,OAASO,EAAWC,qBAAwBR,EAAE,KAAK,OAASS,CAAO,IAAIN,GAAgBI,EAAWC,uBAA0BL,CAAY,OAASM,CAAO,IAC7JT,EAAE,gBAAgB,SAAWO,EAC1BC,OAAUR,EAAE,eAAe,OAAO,OAClCS,CACJ,IACCH,EAAS,KAAO,EACbE,wDAA2D,KAAK,EAAE,6BAA8B,CAChG,MAAO,MAAM,KAAKF,CAAQ,EACxB,KAAK,CAACW,EAAGC,IAAMD,EAAIC,CAAC,EACpB,KAAK,IAAI,CACZ,CAAC,CAAC,IACDd,GAAmB,QAChBI,IAAO,KAAK,EAAE,wCAAyC,CACvD,OAAQJ,EAAkB,OAC1B,KAAMA,EAAkB,OACzB,CAAC,CAAC,GACDK,CACJ,SACCA,CACJ,IAAI,KAAK,YAAYT,EAAGM,CAAQ,CAAC,kBACpC,CAQQ,YAAYN,EAAaM,EAAuB,CACvD,IAAMa,EAAMnB,EAAE,eAAiB,CAAC,EAChC,GAAImB,EAAI,SAAW,EAAG,OAAOV,EAE7B,IAAMW,EAASd,EAAS,KAAO,EACzBe,EAAQD,EAASD,EAAI,OAAQ,GAAMb,EAAS,IAAI,EAAE,QAAQ,CAAC,EAAIa,EACrE,GAAIE,EAAM,SAAW,EAAG,OAAOZ,EAE/B,IAAMa,EAA4BD,EAAM,IAAK,IAAO,CACnD,MAAO,QAAQ,EAAE,QAAQ,GACzB,KAAM,EAAE,MAAQ,GAChB,MAAO,EAAE,QACNb,4BAA+B,EAAE,OAAO,OACxCC,CACJ,EAAE,EAEF,OAAO,KAAK,qBACXa,EACA,iBACAF,EAAS,iBAAmB,OAC7B,CACD,CAQQ,aAAapB,EAAuB,CAC3C,IAAMuB,EAASvB,EAAE,QAAU,GAC3B,MAAI,YAAY,KAAKuB,CAAM,EACnB,MAAM,KAAKA,EAASC,GAAOA,IAAM,IAAM,EAAI,CAAE,EAE9C,MAAM,KAAK,CAAE,OAAQ,CAAE,EAAG,IAAM,CAAC,CACzC,CACD,EA3Ja9B,EACL,OAAS,CACf+B,EACAC,EACAC,EACAC,klEACD,EANYlC,EAANmC,EAAA,CADNC,GAAc,eAAe,GACjBpC",
|
|
4
|
+
"sourcesContent": ["import { css, html, nothing, svg } from 'lit';\nimport { customElement } from 'lit/decorators.js';\nimport { trigramGlyph } from '../tokens/index.js';\nimport type {\n\tCastReadingResponse,\n\tGetDailyHexagramResponse,\n\tGetHexagramResponse,\n\tGetRandomHexagramResponse,\n\tHexagram,\n\tLookupHexagramResponse,\n} from '../types/index.js';\nimport { RoxyDataElement } from '../utils/base-element.js';\nimport { baseStyles } from '../utils/base-styles.js';\nimport { disclosureStyles } from '../utils/disclosure.js';\nimport {\n\ttype InterpSection,\n\tinterpAccordionStyles,\n} from '../utils/interp-accordion.js';\n\ntype HexagramData =\n\t| GetHexagramResponse\n\t| GetRandomHexagramResponse\n\t| LookupHexagramResponse\n\t| GetDailyHexagramResponse\n\t| CastReadingResponse;\n\n/**\n * I Ching hexagram card. Renders /iching/hexagrams/{number},\n * /iching/hexagrams/random, /iching/hexagrams/lookup, /iching/cast and\n * /iching/daily.\n *\n * @remarks\n * **There is deliberately no `mode` input.** Which shape arrived is\n * shape-detected from the payload in {@link RoxyHexagram.resolveHexagram}, which\n * is the rule for every multi-endpoint component here: an attribute and a\n * response can disagree, and only one of them is the reading. A `mode` property\n * shipped anyway, reflected and typed into both framework wrappers, and nothing\n * ever read it.\n */\n@customElement('roxy-hexagram')\nexport class RoxyHexagram extends RoxyDataElement<HexagramData> {\n\tstatic styles = [\n\t\tbaseStyles,\n\t\tdisclosureStyles,\n\t\tinterpAccordionStyles,\n\t\tcss`.card{background:var(--roxy-surface,#fff);border:1px solid var(--roxy-border,#e4e4e7);border-radius:var(--roxy-radius-md,8px);padding:var(--roxy-space-lg,1.5rem);box-shadow:var(--roxy-shadow-sm);gap:var(--roxy-space-lg,1.5rem);grid-template-columns:6rem 1fr;display:grid}@container (width<=480px){.card{grid-template-columns:1fr}}.glyphs{gap:var(--roxy-space-md,1rem);align-content:start;align-self:start;justify-items:center;display:grid}.symbol{color:var(--roxy-accent-ink,#b45309);font-size:3rem;line-height:1}.lines{gap:4px;width:4rem;display:grid}.line{justify-content:center;align-items:center;gap:4px;height:8px;display:flex}.seg{background:var(--roxy-fg,#0a0a0a);border-radius:1px;height:6px;display:block}.line.broken .seg{width:1.4rem}.line.solid .seg{width:3rem}.line.changing .seg{background:var(--roxy-accent,#f59e0b)}.title{font-size:var(--roxy-text-xl,1.5rem);font-weight:var(--roxy-weight-bold,600);letter-spacing:var(--roxy-tracking-tight);margin:0}.subtitle{color:var(--roxy-muted,#71717a);font-size:var(--roxy-text-sm,.875rem);margin:0 0 var(--roxy-space-sm,.5rem)}.trigrams{gap:var(--roxy-space-md,1rem);margin-bottom:var(--roxy-space-sm,.5rem);color:var(--roxy-secondary,#475569);font-size:var(--roxy-text-xs,.75rem);text-transform:uppercase;letter-spacing:.06em;display:flex}.tri-glyph{font-size:var(--roxy-text-xl,1.5rem);color:var(--roxy-accent-ink,#b45309);vertical-align:middle;margin-right:4px}.judgment,.image,.message{margin:0 0 var(--roxy-space-sm,.5rem);font-size:var(--roxy-text-sm,.875rem);color:var(--roxy-fg,#0a0a0a)}.judgment:before{content:\"Judgment. \";font-weight:var(--roxy-weight-bold,600);color:var(--roxy-secondary,#475569)}.image:before{content:\"Image. \";font-weight:var(--roxy-weight-bold,600);color:var(--roxy-secondary,#475569)}.line-meaning{padding-left:var(--roxy-space-sm,.5rem);border-left:2px solid var(--roxy-border,#e4e4e7);color:var(--roxy-muted,#71717a);margin:0}.changing{margin-top:var(--roxy-space-md,1rem);padding-top:var(--roxy-space-md,1rem);border-top:1px solid var(--roxy-border,#e4e4e7);color:var(--roxy-accent-ink,#b45309);font-size:var(--roxy-text-sm,.875rem)}`,\n\t];\n\n\tprivate resolveHexagram(): {\n\t\thex: Hexagram;\n\t\tlines?: number[];\n\t\tchangingLinePositions?: number[];\n\t\tdailyMessage?: string;\n\t\tresultingHexagram?: Hexagram;\n\t} | null {\n\t\tconst d = this.data;\n\t\tif (!d) return null;\n\t\tif ('hexagram' in d && d.hexagram) {\n\t\t\tif ('lines' in d) {\n\t\t\t\tconst cast = d as CastReadingResponse;\n\t\t\t\treturn {\n\t\t\t\t\thex: cast.hexagram as Hexagram,\n\t\t\t\t\tlines: cast.lines,\n\t\t\t\t\tchangingLinePositions: cast.changingLinePositions,\n\t\t\t\t\tresultingHexagram: cast.resultingHexagram as Hexagram | undefined,\n\t\t\t\t};\n\t\t\t}\n\t\t\tconst daily = d as GetDailyHexagramResponse;\n\t\t\treturn {\n\t\t\t\thex: daily.hexagram as Hexagram,\n\t\t\t\tdailyMessage: daily.dailyMessage,\n\t\t\t};\n\t\t}\n\t\treturn { hex: d as Hexagram };\n\t}\n\n\tprotected renderData() {\n\t\tconst resolved = this.resolveHexagram();\n\t\tif (!resolved) return this.renderEmpty();\n\n\t\tconst {\n\t\t\thex: h,\n\t\t\tlines: castLines,\n\t\t\tchangingLinePositions,\n\t\t\tdailyMessage,\n\t\t\tresultingHexagram,\n\t\t} = resolved;\n\t\tconst lines = castLines ?? this.derivedLines(h);\n\t\tconst changing = new Set(changingLinePositions ?? []);\n\n\t\tconst readings = !this.hideReadings;\n\n\t\treturn html`<article class=\"card\" part=\"card\" aria-label=\"${this.t('I Ching hexagram')}\"><div class=\"glyphs\" part=\"chart\">${h.symbol ? html`<div class=\"symbol\">${h.symbol}</div>` : nothing} ${\n\t\t\t\t\tlines.length > 0\n\t\t\t\t\t\t? html`<div class=\"lines\" aria-hidden=\"true\">${lines\n\t\t\t\t\t\t\t\t.slice()\n\t\t\t\t\t\t\t\t.reverse()\n\t\t\t\t\t\t\t\t.map((l, idx) => {\n\t\t\t\t\t\t\t\t\t// reverse so visual top is line 6\n\t\t\t\t\t\t\t\t\tconst realIdx = lines.length - 1 - idx + 1;\n\t\t\t\t\t\t\t\t\tconst isChanging = changing.has(realIdx);\n\t\t\t\t\t\t\t\t\tconst broken = l === 6 || l === 8;\n\t\t\t\t\t\t\t\t\tconst cls = `${broken ? 'broken' : 'solid'}${isChanging ? ' changing' : ''}`;\n\t\t\t\t\t\t\t\t\treturn html`<div class=\"line ${cls}\">${\n\t\t\t\t\t\t\t\t\t\t\tbroken\n\t\t\t\t\t\t\t\t\t\t\t\t? svg`<span class=\"seg\"></span><span class=\"seg\"></span>`\n\t\t\t\t\t\t\t\t\t\t\t\t: svg`<span class=\"seg\"></span>`\n\t\t\t\t\t\t\t\t\t\t}</div>`;\n\t\t\t\t\t\t\t\t})}</div>`\n\t\t\t\t\t\t: nothing\n\t\t\t\t}</div><div part=\"header\"><h2 class=\"title\">${\n\t\t\t\t\t\t// One text node, not two. The markup minifier collapses the space\n\t\t\t\t\t\t// between adjacent template expressions, which rendered the title as\n\t\t\t\t\t\t// \"30.The Clinging\" with the separator eaten. Join in JS instead.\n\t\t\t\t\t\t[\n\t\t\t\t\t\t\th.number != null ? `${h.number}.` : '',\n\t\t\t\t\t\t\th.english ?? h.chinese ?? 'Hexagram',\n\t\t\t\t\t\t]\n\t\t\t\t\t\t\t.filter(Boolean)\n\t\t\t\t\t\t\t.join(' ')\n\t\t\t\t\t}</h2><p class=\"subtitle\">${h.chinese ? html`${h.chinese}` : nothing} ${h.pinyin ? html`· ${h.pinyin}` : nothing}</p><div class=\"trigrams\" part=\"details\">${\n\t\t\t\t\t\th.upperTrigram\n\t\t\t\t\t\t\t? html`<div>${this.t('Upper')} <span class=\"tri-glyph\">${trigramGlyph(h.upperTrigram) ?? ''}</span>${h.upperTrigram}</div>`\n\t\t\t\t\t\t\t: nothing\n\t\t\t\t\t} ${\n\t\t\t\t\t\th.lowerTrigram\n\t\t\t\t\t\t\t? html`<div>${this.t('Lower')} <span class=\"tri-glyph\">${trigramGlyph(h.lowerTrigram) ?? ''}</span>${h.lowerTrigram}</div>`\n\t\t\t\t\t\t\t: nothing\n\t\t\t\t\t}</div>${\n\t\t\t\t\t// The Judgment and the Image are the written oracle of the figure, so\n\t\t\t\t\t// they go with the readings; the figure, the trigrams and which lines\n\t\t\t\t\t// are moving are what stays.\n\t\t\t\t\th.judgment && readings\n\t\t\t\t\t\t? html`<p class=\"judgment\">${h.judgment}</p>`\n\t\t\t\t\t\t: nothing\n\t\t\t\t} ${h.image && readings ? html`<p class=\"image\">${h.image}</p>` : nothing} ${dailyMessage && readings ? html`<p class=\"message\">${dailyMessage}</p>` : nothing} ${\n\t\t\t\t\th.interpretation?.general && readings\n\t\t\t\t\t\t? html`<p>${h.interpretation.general}</p>`\n\t\t\t\t\t\t: nothing\n\t\t\t\t} ${\n\t\t\t\t\tchanging.size > 0\n\t\t\t\t\t\t? html`<div class=\"changing\" part=\"section changing-lines\">${this.t('Changing lines: {{lines}}.', {\n\t\t\t\t\t\t\t\tlines: Array.from(changing)\n\t\t\t\t\t\t\t\t\t.sort((a, b) => a - b)\n\t\t\t\t\t\t\t\t\t.join(', '),\n\t\t\t\t\t\t\t})} ${\n\t\t\t\t\t\t\t\tresultingHexagram?.english\n\t\t\t\t\t\t\t\t\t? html`${this.t('Becomes hexagram {{number}} {{name}}.', {\n\t\t\t\t\t\t\t\t\t\t\tnumber: resultingHexagram.number,\n\t\t\t\t\t\t\t\t\t\t\tname: resultingHexagram.english,\n\t\t\t\t\t\t\t\t\t\t})}`\n\t\t\t\t\t\t\t\t\t: nothing\n\t\t\t\t\t\t\t}</div>`\n\t\t\t\t\t\t: nothing\n\t\t\t\t} ${this.renderLines(h, changing)}</div></article>`;\n\t}\n\n\t/**\n\t * The line readings. Each line carries its oracle statement and, since the 2026-07 API rewrite, a written meaning. Both are rendered: a bare \"Changing lines: 3\" leaves a reader no way to know what line 3 is telling them.\n\t *\n\t * @remarks\n\t * When lines are moving, only those lines are shown: a cast turns on the moving lines, and listing the other five buries the answer. With no lines moving (a lookup, a random draw, the daily hexagram) all six are shown, because there the hexagram is being read as a reference rather than as an answer to a question.\n\t */\n\tprivate renderLines(h: Hexagram, changing: Set<number>) {\n\t\tconst all = h.changingLines ?? [];\n\t\tif (all.length === 0) return nothing;\n\n\t\tconst isCast = changing.size > 0;\n\t\tconst shown = isCast ? all.filter((l) => changing.has(l.position)) : all;\n\t\tif (shown.length === 0) return nothing;\n\n\t\tconst sections: InterpSection[] = shown.map((l) => ({\n\t\t\tlabel: `Line ${l.position}`,\n\t\t\tbody: l.text ?? '',\n\t\t\textra: l.meaning\n\t\t\t\t? html`<p class=\"line-meaning\">${l.meaning}</p>`\n\t\t\t\t: nothing,\n\t\t}));\n\n\t\treturn this.renderInterpretation(\n\t\t\tsections,\n\t\t\t'hexagram-lines',\n\t\t\tisCast ? 'Changing lines' : 'Lines',\n\t\t);\n\t}\n\n\t/**\n\t * Lines for a static hexagram (a lookup, a random draw, the hexagram of the day, none of which carry a cast `lines` array): read the `binary` pattern. 6 digits BOTTOM to top, so index 0 is line 1, the bottom line, exactly like the cast `lines` array. 1 = yang (solid, 7), 0 = yin (broken, 8). A response with no usable `binary` yields no lines and the figure is left undrawn, because the six lines ARE response data: a default pattern would draw one hexagram under the name and Unicode symbol of another. The Unicode `symbol` block (U+4DC0) is in King Wen order, NOT line order, so it must never be used to derive the lines either.\n\t *\n\t * @remarks\n\t * This used to `.reverse()`, because the API served `binary` top-to-bottom while documenting it bottom-to-top, and reversing was the only way to render the figure the right way up. The API fixed the data in 2026-07 (the same inversion was making `/cast` return the vertically MIRRORED hexagram for 56 of the 64 figures), so `binary` and `lines` now point the same way and the reverse would flip every asymmetric hexagram upside down. Do not put it back.\n\t */\n\tprivate derivedLines(h: Hexagram): number[] {\n\t\tconst binary = h.binary ?? '';\n\t\tif (/^[01]{6}$/.test(binary)) {\n\t\t\treturn Array.from(binary, (c) => (c === '1' ? 7 : 8));\n\t\t}\n\t\treturn [];\n\t}\n}\n\ndeclare global {\n\tinterface HTMLElementTagNameMap {\n\t\t'roxy-hexagram': RoxyHexagram;\n\t}\n}\n", "/**\n * Shared string helpers used across components. Single source of truth so the\n * same formatting rules apply to every key/label/title that surfaces in the\n * shadow tree.\n *\n * - `lookupKey`: the ONE normalizer every lookup table in this library is keyed\n * and read by (`tokens/index.ts` glyphs and abbreviations, `i18n/` chrome\n * strings).\n * - `capitalize`: title-cases the first character, lowercases the rest. A\n * DISPLAY helper only; it is not a lookup key (see `lookupKey`).\n * - `humanize`: turns an API key (`birth_date`, `birthDate`, `mahadasha-end`)\n * into a label suitable for display (\"Birth date\", \"Mahadasha end\").\n */\n\n/**\n * Fold a name to the canonical key its lookup table is stored under: lower case, every run of spaces, underscores and hyphens collapsed to one space, trimmed.\n *\n * @remarks\n * This exists because a GUESSED key spelling is a defect class this repo has now shipped twice. The glyph tables were keyed off whatever {@link capitalize} happened to produce (`North node`), while the API returns `North Node`, so every call site that reached the table without first calling `capitalize` missed and fell through to a fabricated abbreviation. Aspects hit the same wall from the other side: `/aspects` returns `SEMI SEXTILE` where synastry returns `SEMI_SEXTILE`.\n *\n * One normalizer, applied when a table is DEFINED and again when it is READ, removes the whole class: no call site has to remember a convention, and no table has to guess a spelling. Use it for every new table keyed by an API-supplied name.\n *\n * @example\n * ```ts\n * lookupKey('North Node'); // 'north node'\n * lookupKey('SEMI_SEXTILE'); // 'semi sextile'\n * lookupKey('semi-sextile'); // 'semi sextile'\n * ```\n */\nexport function lookupKey(s: string): string {\n\treturn s\n\t\t.toLowerCase()\n\t\t.replace(/[\\s_-]+/g, ' ')\n\t\t.trim();\n}\n\nexport function capitalize(s: string): string {\n\tif (!s) return '';\n\treturn s.charAt(0).toUpperCase() + s.slice(1).toLowerCase();\n}\n\nexport function humanize(s: string): string {\n\treturn (\n\t\ts\n\t\t\t.replace(/[_-]+/g, ' ')\n\t\t\t.replace(/([a-z])([A-Z])/g, '$1 $2')\n\t\t\t// Split a trailing/embedded digit off a word so \"person1\" reads \"Person 1\"\n\t\t\t// and every group legend and field label spaces its ordinal.\n\t\t\t.replace(/([a-z])([0-9])/g, '$1 $2')\n\t\t\t.replace(/^\\w/, (c) => c.toUpperCase())\n\t);\n}\n", "/**\n * Symbol constants used across components. Single source of truth so chart\n * wheels, card headers, hexagram displays, and panchang tables stay visually\n * consistent.\n *\n * @remarks\n * **Every table here is keyed by {@link lookupKey} and read ONLY through the accessor beside it.** The raw records are deliberately not exported: a component that indexes a record directly has to guess the key convention, and a guessed spelling renders `No North Node R`, `So South Node R` and `Bl Black Moon Lilith` on a live chart. The API returns `North Node` with a space, while {@link capitalize} produces `North node`, so a call site that indexes without normalising misses the table.\n *\n * **A miss returns `undefined`, never a manufactured abbreviation.** A `?? name.slice(0, 2)` fallback renders a failed lookup as a plausible two-letter code that reads exactly like an intentional abbreviation, so nothing about the output says it is broken. A caller that can omit the glyph should omit it (`?? ''`); a caller that must show something falls back to the FULL name, which is visibly wrong at the size these slots are drawn.\n *\n * `tests/tokens.test.ts` resolves every body, sign and aspect name the committed spec can emit against these tables, so a vocabulary the API gains cannot ship unglyphed.\n */\n\nimport { lookupKey } from '../utils/string.js';\n\n/** Look one name up in a normalized table. The single read path for every map in this file. */\nconst resolve = (\n\ttable: Record<string, string>,\n\tname: string | undefined | null,\n): string | undefined => (name ? table[lookupKey(name)] : undefined);\n\nconst PLANET_GLYPH: Record<string, string> = {\n\tsun: '☉',\n\tmoon: '☽',\n\tmercury: '☿',\n\tvenus: '♀',\n\tearth: '♁',\n\tmars: '♂',\n\tjupiter: '♃',\n\tsaturn: '♄',\n\turanus: '♅',\n\tneptune: '♆',\n\tpluto: '♇',\n\trahu: '☊',\n\tketu: '☋',\n\tascendant: 'Asc',\n\tlagna: 'La',\n\t'north node': '☊',\n\t'south node': '☋',\n\tchiron: '⚷',\n\tlilith: '⚸',\n\t'black moon lilith': '⚸',\n};\n\n/** Astrological glyph for a planet or point, or `undefined` when the library has none for it. */\nexport const planetGlyph = (\n\tname: string | undefined | null,\n): string | undefined => resolve(PLANET_GLYPH, name);\n\nconst PLANET_ABBR: Record<string, string> = {\n\tsun: 'Su',\n\tmoon: 'Mo',\n\tmercury: 'Me',\n\tvenus: 'Ve',\n\tmars: 'Ma',\n\tjupiter: 'Ju',\n\tsaturn: 'Sa',\n\turanus: 'Ur',\n\tneptune: 'Ne',\n\tpluto: 'Pl',\n\trahu: 'Ra',\n\tketu: 'Ke',\n\tascendant: 'Asc',\n\tlagna: 'La',\n};\n\n/** Two-letter graha code for the tight cells of a North/South Indian kundli, or `undefined`. */\nexport const planetAbbr = (\n\tname: string | undefined | null,\n): string | undefined => resolve(PLANET_ABBR, name);\n\nconst SIGN_GLYPH: Record<string, string> = {\n\taries: '♈',\n\ttaurus: '♉',\n\tgemini: '♊',\n\tcancer: '♋',\n\tleo: '♌',\n\tvirgo: '♍',\n\tlibra: '♎',\n\tscorpio: '♏',\n\tsagittarius: '♐',\n\tcapricorn: '♑',\n\taquarius: '♒',\n\tpisces: '♓',\n};\n\n/** Zodiac glyph for a sign name in any case, or `undefined`. */\nexport const signGlyph = (\n\tname: string | undefined | null,\n): string | undefined => resolve(SIGN_GLYPH, name);\n\nconst SIGN_ABBR: Record<string, string> = {\n\taries: 'Ar',\n\ttaurus: 'Ta',\n\tgemini: 'Ge',\n\tcancer: 'Cn',\n\tleo: 'Le',\n\tvirgo: 'Vi',\n\tlibra: 'Li',\n\tscorpio: 'Sc',\n\tsagittarius: 'Sg',\n\tcapricorn: 'Cp',\n\taquarius: 'Aq',\n\tpisces: 'Pi',\n};\n\n/** Two-letter rashi code for kundli cells and grid headers, or `undefined`. */\nexport const signAbbr = (name: string | undefined | null): string | undefined =>\n\tresolve(SIGN_ABBR, name);\n\n/** The twelve signs in zodiacal order. Display values, not lookup keys: read them through {@link signGlyph} / {@link signAbbr}. */\nexport const SIGNS_ORDER = [\n\t'Aries',\n\t'Taurus',\n\t'Gemini',\n\t'Cancer',\n\t'Leo',\n\t'Virgo',\n\t'Libra',\n\t'Scorpio',\n\t'Sagittarius',\n\t'Capricorn',\n\t'Aquarius',\n\t'Pisces',\n] as const;\n\n/**\n * Glyph per aspect. Used by the natal, transit and synastry aspect tables.\n *\n * @remarks\n * These are the nine aspects Unicode itself defines as a set, in its Miscellaneous Symbols block note: `260C, 26BA, 2220, 26B9, 25A1, 25B3, 26BC, 26BB, 260D` for 0, 30, 45, 60, 90, 120, 135, 150 and 180 degrees. That is exactly the vocabulary the API returns, so every aspect resolves to a real glyph and none falls through to a truncated slug.\n *\n * Do not substitute the visually similar maths operators. Unicode lists `⊻` XOR and `⊼` NAND as cross-references FROM the real quincunx and semisextile glyphs, so they look like safe stand-ins and are easy to pair the wrong way round, which renders a 150 degree quincunx with the 30 degree semisextile symbol. An astrologer reads the glyph, not the tooltip.\n */\nconst ASPECT_SYMBOL: Record<string, string> = {\n\tconjunction: '☌',\n\tsemisextile: '⚺',\n\t'semi sextile': '⚺',\n\tsemisquare: '∠',\n\t'semi square': '∠',\n\tsextile: '⚹',\n\tsquare: '□',\n\ttrine: '△',\n\tsesquiquadrate: '⚼',\n\tquincunx: '⚻',\n\topposition: '☍',\n};\n\n/** Aspect glyph for any of the separator forms the endpoints use (`SEMI_SEXTILE`, `SEMI SEXTILE`, `semi-sextile`), or `undefined`. */\nexport const aspectSymbol = (\n\tname: string | undefined | null,\n): string | undefined => resolve(ASPECT_SYMBOL, name);\n\n/** Trigrams used by I Ching hexagrams. Eight trigrams compose 64 hexagrams. */\nconst TRIGRAM_GLYPH: Record<string, string> = {\n\theaven: '☰',\n\tlake: '☱',\n\tfire: '☲',\n\tthunder: '☳',\n\twind: '☴',\n\twater: '☵',\n\tmountain: '☶',\n\tearth: '☷',\n};\n\n/** Trigram glyph for a trigram name in any case, or `undefined`. */\nexport const trigramGlyph = (\n\tname: string | undefined | null,\n): string | undefined => resolve(TRIGRAM_GLYPH, name);\n\n/** Moon phase emoji set. Used by the moon phase card. */\nconst MOON_PHASE_EMOJI: Record<string, string> = {\n\t'new moon': '🌑',\n\t'waxing crescent': '🌒',\n\t'first quarter': '🌓',\n\t'waxing gibbous': '🌔',\n\t'full moon': '🌕',\n\t'waning gibbous': '🌖',\n\t'last quarter': '🌗',\n\t'waning crescent': '🌘',\n};\n\n/**\n * Emoji for a lunar phase, or `undefined`.\n *\n * @remarks\n * The live API suffixes most phase names (`Waxing Gibbous Moon`) and calls the third quarter `Third Quarter Moon`, while only new and full moon carry the suffix in the table. Both reconciliations live here rather than in the card, so any component reading a phase name resolves the same eight phases from the same four spellings.\n */\nexport const moonPhaseEmoji = (\n\tname: string | undefined | null,\n): string | undefined => {\n\tif (!name) return undefined;\n\tconst key = lookupKey(name);\n\tconst bare = key.replace(/ moon$/, '');\n\tconst alias = bare === 'third quarter' ? 'last quarter' : bare;\n\treturn MOON_PHASE_EMOJI[key] ?? MOON_PHASE_EMOJI[alias];\n};\n", "import {\n\ttype ComplexAttributeConverter,\n\ttype CSSResultGroup,\n\thtml,\n\tnothing,\n\ttype PropertyValues,\n} from 'lit';\nimport { property, state } from 'lit/decorators.js';\nimport { ifDefined } from 'lit/directives/if-defined.js';\nimport type { ChromeString } from '../i18n/chrome-strings.js';\nimport { RoxyLocalizedElement } from '../i18n/localized-element.js';\nimport { baseStyles } from './base-styles.js';\nimport { expandCompact } from './compact.js';\nimport { buildRequest, FetchController } from './fetch-controller.js';\nimport {\n\ttype InterpSection,\n\trenderInterpAccordion,\n} from './interp-accordion.js';\nimport { MarkupDataController } from './markup-data.js';\n\n/**\n * Read the `submit-context` attribute into the object a proxied submit carries.\n *\n * @remarks\n * Hand-written rather than `type: Object`, which resolves malformed JSON to `null` in silence: a page whose context never left has nothing to look at, and the route it was meant for reports only that the value it expected is not there. One warning covers both refusals (unparseable, or parsed to something that is not an object) because both leave the request without a context, which is the fact worth reading.\n */\nconst submitContextConverter: ComplexAttributeConverter<\n\tRecord<string, unknown> | undefined\n> = {\n\tfromAttribute: (value) => {\n\t\tif (value == null) return undefined;\n\t\ttry {\n\t\t\tconst parsed: unknown = JSON.parse(value);\n\t\t\tif (parsed && typeof parsed === 'object' && !Array.isArray(parsed)) {\n\t\t\t\treturn parsed as Record<string, unknown>;\n\t\t\t}\n\t\t} catch {\n\t\t\t// Both refusals share the warning below.\n\t\t}\n\t\tconsole.warn(\n\t\t\t'[roxy-ui] submit-context must be a JSON object; sending the request without it.',\n\t\t);\n\t\treturn undefined;\n\t},\n};\n\n/**\n * Shared base for every data-driven Roxy component. Consolidates the things every component used to repeat by hand and adds the self-contained, drop-in behavior: controlled-mode hydration, an opt-in self-fetch (form, request, loading, error, empty), the typed `data` slot, and the render switch. A subclass implements one method, {@link RoxyDataElement.renderData}.\n *\n * @remarks\n * Two render modes, one component, which is the whole drop-in contract:\n *\n * - Controlled: a server (WordPress, JSX SSR, static HTML) fetches the response and injects it as a direct-child `<script type=\"application/json\" class=\"roxy-data\">`. {@link MarkupDataController} hydrates `data` from it on connect. No key reaches the browser. This is the path the WordPress plugin drives, and it is unchanged by the base class.\n * - Uncontrolled: no data is injected, but a `data-endpoint` and a `pk_` `publishable-key` are set. The component renders its own `<roxy-endpoint-form>` (an internal detail, never placed by the consumer), and on submit fetches through {@link FetchController}, which refuses any non-publishable key. The result populates `data` and the component renders it.\n *\n * The JavaScript `data` property always wins over markup, so a host that assigns `el.data = …` after upgrade is authoritative.\n *\n * Self-fetch needs `<roxy-endpoint-form>` (and `<roxy-location-search>`) registered. The CDN bundle and the full `@roxyapi/ui` entry register everything; per-component ESM consumers that want self-fetch import the form component too.\n *\n * Two things every subclass inherits for the host page to shape the render from outside the shadow root, with no JavaScript: the `hide-readings` attribute ({@link RoxyDataElement.hideReadings}), and the `part` names on the base's own branches (`form`, `loading`, `error`, `empty`, `edit-bar`, `attribution`). A component adds `part` to its own structural blocks, drawn from the published part vocabulary.\n *\n * Translation is inherited rather than defined here: `t()`, `translator` and `effectiveLang()` live on {@link RoxyLocalizedElement}, which the two declared widgets extend as well, so the form a visitor fills and the card it produces read the same catalogue.\n *\n * @example\n * ```ts\n * @customElement('roxy-dream-card')\n * export class RoxyDreamCard extends RoxyDataElement<GetDreamSymbolResponse> {\n * static styles = [baseStyles, css`.card { … }`];\n * protected renderData(d: GetDreamSymbolResponse) {\n * return html`<article class=\"card\">…</article>`;\n * }\n * }\n * ```\n */\nexport abstract class RoxyDataElement<\n\tT = unknown,\n> extends RoxyLocalizedElement {\n\tstatic styles: CSSResultGroup = [baseStyles];\n\n\t/** Typed RoxyAPI response. Assigned in JavaScript, hydrated from the roxy-data island, or set by a self-fetch. */\n\t@property({ attribute: false })\n\tdata: T | null = null;\n\n\t/** Endpoint path for self-fetch, e.g. \"astrology/natal-chart\" or \"dreams/symbols/{id}\". Empty disables self-fetch (controlled mode only). */\n\t@property({ type: String, attribute: 'data-endpoint' })\n\tendpoint = '';\n\n\t/** HTTP method for self-fetch. */\n\t@property({ type: String })\n\tmethod: 'GET' | 'POST' = 'POST';\n\n\t/** Browser-safe publishable key (pk_) for self-fetch. A secret key is refused client-side. */\n\t@property({ type: String, attribute: 'publishable-key' })\n\tpublishableKey?: string;\n\n\t/** Override the API origin for self-hosted or proxied deployments. Absolute, or relative to the page for a same-origin route. */\n\t@property({ type: String, attribute: 'base-url' })\n\tbaseUrl?: string;\n\n\t/** Override the OpenAPI spec URL the self-fetch form introspects. */\n\t@property({ type: String, attribute: 'spec-url' })\n\tspecUrl?: string;\n\n\t/** Consumer backend route that proxies the request (holds the secret key). When set, self-fetch POSTs the request here instead of calling RoxyAPI directly, so no key reaches the browser. The server-rendered (WordPress) path. */\n\t@property({ type: String, attribute: 'submit-url' })\n\tsubmitUrl?: string;\n\n\t/**\n\t * Data the host page chooses, as a JSON object, sent to the {@link RoxyDataElement.submitUrl} route as `context` beside the request. The place a page attaches its own verification data to a proxied submission.\n\t *\n\t * @remarks\n\t * Shapeless by design and never read here: the component parses the attribute, hands the object to the request, and leaves every key of it to the page and the route that answers it. Nothing is sent when it is unset, when the JSON does not parse, and when it parses to anything but an object, so a route written before this existed goes on receiving exactly the request it always did.\n\t *\n\t * It rides the proxy path only. A direct call with a `publishable-key` sends what the endpoint declares, so setting this without a `submit-url` does nothing.\n\t *\n\t * @example\n\t * ```html\n\t * <roxy-natal-chart\n\t * data-endpoint=\"astrology/natal-chart\"\n\t * submit-url=\"/api/roxy/proxy\"\n\t * submit-context='{\"token\":\"...\"}'\n\t * ></roxy-natal-chart>\n\t * ```\n\t */\n\t@property({ attribute: 'submit-context', converter: submitContextConverter })\n\tsubmitContext?: Record<string, unknown>;\n\n\t/**\n\t * Where the self-fetch form's city search sends its request, absolute or relative to the page.\n\t *\n\t * @remarks\n\t * The companion of {@link RoxyDataElement.submitUrl}, and it is separate because the two requests have different shapes: the proxy route takes one POSTed `{ path, method, body, query }`, while the city search is a GET the search issues on its own while a visitor types. A birth-data form makes both, so a page that routes its API traffic through its own server names that route here as well. It is forwarded to the internal form, which forwards it to the search; unset, the search keeps its own default.\n\t */\n\t@property({ type: String, attribute: 'location-url' })\n\tlocationUrl?: string;\n\n\t/** Persist the last self-fetch form values in sessionStorage (keyed by endpoint) and prefill the form on reload. */\n\t@property({ type: Boolean })\n\tremember = false;\n\n\t/**\n\t * Render the chart and the data, and omit the written interpretation. Off by default, so a component that does not set it is byte-identical to before.\n\t *\n\t * @remarks\n\t * The suppressed content is the prose an endpoint returns ABOUT the result: the interpretation accordion, the interpretive paragraphs, and the keyword chips that belong to them. Everything a practitioner reads the numbers off stays: wheels, tables, grids, legends, pills, counts and dates. The reading is dropped from the DOM rather than hidden with CSS, so a page that publishes the chart alone never ships the prose it is not showing.\n\t *\n\t * Set it when the page supplies its own words, which is the common case for a practitioner site that wants the graphic under its own writing.\n\t */\n\t@property({ type: Boolean, attribute: 'hide-readings', reflect: true })\n\thideReadings = false;\n\n\t/**\n\t * Remove named structural blocks from this component, as a comma-separated list of `part` names.\n\t *\n\t * @remarks\n\t * The sibling of {@link RoxyDataElement.hideReadings} and deliberately a different tool. `hide-readings` drops the PROSE an endpoint returns about a result; this drops a whole block whatever it contains, which is what a page wants when the block is measurement rather than writing. Hiding the chart-pattern list on a teaching page is the case it exists for: a T-square is data, so `hide-readings` leaves it standing on purpose.\n\t *\n\t * Any name in `components-catalog.json` works, on any component that publishes it, because the rule is generated from the name rather than from a list of components that opted in. A name no block carries costs nothing and hides nothing.\n\t *\n\t * **This hides with CSS, it does not remove from the DOM, and the difference is the reason both exist.** A part name is a rendering concern the base can act on generically; whether a block is prose is a question only the component can answer. So a page that must not SHIP the words uses `hide-readings`, and a page that just should not SHOW a block uses this.\n\t *\n\t * @example\n\t * ```html\n\t * <roxy-natal-chart hide-sections=\"patterns\"></roxy-natal-chart>\n\t * <roxy-natal-chart hide-sections=\"patterns, aspects\"></roxy-natal-chart>\n\t * ```\n\t */\n\t@property({ type: String, attribute: 'hide-sections', reflect: true })\n\thideSections = '';\n\n\t/** Override the self-fetch form's submit-button label. Empty derives one from the endpoint. */\n\t@property({ type: String, attribute: 'submit-label' })\n\tsubmitLabel?: string;\n\n\t/** Render a small \"Spiritual data by RoxyAPI\" credit under a self-fetch or auto-mount result. Off by default; any value except \"off\"/\"false\" enables it. The one-tag widgets script turns it on unless data-attribution=\"off\". Never shown in controlled mode. */\n\t@property({ type: String })\n\tattribution?: string;\n\n\t/** True while an uncontrolled self-fetch is in flight. Public so {@link FetchController} can drive it. */\n\t@state()\n\tloading = false;\n\n\t/** Message from a failed self-fetch, or null. Public so {@link FetchController} can drive it. */\n\t@state()\n\terror: string | null = null;\n\n\t/**\n\t * True once a self-fetch (not a consumer-assigned or island-hydrated `data`) produced the current result. It gates the interactive result affordances, so controlled mode never shows an Edit control or a sticky picker.\n\t */\n\t@state()\n\tprivate selfFetched = false;\n\n\t/** True when the visitor asked to edit a self-fetch result, so the form is restored over the result. */\n\t@state()\n\tprivate editing = false;\n\n\t/** True when the last self-fetch form was a single-enum picker, so it stays visible above the result and a change refetches. */\n\t@state()\n\tprivate sticky = false;\n\n\t/** Last submitted form values (nested per group), kept in memory to restore the form on Edit and to prefill the sticky picker. */\n\tprivate lastValues?: Record<string, unknown>;\n\n\tprivate fetcher: FetchController<T>;\n\n\tconstructor() {\n\t\tsuper();\n\t\t// Controlled mode: hydrate `data` from a direct-child roxy-data island when\n\t\t// no JS property was assigned. Keyless; the server already fetched.\n\t\tnew MarkupDataController<T>(this);\n\t\tthis.fetcher = new FetchController<T>(this);\n\t}\n\n\tprotected willUpdate(changed: PropertyValues): void {\n\t\t// A result asked for in compact form arrives with its same-shaped arrays\n\t\t// columnar, so it is decoded once here and every component goes on\n\t\t// rendering the plain shape. `expandCompact` hands back the same object\n\t\t// when nothing is encoded, so an ordinary response is neither copied nor\n\t\t// re-rendered, and Lit records a property set here inside the update in\n\t\t// progress rather than scheduling another one.\n\t\tif (changed.has('data') && this.data != null) {\n\t\t\tconst expanded = expandCompact(this.data);\n\t\t\tif (expanded !== this.data) this.data = expanded;\n\t\t}\n\t\tif (changed.has('publishableKey')) {\n\t\t\tthis.fetcher.publishableKey = this.publishableKey;\n\t\t}\n\t\tif (changed.has('baseUrl') && this.baseUrl) {\n\t\t\tthis.fetcher.baseUrl = this.baseUrl;\n\t\t}\n\t\tif (changed.has('submitUrl')) {\n\t\t\tthis.fetcher.submitUrl = this.submitUrl;\n\t\t}\n\t\tif (changed.has('submitContext')) {\n\t\t\tthis.fetcher.submitContext = this.submitContext;\n\t\t}\n\t}\n\n\trender(): unknown {\n\t\treturn html`${this.hiddenSectionsStyle()}${this.renderState()}`;\n\t}\n\n\t/**\n\t * The one rule set that acts on {@link RoxyDataElement.hideSections}, generated from the names rather than from a list of components.\n\t *\n\t * @remarks\n\t * `[part~=\"name\"]` is the selector because `part` is a space-separated list: the natal chart's aspect grid carries `section aspects table aspect-grid`, so a `~=` match reaches it by any one of its names while `=` would reach it by none. It is emitted INSIDE the shadow root, which is the only place a rule can see a `part` attribute on the element that declares it.\n\t *\n\t * Names are filtered to the same `[a-z][a-z0-9-]*` shape the catalog and the WordPress setting both use, so nothing a page passes can close the rule or inject a second one. An unknown name compiles to a selector that matches nothing, which is why there is no validation error and no list of legal names to keep in sync.\n\t *\n\t * A `<style>` element in the template rather than a static stylesheet, because static styles are evaluated once and shared across every instance, so two charts on one page could not hide different blocks. Lit supports per-instance style elements; the documented cost is a re-parse when the expression changes, which is irrelevant here because the value is set once from a page attribute and effectively never changes after that.\n\t *\n\t * **`!important` is load-bearing and is not a shortcut around specificity.** Lit puts static `styles` in `adoptedStyleSheets`, and the scoping spec applies those AFTER any `<style>` element inside the same shadow root, so an in-tree rule loses to the component's own stylesheet at equal specificity no matter how it is written. Measured: `patterns` is a bare `section` with no declared display and hid correctly without it, while `legend` carries `display:flex` from the static sheet and stayed visible. The WordPress site-wide rule needs no `!important` for the opposite reason, that an outer-tree `::part()` rule already outranks anything inside.\n\t */\n\tprivate hiddenSectionsStyle(): unknown {\n\t\tconst names = this.hideSections\n\t\t\t.split(',')\n\t\t\t.map((n) => n.trim().toLowerCase())\n\t\t\t.filter((n) => /^[a-z][a-z0-9-]*$/.test(n));\n\t\tif (names.length === 0) return nothing;\n\t\tconst rules = names\n\t\t\t.map((n) => `[part~=\"${n}\"]{display:none!important}`)\n\t\t\t.join('');\n\t\treturn html`<style>${rules}</style>`;\n\t}\n\n\t/** The state machine every render goes through, split out so {@link render} can pair it with the per-instance rules above. */\n\tprivate renderState(): unknown {\n\t\tif (this.loading) return this.renderLoading();\n\t\tif (this.error != null) return this.renderError(this.error);\n\t\tif (this.data != null) {\n\t\t\t// Controlled mode (consumer-assigned or island-hydrated data) renders the\n\t\t\t// result alone, byte-identical to before: no picker, no Edit. The one\n\t\t\t// exception is the widgets auto-mount attrs-complete path, which assigns\n\t\t\t// data directly AND sets `attribution`; a real controlled consumer never\n\t\t\t// sets the attribute, so this stays byte-identical for them.\n\t\t\tif (!this.selfFetched) {\n\t\t\t\treturn this.showAttribution()\n\t\t\t\t\t? html`${this.renderData(this.data)}${this.renderAttribution()}`\n\t\t\t\t\t: this.renderData(this.data);\n\t\t\t}\n\t\t\tif (this.editing) return this.renderForm();\n\t\t\treturn this.renderResult(this.data);\n\t\t}\n\t\treturn this.renderNoData();\n\t}\n\n\t/** Render the populated response. The single method every component implements. */\n\tprotected abstract renderData(data: T): unknown;\n\n\t/**\n\t * The interpretation accordion, gated by {@link RoxyDataElement.hideReadings}. Every component that shows a written reading routes through here instead of calling {@link renderInterpAccordion} directly.\n\t *\n\t * @remarks\n\t * The gate lives on the base rather than in each component because the property does, and a plain render function cannot read component state. One call site per accordion, one place that decides whether prose renders, and the section it emits carries the same `readings` part in every component.\n\t *\n\t * Prose that is NOT in an accordion (a summary paragraph, a per-item interpretation) is still the component's own to gate, since only the component knows which of its blocks are readings.\n\t *\n\t * @param heading - English source copy, translated here. Typed as {@link ChromeString} so the compiler, not a reviewer, rejects a heading no catalogue carries.\n\t */\n\tprotected renderInterpretation(\n\t\tsections: InterpSection[],\n\t\tname: string,\n\t\theading?: ChromeString,\n\t): unknown {\n\t\tif (this.hideReadings) return nothing;\n\t\t// Localized HERE rather than in the accordion: that is a plain render\n\t\t// function with no host, so it cannot read a language, and this is the one\n\t\t// call site every component routes through.\n\t\treturn renderInterpAccordion(sections, name, this.t(heading ?? 'Reading'));\n\t}\n\n\t/**\n\t * A self-fetch result plus its re-query affordance. A single-enum form keeps its picker above the result so a new selection refetches (a sign switch is a new reading); any other form gets a compact Edit control that restores the form with the previous values.\n\t */\n\tprotected renderResult(data: T): unknown {\n\t\tconst body = this.sticky\n\t\t\t? html`${this.renderForm()}${this.renderData(data)}`\n\t\t\t: html`<div class=\"roxy-edit-bar\" part=\"edit-bar\"><button type=\"button\" class=\"roxy-edit\" @click=\"${this.onEdit}\">${this.t('Edit query')}</button></div>${this.renderData(data)}`;\n\t\treturn this.showAttribution()\n\t\t\t? html`${body}${this.renderAttribution()}`\n\t\t\t: body;\n\t}\n\n\tprivate onEdit = () => {\n\t\tthis.editing = true;\n\t};\n\n\t/** True when the attribution credit renders: the attribute is present and not explicitly disabled. */\n\tprivate showAttribution(): boolean {\n\t\treturn (\n\t\t\tthis.attribution != null &&\n\t\t\tthis.attribution !== 'off' &&\n\t\t\tthis.attribution !== 'false'\n\t\t);\n\t}\n\n\t/** Small muted credit under a self-fetch or auto-mount result. Reached only from the result path, so controlled mode never renders it. */\n\tprotected renderAttribution(): unknown {\n\t\treturn html`<div class=\"roxy-attribution\" part=\"attribution\"><a href=\"https://roxyapi.com/?utm_source=widget&utm_medium=embed\" target=\"_blank\" rel=\"noopener\">${this.t('Spiritual data by RoxyAPI')}</a></div>`;\n\t}\n\n\t/** The data-absent branch: the self-fetch form when an endpoint is set, otherwise the empty state. */\n\tprotected renderNoData(): unknown {\n\t\treturn this.endpoint ? this.renderForm() : this.renderEmpty();\n\t}\n\n\t/** Internal self-fetch form. Reuses the introspecting `<roxy-endpoint-form>`; the consumer never places it. */\n\tprotected renderForm(): unknown {\n\t\treturn html`<roxy-endpoint-form part=\"form\" data-endpoint=\"${this.endpoint}\" method=\"${this.method}\" spec-url=\"${ifDefined(this.specUrl)}\" publishable-key=\"${ifDefined(this.publishableKey)}\" location-url=\"${ifDefined(this.locationUrl)}\" submit-label=\"${ifDefined(this.submitLabel)}\" lang=\"${ifDefined(this.effectiveLang())}\" .initialValues=\"${this.formInitialValues()}\" @roxy-submit=\"${this.onFormSubmit}\"></roxy-endpoint-form>`;\n\t}\n\n\t/** Prefill source for the form: the last submission (Edit / sticky refetch) wins over remembered storage. */\n\tprivate formInitialValues(): Record<string, unknown> | undefined {\n\t\treturn (\n\t\t\tthis.lastValues ?? (this.remember ? this.readRemembered() : undefined)\n\t\t);\n\t}\n\n\tprivate onFormSubmit = (e: Event) => {\n\t\tconst detail = (e as CustomEvent).detail as {\n\t\t\tvalues: Record<string, unknown>;\n\t\t\tqueryKeys?: string[];\n\t\t\tsticky?: boolean;\n\t\t};\n\t\tthis.lastValues = detail.values;\n\t\tthis.sticky = !!detail.sticky;\n\t\tthis.selfFetched = true;\n\t\tthis.editing = false;\n\t\tif (this.remember) this.writeRemembered(detail.values);\n\t\tvoid this.fetcher.run(\n\t\t\tbuildRequest(\n\t\t\t\tthis.endpoint,\n\t\t\t\tthis.method,\n\t\t\t\tdetail.values,\n\t\t\t\tdetail.queryKeys ?? [],\n\t\t\t),\n\t\t);\n\t};\n\n\t/** sessionStorage key for this component's remembered form values, scoped by endpoint. */\n\tprivate rememberKey(): string {\n\t\treturn `roxy-ui:form:${this.endpoint}`;\n\t}\n\n\tprivate readRemembered(): Record<string, unknown> | undefined {\n\t\ttry {\n\t\t\tconst raw = sessionStorage.getItem(this.rememberKey());\n\t\t\treturn raw ? (JSON.parse(raw) as Record<string, unknown>) : undefined;\n\t\t} catch {\n\t\t\treturn undefined;\n\t\t}\n\t}\n\n\tprivate writeRemembered(values: Record<string, unknown>): void {\n\t\ttry {\n\t\t\tsessionStorage.setItem(this.rememberKey(), JSON.stringify(values));\n\t\t} catch {\n\t\t\t// Private mode / disabled storage: remembering is best-effort, never fatal.\n\t\t}\n\t}\n\n\t/** Terminal empty state: one translated message for every component, addressable as `::part(empty)`. Override only where an empty state must DO something a message cannot. */\n\tprotected renderEmpty(): unknown {\n\t\treturn html`<div class=\"roxy-empty\" role=\"status\" part=\"empty\">${this.t('No data')}</div>`;\n\t}\n\n\t/** Loading placeholder shown during a self-fetch. */\n\tprotected renderLoading(): unknown {\n\t\treturn html`<div class=\"roxy-skeleton\" style=\"height:8rem\" role=\"status\" aria-label=\"${this.t('Loading')}\" part=\"loading\"></div>`;\n\t}\n\n\t/**\n\t * Error state shown when a self-fetch fails. Keeps the form in view so the request can be retried.\n\t *\n\t * The message goes through `t()` because ONE of the messages that reaches here is ours: `KEY_REFUSED_MESSAGE` (`utils/key-guard.ts`), which {@link FetchController} assigns when a site owner pastes a secret key into a browser page, and which `<roxy-location-search>` renders in its own shadow root from the same constant. Translating it in one place and not the other would put two languages on one page. Everything else that lands here is a wire fact (an HTTP status, a browser network error), misses the catalogue and renders unchanged.\n\t */\n\tprotected renderError(message: string): unknown {\n\t\tconst banner = html`<div class=\"roxy-error\" role=\"alert\" part=\"error\">${this.t(message)}</div>`;\n\t\treturn this.endpoint ? html`${banner}${this.renderForm()}` : banner;\n\t}\n}\n", "import { LitElement } from 'lit';\nimport { resolveLang } from './lang.js';\nimport { LocaleController } from './locale-controller.js';\nimport { translate } from './registry.js';\n\n/**\n * The base every element that writes WORDS extends: it resolves the page language and translates its own chrome.\n *\n * @remarks\n * This is deliberately smaller than {@link RoxyDataElement}, and the split is what makes the widgets translatable at all. `<roxy-endpoint-form>` and `<roxy-location-search>` are the two declared widgets: they fetch, they hold state, and they are NOT data components, so they cannot inherit the data base without dragging its controlled-mode hydration, its self-fetch controller and its own form rendering (which renders the form, so the form inheriting it would compose itself). They extended `LitElement` directly instead, which meant they had no `t()` and no {@link LocaleController}, so a Spanish page rendered a Spanish result card over an English form and neither widget re-rendered when a deferred locale payload landed.\n *\n * So the mechanism lives here ONCE and all three inherit it. There is no second translator, no second registry and no second way to resolve a language: adding one is how a catalogue entry and a call site drift apart.\n *\n * Two costs are why this is its own module rather than a second export of `utils/base-element.ts`. Every `dist/cdn/components/*.js` is a self-contained IIFE, so importing the data base into the city search would compile `FetchController`, `MarkupDataController` and the interpretation accordion into a bundle that uses none of them. And `utils/base-element.ts` imports THIS file, so putting the class there would close a cycle the moment a widget imported it.\n */\nexport abstract class RoxyLocalizedElement extends LitElement {\n\tconstructor() {\n\t\tsuper();\n\t\t// Re-render if a chrome-string catalogue lands after this element upgraded.\n\t\t// A host page loads the payload as its own script tag, so it can arrive\n\t\t// after first paint and there is nothing the site owner could do about it.\n\t\tnew LocaleController(this);\n\t}\n\n\t/**\n\t * The chrome string for this element's language, keyed by its own English source text.\n\t *\n\t * @remarks\n\t * Pass the English copy, never a key. With no catalogue registered the source string is returned unchanged, so an English page pays nothing and a language we do not ship degrades to English rather than to a visible key.\n\t *\n\t * Chrome only. A value the API returned (a planet, a sign, an aspect, a house system) is NOT translated here: it is rendered as the response carries it, so the words on the chart and the words in the response can never disagree. The same holds for a label derived from a spec field NAME through `humanize()`: a catalogue keyed on English source text cannot reach a string computed per response. A derived name is catalogued only where the set it comes from is CLOSED and small enough to enumerate against the spec, which is true of the nine form group names and of nothing else so far.\n\t *\n\t * @example\n\t * ```ts\n\t * this.t('Aspect grid'); // 'Cuadricula de aspectos' under lang=\"es\"\n\t * this.t('{{count}} planets', { count: 12 }); // '12 planetas'\n\t * ```\n\t */\n\tprotected t(source: string, vars?: Record<string, string | number>): string {\n\t\treturn translate(this.effectiveLang(), source, vars);\n\t}\n\n\t/** {@link RoxyLocalizedElement.t} as a value, bound once, for a shared render helper that has no host of its own and therefore cannot resolve a page language (`utils/hd-reading.ts`). Named `translator` and not `translate` because `HTMLElement.translate` is a real DOM property and shadowing it with a protected member makes every `@customElement` decorator in the library fail to typecheck. */\n\tprotected readonly translator = (\n\t\tsource: string,\n\t\tvars?: Record<string, string | number>,\n\t): string => this.t(source, vars);\n\n\t/**\n\t * Site-owner language for this element: the `lang` attribute, the nearest ancestor carrying one, or the document. Protected so a component that composes another can forward it (a child inside this shadow root cannot reach the host page on its own).\n\t *\n\t * Full tag, region included. The truncation to what `?lang=` accepts happens where the request is built, in `<roxy-endpoint-form>`.\n\t */\n\tprotected effectiveLang(): string | undefined {\n\t\treturn resolveLang(this);\n\t}\n}\n", "/**\n * Where a component's language comes from, and what is safe to send to the API.\n *\n * @remarks\n * Two different answers, and conflating them is the whole reason this file is separate from the catalogue:\n *\n * - {@link resolveLang} answers \"what language is this PAGE in\", and keeps the full tag, because `es-AR` is a legitimate thing for a catalogue to want to differ on.\n * - {@link apiLang} answers \"what may go on the query string\", which is a narrower question with a hard edge: `?lang=es-AR` is a 400, `?lang=es` is a 200.\n *\n * The full tag is not a nicety the catalogue happens to tolerate: `utils/format.ts` hands it to `Intl`, which reads the region and writes `15 de ene de 1990` for `es-AR` where it writes `15 ene 1990` for `es`. Passing the API answer to a formatter demotes every regional visitor to the base language and nothing fails, so the two values are never interchangeable.\n */\n\nimport { API_LANGUAGES } from '../generated/api-languages.js';\n\n/**\n * The site-owner language for an element, resolved through the four-link chain the revamp design specifies.\n *\n * @remarks\n * 1. the element's own `lang` attribute (the explicit per-embed override),\n * 2. the nearest ancestor carrying `lang`, so one wrapper localizes a whole section,\n * 3. `document.documentElement.lang`, which is what makes this work on a real CMS with no markup change at all: WordPress emits `<html lang=\"es-AR\">` on every page of a Spanish site,\n * 4. nothing, which the callers read as English.\n *\n * All four links matter: with only the first, a component on a fully Spanish page renders English chrome and the only remedy is hand-editing every embed.\n *\n * `navigator.language` is deliberately NOT in the chain. It is the VISITOR's preference, not the site's: it fragments the API cache across every locale a visitor might carry and silently serves two people different content from the same URL.\n *\n * Link 2 uses `closest`, which stops at a shadow boundary. A component composed INSIDE another component's shadow root therefore cannot see the host page, which is why every composing component forwards `lang` to its children explicitly.\n */\nexport function resolveLang(el: HTMLElement): string | undefined {\n\t// Native accessor, never a Lit @property: declaring one would shadow\n\t// HTMLElement.lang and break the platform attribute for every consumer.\n\tif (el.lang) return el.lang;\n\tif (typeof document === 'undefined') return undefined;\n\tconst inherited = el.closest?.('[lang]')?.getAttribute('lang');\n\tif (inherited) return inherited;\n\treturn document.documentElement.lang || undefined;\n}\n\n/**\n * Which script a Chinese page is written in, read off the region it names.\n *\n * @remarks\n * Chinese is the one language the API keys by SCRIPT rather than by language alone, because `zh`\n * on its own does not say which of the two a reader can actually read. Real pages almost never\n * write the script: a Taiwanese site writes `zh-TW` and a mainland site writes `zh-CN`, which is\n * what the region-to-script correspondence every internationalisation library ships is for.\n * Without this step both of those degrade to English, which takes the whole Chinese audience off\n * the domains the API answers in Chinese at all.\n *\n * A bare `zh` with neither region nor script resolves to nothing on purpose: guessing a script for\n * a reader who did not name one picks characters half of them cannot read.\n */\nconst ZH_SCRIPT_BY_REGION: Readonly<Record<string, string>> = {\n\ttw: 'hant',\n\thk: 'hant',\n\tmo: 'hant',\n\tcn: 'hans',\n\tsg: 'hans',\n\tmy: 'hans',\n};\n\n/** The API's own spelling of a tag, matched case-insensitively, or undefined when it serves no such language. */\nfunction asApiLang(tag: string): string | undefined {\n\tconst wanted = tag.toLowerCase();\n\treturn API_LANGUAGES.find((l) => l.toLowerCase() === wanted);\n}\n\n/**\n * The value safe to put on `?lang=`, or `undefined` to leave the request on the API default.\n *\n * @remarks\n * Three steps, and the order is load-bearing the moment {@link resolveLang} starts reading `<html lang>`:\n *\n * - **A tag the API serves goes as it is**, matched without regard to case, so `zh-Hant` and `ZH-HANT` both send the spelling the API declares. This comes first because the next step would throw away the very subtag those tags are identified by.\n * - **Chinese resolves its script**, from an explicit script subtag or from the region ({@link ZH_SCRIPT_BY_REGION}), because that is where the language actually lives.\n * - **Everything else drops its region.** A regional tag is a 400, so a Spanish WordPress site would go from English-but-working to broken the day the language chain was completed. `es-AR`, `es-419` and `ES` all send `es`.\n *\n * **An unsupported language is omitted, not sent.** The chain surfaces whatever the host page carries, including languages the API does not translate, and an unlisted tag is the same 400. Omitting it degrades to English, which is the behaviour those pages already had.\n */\nexport function apiLang(el: HTMLElement): string | undefined {\n\tconst tag = resolveLang(el);\n\tif (!tag) return undefined;\n\tconst exact = asApiLang(tag);\n\tif (exact) return exact;\n\tconst parts = tag.toLowerCase().split('-');\n\tconst base = parts[0] as string;\n\tif (base === 'zh') {\n\t\tconst script =\n\t\t\tparts.find((p) => p === 'hans' || p === 'hant') ??\n\t\t\tZH_SCRIPT_BY_REGION[parts[1] ?? ''];\n\t\treturn script ? asApiLang(`zh-${script}`) : undefined;\n\t}\n\treturn asApiLang(base);\n}\n", "/**\n * The chrome-string catalogue: one resolver reading one registry, so a translation can arrive from anywhere without a component changing.\n *\n * @remarks\n * **The key IS the canonical English string**, folded through {@link lookupKey}. There is no invented key vocabulary to keep in sync with the copy, which is the same rule the glyph tables in `tokens/index.ts` follow (they key off the exact value the API returns). Two consequences that are the whole point:\n *\n * - **English costs zero bytes.** A miss returns the source string, so the English build ships no catalogue at all, and a site that never loads a locale payload is byte-identical to one built before this file existed.\n * - **A missing translation degrades to English, never to a key.** The failure mode of a keyed catalogue is a raw `natal.tabs.wheel` on the page; here the worst case is the English word.\n *\n * **The registry lives on `globalThis`, not in module scope, because it has to.** Every `dist/cdn/components/*.js` is a self-contained IIFE with its own copy of this module, so a `Map` here would be invisible to the second component on the page. One global object, written by the locale payload and read by every bundle, is what makes `dist/cdn/locales/es.js` a single download that translates all of them.\n *\n * Load order is not guaranteed on a real host (WordPress enqueues scripts in an order the plugin does not fully control, and a payload may be deferred), so {@link onLocaleChange} lets an element that has already rendered in English re-render when its catalogue lands.\n */\n\nimport { lookupKey } from '../utils/string.js';\n\n/** Shared mutable state, addressed by a name rather than a module binding so every bundle on the page reaches the same object. */\ninterface LocaleRegistry {\n\t/** Language tag (lower case) to catalogue, keyed by {@link lookupKey} of the English source string. */\n\tcatalogs: Record<string, Record<string, string>>;\n\t/**\n\t * Language tag (lower case) to the API's field-label map: `fields` keyed by wire name,\n\t * `enums` keyed `{fieldName}.{value}`.\n\t *\n\t * A SEPARATE key space from `catalogs` on purpose. A chrome string is keyed by the English\n\t * text a component writes, which is a constant in our source; a field label is keyed by a\n\t * name that only the OpenAPI spec knows, computed per operation, so no catalogue keyed on\n\t * English source text can ever reach it. Same registry because the delivery problem is\n\t * identical (a payload that may land after first paint), so it reuses one global object and\n\t * one listener set rather than growing a second of each.\n\t */\n\tfieldLabels: Record<string, FieldLabels>;\n\t/** Language tags whose fetch is in flight or done, so N forms on a page cost ONE request. */\n\trequested: Set<string>;\n\t/** Elements waiting to re-render when a catalogue arrives. */\n\tlisteners: Set<() => void>;\n}\n\n/** The `/languages/field-labels` payload, minus the echoed `lang`. */\nexport interface FieldLabels {\n\tfields: Record<string, string>;\n\tenums: Record<string, string>;\n}\n\nconst GLOBAL_KEY = '__ROXY_UI_I18N__';\n\nfunction registry(): LocaleRegistry {\n\tconst holder = globalThis as unknown as Record<string, LocaleRegistry>;\n\tconst existing = holder[GLOBAL_KEY];\n\tif (existing) return existing;\n\tconst created: LocaleRegistry = {\n\t\tcatalogs: {},\n\t\tfieldLabels: {},\n\t\trequested: new Set(),\n\t\tlisteners: new Set(),\n\t};\n\tholder[GLOBAL_KEY] = created;\n\treturn created;\n}\n\n/**\n * Publish a catalogue for a language tag and wake every mounted element.\n *\n * @remarks\n * The catalogue is authored keyed by the English source string, exactly as it appears at the call site, and normalized here. That keeps the source file readable and diffable against the component that renders it, while the runtime lookup stays a single property read.\n *\n * This is the ONLY way into the registry, so a catalogue can later come from a static file, a server response, or a host page inlining a script tag, without a component knowing the difference.\n */\nexport function registerLocale(\n\tlang: string,\n\tcatalog: Record<string, string>,\n): void {\n\tconst reg = registry();\n\tconst normalized: Record<string, string> = {};\n\tfor (const [source, translated] of Object.entries(catalog)) {\n\t\tnormalized[lookupKey(source)] = translated;\n\t}\n\treg.catalogs[lang.toLowerCase()] = normalized;\n\tfor (const listener of reg.listeners) listener();\n}\n\n/**\n * Replace `{{name}}` placeholders. Copied from the API-side translator so both sides of the product interpolate identically; an unknown placeholder is left verbatim rather than blanked, so a typo in a catalogue is visible instead of silently eating the value.\n */\nexport function interpolate(\n\ttemplate: string,\n\tvars?: Record<string, string | number>,\n): string {\n\tif (!vars) return template;\n\treturn template.replace(/\\{\\{(\\w+)\\}\\}/g, (match, key: string) =>\n\t\tkey in vars ? String(vars[key] ?? '') : match,\n\t);\n}\n\n/**\n * The chrome string for `lang`, falling back to the English `source` it is keyed by.\n *\n * @remarks\n * A regional tag resolves against its base language, so `es-AR` and `es-419` both read the `es` catalogue and a site does not have to know which tags we happen to ship. An exact regional catalogue still wins if one is ever registered.\n */\nexport function translate(\n\tlang: string | undefined,\n\tsource: string,\n\tvars?: Record<string, string | number>,\n): string {\n\tif (!lang) return interpolate(source, vars);\n\tconst { catalogs } = registry();\n\tconst tag = lang.toLowerCase();\n\tconst catalog = catalogs[tag] ?? catalogs[tag.split('-')[0] as string];\n\treturn interpolate(catalog?.[lookupKey(source)] ?? source, vars);\n}\n\n/**\n * Publish a field-label map for a language tag and wake every mounted element.\n *\n * @remarks\n * Exported so a host that already has the payload (a server-rendered page, a test, a WordPress\n * plugin inlining it) can supply it without a network call, exactly as {@link registerLocale}\n * allows for chrome strings.\n */\nexport function registerFieldLabels(lang: string, labels: FieldLabels): void {\n\tconst reg = registry();\n\treg.fieldLabels[lang.toLowerCase()] = labels;\n\tfor (const listener of reg.listeners) listener();\n}\n\n/** The field-label map for `lang`, resolving a regional tag against its base language. */\nfunction labelsFor(lang: string | undefined): FieldLabels | undefined {\n\tif (!lang) return undefined;\n\tconst { fieldLabels } = registry();\n\tconst tag = lang.toLowerCase();\n\treturn fieldLabels[tag] ?? fieldLabels[tag.split('-')[0] as string];\n}\n\n/**\n * The label for a request field name, or `undefined` when nothing has been published.\n *\n * @remarks\n * Returning `undefined` rather than the name is deliberate: the caller owns the fallback, which is\n * `humanize()`, and that keeps this resolver honest about what it actually knows. A form renders\n * identically to before until a payload arrives.\n */\nexport function fieldLabel(\n\tlang: string | undefined,\n\tname: string,\n): string | undefined {\n\treturn labelsFor(lang)?.fields[name];\n}\n\n/** The label for one selectable option, keyed `{fieldName}.{value}` as the API publishes it. */\nexport function optionLabel(\n\tlang: string | undefined,\n\tfield: string,\n\tvalue: string,\n): string | undefined {\n\treturn labelsFor(lang)?.enums[`${field}.${value}`];\n}\n\n/** Subscribe to catalogue arrivals. Returns the unsubscribe, so an element can drop it on disconnect. */\nexport function onLocaleChange(listener: () => void): () => void {\n\tconst { listeners } = registry();\n\tlisteners.add(listener);\n\treturn () => {\n\t\tlisteners.delete(listener);\n\t};\n}\n", "import type { ReactiveController, ReactiveControllerHost } from 'lit';\nimport { onLocaleChange } from './registry.js';\n\n/**\n * Re-renders its host when a chrome-string catalogue arrives.\n *\n * @remarks\n * Without this the catalogue would have to be on the page BEFORE the elements upgrade, which is not something a component can require of a real host. WordPress orders enqueued scripts by dependency and a site owner can add `defer` to any of them; a CDN embed is two independent `<script src>` tags. Any of those can land the locale payload after the first paint, and the visible result would be a chart that renders in English on a Spanish page for no reason the site owner can see or fix.\n *\n * Mirrors `MarkupDataController`: constructed in {@link RoxyDataElement}'s constructor, subscribes on connect, drops the subscription on disconnect. Registration is idempotent and a re-register of the same language simply re-renders, so a payload loaded twice is harmless.\n */\nexport class LocaleController implements ReactiveController {\n\tprivate readonly host: ReactiveControllerHost;\n\tprivate unsubscribe?: () => void;\n\n\tconstructor(host: ReactiveControllerHost) {\n\t\tthis.host = host;\n\t\thost.addController(this);\n\t}\n\n\thostConnected(): void {\n\t\tthis.unsubscribe = onLocaleChange(() => this.host.requestUpdate());\n\t}\n\n\thostDisconnected(): void {\n\t\tthis.unsubscribe?.();\n\t\tthis.unsubscribe = undefined;\n\t}\n}\n", "import { css } from 'lit';\n\n/**\n * Shared host styles every component pulls in. Sets default font, color,\n * container query support, and the entry fade-in.\n */\nexport const baseStyles = css`:host{--roxy-label-col:minmax(0, 25%);font-family:var(--roxy-font-sans,system-ui, -apple-system, BlinkMacSystemFont, \"Segoe UI\", Roboto, sans-serif);color:var(--roxy-fg,#0a0a0a);font-size:var(--roxy-text-base,1rem);line-height:var(--roxy-leading-normal,1.5);animation:roxy-fade-in var(--roxy-motion-duration,.2s) var(--roxy-motion-easing,cubic-bezier(.4, 0, .2, 1)) both;background:0 0;display:block;container-type:inline-size}:host([bare]){--roxy-surface:transparent;--roxy-shadow-sm:none;--roxy-shadow-md:none}*,:before,:after{box-sizing:border-box}h1,h2,h3,h4{font-family:var(--roxy-font-display,var(--roxy-font-sans,system-ui, -apple-system, BlinkMacSystemFont, \"Segoe UI\", Roboto, sans-serif))}@keyframes roxy-fade-in{0%{opacity:0;transform:translateY(2px)}to{opacity:1;transform:translateY(0)}}@media (prefers-reduced-motion:reduce){:host{animation:none}}.roxy-skeleton{background:linear-gradient(90deg, var(--roxy-border,#e4e4e7) 0%, color-mix(in srgb, var(--roxy-border,#e4e4e7) 60%, transparent) 50%, var(--roxy-border,#e4e4e7) 100%);border-radius:var(--roxy-radius-md,8px);background-size:200% 100%;animation:1.4s ease-in-out infinite roxy-shimmer}@keyframes roxy-shimmer{0%{background-position:200% 0}to{background-position:-200% 0}}@media (prefers-reduced-motion:reduce){.roxy-skeleton{animation:none}}.roxy-sr-only{clip-path:inset(50%);white-space:nowrap;border:0;width:1px;height:1px;margin:0;padding:0;position:absolute;overflow:hidden}.roxy-empty{padding:var(--roxy-space-lg,1.5rem);color:var(--roxy-muted,#71717a);text-align:center;font-size:var(--roxy-text-sm,.875rem)}.roxy-error{gap:var(--roxy-space-sm,.5rem);padding:var(--roxy-space-lg,1.5rem);background:var(--roxy-surface,#fff);border:1px solid var(--roxy-danger,#dc2626);border-radius:var(--roxy-radius-md,8px);color:var(--roxy-danger-fg,#991b1b);font-size:var(--roxy-text-sm,.875rem);justify-items:start;display:grid}:host(:focus-within) .roxy-card{outline:2px solid var(--roxy-ring,#f59e0b66);outline-offset:2px}.roxy-attribution{margin-top:var(--roxy-space-sm,.5rem);font-size:var(--roxy-text-xs,.75rem);color:var(--roxy-muted,#71717a);text-align:right}.roxy-attribution a{color:inherit;text-decoration:none}.roxy-attribution a:hover{color:var(--roxy-accent-ink,#b45309);text-decoration:underline}.roxy-attribution a:focus-visible{outline:2px solid var(--roxy-ring,#f59e0b66);outline-offset:2px}.roxy-edit-bar{margin-bottom:var(--roxy-space-sm,.5rem);justify-content:flex-end;display:flex}.roxy-edit{padding:var(--roxy-space-xs,.25rem) var(--roxy-space-md,1rem);border:1px solid var(--roxy-border,#e4e4e7);border-radius:var(--roxy-radius-md,8px);color:var(--roxy-fg,#0a0a0a);font-family:inherit;font-size:var(--roxy-text-sm,.875rem);cursor:pointer;background:0 0}.roxy-edit:hover{border-color:var(--roxy-accent,#f59e0b);color:var(--roxy-accent-ink,#b45309)}.roxy-edit:focus-visible{outline:2px solid var(--roxy-ring,#f59e0b66);outline-offset:2px}:host{font-variant-emoji:text}`;\n", "const COLS = '__cols';\nconst ROWS = '__rows';\n\nfunction isPlainObject(value: unknown): value is Record<string, unknown> {\n\treturn typeof value === 'object' && value !== null && !Array.isArray(value);\n}\n\n/**\n * Walk a value, rebuilding only the branches that actually hold an encoded array.\n *\n * @remarks\n * The identity return is the contract, not an optimisation: a response with nothing encoded in it comes back as the same object, so every render path that existed before this decoder sees the exact bytes it always saw.\n */\nfunction decode(value: unknown): unknown {\n\tif (Array.isArray(value)) {\n\t\tlet rebuilt = false;\n\t\tconst out = value.map((item) => {\n\t\t\tconst next = decode(item);\n\t\t\tif (next !== item) rebuilt = true;\n\t\t\treturn next;\n\t\t});\n\t\treturn rebuilt ? out : value;\n\t}\n\tif (!isPlainObject(value)) return value;\n\n\tconst cols = value[COLS];\n\tconst rows = value[ROWS];\n\t// Exactly the two keys and nothing else: a real payload that happens to carry\n\t// a field of either name is left alone.\n\tif (\n\t\tArray.isArray(cols) &&\n\t\tArray.isArray(rows) &&\n\t\tObject.keys(value).length === 2\n\t) {\n\t\treturn rows.map((row) => {\n\t\t\tconst item: Record<string, unknown> = {};\n\t\t\t(cols as string[]).forEach((col, i) => {\n\t\t\t\titem[col] = decode((row as unknown[])[i]);\n\t\t\t});\n\t\t\treturn item;\n\t\t});\n\t}\n\n\tlet rebuilt = false;\n\tconst out: Record<string, unknown> = {};\n\tfor (const [key, item] of Object.entries(value)) {\n\t\tconst next = decode(item);\n\t\tif (next !== item) rebuilt = true;\n\t\tout[key] = next;\n\t}\n\treturn rebuilt ? out : value;\n}\n\n/**\n * Turn a compact API response back into the plain shape the components render.\n *\n * @remarks\n * Asking a Remote MCP tool for a compact result trades repeated field names for a header: an array of same-shaped objects arrives as `{ __cols: [names], __rows: [[values]] }`, which costs an agent far fewer tokens to read and carries exactly the same data. This is the decoder, applied at every depth, so a compact result renders in a component with nothing else to do.\n *\n * Every data component runs it on the way in, so a page that sets `data` from a tool result needs no call of its own. It is exported for the paths that hold the JSON before an element does.\n *\n * A value with nothing encoded in it is returned unchanged, by reference.\n *\n * @example\n * ```ts\n * expandCompact({ aspects: { __cols: ['a', 'b'], __rows: [['sun', 'moon'], ['sun', 'mars'], ['moon', 'mars']] } });\n * // { aspects: [{ a: 'sun', b: 'moon' }, { a: 'sun', b: 'mars' }, { a: 'moon', b: 'mars' }] }\n * ```\n */\nexport function expandCompact<T>(value: T): T {\n\treturn decode(value) as T;\n}\n", "/**\n * The one place the \"publishable key only\" rule lives. Every client-side fetch boundary ({@link ../components/location-search.ts}, {@link ./fetch-controller.ts}) calls through here so a secret or legacy unprefixed key is refused identically: no network call, the same visible message, the same `roxy-validation-error` event. Centralising it is what stops the two paths drifting, which is exactly how `<roxy-location-search>` used to warn-then-fetch a secret key while the controller fail-closed.\n */\n\n/** Canonical refusal message. Both fetch boundaries surface this exact wording. */\nexport const KEY_REFUSED_MESSAGE =\n\t'Client-side components accept a pk_ publishable key only. Use a publishable key with an origin allowlist, or render server-side.';\n\n/** True when the key is a browser-safe `pk_` publishable key. */\nexport function isPublishableKey(key: string | undefined | null): boolean {\n\treturn !!key && key.startsWith('pk_');\n}\n\n/**\n * The fail-closed condition: a key is PRESENT and is NOT a `pk_` key. An absent key is not refused, so a keyless public call (a form-slotted city search with no key set) still proceeds; only a real secret/legacy token in the browser is stopped.\n */\nexport function keyIsRefused(key: string | undefined | null): boolean {\n\treturn !!key && !key.startsWith('pk_');\n}\n\n/**\n * Announce a refused key: dispatch the shared `roxy-validation-error` (bubbling, composed) and, when `warn` is set, log it once for the developer. The caller sets its own visible error state and skips the fetch; this only handles the parts both boundaries share.\n */\nexport function dispatchKeyRefusal(\n\thost: EventTarget,\n\topts: { warn?: boolean } = {},\n): void {\n\tif (opts.warn) console.warn(KEY_REFUSED_MESSAGE);\n\thost.dispatchEvent(\n\t\tnew CustomEvent('roxy-validation-error', {\n\t\t\tdetail: { reason: 'possible-secret-key', message: KEY_REFUSED_MESSAGE },\n\t\t\tbubbles: true,\n\t\t\tcomposed: true,\n\t\t}),\n\t);\n}\n", "import type { ReactiveController, ReactiveControllerHost } from 'lit';\nimport {\n\tdispatchKeyRefusal,\n\tKEY_REFUSED_MESSAGE,\n\tkeyIsRefused,\n} from './key-guard.js';\n\n/**\n * Host slots the controller drives. {@link RoxyDataElement} satisfies this, so the form mixin can attach a controller without the component wiring state by hand.\n *\n * @remarks\n * Intersected with `HTMLElement` because the controller dispatches events on the host. Lit's `ReactiveControllerHost` is the update-lifecycle contract only (`addController`, `requestUpdate`, `updateComplete`) and carries no DOM surface, even though every real host is a `LitElement` and therefore an `HTMLElement`. Declaring the DOM half is what the controller actually needs; it used to reach it through a `this.host as unknown as EventTarget` double cast instead, which asserted a capability the type never promised.\n */\ntype FetchHost<T> = ReactiveControllerHost &\n\tHTMLElement & {\n\t\tdata: T | null;\n\t\tloading: boolean;\n\t\terror: string | null;\n\t};\n\n/** Default RoxyAPI v2 origin. A component overrides it per instance via its `base-url` attribute. */\n/** The public API root. Exported so anything else that must reach the API (the field-label\n * fetch in `endpoint-form`) uses the SAME origin as every data request instead of a second copy. */\nexport const DEFAULT_BASE_URL = 'https://roxyapi.com/api/v2';\n\n/**\n * Turn a failed `Response` into the message to show: the API's own `{ error }` string when the body carries one, else the status line.\n *\n * @remarks\n * Exported so every client-side fetch boundary renders the same words for the same failure, the way {@link keyIsRefused} centralizes the key refusal. A boundary that discards the response body cannot tell a rejected request from an empty result, and renders the two identically.\n */\nexport async function readApiError(res: Response): Promise<string> {\n\ttry {\n\t\tconst body = (await res.json()) as { error?: string };\n\t\tif (body?.error) return body.error;\n\t} catch {\n\t\t// Non-JSON error body: fall through to the status line.\n\t}\n\treturn `Request failed (${res.status})`;\n}\n\n/** A single request the controller issues on the component's behalf. */\nexport interface RoxyRequest {\n\t/** Path under the API base, e.g. \"/dreams/symbols/water\" or \"/astrology/natal-chart\". */\n\tpath: string;\n\tmethod?: 'GET' | 'POST';\n\t/** JSON body for POST endpoints. */\n\tbody?: unknown;\n\t/** Query string parameters; nullish values are dropped. */\n\tquery?: Record<string, string | number | undefined>;\n}\n\n/**\n * Client-side fetch for uncontrolled (self-fetching) components: drives `host.data` / `host.loading` / `host.error` and cancels a stale request when a newer one starts or the host disconnects.\n *\n * @remarks\n * Security boundary. The only credential this ever sends is a `pk_` publishable key, which carries a server-side origin allowlist. A secret (`sk_`) or legacy unprefixed key is refused before any network call and surfaced as an error, so a server secret cannot leak into a browser request. This centralizes the guard that originated in `<roxy-location-search>` so every self-fetching component enforces it identically.\n *\n * Controlled-mode components never construct this. When a server injects the response as a `<script class=\"roxy-data\">` island, there is no key and no fetch, which is the path server-rendered consumers (WordPress, JSX SSR, static HTML) rely on.\n */\nexport class FetchController<T = unknown> implements ReactiveController {\n\tprivate readonly host: FetchHost<T>;\n\tprivate abort?: AbortController;\n\n\t/** Browser-safe publishable key. Set by the host from its `publishable-key` attribute. */\n\tpublishableKey?: string;\n\t/** API origin, overridable for self-hosted or proxied deployments. */\n\tbaseUrl = DEFAULT_BASE_URL;\n\t/**\n\t * Consumer backend route that holds the secret key. When set, the request is POSTed here as `{ path, method, body, query }` instead of called against RoxyAPI directly, so no key (publishable or secret) is sent from the browser. This is the canonical path for server-rendered hosts (WordPress); the backend proxies the request with its own `sk_` key and returns the JSON response.\n\t */\n\tsubmitUrl?: string;\n\t/**\n\t * Object the host page attaches to the proxied request, carried beside it as `context`. Set by the host from its `submit-context` attribute, and shapeless on purpose: this passes it through and reads no key of it, so what it holds is for the page and its own route to agree on.\n\t *\n\t * @remarks\n\t * Only the {@link FetchController.submitUrl} path can carry it, because that is the only body this code writes. A direct call sends the request the endpoint declares and nothing beside it.\n\t */\n\tsubmitContext?: Record<string, unknown>;\n\n\tconstructor(host: FetchHost<T>) {\n\t\tthis.host = host;\n\t\thost.addController(this);\n\t}\n\n\thostDisconnected() {\n\t\tthis.abort?.abort();\n\t\tthis.abort = undefined;\n\t}\n\n\t/**\n\t * Issue the request and resolve once `host.data` (success) or `host.error`\n\t * (failure) is set. A no-op return when a non-publishable key is present:\n\t * the error is already surfaced and nothing is sent.\n\t */\n\tasync run(req: RoxyRequest): Promise<void> {\n\t\t// submit-url proxy: no key leaves the browser; the consumer's backend holds it.\n\t\tif (!this.submitUrl && this.secretKeyRefused()) return;\n\t\tthis.abort?.abort();\n\t\tconst controller = new AbortController();\n\t\tthis.abort = controller;\n\t\tthis.host.loading = true;\n\t\tthis.host.error = null;\n\t\ttry {\n\t\t\tconst res = this.submitUrl\n\t\t\t\t? await fetch(this.submitUrl, {\n\t\t\t\t\t\tmethod: 'POST',\n\t\t\t\t\t\theaders: {\n\t\t\t\t\t\t\tAccept: 'application/json',\n\t\t\t\t\t\t\t'Content-Type': 'application/json',\n\t\t\t\t\t\t},\n\t\t\t\t\t\tbody: this.proxyBody(req),\n\t\t\t\t\t\tsignal: controller.signal,\n\t\t\t\t\t})\n\t\t\t\t: await this.callApi(req, controller.signal);\n\t\t\tif (!res.ok) throw new Error(await readApiError(res));\n\t\t\tconst json = (await res.json()) as T;\n\t\t\tif (controller.signal.aborted) return;\n\t\t\tthis.host.data = json;\n\t\t} catch (err) {\n\t\t\tif ((err as { name?: string })?.name === 'AbortError') return;\n\t\t\tthis.host.error = err instanceof Error ? err.message : String(err);\n\t\t} finally {\n\t\t\tif (this.abort === controller) this.abort = undefined;\n\t\t\tif (!controller.signal.aborted) this.host.loading = false;\n\t\t}\n\t}\n\n\t/**\n\t * The body of a proxied POST: the request, plus {@link FetchController.submitContext} under `context` when the host set one.\n\t *\n\t * @remarks\n\t * The context is appended rather than declared on {@link RoxyRequest}, so with none set the payload is the request object itself and every route already written against it keeps receiving the same four keys in the same order. A `null` or an empty object would be a fifth key such a route never agreed to read.\n\t */\n\tprivate proxyBody(req: RoxyRequest): string {\n\t\treturn JSON.stringify(\n\t\t\tthis.submitContext ? { ...req, context: this.submitContext } : req,\n\t\t);\n\t}\n\n\t/** Direct call against RoxyAPI with the publishable key (the no-backend path). */\n\tprivate callApi(req: RoxyRequest, signal: AbortSignal): Promise<Response> {\n\t\t// Resolved against the page, so a same-origin base (\"/api/roxy\") is as valid as an\n\t\t// absolute one. Every route a host page can name resolves the same way, and a bare\n\t\t// `new URL()` would reject the relative shape with an opaque \"Invalid URL\".\n\t\tconst url = new URL(`${this.baseUrl}${req.path}`, document.baseURI);\n\t\tfor (const [k, v] of Object.entries(req.query ?? {})) {\n\t\t\tif (v != null) url.searchParams.set(k, String(v));\n\t\t}\n\t\tconst headers: Record<string, string> = { Accept: 'application/json' };\n\t\tif (this.publishableKey) headers['X-API-Key'] = this.publishableKey;\n\t\tif (req.body != null) headers['Content-Type'] = 'application/json';\n\t\treturn fetch(url, {\n\t\t\tmethod: req.method ?? 'GET',\n\t\t\theaders,\n\t\t\tbody: req.body != null ? JSON.stringify(req.body) : undefined,\n\t\t\tsignal,\n\t\t});\n\t}\n\n\t/** True when a key is set and it is not a browser-safe `pk_` publishable key. Surfaces the error and refuses to send, via the shared {@link keyIsRefused} guard so every fetch boundary fail-closes identically. */\n\tprivate secretKeyRefused(): boolean {\n\t\tif (!keyIsRefused(this.publishableKey)) return false;\n\t\tthis.host.error = KEY_REFUSED_MESSAGE;\n\t\tdispatchKeyRefusal(this.host);\n\t\treturn true;\n\t}\n}\n\n/**\n * Translate flat form values into a {@link RoxyRequest} for an endpoint. The `{name}` segments in the endpoint template are substituted from the values and removed; the rest become the JSON body for POST or query parameters for GET. This is the spec-light request builder the base element uses to turn a `<roxy-endpoint-form>` submission into a self-fetch, so a component needs no per-endpoint glue.\n *\n * @param queryKeys - Names the spec declares as `in: query` for this operation, which `<roxy-endpoint-form>` reports on its `roxy-submit` event. A POST operation can still take query parameters (every localized endpoint takes `?lang=`), and sending one in the JSON body silently drops it, so those names are routed to the query string on POST as well as GET.\n */\nexport function buildRequest(\n\tendpoint: string,\n\tmethod: 'GET' | 'POST',\n\tvalues: Record<string, unknown>,\n\tqueryKeys: readonly string[] = [],\n): RoxyRequest {\n\tconst rest: Record<string, unknown> = { ...values };\n\tconst path = `/${endpoint.replace(/^\\//, '')}`.replace(\n\t\t/\\{([^}]+)\\}/g,\n\t\t(_match, name: string) => {\n\t\t\tconst v = rest[name];\n\t\t\tdelete rest[name];\n\t\t\treturn encodeURIComponent(String(v ?? ''));\n\t\t},\n\t);\n\tconst inQuery = new Set(queryKeys);\n\tconst query: Record<string, string | number | undefined> = {};\n\tconst body: Record<string, unknown> = {};\n\tfor (const [k, v] of Object.entries(rest)) {\n\t\tif (v === undefined || v === '') continue;\n\t\tif (method === 'GET' || inQuery.has(k)) query[k] = v as string | number;\n\t\telse body[k] = v;\n\t}\n\treturn { path, method, query, body: method === 'POST' ? body : undefined };\n}\n", "/**\n * The interpretation accordion: the one way this library shows a label, a short value, and a body of prose behind a disclosure.\n *\n * @remarks\n * Exclusive by construction (`<details name>`), so a card grows by at most one open section and never becomes a wall of text. Callers pass their own group `name` so two accordions on one page do not fight over which section is open.\n *\n * This lives here rather than in a component because the same accordion is the right shape wherever an endpoint returns a labelled reading: the Human Design bodygraph and type card use it for strategy, authority, and aura; `roxy-hexagram` uses it for the changing lines. A card that draws its own disclosure, because its summary carries more than a label and an aside, still renders the shared body and imports {@link readingDetailStyles} for it rather than restating those rules.\n *\n * **Call it through `RoxyDataElement.renderInterpretation`, never directly.** That method is where `hide-readings` is honoured, so a direct call renders prose a host asked to be left out. The section it emits carries `part=\"section readings\"` and each row `part=\"reading\"`, which is what makes the readings of EVERY component addressable under one name from outside the shadow root.\n */\n\nimport { css, html, nothing } from 'lit';\nimport type { ChromeString } from '../i18n/chrome-strings.js';\nimport { chevron } from './disclosure.js';\nimport type { Translate } from './hd-reading.js';\n\n/** One row: the label, the short value shown as the aside, and the interpretation body. `extra` renders under the body for a section that carries more than prose. */\nexport interface InterpSection {\n\tlabel: string;\n\taside?: string;\n\tbody: string;\n\textra?: unknown;\n}\n\n/**\n * Styles for the markup {@link renderReadingDetail} emits. Import this wherever that helper is called; {@link interpAccordionStyles} already embeds it, so an accordion caller needs only the one.\n *\n * @remarks\n * Separate from the accordion shell because the two are needed independently: a card can draw its own disclosure and still render the shared reading body, and hand-copying these rules is how the chip colour and spacing drifted apart across five components.\n *\n * No margin-top on the chip row. The body above already spaces its children, so a margin here would set the chips twice as far out as every other row.\n */\nexport const readingDetailStyles = css`.interp-keywords{flex-wrap:wrap;gap:.25rem;display:flex}.interp-keywords .kw{border-radius:var(--roxy-radius-full,9999px);background:color-mix(in srgb, var(--roxy-accent,#f59e0b) 14%, transparent);color:var(--roxy-fg,#0a0a0a);font-size:var(--roxy-text-xs,.75rem);padding:1px 8px}`;\n\nexport const interpAccordionStyles = css`.block{border-top:1px solid var(--roxy-border,#e4e4e7);padding-top:var(--roxy-space-md,1rem)}.block h3{margin:0 0 var(--roxy-space-sm,.5rem);font-size:var(--roxy-text-sm,.875rem);font-weight:var(--roxy-weight-bold,600);color:var(--roxy-muted,#71717a);text-transform:uppercase;letter-spacing:.06em}.interp-card{border:1px solid var(--roxy-border,#e4e4e7);border-radius:var(--roxy-radius-md,8px);padding:var(--roxy-space-sm,.5rem) var(--roxy-space-md,1rem);margin-bottom:var(--roxy-space-xs,.25rem)}.interp-card summary{cursor:pointer;color:var(--roxy-fg,#0a0a0a);align-items:center;gap:var(--roxy-space-sm,.5rem);font-weight:500;font-size:var(--roxy-text-sm,.875rem);display:flex}.interp-card summary:focus-visible{outline:2px solid var(--roxy-ring,#f59e0b66);outline-offset:2px;border-radius:var(--roxy-radius-sm,4px)}.interp-lead{flex-wrap:wrap;flex:auto;order:1;align-items:baseline;gap:.4rem;min-width:0;display:inline-flex}.interp-aside{flex-shrink:0;order:2;align-items:center;gap:.5rem;display:inline-flex}.roxy-chevron{order:3}.interp-aside small{color:var(--roxy-muted,#71717a);white-space:nowrap;font-weight:400}@container (width<=26rem){.interp-card summary{flex-wrap:wrap}.roxy-chevron{order:2}.interp-aside{flex-basis:100%;order:3;justify-content:flex-end}}.interp-body{margin-top:var(--roxy-space-sm,.5rem);gap:var(--roxy-space-sm,.5rem);color:var(--roxy-fg,#0a0a0a);font-size:var(--roxy-text-sm,.875rem);overflow-wrap:anywhere;line-height:1.6;display:grid}.interp-body p{margin:0}${readingDetailStyles}`;\n\n/** The keyword chips a reading carries, or nothing. One renderer because four components drew the identical row, and the markup has to match {@link readingDetailStyles}, which is the pairing that drifts when it is copied. */\nexport function renderKeywordChips(keywords: readonly string[] | undefined) {\n\tif (!keywords?.length) return nothing;\n\treturn html`<div class=\"interp-keywords\">${keywords.map((k) => html`<span class=\"kw\">${k}</span>`)}</div>`;\n}\n\n/** The prose an endpoint returns ABOUT one contact: a summary, up to three labelled lines, and the keyword chips under them. Every field is optional, so a narrower response renders fewer rows rather than empty ones. */\nexport interface ReadingDetail {\n\tsummary?: string;\n\timpact?: string;\n\ttiming?: string;\n\tguidance?: string;\n\tkeywords?: readonly string[];\n}\n\n/** Render one {@link ReadingDetail}. The three labels are copy, so this takes the translator, and they are typed {@link ChromeString} because the lookup is one indirection from the call: a scan of `t(...)` sites cannot follow that, and the compiler can. */\nexport function renderReadingDetail(\n\td: ReadingDetail | undefined,\n\tt: Translate,\n) {\n\tif (!d) return nothing;\n\tconst line = (label: ChromeString, value: string | undefined) =>\n\t\tvalue ? html`<p><strong>${t(label)}</strong> ${value}</p>` : nothing;\n\treturn html`${d.summary ? html`<p>${d.summary}</p>` : nothing} ${line('Impact:', d.impact)}${line('Timing:', d.timing)}${line('Guidance:', d.guidance)} ${renderKeywordChips(d.keywords)}`;\n}\n\n/**\n * Render the accordion. Sections with no body are dropped, so a caller can pass the full set and let a narrower response render only what it carries. `name` groups the `<details>` exclusively, so opening one closes the last.\n */\nexport function renderInterpAccordion(\n\tsections: InterpSection[],\n\tname: string,\n\theading: string,\n) {\n\tconst shown = sections.filter((s) => Boolean(s.body));\n\tif (shown.length === 0) return nothing;\n\n\treturn html`<section class=\"block\" part=\"section readings\"><h3>${heading}</h3>${shown.map(\n\t\t\t(\n\t\t\t\ts,\n\t\t\t\ti,\n\t\t\t) => html`<details class=\"interp-card\" part=\"reading\" name=\"${name}\" ?open=\"${i === 0}\"><summary><span class=\"interp-lead\">${s.label}</span> ${chevron()} ${s.aside ? html`<span class=\"interp-aside\"><small>${s.aside}</small></span>` : nothing}</summary><div class=\"interp-body\"><p>${s.body}</p>${s.extra ?? nothing}</div></details>`,\n\t\t)}</section>`;\n}\n", "import type { TemplateResult } from 'lit';\nimport { css, html } from 'lit';\n\n/**\n * Disclosure chevron for `<details>`/`<summary>` accordions. Replaces the\n * browser default triangle with a thin chevron that rotates when the host\n * `<details>` opens. Render it inside the `<summary>` and pair with\n * {@link disclosureStyles}.\n */\nexport function chevron(): TemplateResult {\n\treturn html`<svg class=\"roxy-chevron\" viewBox=\"0 0 16 16\" width=\"14\" height=\"14\" aria-hidden=\"true\"><path d=\"M4 6l4 4 4-4\" fill=\"none\" stroke=\"currentColor\" stroke-width=\"1.5\" stroke-linecap=\"round\" stroke-linejoin=\"round\"/></svg>`;\n}\n\n/**\n * Shared `<details>` accordion styling: hides the native disclosure triangle\n * and rotates the {@link chevron} 180 degrees when the accordion is open.\n * Import into any component that renders disclosure accordions so the chevron\n * looks and behaves identically.\n */\nexport const disclosureStyles = css`summary{list-style:none}summary::-webkit-details-marker{display:none}.roxy-chevron{aspect-ratio:auto;width:14px;height:14px;color:var(--roxy-muted,#71717a);transition:transform var(--roxy-motion-duration,.2s) var(--roxy-motion-easing,ease);flex-shrink:0}details[open]>summary .roxy-chevron{transform:rotate(180deg)}@media (prefers-reduced-motion:reduce){.roxy-chevron{transition:none}}`;\n", "import type { ReactiveController, ReactiveControllerHost } from 'lit';\n\n/**\n * Marker class on the inline JSON script a server emits inside a component.\n *\n * @example\n * ```html\n * <roxy-natal-chart>\n * <script type=\"application/json\" class=\"roxy-data\">{ ...response... }</script>\n * </roxy-natal-chart>\n * ```\n */\nconst ROXY_DATA_CLASS = 'roxy-data';\n\n/**\n * Serialize a RoxyAPI response for embedding inside an inline `<script type=\"application/json\" class=\"roxy-data\">`. This is the safe writer counterpart to {@link MarkupDataController}, the reader: server-rendered and cached consumers (WordPress, JSX SSR, static HTML) emit the script with this, and the component hydrates `data` from it on connect.\n *\n * @remarks\n * Use this instead of a bare `JSON.stringify`. A raw stringify of a response that contains the literal text `</script>` (common in long interpretation prose) closes the script element early, corrupting the page and creating an HTML-injection vector. This escapes the script-unsafe characters to their `\\uXXXX` JSON escapes, which `JSON.parse` restores to the original characters, so the value the component receives is identical to the response you passed.\n *\n * `<` is the load-bearing escape (it defeats `</script>` and `<!--`). `>` and `&` are escaped for defence in depth, and U+2028 / U+2029 because they are valid in JSON yet are line terminators in a `<script>` context and break some parsers. The escapes introduce only `\\uXXXX` sequences, so the replacements never feed each other and order is irrelevant.\n *\n * Pass the unwrapped RoxyAPI response, the same shape you would assign to `element.data`. Do not pass the SDK envelope (`{ data, error, request, response }`).\n *\n * @example\n * ```ts\n * import { serializeRoxyData } from '@roxyapi/ui';\n *\n * const { data } = await roxy.dreams.getDreamSymbol({ path: { id: 'water' } });\n * const html = `<roxy-dream-card><script type=\"application/json\" class=\"roxy-data\">${serializeRoxyData(data)}</script></roxy-dream-card>`;\n * ```\n */\nexport function serializeRoxyData(data: unknown): string {\n\treturn JSON.stringify(data)\n\t\t.replace(/</g, '\\\\u003c')\n\t\t.replace(/>/g, '\\\\u003e')\n\t\t.replace(/&/g, '\\\\u0026')\n\t\t.replace(/\\u2028/g, '\\\\u2028')\n\t\t.replace(/\\u2029/g, '\\\\u2029');\n}\n\n/**\n * Build the complete `<script type=\"application/json\" class=\"roxy-data\">…</script>` element a server nests inside a `roxy-*` component for the no-JavaScript hydration path. The payload is escaped via {@link serializeRoxyData}, so it is safe to drop straight into HTML output.\n *\n * @remarks\n * The element carries both `type=\"application/json\"` and `class=\"roxy-data\"` because {@link MarkupDataController} reads only a direct-child script that has both. Emit one of these inside the target component; the JavaScript `data` property still wins if it is later assigned.\n *\n * @example\n * ```ts\n * import { roxyDataScript } from '@roxyapi/ui';\n *\n * const { data } = await roxy.crystals.getCrystal({ path: { id: 'amethyst' } });\n * const html = `<roxy-crystal-grid>${roxyDataScript(data)}</roxy-crystal-grid>`;\n * ```\n */\nexport function roxyDataScript(data: unknown): string {\n\treturn `<script type=\"application/json\" class=\"${ROXY_DATA_CLASS}\">${serializeRoxyData(data)}</script>`;\n}\n\n/**\n * True when the element is a `<script type=\"application/json\">`. Uses tag name and attribute rather than `instanceof HTMLScriptElement` so the check holds in every DOM implementation, including server-rendered and hydration runtimes where the constructor global may be absent.\n */\nfunction isJsonScript(el: Element): boolean {\n\treturn (\n\t\tel.nodeName === 'SCRIPT' && el.getAttribute('type') === 'application/json'\n\t);\n}\n\n/**\n * Host shape the controller drives: any reactive element that exposes a public `data` slot. The controller only writes `data` when the host left it unset, so the JavaScript property path always wins.\n */\ninterface DataHost extends ReactiveControllerHost, HTMLElement {\n\tdata?: unknown;\n}\n\n/**\n * Reactive controller that lets a component hydrate its `data` from embedded markup when no `data` property was assigned in JavaScript.\n *\n * @remarks\n * The server-side and cached-render model: a backend renders the RoxyAPI response into a direct-child `<script type=\"application/json\" class=\"roxy-data\">` element, ships static HTML, and never runs per-element JavaScript to assign a property. On connect this controller reads that script, parses it, and feeds the result to the host. The JavaScript property path is untouched and authoritative: if `host.data` already holds a value when the host connects, the controller does nothing and the markup is ignored.\n *\n * Source resolution order on connect, first hit wins:\n *\n * 1. `host.data` already set in JavaScript -> leave it, read nothing.\n * 2. A direct-child `<script type=\"application/json\" class=\"roxy-data\">` -> parse and use. Direct-child only, so a nested component's own script is never read by an ancestor.\n *\n * Fetching from a URL is intentionally unsupported: that would require a browser-visible key and breaks the server-rendered, cached model these consumers rely on.\n *\n * Timing: {@link hostConnected} runs inside the host `connectedCallback`. For an element parsed from server HTML, its direct children are present by the time the custom element upgrades and connects, so the script is readable here. For an element created with `document.createElement` and connected before any child is appended, there is nothing to read and the property path is the only source, which is exactly the existing behavior.\n *\n * Failure is safe: malformed JSON or a missing script leaves `host.data` untouched, so the host renders its normal empty state.\n *\n * Reading the script never mutates it, and only the marked script is touched, so any sibling fallback markup a server nested inside the element (for no-JavaScript, AMP, or crawler rendering) is left in place.\n *\n * @example\n * ```ts\n * import { MarkupDataController } from '../utils/markup-data.js';\n *\n * export class RoxyExample extends LitElement {\n * constructor() {\n * super();\n * new MarkupDataController(this);\n * }\n *\n * @property({ attribute: false })\n * data: ExampleResponse | null = null;\n * }\n * ```\n */\nexport class MarkupDataController<T = unknown> implements ReactiveController {\n\tprivate readonly host: DataHost;\n\n\tconstructor(host: DataHost) {\n\t\tthis.host = host;\n\t\thost.addController(this);\n\t}\n\n\thostConnected() {\n\t\t// Property path wins. If the consumer (React, vanilla `.data =`, the\n\t\t// widgets script, an MCP agent) already set data, never look at markup.\n\t\tif (this.host.data != null) return;\n\n\t\tconst parsed = this.read();\n\t\tif (parsed === undefined) return;\n\n\t\tthis.host.data = parsed as T;\n\t\tthis.host.requestUpdate();\n\t}\n\n\t/**\n\t * Resolve the embedded payload. Returns `undefined` when there is nothing valid to read so the caller can leave `host.data` untouched.\n\t */\n\tprivate read(): T | undefined {\n\t\tconst inline = this.findInlineScript();\n\t\treturn inline ? this.parse(inline.textContent) : undefined;\n\t}\n\n\t/**\n\t * Direct-child `<script type=\"application/json\" class=\"roxy-data\">`. Scoped to immediate children so a nested data-driven component never has its script read by an ancestor, and so sibling fallback markup is ignored.\n\t */\n\tprivate findInlineScript(): Element | null {\n\t\tfor (const child of Array.from(this.host.children)) {\n\t\t\tif (isJsonScript(child) && child.classList.contains(ROXY_DATA_CLASS)) {\n\t\t\t\treturn child;\n\t\t\t}\n\t\t}\n\t\treturn null;\n\t}\n\n\tprivate parse(text: string | null): T | undefined {\n\t\tif (!text?.trim()) return undefined;\n\t\ttry {\n\t\t\treturn JSON.parse(text) as T;\n\t\t} catch {\n\t\t\t// Malformed embedded JSON: fail safe, leave the host empty state in\n\t\t\t// place rather than throwing during connect.\n\t\t\treturn undefined;\n\t\t}\n\t}\n}\n"],
|
|
5
|
+
"mappings": "wMAAA,OAAS,OAAAA,GAAK,QAAAC,EAAM,WAAAC,EAAS,OAAAC,MAAW,MACxC,OAAS,iBAAAC,OAAqB,oBC4BvB,SAASC,EAAUC,EAAmB,CAC5C,OAAOA,EACL,YAAY,EACZ,QAAQ,WAAY,GAAG,EACvB,KAAK,CACR,CClBA,IAAMC,GAAU,CACfC,EACAC,IACyBA,EAAOD,EAAME,EAAUD,CAAI,CAAC,EAAI,OAuI1D,IAAME,GAAwC,CAC7C,OAAQ,IACR,KAAM,IACN,KAAM,IACN,QAAS,IACT,KAAM,IACN,MAAO,IACP,SAAU,IACV,MAAO,GACR,EAGaC,EACZC,GACwBC,GAAQH,GAAeE,CAAI,ECxKpD,OAGC,QAAAE,EACA,WAAAC,MAEM,MACP,OAAS,YAAAC,EAAU,SAAAC,MAAa,oBAChC,OAAS,aAAAC,MAAiB,+BCR1B,OAAS,cAAAC,OAAkB,MC6BpB,SAASC,EAAYC,EAAqC,CAGhE,GAAIA,EAAG,KAAM,OAAOA,EAAG,KACvB,GAAI,OAAO,SAAa,IAAa,OACrC,IAAMC,EAAYD,EAAG,UAAU,QAAQ,GAAG,aAAa,MAAM,EAC7D,OAAIC,GACG,SAAS,gBAAgB,MAAQ,MACzC,CCOA,IAAMC,EAAa,mBAEnB,SAASC,GAA2B,CACnC,IAAMC,EAAS,WACTC,EAAWD,EAAOF,CAAU,EAClC,GAAIG,EAAU,OAAOA,EACrB,IAAMC,EAA0B,CAC/B,SAAU,CAAC,EACX,YAAa,CAAC,EACd,UAAW,IAAI,IACf,UAAW,IAAI,GAChB,EACA,OAAAF,EAAOF,CAAU,EAAII,EACdA,CACR,CA0BO,SAASC,EACfC,EACAC,EACS,CACT,OAAKA,EACED,EAAS,QAAQ,iBAAkB,CAACE,EAAOC,IACjDA,KAAOF,EAAO,OAAOA,EAAKE,CAAG,GAAK,EAAE,EAAID,CACzC,EAHkBF,CAInB,CAQO,SAASI,EACfC,EACAC,EACAL,EACS,CACT,GAAI,CAACI,EAAM,OAAON,EAAYO,EAAQL,CAAI,EAC1C,GAAM,CAAE,SAAAM,CAAS,EAAIC,EAAS,EACxBC,EAAMJ,EAAK,YAAY,EACvBK,EAAUH,EAASE,CAAG,GAAKF,EAASE,EAAI,MAAM,GAAG,EAAE,CAAC,CAAW,EACrE,OAAOV,EAAYW,IAAUC,EAAUL,CAAM,CAAC,GAAKA,EAAQL,CAAI,CAChE,CAiDO,SAASW,EAAeC,EAAkC,CAChE,GAAM,CAAE,UAAAC,CAAU,EAAIC,EAAS,EAC/B,OAAAD,EAAU,IAAID,CAAQ,EACf,IAAM,CACZC,EAAU,OAAOD,CAAQ,CAC1B,CACD,CC1JO,IAAMG,EAAN,KAAqD,CAI3D,YAAYC,EAA8B,CACzC,KAAK,KAAOA,EACZA,EAAK,cAAc,IAAI,CACxB,CAEA,eAAsB,CACrB,KAAK,YAAcC,EAAe,IAAM,KAAK,KAAK,cAAc,CAAC,CAClE,CAEA,kBAAyB,CACxB,KAAK,cAAc,EACnB,KAAK,YAAc,MACpB,CACD,EHbO,IAAeC,EAAf,cAA4CC,EAAW,CAC7D,aAAc,CACb,MAAM,EA0BP,KAAmB,WAAa,CAC/BC,EACAC,IACY,KAAK,EAAED,EAAQC,CAAI,EAzB/B,IAAIC,EAAiB,IAAI,CAC1B,CAgBU,EAAEF,EAAgBC,EAAgD,CAC3E,OAAOE,EAAU,KAAK,cAAc,EAAGH,EAAQC,CAAI,CACpD,CAaU,eAAoC,CAC7C,OAAOG,EAAY,IAAI,CACxB,CACD,EIxDA,OAAS,OAAAC,OAAW,MAMb,IAAMC,EAAaD,+4FCN1B,IAAME,GAAO,SACPC,GAAO,SAEb,SAASC,GAAcC,EAAkD,CACxE,OAAO,OAAOA,GAAU,UAAYA,IAAU,MAAQ,CAAC,MAAM,QAAQA,CAAK,CAC3E,CAQA,SAASC,EAAOD,EAAyB,CACxC,GAAI,MAAM,QAAQA,CAAK,EAAG,CACzB,IAAIE,EAAU,GACRC,EAAMH,EAAM,IAAKI,GAAS,CAC/B,IAAMC,EAAOJ,EAAOG,CAAI,EACxB,OAAIC,IAASD,IAAMF,EAAU,IACtBG,CACR,CAAC,EACD,OAAOH,EAAUC,EAAMH,CACxB,CACA,GAAI,CAACD,GAAcC,CAAK,EAAG,OAAOA,EAElC,IAAMM,EAAON,EAAMH,EAAI,EACjBU,EAAOP,EAAMF,EAAI,EAGvB,GACC,MAAM,QAAQQ,CAAI,GAClB,MAAM,QAAQC,CAAI,GAClB,OAAO,KAAKP,CAAK,EAAE,SAAW,EAE9B,OAAOO,EAAK,IAAKC,GAAQ,CACxB,IAAMJ,EAAgC,CAAC,EACvC,OAACE,EAAkB,QAAQ,CAACG,EAAKC,IAAM,CACtCN,EAAKK,CAAG,EAAIR,EAAQO,EAAkBE,CAAC,CAAC,CACzC,CAAC,EACMN,CACR,CAAC,EAGF,IAAIF,EAAU,GACRC,EAA+B,CAAC,EACtC,OAAW,CAACQ,EAAKP,CAAI,IAAK,OAAO,QAAQJ,CAAK,EAAG,CAChD,IAAMK,EAAOJ,EAAOG,CAAI,EACpBC,IAASD,IAAMF,EAAU,IAC7BC,EAAIQ,CAAG,EAAIN,CACZ,CACA,OAAOH,EAAUC,EAAMH,CACxB,CAkBO,SAASY,EAAiBZ,EAAa,CAC7C,OAAOC,EAAOD,CAAK,CACpB,CClEO,IAAMa,EACZ,mIAUM,SAASC,EAAaC,EAAyC,CACrE,MAAO,CAAC,CAACA,GAAO,CAACA,EAAI,WAAW,KAAK,CACtC,CAKO,SAASC,EACfC,EACAC,EAA2B,CAAC,EACrB,CACHA,EAAK,MAAM,QAAQ,KAAKC,CAAmB,EAC/CF,EAAK,cACJ,IAAI,YAAY,wBAAyB,CACxC,OAAQ,CAAE,OAAQ,sBAAuB,QAASE,CAAoB,EACtE,QAAS,GACT,SAAU,EACX,CAAC,CACF,CACD,CCZO,IAAMC,GAAmB,6BAQhC,eAAsBC,GAAaC,EAAgC,CAClE,GAAI,CACH,IAAMC,EAAQ,MAAMD,EAAI,KAAK,EAC7B,GAAIC,GAAM,MAAO,OAAOA,EAAK,KAC9B,MAAQ,CAER,CACA,MAAO,mBAAmBD,EAAI,MAAM,GACrC,CAqBO,IAAME,EAAN,KAAiE,CAoBvE,YAAYC,EAAoB,CAbhC,aAAUL,GAcT,KAAK,KAAOK,EACZA,EAAK,cAAc,IAAI,CACxB,CAEA,kBAAmB,CAClB,KAAK,OAAO,MAAM,EAClB,KAAK,MAAQ,MACd,CAOA,MAAM,IAAIC,EAAiC,CAE1C,GAAI,CAAC,KAAK,WAAa,KAAK,iBAAiB,EAAG,OAChD,KAAK,OAAO,MAAM,EAClB,IAAMC,EAAa,IAAI,gBACvB,KAAK,MAAQA,EACb,KAAK,KAAK,QAAU,GACpB,KAAK,KAAK,MAAQ,KAClB,GAAI,CACH,IAAML,EAAM,KAAK,UACd,MAAM,MAAM,KAAK,UAAW,CAC5B,OAAQ,OACR,QAAS,CACR,OAAQ,mBACR,eAAgB,kBACjB,EACA,KAAM,KAAK,UAAUI,CAAG,EACxB,OAAQC,EAAW,MACpB,CAAC,EACA,MAAM,KAAK,QAAQD,EAAKC,EAAW,MAAM,EAC5C,GAAI,CAACL,EAAI,GAAI,MAAM,IAAI,MAAM,MAAMD,GAAaC,CAAG,CAAC,EACpD,IAAMM,EAAQ,MAAMN,EAAI,KAAK,EAC7B,GAAIK,EAAW,OAAO,QAAS,OAC/B,KAAK,KAAK,KAAOC,CAClB,OAASC,EAAK,CACb,GAAKA,GAA2B,OAAS,aAAc,OACvD,KAAK,KAAK,MAAQA,aAAe,MAAQA,EAAI,QAAU,OAAOA,CAAG,CAClE,QAAE,CACG,KAAK,QAAUF,IAAY,KAAK,MAAQ,QACvCA,EAAW,OAAO,UAAS,KAAK,KAAK,QAAU,GACrD,CACD,CAQQ,UAAUD,EAA0B,CAC3C,OAAO,KAAK,UACX,KAAK,cAAgB,CAAE,GAAGA,EAAK,QAAS,KAAK,aAAc,EAAIA,CAChE,CACD,CAGQ,QAAQA,EAAkBI,EAAwC,CAIzE,IAAMC,EAAM,IAAI,IAAI,GAAG,KAAK,OAAO,GAAGL,EAAI,IAAI,GAAI,SAAS,OAAO,EAClE,OAAW,CAACM,EAAGC,CAAC,IAAK,OAAO,QAAQP,EAAI,OAAS,CAAC,CAAC,EAC9CO,GAAK,MAAMF,EAAI,aAAa,IAAIC,EAAG,OAAOC,CAAC,CAAC,EAEjD,IAAMC,EAAkC,CAAE,OAAQ,kBAAmB,EACrE,OAAI,KAAK,iBAAgBA,EAAQ,WAAW,EAAI,KAAK,gBACjDR,EAAI,MAAQ,OAAMQ,EAAQ,cAAc,EAAI,oBACzC,MAAMH,EAAK,CACjB,OAAQL,EAAI,QAAU,MACtB,QAAAQ,EACA,KAAMR,EAAI,MAAQ,KAAO,KAAK,UAAUA,EAAI,IAAI,EAAI,OACpD,OAAAI,CACD,CAAC,CACF,CAGQ,kBAA4B,CACnC,OAAKK,EAAa,KAAK,cAAc,GACrC,KAAK,KAAK,MAAQC,EAClBC,EAAmB,KAAK,IAAI,EACrB,IAHwC,EAIhD,CACD,EAOO,SAASC,EACfC,EACAC,EACAC,EACAC,EAA+B,CAAC,EAClB,CACd,IAAMC,EAAgC,CAAE,GAAGF,CAAO,EAC5CG,EAAO,IAAIL,EAAS,QAAQ,MAAO,EAAE,CAAC,GAAG,QAC9C,eACA,CAACM,EAAQC,IAAiB,CACzB,IAAMb,EAAIU,EAAKG,CAAI,EACnB,cAAOH,EAAKG,CAAI,EACT,mBAAmB,OAAOb,GAAK,EAAE,CAAC,CAC1C,CACD,EACMc,EAAU,IAAI,IAAIL,CAAS,EAC3BM,EAAqD,CAAC,EACtDzB,EAAgC,CAAC,EACvC,OAAW,CAACS,EAAGC,CAAC,IAAK,OAAO,QAAQU,CAAI,EACnCV,IAAM,QAAaA,IAAM,KACzBO,IAAW,OAASO,EAAQ,IAAIf,CAAC,EAAGgB,EAAMhB,CAAC,EAAIC,EAC9CV,EAAKS,CAAC,EAAIC,GAEhB,MAAO,CAAE,KAAAW,EAAM,OAAAJ,EAAQ,MAAAQ,EAAO,KAAMR,IAAW,OAASjB,EAAO,MAAU,CAC1E,CC3LA,OAAS,OAAA0B,EAAK,QAAAC,EAAM,WAAAC,MAAe,MCVnC,OAAS,OAAAC,GAAK,QAAAC,OAAY,MAQnB,SAASC,GAA0B,CACzC,OAAOD,8NACR,CAQO,IAAME,EAAmBH,sYDazB,IAAMI,GAAsBC,2RAEtBC,EAAwBD,09CAA49CD,EAAmB,GA+B7gD,SAASG,EACfC,EACAC,EACAC,EACC,CACD,IAAMC,EAAQH,EAAS,OAAQI,GAAM,EAAQA,EAAE,IAAK,EACpD,OAAID,EAAM,SAAW,EAAUE,EAExBC,uDAA0DJ,CAAO,QAAQC,EAAM,IACpF,CACCC,EACAG,IACID,sDAAyDL,CAAI,YAAYM,IAAM,CAAC,wCAAwCH,EAAE,KAAK,WAAWI,EAAQ,CAAC,IAAIJ,EAAE,MAAQE,sCAAyCF,EAAE,KAAK,kBAAoBC,CAAO,yCAAyCD,EAAE,IAAI,OAAOA,EAAE,OAASC,CAAO,kBAC1T,CAAC,YACH,CEnEA,IAAMI,GAAkB,YAkDxB,SAASC,GAAaC,EAAsB,CAC3C,OACCA,EAAG,WAAa,UAAYA,EAAG,aAAa,MAAM,IAAM,kBAE1D,CA2CO,IAAMC,EAAN,KAAsE,CAG5E,YAAYC,EAAgB,CAC3B,KAAK,KAAOA,EACZA,EAAK,cAAc,IAAI,CACxB,CAEA,eAAgB,CAGf,GAAI,KAAK,KAAK,MAAQ,KAAM,OAE5B,IAAMC,EAAS,KAAK,KAAK,EACrBA,IAAW,SAEf,KAAK,KAAK,KAAOA,EACjB,KAAK,KAAK,cAAc,EACzB,CAKQ,MAAsB,CAC7B,IAAMC,EAAS,KAAK,iBAAiB,EACrC,OAAOA,EAAS,KAAK,MAAMA,EAAO,WAAW,EAAI,MAClD,CAKQ,kBAAmC,CAC1C,QAAWC,KAAS,MAAM,KAAK,KAAK,KAAK,QAAQ,EAChD,GAAIN,GAAaM,CAAK,GAAKA,EAAM,UAAU,SAASC,EAAe,EAClE,OAAOD,EAGT,OAAO,IACR,CAEQ,MAAME,EAAoC,CACjD,GAAKA,GAAM,KAAK,EAChB,GAAI,CACH,OAAO,KAAK,MAAMA,CAAI,CACvB,MAAQ,CAGP,MACD,CACD,CACD,EXrIA,IAAMC,GAEF,CACH,cAAgBC,GAAU,CACzB,GAAIA,GAAS,KACb,IAAI,CACH,IAAMC,EAAkB,KAAK,MAAMD,CAAK,EACxC,GAAIC,GAAU,OAAOA,GAAW,UAAY,CAAC,MAAM,QAAQA,CAAM,EAChE,OAAOA,CAET,MAAQ,CAER,CACA,QAAQ,KACP,iFACD,EAED,CACD,EA8BsBC,EAAf,cAEGC,CAAqB,CAiI9B,aAAc,CACb,MAAM,EA7HP,UAAiB,KAIjB,cAAW,GAIX,YAAyB,OAiDzB,cAAW,GAWX,kBAAe,GAmBf,kBAAe,GAYf,aAAU,GAIV,WAAuB,KAMvB,KAAQ,YAAc,GAItB,KAAQ,QAAU,GAIlB,KAAQ,OAAS,GA8HjB,KAAQ,OAAS,IAAM,CACtB,KAAK,QAAU,EAChB,EAiCA,KAAQ,aAAgBC,GAAa,CACpC,IAAMC,EAAUD,EAAkB,OAKlC,KAAK,WAAaC,EAAO,OACzB,KAAK,OAAS,CAAC,CAACA,EAAO,OACvB,KAAK,YAAc,GACnB,KAAK,QAAU,GACX,KAAK,UAAU,KAAK,gBAAgBA,EAAO,MAAM,EAChD,KAAK,QAAQ,IACjBC,EACC,KAAK,SACL,KAAK,OACLD,EAAO,OACPA,EAAO,WAAa,CAAC,CACtB,CACD,CACD,EAzKC,IAAIE,EAAwB,IAAI,EAChC,KAAK,QAAU,IAAIC,EAAmB,IAAI,CAC3C,CAtIA,YAAO,OAAyB,CAACC,CAAU,EAwIjC,WAAWC,EAA+B,CAOnD,GAAIA,EAAQ,IAAI,MAAM,GAAK,KAAK,MAAQ,KAAM,CAC7C,IAAMC,EAAWC,EAAc,KAAK,IAAI,EACpCD,IAAa,KAAK,OAAM,KAAK,KAAOA,EACzC,CACID,EAAQ,IAAI,gBAAgB,IAC/B,KAAK,QAAQ,eAAiB,KAAK,gBAEhCA,EAAQ,IAAI,SAAS,GAAK,KAAK,UAClC,KAAK,QAAQ,QAAU,KAAK,SAEzBA,EAAQ,IAAI,WAAW,IAC1B,KAAK,QAAQ,UAAY,KAAK,WAE3BA,EAAQ,IAAI,eAAe,IAC9B,KAAK,QAAQ,cAAgB,KAAK,cAEpC,CAEA,QAAkB,CACjB,OAAOG,IAAO,KAAK,oBAAoB,CAAC,GAAG,KAAK,YAAY,CAAC,EAC9D,CAcQ,qBAA+B,CACtC,IAAMC,EAAQ,KAAK,aACjB,MAAM,GAAG,EACT,IAAKC,GAAMA,EAAE,KAAK,EAAE,YAAY,CAAC,EACjC,OAAQA,GAAM,oBAAoB,KAAKA,CAAC,CAAC,EAC3C,GAAID,EAAM,SAAW,EAAG,OAAOE,EAC/B,IAAMC,EAAQH,EACZ,IAAKC,GAAM,WAAWA,CAAC,4BAA4B,EACnD,KAAK,EAAE,EACT,OAAOF,WAAcI,CAAK,UAC3B,CAGQ,aAAuB,CAC9B,OAAI,KAAK,QAAgB,KAAK,cAAc,EACxC,KAAK,OAAS,KAAa,KAAK,YAAY,KAAK,KAAK,EACtD,KAAK,MAAQ,KAMX,KAAK,YAKN,KAAK,QAAgB,KAAK,WAAW,EAClC,KAAK,aAAa,KAAK,IAAI,EAL1B,KAAK,gBAAgB,EACzBJ,IAAO,KAAK,WAAW,KAAK,IAAI,CAAC,GAAG,KAAK,kBAAkB,CAAC,GAC5D,KAAK,WAAW,KAAK,IAAI,EAKvB,KAAK,aAAa,CAC1B,CAeU,qBACTK,EACAC,EACAC,EACU,CACV,OAAI,KAAK,aAAqBJ,EAIvBK,EAAsBH,EAAUC,EAAM,KAAK,EAAEC,GAAW,SAAS,CAAC,CAC1E,CAKU,aAAaE,EAAkB,CACxC,IAAMC,EAAO,KAAK,OACfV,IAAO,KAAK,WAAW,CAAC,GAAG,KAAK,WAAWS,CAAI,CAAC,GAChDT,+FAAkG,KAAK,MAAM,KAAK,KAAK,EAAE,YAAY,CAAC,kBAAkB,KAAK,WAAWS,CAAI,CAAC,GAChL,OAAO,KAAK,gBAAgB,EACzBT,IAAOU,CAAI,GAAG,KAAK,kBAAkB,CAAC,GACtCA,CACJ,CAOQ,iBAA2B,CAClC,OACC,KAAK,aAAe,MACpB,KAAK,cAAgB,OACrB,KAAK,cAAgB,OAEvB,CAGU,mBAA6B,CACtC,OAAOV,sJAAyJ,KAAK,EAAE,2BAA2B,CAAC,YACpM,CAGU,cAAwB,CACjC,OAAO,KAAK,SAAW,KAAK,WAAW,EAAI,KAAK,YAAY,CAC7D,CAGU,YAAsB,CAC/B,OAAOA,mDAAsD,KAAK,QAAQ,aAAa,KAAK,MAAM,eAAeW,EAAU,KAAK,OAAO,CAAC,sBAAsBA,EAAU,KAAK,cAAc,CAAC,mBAAmBA,EAAU,KAAK,WAAW,CAAC,mBAAmBA,EAAU,KAAK,WAAW,CAAC,WAAWA,EAAU,KAAK,cAAc,CAAC,CAAC,qBAAqB,KAAK,kBAAkB,CAAC,mBAAmB,KAAK,YAAY,yBACpZ,CAGQ,mBAAyD,CAChE,OACC,KAAK,aAAe,KAAK,SAAW,KAAK,eAAe,EAAI,OAE9D,CAwBQ,aAAsB,CAC7B,MAAO,gBAAgB,KAAK,QAAQ,EACrC,CAEQ,gBAAsD,CAC7D,GAAI,CACH,IAAMC,EAAM,eAAe,QAAQ,KAAK,YAAY,CAAC,EACrD,OAAOA,EAAO,KAAK,MAAMA,CAAG,EAAgC,MAC7D,MAAQ,CACP,MACD,CACD,CAEQ,gBAAgBC,EAAuC,CAC9D,GAAI,CACH,eAAe,QAAQ,KAAK,YAAY,EAAG,KAAK,UAAUA,CAAM,CAAC,CAClE,MAAQ,CAER,CACD,CAGU,aAAuB,CAChC,OAAOb,uDAA0D,KAAK,EAAE,SAAS,CAAC,QACnF,CAGU,eAAyB,CAClC,OAAOA,6EAAgF,KAAK,EAAE,SAAS,CAAC,yBACzG,CAOU,YAAYc,EAA0B,CAC/C,IAAMC,EAASf,sDAAyD,KAAK,EAAEc,CAAO,CAAC,SACvF,OAAO,KAAK,SAAWd,IAAOe,CAAM,GAAG,KAAK,WAAW,CAAC,GAAKA,CAC9D,CACD,EApVCC,EAAA,CADCC,EAAS,CAAE,UAAW,EAAM,CAAC,GANT5B,EAOrB,oBAIA2B,EAAA,CADCC,EAAS,CAAE,KAAM,OAAQ,UAAW,eAAgB,CAAC,GAVjC5B,EAWrB,wBAIA2B,EAAA,CADCC,EAAS,CAAE,KAAM,MAAO,CAAC,GAdL5B,EAerB,sBAIA2B,EAAA,CADCC,EAAS,CAAE,KAAM,OAAQ,UAAW,iBAAkB,CAAC,GAlBnC5B,EAmBrB,8BAIA2B,EAAA,CADCC,EAAS,CAAE,KAAM,OAAQ,UAAW,UAAW,CAAC,GAtB5B5B,EAuBrB,uBAIA2B,EAAA,CADCC,EAAS,CAAE,KAAM,OAAQ,UAAW,UAAW,CAAC,GA1B5B5B,EA2BrB,uBAIA2B,EAAA,CADCC,EAAS,CAAE,KAAM,OAAQ,UAAW,YAAa,CAAC,GA9B9B5B,EA+BrB,yBAoBA2B,EAAA,CADCC,EAAS,CAAE,UAAW,iBAAkB,UAAW/B,EAAuB,CAAC,GAlDvDG,EAmDrB,6BASA2B,EAAA,CADCC,EAAS,CAAE,KAAM,OAAQ,UAAW,cAAe,CAAC,GA3DhC5B,EA4DrB,2BAIA2B,EAAA,CADCC,EAAS,CAAE,KAAM,OAAQ,CAAC,GA/DN5B,EAgErB,wBAWA2B,EAAA,CADCC,EAAS,CAAE,KAAM,QAAS,UAAW,gBAAiB,QAAS,EAAK,CAAC,GA1EjD5B,EA2ErB,4BAmBA2B,EAAA,CADCC,EAAS,CAAE,KAAM,OAAQ,UAAW,gBAAiB,QAAS,EAAK,CAAC,GA7FhD5B,EA8FrB,4BAIA2B,EAAA,CADCC,EAAS,CAAE,KAAM,OAAQ,UAAW,cAAe,CAAC,GAjGhC5B,EAkGrB,2BAIA2B,EAAA,CADCC,EAAS,CAAE,KAAM,MAAO,CAAC,GArGL5B,EAsGrB,2BAIA2B,EAAA,CADCE,EAAM,GAzGc7B,EA0GrB,uBAIA2B,EAAA,CADCE,EAAM,GA7Gc7B,EA8GrB,qBAMQ2B,EAAA,CADPE,EAAM,GAnHc7B,EAoHb,2BAIA2B,EAAA,CADPE,EAAM,GAvHc7B,EAwHb,uBAIA2B,EAAA,CADPE,EAAM,GA3Hc7B,EA4Hb,sBH9JF,IAAM8B,EAAN,cAA2BC,CAA8B,CAQvD,iBAMC,CACR,IAAMC,EAAI,KAAK,KACf,GAAI,CAACA,EAAG,OAAO,KACf,GAAI,aAAcA,GAAKA,EAAE,SAAU,CAClC,GAAI,UAAWA,EAAG,CACjB,IAAMC,EAAOD,EACb,MAAO,CACN,IAAKC,EAAK,SACV,MAAOA,EAAK,MACZ,sBAAuBA,EAAK,sBAC5B,kBAAmBA,EAAK,iBACzB,CACD,CACA,IAAMC,EAAQF,EACd,MAAO,CACN,IAAKE,EAAM,SACX,aAAcA,EAAM,YACrB,CACD,CACA,MAAO,CAAE,IAAKF,CAAc,CAC7B,CAEU,YAAa,CACtB,IAAMG,EAAW,KAAK,gBAAgB,EACtC,GAAI,CAACA,EAAU,OAAO,KAAK,YAAY,EAEvC,GAAM,CACL,IAAKC,EACL,MAAOC,EACP,sBAAAC,EACA,aAAAC,EACA,kBAAAC,CACD,EAAIL,EACEM,EAAQJ,GAAa,KAAK,aAAaD,CAAC,EACxCM,EAAW,IAAI,IAAIJ,GAAyB,CAAC,CAAC,EAE9CK,EAAW,CAAC,KAAK,aAEvB,OAAOC,kDAAqD,KAAK,EAAE,kBAAkB,CAAC,sCAAsCR,EAAE,OAASQ,wBAA2BR,EAAE,MAAM,SAAWS,CAAO,IACzLJ,EAAM,OAAS,EACZG,0CAA6CH,EAC5C,MAAM,EACN,QAAQ,EACR,IAAI,CAACK,EAAGC,IAAQ,CAEhB,IAAMC,EAAUP,EAAM,OAAS,EAAIM,EAAM,EACnCE,EAAaP,EAAS,IAAIM,CAAO,EACjCE,EAASJ,IAAM,GAAKA,IAAM,EAEhC,OAAOF,qBADK,GAAGM,EAAS,SAAW,OAAO,GAAGD,EAAa,YAAc,EAAE,EACxC,KAChCC,EACGC,sDACAA,4BACJ,QACF,CAAC,CAAC,SACFN,CACJ,8CAIE,CACCT,EAAE,QAAU,KAAO,GAAGA,EAAE,MAAM,IAAM,GACpCA,EAAE,SAAWA,EAAE,SAAW,UAC3B,EACE,OAAO,OAAO,EACd,KAAK,GAAG,CACX,4BAA4BA,EAAE,QAAUQ,IAAOR,EAAE,OAAO,GAAKS,CAAO,IAAIT,EAAE,OAASQ,MAASR,EAAE,MAAM,GAAKS,CAAO,4CAC/GT,EAAE,aACCQ,SAAY,KAAK,EAAE,OAAO,CAAC,4BAA4BQ,EAAahB,EAAE,YAAY,GAAK,EAAE,UAAUA,EAAE,YAAY,SACjHS,CACJ,IACCT,EAAE,aACCQ,SAAY,KAAK,EAAE,OAAO,CAAC,4BAA4BQ,EAAahB,EAAE,YAAY,GAAK,EAAE,UAAUA,EAAE,YAAY,SACjHS,CACJ,SAIAT,EAAE,UAAYO,EACXC,wBAA2BR,EAAE,QAAQ,OACrCS,CACJ,IAAIT,EAAE,OAASO,EAAWC,qBAAwBR,EAAE,KAAK,OAASS,CAAO,IAAIN,GAAgBI,EAAWC,uBAA0BL,CAAY,OAASM,CAAO,IAC7JT,EAAE,gBAAgB,SAAWO,EAC1BC,OAAUR,EAAE,eAAe,OAAO,OAClCS,CACJ,IACCH,EAAS,KAAO,EACbE,wDAA2D,KAAK,EAAE,6BAA8B,CAChG,MAAO,MAAM,KAAKF,CAAQ,EACxB,KAAK,CAACW,EAAGC,IAAMD,EAAIC,CAAC,EACpB,KAAK,IAAI,CACZ,CAAC,CAAC,IACDd,GAAmB,QAChBI,IAAO,KAAK,EAAE,wCAAyC,CACvD,OAAQJ,EAAkB,OAC1B,KAAMA,EAAkB,OACzB,CAAC,CAAC,GACDK,CACJ,SACCA,CACJ,IAAI,KAAK,YAAYT,EAAGM,CAAQ,CAAC,kBACpC,CAQQ,YAAYN,EAAaM,EAAuB,CACvD,IAAMa,EAAMnB,EAAE,eAAiB,CAAC,EAChC,GAAImB,EAAI,SAAW,EAAG,OAAOV,EAE7B,IAAMW,EAASd,EAAS,KAAO,EACzBe,EAAQD,EAASD,EAAI,OAAQ,GAAMb,EAAS,IAAI,EAAE,QAAQ,CAAC,EAAIa,EACrE,GAAIE,EAAM,SAAW,EAAG,OAAOZ,EAE/B,IAAMa,EAA4BD,EAAM,IAAK,IAAO,CACnD,MAAO,QAAQ,EAAE,QAAQ,GACzB,KAAM,EAAE,MAAQ,GAChB,MAAO,EAAE,QACNb,4BAA+B,EAAE,OAAO,OACxCC,CACJ,EAAE,EAEF,OAAO,KAAK,qBACXa,EACA,iBACAF,EAAS,iBAAmB,OAC7B,CACD,CAQQ,aAAapB,EAAuB,CAC3C,IAAMuB,EAASvB,EAAE,QAAU,GAC3B,MAAI,YAAY,KAAKuB,CAAM,EACnB,MAAM,KAAKA,EAASC,GAAOA,IAAM,IAAM,EAAI,CAAE,EAE9C,CAAC,CACT,CACD,EA/Ja9B,EACL,OAAS,CACf+B,EACAC,EACAC,EACAC,klEACD,EANYlC,EAANmC,EAAA,CADNC,GAAc,eAAe,GACjBpC",
|
|
6
6
|
"names": ["css", "html", "nothing", "svg", "customElement", "lookupKey", "s", "resolve", "table", "name", "lookupKey", "TRIGRAM_GLYPH", "trigramGlyph", "name", "resolve", "html", "nothing", "property", "state", "ifDefined", "LitElement", "resolveLang", "el", "inherited", "GLOBAL_KEY", "registry", "holder", "existing", "created", "interpolate", "template", "vars", "match", "key", "translate", "lang", "source", "catalogs", "registry", "tag", "catalog", "lookupKey", "onLocaleChange", "listener", "listeners", "registry", "LocaleController", "host", "onLocaleChange", "RoxyLocalizedElement", "LitElement", "source", "vars", "LocaleController", "translate", "resolveLang", "css", "baseStyles", "COLS", "ROWS", "isPlainObject", "value", "decode", "rebuilt", "out", "item", "next", "cols", "rows", "row", "col", "i", "key", "expandCompact", "KEY_REFUSED_MESSAGE", "keyIsRefused", "key", "dispatchKeyRefusal", "host", "opts", "KEY_REFUSED_MESSAGE", "DEFAULT_BASE_URL", "readApiError", "res", "body", "FetchController", "host", "req", "controller", "json", "err", "signal", "url", "k", "v", "headers", "keyIsRefused", "KEY_REFUSED_MESSAGE", "dispatchKeyRefusal", "buildRequest", "endpoint", "method", "values", "queryKeys", "rest", "path", "_match", "name", "inQuery", "query", "css", "html", "nothing", "css", "html", "chevron", "disclosureStyles", "readingDetailStyles", "css", "interpAccordionStyles", "renderInterpAccordion", "sections", "name", "heading", "shown", "s", "nothing", "html", "i", "chevron", "ROXY_DATA_CLASS", "isJsonScript", "el", "MarkupDataController", "host", "parsed", "inline", "child", "ROXY_DATA_CLASS", "text", "submitContextConverter", "value", "parsed", "RoxyDataElement", "RoxyLocalizedElement", "e", "detail", "buildRequest", "MarkupDataController", "FetchController", "baseStyles", "changed", "expanded", "expandCompact", "html", "names", "n", "nothing", "rules", "sections", "name", "heading", "renderInterpAccordion", "data", "body", "ifDefined", "raw", "values", "message", "banner", "__decorateClass", "property", "state", "RoxyHexagram", "RoxyDataElement", "d", "cast", "daily", "resolved", "h", "castLines", "changingLinePositions", "dailyMessage", "resultingHexagram", "lines", "changing", "readings", "html", "nothing", "l", "idx", "realIdx", "isChanging", "broken", "svg", "trigramGlyph", "a", "b", "all", "isCast", "shown", "sections", "binary", "c", "baseStyles", "disclosureStyles", "interpAccordionStyles", "css", "__decorateClass", "customElement"]
|
|
7
7
|
}
|
|
@@ -83,6 +83,19 @@ export declare class RoxyVastuMandala extends RoxyDataElement<VastuData> {
|
|
|
83
83
|
private renderFacts;
|
|
84
84
|
/** Every verse the drawing rests on, or the convention where no verse states the rule. */
|
|
85
85
|
private renderSources;
|
|
86
|
+
/**
|
|
87
|
+
* An area in the square of the plot unit: the number plus the standard symbol for the wire unit
|
|
88
|
+
* the response echoed, with the catalogue's own word for that unit as the `title`, one hover
|
|
89
|
+
* away and translated.
|
|
90
|
+
*
|
|
91
|
+
* @remarks
|
|
92
|
+
* The symbol is fixed on the WIRE value, not read out of the field-label catalogue: `ft²` and
|
|
93
|
+
* `m²` are what every practitioner writes whatever language the card is in, and hanging a
|
|
94
|
+
* superscript off a translator's word is not that convention. `conventions.unit` is absent on a
|
|
95
|
+
* payload from before the API started echoing it, and a default here would be a guess about
|
|
96
|
+
* which unit the reader actually sent, so the bare number prints on its own with no title.
|
|
97
|
+
*/
|
|
98
|
+
private areaLabel;
|
|
86
99
|
/** The name of one ring, falling back to the wire id for a class the API might add. */
|
|
87
100
|
private ringLabel;
|
|
88
101
|
/** How the stated effect reads, falling back to the wire value. */
|