schematex 0.3.0 → 0.3.2

package/dist/{chunk-SQKLKBBK.cjs → chunk-RODV6PC4.cjs}

@@ -1,6 +1,6 @@
 'use strict';
 
-var chunkXTATRNUN_cjs = require('./chunk-XTATRNUN.cjs');
+var chunkYTEEZV6J_cjs = require('./chunk-YTEEZV6J.cjs');
 
 // src/ai/registry.ts
 var DIAGRAM_REGISTRY = [
@@ -483,6 +483,25 @@ var EXAMPLES = [
     "dsl": 'genogram "BRCA1 Family"\n  I_1 [male, 1930, 1995, deceased]\n  I_2 [female, 1932, 1990, deceased, conditions: ovarian_cancer(full, #B388FF)]\n  I_1 -- I_2\n    II_1 [female, 1955, conditions: breast_cancer(full, #EC407A)]\n    II_2 [male, 1958]\n    II_3 [female, 1960]\n  II_1 -- II_4 [male, 1954]\n    III_1 [female, 1985, index, conditions: breast_cancer(full, #EC407A)]\n    III_2 [male, 1988]',
     "notes": "## Scenario\n\nA family history genogram for hereditary breast/ovarian cancer, documented at the initial genetic counseling intake before formal pedigree analysis. For standardized clinical pedigree notation (NSGC), use the Pedigree diagram type instead.\n\n## Annotation key\n\n- `conditions: ovarian_cancer(full)` / `conditions: breast_cancer(full)` \u2014 medical conditions filling the symbol; color is optional hex\n- `deceased` with birth and death years \u2014 marks individuals with a slash and date range\n- `index` \u2014 marks the proband who triggered the clinical referral\n\n## How to read\n\nThe maternal grandmother (I_2) had ovarian cancer and is deceased. Her daughter (II_1) developed breast cancer. The proband (III_1, index) is a third-generation female with breast cancer \u2014 the inheritance pattern spanning three generations justifies BRCA genetic testing."
   },
+  {
+    "slug": "genogram-foster-care",
+    "diagram": "genogram",
+    "title": "Foster care / child protection",
+    "description": "Foster-care genogram for a real LATAM child-protection case \u2014 biological parents (cohabitation ended), abuse, current foster placement (dotted secondary link), unknown-count siblings, and a maternal uncle as known-relative-with-unknown-ancestry.",
+    "standard": "McGoldrick 2020 + Bennett 2022 (adopted-out / dual-parent convention)",
+    "tags": [
+      "foster-care",
+      "dual-parent",
+      "abuse",
+      "sibling-of",
+      "unknown-siblings",
+      "latam"
+    ],
+    "complexity": 3,
+    "featured": true,
+    "dsl": 'genogram "Familia Isa\xEDas"\n  victor [male, label: "V\xEDctor Seguel"]\n  monica [female, label: "M\xF3nica Barrientos"]\n  victor ~/~ monica\n    ?\n    isaias [male, 2020, age: 6, label: "Isa\xEDas", index]\n  pablo_sr [male, label: "Don Pablo"]\n  priscila [female, label: "Do\xF1a Priscila"]\n  pablo_sr -- priscila\n    pablo_jr [male, label: "Pablo (jr)"]\n    alanis [female, label: "Alanis"]\n    isaias [foster]\n  tio_materno [male, label: "T\xEDo materno", sibling-of: monica]\n  victor -physical-abuse-> isaias\n  monica -physical-abuse-> isaias\n  tio_materno -nevermet- isaias',
+    "notes": '## Scenario\n\nA foster-care social worker in Chile is preparing the case file for Isa\xEDas, a 6-year-old boy removed from his biological parents (V\xEDctor and M\xF3nica) due to physical abuse from both. He currently lives with foster parents Don Pablo and Do\xF1a Priscila, who have two biological children of their own. The case file mentions Isa\xEDas has siblings whose names and ages are unknown, and a maternal uncle who is a potential reunification resource but currently has no contact.\n\nA judge or psychologist receiving this diagram must, at a glance, correctly conclude:\n\n1. Isa\xEDas is the **biological son** of V\xEDctor and M\xF3nica \u2014 solid parent-child line down from the bio couple.\n2. He **currently lives** with Don Pablo and Do\xF1a Priscila as a foster child \u2014 *secondary dotted link* from the foster couple, drawn without pulling Isa\xEDas away from his bio-parent position.\n3. He was **removed due to physical abuse** from both bio parents \u2014 directional red zigzag arrows.\n4. The **maternal uncle** is M\xF3nica\'s brother (`sibling-of: monica`) with **no current relationship** to Isa\xEDas \u2014 dashed bracket between M\xF3nica and T\xEDo + `nevermet` line.\n5. Isa\xEDas has **unknown-count siblings** still with the bio parents \u2014 single `?` diamond placeholder.\n6. **Isa\xEDas is the index person** \u2014 concentric outer border highlight.\n\n## Annotation key\n\n- `~/~` \u2014 cohabitation ended (never-married); standard for LATAM caseloads where bio parents lived together unmarried and the relationship has broken. Distinct from `-x-` divorce (no marriage) and `-/-` separation (still married).\n- Re-declaring `isaias [foster]` under the foster couple after declaring him under the bio couple \u2192 engine treats the second declaration as a **secondary "current caregiver" link** (dotted), preserving all attributes from the first declaration.\n- `?` on a child line \u2192 a single diamond with `?` glyph meaning "\u22651 siblings, count and identities unknown" (standard pedigree convention).\n- `[sibling-of: monica]` \u2192 places T\xEDo materno on M\xF3nica\'s generation with a dashed bracket between them, **without** synthesizing phantom maternal grandparents.\n- `-physical-abuse->` \u2192 directional red arrow; the `>` indicates the perpetrator (left side) and victim (right side).\n\n## Why this matters\n\nA genogram engine that quietly rendered Isa\xEDas as a third biological child of Don Pablo + Do\xF1a Priscila \u2014 or dropped his sex and label when the `[foster]` redeclaration overwrote the original \u2014 would invert the case story. This example exercises every fix from the 2026-04 foster-care brief: dual-parent rendering, same-id merge, sibling-of, cohabiting-ended, and the unknown-siblings placeholder.'
+  },
   {
     "slug": "genogram-medical-history",
     "diagram": "genogram",
@@ -940,7 +959,7 @@ var EXAMPLES = [
 var SYNTAX = {
   "genogram": {
     "title": "Genogram",
-    "content": '## 1. Your first genogram\n\nThe smallest clinically useful genogram: two parents, one child.\n\n```\ngenogram\n  alice [female, 1980]\n  bob [male, 1978]\n  alice -- bob "m. 2005"\n    carol [female, 2008]\n```\n\nFour rules cover 80% of usage:\n\n1. Start with the keyword `genogram`, optionally followed by a quoted title.\n2. Declare each person on their own line: `id [attributes]`. Attributes go in square brackets, comma-separated.\n3. Connect two people with a **couple operator** \u2014 `--` (marriage) here; see \xA74.1 for all six. A trailing quoted string is the relationship label.\n4. **Indent under the couple line** to add their children.\n\n> Comments must be on their own line, starting with `#`. Trailing inline comments (`bob [male, 1978] # ...`) are not supported and will break the parser \u2014 see \xA78.\n\n---\n\n## 2. Individuals\n\nAn individual line is `id [attr1, attr2, \u2026]`. Attributes are comma-separated, order-independent, all optional.\n\n**ID rules.** Must match `[a-zA-Z][a-zA-Z0-9_-]*`. IDs are case-insensitive internally but preserve their original casing as the display label (override with `label:"\u2026"`).\n\n**Attributes accepted by the parser today:**\n\n| Attribute | Values | Effect |\n|---|---|---|\n| Sex | `male`, `female`, `unknown`, `other` | Shape: square, circle, diamond, diamond |\n| Status | `deceased`, `stillborn`, `miscarriage`, `abortion` | Visual modifier (X-out, scaled shape, etc.) |\n| Birth year | 4-digit number, e.g. `1980` | First 4-digit token = birth year |\n| Death year | 4-digit number after birth, e.g. `1980, 2055` | Second 4-digit token = death year |\n| `index` | flag | Concentric shape = identified patient |\n| `age:N` | e.g. `age:42` | Age shown inside shape |\n| `death:YYYY` | e.g. `death:2020` | Explicit death year |\n| `label:"\u2026"` | e.g. `label:"Dr. Smith"` | Display label override |\n| `conditions:\u2026` | see \xA75 | Medical/psychological conditions |\n| `key:value` | any custom | Stored as metadata |\n\n```\ngenogram\n  grandma [female, 1920, 2002, deceased]\n  dad [male, 1950, age:74]\n  me [male, 1985, index]\n  daughter [female, 2012, label:"Em"]\n```\n\n---\n\n## 3. Shapes\n\n| Visual | Sex value | Meaning |\n|---|---|---|\n| \u2610 Square | `male` | Male |\n| \u25CB Circle | `female` | Female |\n| \u25C7 Diamond | `unknown`, `other`, *or* attribute omitted | Unknown / unspecified |\n\nStatus modifiers layer on top of the base shape:\n\n```\ngenogram\n  alive [male, 1960]\n  passed [male, 1930, 2010, deceased]\n  stillborn_child [unknown, stillborn]\n  lost [unknown, miscarriage]\n```\n\n---\n\n## 4. Connections\n\n### 4.1 Couple operators\n\nThe parser tries these in order. The first one that matches wins \u2014 so `-x-` beats `--`.\n\n| Operator | Type | Example | Meaning |\n|---|---|---|---|\n| `-x-` | divorced | `a -x- b` | Divorce |\n| `-/-` | separated | `a -/- b` | Separation |\n| `-o-` | engaged | `a -o- b` | Engagement |\n| `==` | consanguineous | `a == b` | Blood-related couple |\n| `--` | married | `a -- b` | Marriage |\n| `~` | cohabiting | `a ~ b` | Cohabiting / LTR |\n\nA trailing quoted string becomes the relationship label (`a -- b "m. 2005"`).\n\n### 4.2 Inline individual on the right side\n\nIf the right-hand person hasn\'t been declared yet, you can declare them in-place:\n\n```\ngenogram\n  ann [female, 1970]\n  ann -- ben [male, 1968] "m. 1995"\n    kim [female, 1997]\n```\n\n### 4.3 Children (indented under a couple)\n\nIndentation under a couple line = "these are the children of this couple." Any indent greater than the couple\'s indent works; by convention use 2 more spaces. Children are rendered in order of declaration (render also sorts by birth year when present).\n\n```\ngenogram\n  dad [male, 1950]\n  mom [female, 1952]\n  dad -- mom\n    eldest [male, 1975]\n    middle [female, 1978, adopted]\n    twin_a [male, 1985, twin-identical]\n    twin_b [male, 1985, twin-identical]\n```\n\n**Special child attributes:**\n\n| Attribute | Effect |\n|---|---|\n| `adopted` | Adoption line style |\n| `foster` | Foster relationship |\n| `twin-identical` | Grouped with other `twin-identical` children of the same couple |\n| `twin-fraternal` | Grouped with other `twin-fraternal` children |\n\n### 4.4 Emotional relationships\n\nSeparate line, parser pattern `A -TYPE- B` (non-directional) or `A -TYPE-> B` (directional).  An optional quoted label goes at the end. **Both individuals must already be declared** before the emotional line.\n\n```\nharry -cutoff- petunia           # non-directional\nharry -hostile- dudley "since 1991"\nuncle -abuse-> nephew             # directional (arrow)\n```\n\nAll 32 types the parser accepts today:\n\n| Category | Types |\n|---|---|\n| Positive / close | `harmony`, `close`, `bestfriends`, `love`, `inlove`, `friendship` |\n| Negative / hostile | `hostile`, `conflict`, `enmity`, `distant-hostile`, `cutoff` |\n| Ambivalent | `close-hostile`, `fused`, `fused-hostile` |\n| Distance | `distant`, `normal`, `nevermet` |\n| Abuse *(directional)* | `abuse`, `physical-abuse`, `emotional-abuse`, `sexual-abuse`, `neglect` |\n| Control *(directional)* | `manipulative`, `controlling`, `jealous` |\n| Special | `focused`, `focused-neg`, `distrust`, `admirer`, `limerence` |\n\n```\ngenogram\n  dad [male, 1950]\n  son [male, 1985]\n  daughter [female, 1988]\n  dad -close- daughter\n  dad -conflict- son\n  son -cutoff- dad "since 2010"\n```\n\n---\n\n## 5. Medical conditions\n\nSyntax: `conditions: name(fill) [+ name(fill, #color)]\u2026`\n\n```\nfather [male, 1945, conditions: heart(full, #E53935)]\nmother [female, 1948, conditions: diabetes(half-left) + anxiety(half-right, #26A69A)]\n```\n\n- **`name`** \u2014 any identifier you choose (displayed in legend/tooltip).\n- **`fill`** \u2014 required, controls which region of the shape is colored. See table below.\n- **`color`** \u2014 optional hex. Default depends on the renderer theme.\n- Multiple conditions are joined with `+`. Each needs its own `(fill)`.\n\n**Fill positions:**\n\n| `fill` value | Region |\n|---|---|\n| `full` | Entire shape |\n| `half-left` / `half-right` | Left / right half |\n| `half-top` / `half-bottom` | Top / bottom half |\n| `quad-tl` / `quad-tr` / `quad-bl` / `quad-br` | One quadrant |\n| `striped` | Diagonal stripe pattern (asymptomatic carrier) |\n| `dotted` | Dot pattern |\n\n```\ngenogram\n  dad [male, 1950, conditions: heart(full, #E53935)]\n  mom [female, 1952, conditions: diabetes(half-left) + depression(half-right, #5C6BC0)]\n  dad -- mom\n    son [male, 1980, conditions: carrier(striped)]\n```\n\n---\n\n## 6. Labels & comments\n\n- **Title:** `genogram "Smith Family"` \u2014 first line only.\n- **Person label override:** `alice [female, label:"Dr. Alice Smith"]`.\n- **Relationship label:** trailing quoted string on a couple or emotional line \u2014 `alice -- bob "m. 2005"`.\n- **Comments:** `#` at the start of a line (after leading whitespace). Inline comments are **not** supported.\n\n```\ngenogram "Smith Family"\n  # this line is a comment \u2014 fine\n  alice [female, 1980]   # \u2190 THIS trailing comment breaks the parser\n```\n\n---\n\n## 7. Reserved words & escaping\n\n**Reserved at line start:** `genogram` (header keyword).\n\n**Reserved operator tokens** inside a line \u2014 avoid using these sequences in IDs:\n`--`, `~`, `==`, `-x-`, `-/-`, `-o-`, and any `-<type>-` / `-<type>->` matching an emotional-relationship type.\n\n**Strings with spaces** must be double-quoted: titles, labels, `label:"\u2026"`. Single quotes and backticks are not recognized.\n\n---\n\n## 8. Common mistakes\n\nReal parser errors, what triggers them, and how to fix.\n\n| You wrote | Parser says | Fix |\n|---|---|---|\n| `alex [nonbinary, 1995]` | `Unknown property \'nonbinary\'` | Use `unknown` or `other` (nonbinary is \xA713 Roadmap) |\n| `alice [female, transgender]` | `Unknown property \'transgender\'` | Not yet parseable (\xA713 Roadmap) |\n| `dad -- mom`  \u2190 followed by `child [male, 2010]` at the **same indent** | Child parsed as a new top-level individual, not as their child | Indent the child line deeper than the couple line (2 spaces is enough) |\n| `A -- B` where `A` was never declared | `Unknown individual \'A\'` | Declare `A [sex, year]` on a line above |\n| `father -- mother "married"` on line 1 (no `genogram` header) | `Expected "genogram" header` | Start the file with `genogram` or `genogram "Title"` |\n| `conditions: diabetes + cancer` (no parens) | `Invalid condition format \'diabetes\'` | Add fill: `conditions: diabetes(half-left) + cancer(half-right)` |\n| `[triplet-identical]` | `Unknown property \'triplet-identical\'` | Triplets not yet parseable (\xA713 Roadmap) |\n| `dad -- mom # first marriage` | Trailing inline `#` comment is treated as part of the label / errors | Move the comment to its own line |\n\n---\n\n## 9. Grammar (EBNF)\n\n```text\ndocument       = header (blank | comment | individual | couple-block | emotional)*\n\nheader         = "genogram" ( WS quoted-string )? NEWLINE\nquoted-string  = \'"\' any-char-but-quote* \'"\'\n\nindividual     = INDENT id ( "[" attrs "]" )? NEWLINE\ncouple-block   = INDENT id WS coupleOp WS right-side ( WS quoted-string )? NEWLINE\n                   ( deeper-indent child )*\nchild          = INDENT id ( "[" attrs "]" )? NEWLINE\nright-side     = id ( "[" attrs "]" )?\n\nemotional      = INDENT id WS "-" type "-"  id ( WS quoted-string )? NEWLINE\n               | INDENT id WS "-" type "->" id ( WS quoted-string )? NEWLINE\n\ncoupleOp       = "-x-" | "-/-" | "-o-" | "==" | "--" | "~"\ntype           = "harmony" | "close" | "bestfriends" | "love" | "inlove"\n               | "friendship" | "hostile" | "conflict" | "enmity"\n               | "distant-hostile" | "cutoff" | "close-hostile" | "fused"\n               | "fused-hostile" | "distant" | "normal" | "nevermet"\n               | "abuse" | "physical-abuse" | "emotional-abuse"\n               | "sexual-abuse" | "neglect" | "manipulative" | "controlling"\n               | "jealous" | "focused" | "focused-neg" | "distrust"\n               | "admirer" | "limerence"\n\nid             = [a-zA-Z] [a-zA-Z0-9_-]*\nattrs          = attr ("," attr)*\nattr           = "male" | "female" | "unknown" | "other"\n               | "deceased" | "stillborn" | "miscarriage" | "abortion"\n               | "adopted" | "foster" | "twin-identical" | "twin-fraternal"\n               | "index"\n               | digit digit digit digit                         // year\n               | "age" ":" digits\n               | "death" ":" digit digit digit digit\n               | "label" ":" quoted-string\n               | "conditions" ":" condition ("+" condition)*\n               | key ":" value                                    // custom\ncondition      = name "(" fill ("," "#" hex)? ")"\nfill           = "full" | "half-left" | "half-right" | "half-top" | "half-bottom"\n               | "quad-tl" | "quad-tr" | "quad-bl" | "quad-br"\n               | "striped" | "dotted"\n\ncomment        = INDENT "#" any NEWLINE\n```\n\nAuthoritative source: `src/diagrams/genogram/parser.ts`. If this diverges from the parser, the parser wins \u2014 please open an issue.\n\n---'
+    "content": '## 1. Your first genogram\n\nThe smallest clinically useful genogram: two parents, one child.\n\n```\ngenogram\n  alice [female, 1980]\n  bob [male, 1978]\n  alice -- bob "m. 2005"\n    carol [female, 2008]\n```\n\nFour rules cover 80% of usage:\n\n1. Start with the keyword `genogram`, optionally followed by a quoted title.\n2. Declare each person on their own line: `id [attributes]`. Attributes go in square brackets, comma-separated.\n3. Connect two people with a **couple operator** \u2014 `--` (marriage) here; see \xA74.1 for all six. A trailing quoted string is the relationship label.\n4. **Indent under the couple line** to add their children.\n\n> Comments must be on their own line, starting with `#`. Trailing inline comments (`bob [male, 1978] # ...`) are not supported and will break the parser \u2014 see \xA78.\n\n---\n\n## 2. Individuals\n\nAn individual line is `id [attr1, attr2, \u2026]`. Attributes are comma-separated, order-independent, all optional.\n\n**ID rules.** Must match `[a-zA-Z][a-zA-Z0-9_-]*`. IDs are case-insensitive internally but preserve their original casing as the display label (override with `label:"\u2026"`).\n\n**Attributes accepted by the parser today:**\n\n| Attribute | Values | Effect |\n|---|---|---|\n| Sex | `male`, `female`, `unknown`, `other` | Shape: square, circle, diamond, diamond |\n| Status | `deceased`, `stillborn`, `miscarriage`, `abortion` | Visual modifier (X-out, scaled shape, etc.) |\n| Birth year | 4-digit number, e.g. `1980` | First 4-digit token = birth year |\n| Death year | 4-digit number after birth, e.g. `1980, 2055` | Second 4-digit token = death year |\n| `index` | flag | Concentric shape = identified patient |\n| `unknown-siblings` | flag | Diamond with `?` \u2014 placeholder for \u22651 siblings of unknown count |\n| `age:N` | e.g. `age:42` | Age shown inside shape |\n| `death:YYYY` | e.g. `death:2020` | Explicit death year |\n| `label:"\u2026"` | e.g. `label:"Dr. Smith"` | Display label override |\n| `sibling-of:<id>` | e.g. `sibling-of:monica` | Pins same generation as the referenced sibling, draws a dashed bracket \u2014 for known relatives with unknown ancestry. |\n| `conditions:\u2026` | see \xA75 | Medical/psychological conditions |\n| `key:value` | any custom | Stored as metadata |\n\n```\ngenogram\n  grandma [female, 1920, 2002, deceased]\n  dad [male, 1950, age:74]\n  me [male, 1985, index]\n  daughter [female, 2012, label:"Em"]\n```\n\n---\n\n## 3. Shapes\n\n| Visual | Sex value | Meaning |\n|---|---|---|\n| \u2610 Square | `male` | Male |\n| \u25CB Circle | `female` | Female |\n| \u25C7 Diamond | `unknown`, `other`, *or* attribute omitted | Unknown / unspecified |\n\nStatus modifiers layer on top of the base shape:\n\n```\ngenogram\n  alive [male, 1960]\n  passed [male, 1930, 2010, deceased]\n  stillborn_child [unknown, stillborn]\n  lost [unknown, miscarriage]\n```\n\n---\n\n## 4. Connections\n\n### 4.1 Couple operators\n\nThe parser tries these in order. The first one that matches wins \u2014 so `-x-` beats `--`.\n\n| Operator | Type | Example | Meaning |\n|---|---|---|---|\n| `-x-` | divorced | `a -x- b` | Divorce |\n| `-/-` | separated | `a -/- b` | Separation (married) |\n| `-//` | separated | `a -// b` | Separation (alias for `-/-`) |\n| `-o-` | engaged | `a -o- b` | Engagement |\n| `==` | consanguineous | `a == b` | Blood-related couple |\n| `--` | married | `a -- b` | Marriage |\n| `~` | cohabiting | `a ~ b` | Cohabiting / LTR (current) |\n| `~/~` | cohabiting-ended | `a ~/~ b` | Cohabitation has ended (never-married). Common in LATAM child-protection caseloads where biological parents lived together unmarried and the relationship has since broken \u2014 distinct from `-x-` divorce (no marriage) and `-/-` separation (still married). |\n\nA trailing quoted string becomes the relationship label (`a -- b "m. 2005"`).\n\n### 4.2 Inline individual on the right side\n\nIf the right-hand person hasn\'t been declared yet, you can declare them in-place:\n\n```\ngenogram\n  ann [female, 1970]\n  ann -- ben [male, 1968] "m. 1995"\n    kim [female, 1997]\n```\n\n### 4.3 Children (indented under a couple)\n\nIndentation under a couple line = "these are the children of this couple." Any indent greater than the couple\'s indent works; by convention use 2 more spaces. Children are rendered in order of declaration (render also sorts by birth year when present).\n\n```\ngenogram\n  dad [male, 1950]\n  mom [female, 1952]\n  dad -- mom\n    eldest [male, 1975]\n    middle [female, 1978, adopted]\n    twin_a [male, 1985, twin-identical]\n    twin_b [male, 1985, twin-identical]\n```\n\n**Special child attributes:**\n\n| Attribute | Effect |\n|---|---|\n| `adopted` | Adoption line style |\n| `foster` | Foster relationship |\n| `guardian` | Guardianship by a non-parent relative (e.g. grandparent custody). Same primitive as `foster` \u2014 drawn as a secondary "current caregiver" link when biological parents are also declared. |\n| `twin-identical` | Grouped with other `twin-identical` children of the same couple |\n| `twin-fraternal` | Grouped with other `twin-fraternal` children |\n| `unknown-siblings` | Single diamond with `?` glyph \u2014 "\u22651 siblings, count and identities unknown" (pedigree convention). |\n\n### 4.3.1 Dual-parent families (foster, adoption, guardianship)\n\nChildren placed with a non-biological caregiver while biological parents are still part of the case can be declared under both couples. **Declare the child with full attributes the first time** (under the biological couple), then **redeclare with just `[foster]` / `[adopted]` / `[guardian]`** under the current caregiver. The first declaration wins layout; the second is drawn as a secondary dotted "current caregiver" link that does not pull the child away from their biological position.\n\n```\ngenogram "Foster placement"\n  bp1 [male, label: "Bio dad"]\n  bp2 [female, label: "Bio mom"]\n  bp1 ~/~ bp2\n    child [male, 2018, index]\n  fp1 [male, label: "Foster dad"]\n  fp2 [female, label: "Foster mom"]\n  fp1 -- fp2\n    own [male, 2010]\n    child [foster]\n```\n\nThe same primitive serves adoption (closed/open), foster placement, and guardianship by a relative \u2014 only the keyword differs. Re-declaration **merges** non-conflicting attributes (sex, birth year, label, `index` marker) into the original; declaring a conflicting `male` vs `female` raises a parse error rather than silently overwriting.\n\n### 4.3.2 Unknown-count siblings\n\nWhen a case file mentions "the child has siblings" without naming them, use either the `?` shorthand on its own line, or `[unknown-siblings]` on a regular id. Both render as a single diamond with a "?" glyph \u2014 the standard pedigree marker for "one or more siblings, identities unknown."\n\n```\ngenogram\n  dad [male]\n  mom [female]\n  dad -- mom\n    ?\n    known_kid [male, 2018]\n```\n\n### 4.3.3 Sibling-of (known relative, unknown ancestry)\n\nTo express "X is a sibling of Y" without inventing parents, use the `sibling-of: <id>` property. The renderer pins X to Y\'s generation and draws a dashed bracket above the two \u2014 the standard pedigree convention for a known relative whose ancestry is not part of the case.\n\n```\ngenogram\n  monica [female, 1990]\n  uncle [male, label: "T\xEDo materno", sibling-of: monica]\n```\n\n### 4.4 Emotional relationships\n\nSeparate line, parser pattern `A -TYPE- B` (non-directional) or `A -TYPE-> B` (directional).  An optional quoted label goes at the end. **Both individuals must already be declared** before the emotional line.\n\n```\nharry -cutoff- petunia           # non-directional\nharry -hostile- dudley "since 1991"\nuncle -abuse-> nephew             # directional (arrow)\n```\n\nAll 32 types the parser accepts today:\n\n| Category | Types |\n|---|---|\n| Positive / close | `harmony`, `close`, `bestfriends`, `love`, `inlove`, `friendship` |\n| Negative / hostile | `hostile`, `conflict`, `enmity`, `distant-hostile`, `cutoff` |\n| Ambivalent | `close-hostile`, `fused`, `fused-hostile` |\n| Distance | `distant`, `normal`, `nevermet` |\n| Abuse *(directional)* | `abuse`, `physical-abuse`, `emotional-abuse`, `sexual-abuse`, `neglect` |\n| Control *(directional)* | `manipulative`, `controlling`, `jealous` |\n| Special | `focused`, `focused-neg`, `distrust`, `admirer`, `limerence` |\n\n```\ngenogram\n  dad [male, 1950]\n  son [male, 1985]\n  daughter [female, 1988]\n  dad -close- daughter\n  dad -conflict- son\n  son -cutoff- dad "since 2010"\n```\n\n---\n\n## 5. Medical conditions\n\nSyntax: `conditions: name(fill) [+ name(fill, #color)]\u2026`\n\n```\nfather [male, 1945, conditions: heart(full, #E53935)]\nmother [female, 1948, conditions: diabetes(half-left) + anxiety(half-right, #26A69A)]\n```\n\n- **`name`** \u2014 any identifier you choose (displayed in legend/tooltip).\n- **`fill`** \u2014 required, controls which region of the shape is colored. See table below.\n- **`color`** \u2014 optional hex. Default depends on the renderer theme.\n- Multiple conditions are joined with `+`. Each needs its own `(fill)`.\n\n**Fill positions:**\n\n| `fill` value | Region |\n|---|---|\n| `full` | Entire shape |\n| `half-left` / `half-right` | Left / right half |\n| `half-top` / `half-bottom` | Top / bottom half |\n| `quad-tl` / `quad-tr` / `quad-bl` / `quad-br` | One quadrant |\n| `striped` | Diagonal stripe pattern (asymptomatic carrier) |\n| `dotted` | Dot pattern |\n\n```\ngenogram\n  dad [male, 1950, conditions: heart(full, #E53935)]\n  mom [female, 1952, conditions: diabetes(half-left) + depression(half-right, #5C6BC0)]\n  dad -- mom\n    son [male, 1980, conditions: carrier(striped)]\n```\n\n---\n\n## 6. Labels & comments\n\n- **Title:** `genogram "Smith Family"` \u2014 first line only.\n- **Person label override:** `alice [female, label:"Dr. Alice Smith"]`.\n- **Relationship label:** trailing quoted string on a couple or emotional line \u2014 `alice -- bob "m. 2005"`.\n- **Comments:** `#` at the start of a line (after leading whitespace). Inline comments are **not** supported.\n\n```\ngenogram "Smith Family"\n  # this line is a comment \u2014 fine\n  alice [female, 1980]   # \u2190 THIS trailing comment breaks the parser\n```\n\n---\n\n## 7. Reserved words & escaping\n\n**Reserved at line start:** `genogram` (header keyword).\n\n**Reserved operator tokens** inside a line \u2014 avoid using these sequences in IDs:\n`--`, `~`, `~/~`, `==`, `-x-`, `-/-`, `-//`, `-o-`, and any `-<type>-` / `-<type>->` matching an emotional-relationship type.\n\n**Reserved id `?`** \u2014 bare `?` on a child line auto-generates a synthetic placeholder with the `unknown-siblings` marker. Do not use `?` as a real id.\n\n**Strings with spaces** must be double-quoted: titles, labels, `label:"\u2026"`. Single quotes and backticks are not recognized.\n\n---\n\n## 8. Common mistakes\n\nReal parser errors, what triggers them, and how to fix.\n\n| You wrote | Parser says | Fix |\n|---|---|---|\n| `alex [nonbinary, 1995]` | `Unknown property \'nonbinary\'` | Use `unknown` or `other` (nonbinary is \xA713 Roadmap) |\n| `alice [female, transgender]` | `Unknown property \'transgender\'` | Not yet parseable (\xA713 Roadmap) |\n| `dad -- mom`  \u2190 followed by `child [male, 2010]` at the **same indent** | Child parsed as a new top-level individual, not as their child | Indent the child line deeper than the couple line (2 spaces is enough) |\n| `A -- B` where `A` was never declared | `Unknown individual \'A\'` | Declare `A [sex, year]` on a line above |\n| `father -- mother "married"` on line 1 (no `genogram` header) | `Expected "genogram" header` | Start the file with `genogram` or `genogram "Title"` |\n| `conditions: diabetes + cancer` (no parens) | `Invalid condition format \'diabetes\'` | Add fill: `conditions: diabetes(half-left) + cancer(half-right)` |\n| `[triplet-identical]` | `Unknown property \'triplet-identical\'` | Triplets not yet parseable (\xA713 Roadmap) |\n| `dad -- mom # first marriage` | Trailing inline `#` comment is treated as part of the label / errors | Move the comment to its own line |\n| Same id declared twice with different sex (`x [male]` then `x [female]`) | `Conflicting sex for \'x\': previously \'male\', now \'female\'` | Pick one or rename one of the ids |\n| `child [foster]` redeclared but biological parents never declared | `child` becomes the foster couple\'s regular child (no secondary link drawn) | This is intentional \u2014 secondary links require an existing primary parent-child rel from a prior declaration |\n\n---\n\n## 9. Grammar (EBNF)\n\n```text\ndocument       = header (blank | comment | individual | couple-block | emotional)*\n\nheader         = "genogram" ( WS quoted-string )? NEWLINE\nquoted-string  = \'"\' any-char-but-quote* \'"\'\n\nindividual     = INDENT id ( "[" attrs "]" )? NEWLINE\ncouple-block   = INDENT id WS coupleOp WS right-side ( WS quoted-string )? NEWLINE\n                   ( deeper-indent child )*\nchild          = INDENT id ( "[" attrs "]" )? NEWLINE\n               | INDENT "?" NEWLINE                              // unknown-count sibling shorthand\nright-side     = id ( "[" attrs "]" )?\n\nemotional      = INDENT id WS "-" type "-"  id ( WS quoted-string )? NEWLINE\n               | INDENT id WS "-" type "->" id ( WS quoted-string )? NEWLINE\n\ncoupleOp       = "~/~" | "-//" | "-x-" | "-/-" | "-o-" | "==" | "--" | "~"\ntype           = "harmony" | "close" | "bestfriends" | "love" | "inlove"\n               | "friendship" | "hostile" | "conflict" | "enmity"\n               | "distant-hostile" | "cutoff" | "close-hostile" | "fused"\n               | "fused-hostile" | "distant" | "normal" | "nevermet"\n               | "abuse" | "physical-abuse" | "emotional-abuse"\n               | "sexual-abuse" | "neglect" | "manipulative" | "controlling"\n               | "jealous" | "focused" | "focused-neg" | "distrust"\n               | "admirer" | "limerence"\n\nid             = [a-zA-Z] [a-zA-Z0-9_-]*\nattrs          = attr ("," attr)*\nattr           = "male" | "female" | "unknown" | "other"\n               | "deceased" | "stillborn" | "miscarriage" | "abortion"\n               | "adopted" | "foster" | "guardian"\n               | "twin-identical" | "twin-fraternal"\n               | "index" | "unknown-siblings"\n               | digit digit digit digit                         // year\n               | "age" ":" digits\n               | "death" ":" digit digit digit digit\n               | "label" ":" quoted-string\n               | "sibling-of" ":" id\n               | "conditions" ":" condition ("+" condition)*\n               | key ":" value                                    // custom\ncondition      = name "(" fill ("," "#" hex)? ")"\nfill           = "full" | "half-left" | "half-right" | "half-top" | "half-bottom"\n               | "quad-tl" | "quad-tr" | "quad-bl" | "quad-br"\n               | "striped" | "dotted"\n\ncomment        = INDENT "#" any NEWLINE\n```\n\nAuthoritative source: `src/diagrams/genogram/parser.ts`. If this diverges from the parser, the parser wins \u2014 please open an issue.\n\n---'
   },
   "ecomap": {
     "title": "Ecomap",
@@ -1104,7 +1123,7 @@ function getExamples(type, opts = {}) {
 function validateDsl(type, dsl) {
   const config = type ? { type } : void 0;
   try {
-    chunkXTATRNUN_cjs.parse(dsl, config);
+    chunkYTEEZV6J_cjs.parse(dsl, config);
     return { ok: true, type: type ?? resolveTypeFromText(dsl) };
   } catch (err) {
     return {
@@ -1120,7 +1139,7 @@ function renderDsl(type, dsl, options = {}) {
     ...type ? { type } : {}
   };
   try {
-    const svg = chunkXTATRNUN_cjs.render(dsl, config);
+    const svg = chunkYTEEZV6J_cjs.render(dsl, config);
     return { ok: true, type: type ?? resolveTypeFromText(dsl), svg };
   } catch (err) {
     return {
@@ -1144,5 +1163,5 @@ exports.getSyntax = getSyntax;
 exports.listDiagrams = listDiagrams;
 exports.renderDsl = renderDsl;
 exports.validateDsl = validateDsl;
-//# sourceMappingURL=chunk-SQKLKBBK.cjs.map
-//# sourceMappingURL=chunk-SQKLKBBK.cjs.map
+//# sourceMappingURL=chunk-RODV6PC4.cjs.map
+//# sourceMappingURL=chunk-RODV6PC4.cjs.map