jui-tools-mcp-server 2.5.0 → 2.6.0

package/data/attribute_definitions.json

@@ -101,8 +101,7 @@
         "binding"
       ],
       "description": "Width weight for flexible layouts (binding supported)",
-      "platform": "swift",
-      "mode": "uikit"
+      "platform": "swift"
     },
     "heightWeight": {
       "type": [
@@ -110,8 +109,10 @@
         "binding"
       ],
       "description": "Height weight for flexible layouts (binding supported)",
-      "platform": "swift",
-      "mode": "uikit"
+      "platform": [
+        "swift",
+        "kotlin"
+      ]
     },
     "maxWidthWeight": {
       "type": [
@@ -180,7 +181,7 @@
         "string",
         "binding"
       ],
-      "description": "Background color - hex string (#RRGGBB or #RRGGBBAA) or color name from colors.json (can be data binding)"
+      "description": "Background color - hex string (#RRGGBB or #RRGGBBAA) or color name from colors.json (can be data binding). `backgroundColor` folds here: the genuine layout reads of that spelling all chain with `background` (kjui blurview_component.rb:42 `background || backgroundColor`, kjui segment_component.rb:55 `backgroundColor || background`, rjui blur_converter.rb:58 and circle_view_converter.rb:55). Note the two kjui sites read the pair in OPPOSITE order, so a layout setting both drew two different colours until the normalizer began folding them — the same defect shape as CheckBox's accent chain (plan 51-E). When a `gradient` is also declared on the same view, the GRADIENT wins and this is the fallback fill — not a layer underneath it. Full ruling in attribute_semantics.json -> backgroundFill; do not restate it in toolchain comments."
     },
     "tapBackground": {
       "type": [
@@ -231,7 +232,7 @@
         "string",
         "binding"
       ],
-      "description": "Border color - hex string or color name from colors.json (binding supported)"
+      "description": "Border color - hex string or color name from colors.json (binding supported). There is deliberately NO default: a border is drawn only when borderWidth AND borderColor are both declared, and neither half summons one on its own (2026-08-03 user ruling, recorded in attribute_semantics.json#semantics.border and gated by `jui conformance gate --cross-effect` against the five `observable` entries there). Declaring a default here would make borderWidth alone draw, which is the direction d2c8628 took once and the ruling superseded."
     },
     "borderStyle": {
       "type": "string",
@@ -243,15 +244,6 @@
       "default": "solid",
       "description": "Border line style - solid (default), dashed, or dotted"
     },
-    "alpha": {
-      "type": [
-        "number",
-        "binding"
-      ],
-      "min": 0,
-      "max": 1,
-      "description": "Opacity (0-1) - can be data binding"
-    },
     "opacity": {
       "type": [
         "number",
@@ -259,7 +251,7 @@
       ],
       "min": 0,
       "max": 1,
-      "description": "Opacity (0-1), alias for alpha - can be data binding",
+      "description": "Opacity (0-1) - can be data binding. `alpha` is an accepted alias spelling.",
       "aliases": [
         "alpha"
       ]
@@ -671,7 +663,8 @@
         "boolean",
         "binding"
       ],
-      "description": "Whether to clip content to bounds (binding supported)"
+      "description": "Whether to clip content to bounds (binding supported). Defaults to FALSE: content is not clipped unless the layout asks. A clipping default would silently destroy a child's `shadow` and would make `clipToBounds: true` inert on the platform that already clips. Full ruling in attribute_semantics.json -> clipToBounds; do not restate it in toolchain comments.",
+      "default": false
     },
     "onclick": {
       "type": [
@@ -734,7 +727,7 @@
     },
     "variables": {
       "type": "object",
-      "description": "Variables for include",
+      "description": "Variables for include The SwiftUI codegen DOES read this (base_view_converter.rb), but only to echo it back as a `// variables: ...` comment — nothing reaches the rendered view, so `mode: uikit` stands. Recorded because the 2026-08-05 mode audit flags the read and the next auditor would otherwise re-derive it: the read is real, the effect is not.",
       "platform": "swift",
       "mode": "uikit"
     },
@@ -778,7 +771,7 @@
     },
     "binding_id": {
       "type": "string",
-      "description": "Binding ID",
+      "description": "Binding ID The SwiftUI codegen DOES read this (base_view_converter.rb), but only to echo it back as a `// binding_id: ...` comment — nothing reaches the rendered view, so `mode: uikit` stands. Recorded because the 2026-08-05 mode audit flags the read and the next auditor would otherwise re-derive it: the read is real, the effect is not.",
       "platform": "swift",
       "mode": "uikit"
     },
@@ -836,24 +829,46 @@
     },
     "events": {
       "type": "object",
-      "description": "Complex event handlers",
-      "platform": "swift",
-      "mode": "uikit"
+      "description": "Complex event handlers"
     },
     "effectStyle": {
-      "type": "string",
-      "description": "Visual effect style",
-      "platform": "swift",
-      "mode": "uikit"
-    },
+        "type": "string",
+        "enum": [
+          "Light",
+          "Dark",
+          "ExtraLight",
+          "Regular",
+          "Prominent",
+          "UltraThin",
+          "Thin",
+          "Thick",
+          "Chrome",
+          "systemMaterial",
+          "systemUltraThinMaterial",
+          "systemThinMaterial",
+          "systemThickMaterial",
+          "systemChromeMaterial"
+        ],
+        "valueAliases": {
+          "systemMaterial": "Regular",
+          "systemUltraThinMaterial": "UltraThin",
+          "systemThinMaterial": "Thin",
+          "systemThickMaterial": "Thick",
+          "systemChromeMaterial": "Chrome"
+        },
+        "default": "Regular",
+        "description": "Visual effect (blur) style. Measured across the three converters 2026-08-05: the UIKit trio Light/Dark/ExtraLight is what all three map (sjui blur_converter.rb:71, kjui blurview_component.rb:38, rjui blur_converter.rb:98), and web additionally maps the SwiftUI material names. Every converter downcases before matching, so the casing here is presentational. `Regular` is the fallback all three already use for an unrecognised or absent value, hence the declared default. Enumerated because it was declared as a bare string while Blur.effectStyle — the same concept on the component that owns it — carried the enum: the split let the common spelling reach the render stage unvalidated, which is what the codegen-effect gate reported once the mode audit put these fixtures back in scope. Declared on `common`, so it applies on all three platforms and not only on Blur; the ios material/tint table is pinned in attribute_semantics.json -> effectStyle, which is also where the system* valueAliases and the tint layer order are ruled."
+      },
     "tag": {
       "type": [
         "number",
         "binding"
       ],
       "description": "View tag for identification (binding supported)",
-      "platform": "swift",
-      "mode": "uikit"
+      "platform": [
+        "swift",
+        "react"
+      ]
     },
     "userInteractionEnabled": {
       "type": [
@@ -904,8 +919,7 @@
     "touchDisabledState": {
       "type": "string",
       "description": "Touch disable mode",
-      "platform": "swift",
-      "mode": "uikit"
+      "platform": "swift"
     },
     "touchEnabledViewIds": {
       "type": "array",
@@ -919,7 +933,7 @@
     },
     "bindingScript": {
       "type": "string",
-      "description": "Custom Swift binding code",
+      "description": "Custom Swift binding code The SwiftUI codegen DOES read this (base_view_converter.rb), but only to echo it back as a `// bindingScript: ...` comment — nothing reaches the rendered view, so `mode: uikit` stands. Recorded because the 2026-08-05 mode audit flags the read and the next auditor would otherwise re-derive it: the read is real, the effect is not.",
       "platform": "swift",
       "mode": "uikit"
     },
@@ -937,7 +951,7 @@
         "centerHorizontal",
         "center"
       ],
-      "description": "Content gravity/alignment"
+      "description": "Content gravity/alignment. A single value names ONE axis; the axis it does not name falls to the container default (top vertically, start horizontally), so in LTR `left` and `top` both resolve to (start, top) and render identically. Use the array form to name both axes. Full ruling in attribute_semantics.json -> gravityDefaults; do not restate it in toolchain comments."
     },
     "onAppear": {
       "type": "string",
@@ -1097,6 +1111,20 @@
       "description": "Debug: original height string before parsing. Dynamic-only; not emitted to static code.",
       "platform": "swift",
       "mode": "dynamic-only"
+    },
+    "offsetX": {
+      "type": [
+        "number",
+        "binding"
+      ],
+      "description": "Horizontal offset applied after layout, in pt / dp / px. Measurement and sibling placement are unchanged — the layout is computed first and the offset moves only this view. Its INTERACTIVE region moves with it: an offset control is tappable where it is drawn, which is what rules out a draw-only translation. Absolute, not RTL-mirroring, like leftMargin/rightMargin rather than startMargin/endMargin. Pairs with offsetY; either one alone implies 0 for the other. Full ruling (including the android primitive) in attribute_semantics.json -> offset."
+    },
+    "offsetY": {
+      "type": [
+        "number",
+        "binding"
+      ],
+      "description": "Vertical offset applied after layout, in pt / dp / px. Measurement and sibling placement are unchanged — the layout is computed first and the offset moves only this view. Its INTERACTIVE region moves with it: an offset control is tappable where it is drawn, which is what rules out a draw-only translation. Absolute, not RTL-mirroring, like leftMargin/rightMargin rather than startMargin/endMargin. Pairs with offsetX; either one alone implies 0 for the other. Full ruling (including the android primitive) in attribute_semantics.json -> offset."
     }
   },
   "Label": {
@@ -1221,9 +1249,7 @@
         "array",
         "string"
       ],
-      "description": "Edge insets as array or pipe-separated string",
-      "deprecated": "kotlin",
-      "deprecation_note": "Compose Text has no edgeInset; use padding* instead."
+      "description": "Edge insets as array or pipe-separated string. Applied on every platform including Compose, where it maps to .padding() (kjui text_component.rb / DynamicTextComponent.kt) - the former \"Compose Text has no edgeInset\" deprecation was contradicted by that implementation and was retracted 2026-08-05."
     },
     "underline": {
       "type": [
@@ -1231,7 +1257,7 @@
         "object",
         "array"
       ],
-      "description": "Underline styling (boolean for simple, object for styled)",
+      "description": "Underline styling: boolean for a plain line, object to style it. The object face must never draw LESS than `true` does — a platform that cannot honour lineStyle or color still draws the plain Single line in the text colour. `lineStyle: \"None\"` is the one object value that draws nothing, exactly like `false`. Full ruling in attribute_semantics.json -> textDecoration; do not restate it in toolchain comments.",
       "properties": {
         "lineStyle": {
           "type": "string",
@@ -1258,7 +1284,7 @@
         "boolean",
         "object"
       ],
-      "description": "Strikethrough styling (boolean for simple, object for styled)",
+      "description": "Strikethrough styling: boolean for a plain line, object to style it. Same contract as Label.underline, minus lineOffset, which strikethrough does not declare and must not invent. `lineStyle: \"None\"` draws nothing, exactly like `false`. Full ruling in attribute_semantics.json -> textDecoration; do not restate it in toolchain comments.",
       "properties": {
         "lineStyle": {
           "type": "string",
@@ -1278,7 +1304,7 @@
     },
     "autoShrink": {
       "type": "boolean",
-      "description": "Enable auto-shrink"
+      "description": "Enable auto-shrink. Active only on a bounded axis (explicit size, matchParent, or a max bound) — a no-op under wrapContent, which grows to the content and leaves nothing to shrink into. Full ruling in attribute_semantics.json -> autoShrink."
     },
     "minimumScaleFactor": {
       "type": [
@@ -1442,7 +1468,7 @@
     },
     "hintAttributes": {
       "type": "object",
-      "description": "Hint text styling attributes",
+      "description": "Hint text styling attributes. The nested keys win over the flat spellings (hintColor / hintFont / hintFontSize): a bag scoped to the hint is the more specific statement. That is the ordinary cascade rule and what all four readers do (rjui label_converter, kjui text_component, sjui Label and SelectBox) - it was unwritten until 2026-08-05, when the one converter that had it backwards was found by contradicting its own comment.",
       "properties": {
         "font": {
           "type": "string",
@@ -1468,6 +1494,13 @@
         "number"
       ],
       "description": "Font weight (e.g., 'bold', 'semibold', '500', 600)"
+    },
+    "disabledFontColor": {
+      "type": [
+        "string",
+        "binding"
+      ],
+      "description": "Font color when disabled - hex string or color name from colors.json (binding supported). Declared from the implementation, which already read it: sjui label_converter.rb:179-180 (plan 51-E)."
     }
   },
   "TextField": {
@@ -1476,8 +1509,11 @@
         "string",
         "binding"
       ],
-      "description": "Text content (binding for two-way)",
-      "binding_direction": "two-way"
+      "description": "Text content (binding for two-way). `value` folds here (sjui textfield_converter.rb:527 reads `text || value || bind`).",
+      "binding_direction": "two-way",
+      "aliases": [
+        "value"
+      ]
     },
     "hint": {
       "type": "string",
@@ -1492,27 +1528,23 @@
         "string",
         "binding"
       ],
-      "description": "Placeholder color - hex string or color name from colors.json (binding supported)",
-      "deprecated": "swiftui",
-      "deprecation_note": "SwiftUI TextField placeholder cannot be color-styled."
+      "description": "Placeholder color - hex string or color name from colors.json (binding supported). `placeholderColor` is an accepted alias spelling.",
+      "aliases": [
+        "placeholderColor"
+      ]
     },
     "hintFont": {
       "type": "string",
-      "description": "Placeholder font",
-      "deprecated": "swiftui",
-      "deprecation_note": "SwiftUI TextField placeholder cannot be custom-font-styled."
+      "description": "Placeholder font"
     },
     "hintFontSize": {
       "type": "number",
-      "description": "Placeholder font size",
-      "deprecated": "swiftui",
-      "deprecation_note": "SwiftUI TextField placeholder cannot be custom-size-styled."
+      "description": "Placeholder font size"
     },
     "hintAttributes": {
       "type": "object",
-      "description": "Hint text attributes (font, color, etc.)",
-      "platform": "swift",
-      "mode": "uikit"
+      "description": "Hint text attributes (font, fontSize, fontColor). The nested keys win over the flat spellings (hintColor / hintFont / hintFontSize): a bag scoped to the hint is the more specific statement. That is the ordinary cascade rule and what all four readers do (rjui label_converter, kjui text_component, sjui Label and SelectBox) - it was unwritten until 2026-08-05, when the one converter that had it backwards was found by contradicting its own comment.",
+      "platform": "swift"
     },
     "font": {
       "type": [
@@ -1577,7 +1609,22 @@
     },
     "inputType": {
       "type": "string",
-      "description": "Input type for Android (Android-only; `input` is the cross-platform attribute)",
+      "enum": [
+        "text",
+        "number",
+        "numberDecimal",
+        "phone",
+        "email",
+        "password",
+        "multiline",
+        "textEmailAddress",
+        "textPassword"
+      ],
+      "valueAliases": {
+        "textEmailAddress": "email",
+        "textPassword": "password"
+      },
+      "description": "Input type for Android (Android-only; `input` is the cross-platform attribute). Both the JsonUI spellings and the raw android:inputType names the frozen XML mapper passed through are accepted; the latter normalize to the former.",
       "platform": "kotlin"
     },
     "returnKeyType": {
@@ -1602,7 +1649,31 @@
         "string",
         "binding"
       ],
-      "description": "Content type for autofill (binding supported)"
+      "enum": [
+        "username",
+        "password",
+        "newPassword",
+        "oneTimeCode",
+        "email",
+        "emailAddress",
+        "name",
+        "givenName",
+        "familyName",
+        "telephoneNumber",
+        "tel",
+        "phone",
+        "streetAddress",
+        "postalCode",
+        "country",
+        "creditCardNumber",
+        "URL"
+      ],
+      "valueAliases": {
+        "emailAddress": "email",
+        "tel": "telephoneNumber",
+        "phone": "telephoneNumber"
+      },
+      "description": "Content type for autofill (binding supported). The enum is the set of tokens at least one platform actually maps: iOS to .textContentType, web to the autoComplete attribute, Android to the keyboard type. `email` (not emailAddress) and `telephoneNumber` (not tel) are the canonical spellings — the web converter only matches those two, so the alternates are normalized before conversion. Tokens no platform maps are deliberately absent: declaring UIKit's full UITextContentType list would enumerate values that cannot reach any output."
     },
     "secure": {
       "type": [
@@ -1663,21 +1734,21 @@
     },
     "accessoryBackground": {
       "type": "string",
-      "description": "Input accessory background - hex string or color name from colors.json",
+      "description": "Input accessory toolbar background - hex string or color name from colors.json. UIKit only: read by SJUITextField's accessory toolbar; SwiftUI has no input-accessory surface.",
       "platform": "swift",
-      "mode": "swiftui"
+      "mode": "uikit"
     },
     "accessoryTextColor": {
       "type": "string",
-      "description": "Input accessory text color - hex string or color name from colors.json",
+      "description": "Input accessory toolbar text color - hex string or color name from colors.json. UIKit only (see accessoryBackground).",
       "platform": "swift",
-      "mode": "swiftui"
+      "mode": "uikit"
     },
     "doneText": {
       "type": "string",
-      "description": "Done button text",
+      "description": "Text of the input accessory toolbar's Done button. UIKit only (see accessoryBackground).",
       "platform": "swift",
-      "mode": "swiftui"
+      "mode": "uikit"
     },
     "tintColor": {
       "type": "string",
@@ -1691,9 +1762,7 @@
           "type": "string",
           "description": "Caret color - hex string or color name from colors.json"
         }
-      },
-      "deprecated": "swiftui",
-      "deprecation_note": "SwiftUI cannot style the caret (iOS 17 has partial .tint API)."
+      }
     },
     "onTextChange": {
       "type": "string",
@@ -1701,24 +1770,36 @@
     },
     "autocapitalizationType": {
       "type": "string",
-      "description": "Auto-capitalization type"
+      "enum": [
+        "none",
+        "words",
+        "sentences",
+        "allCharacters",
+        "characters"
+      ],
+      "valueAliases": {
+        "characters": "allCharacters"
+      },
+      "description": "Auto-capitalization type. UIKit's vocabulary, honoured on every platform (.textInputAutocapitalization / KeyboardCapitalization / the HTML autocapitalize attribute). `characters` is an accepted alias spelling of allCharacters."
     },
     "autocorrectionType": {
       "type": "string",
-      "description": "Auto-correction type"
-    },
-    "spellCheckingType": {
-      "type": "string",
-      "description": "Spell checking type",
-      "platform": "swift",
-      "deprecated": "swift",
-      "deprecation_note": "Compose does not expose spell-checking control."
-    },
-    "keyboardAppearance": {
-      "type": "string",
-      "description": "Keyboard appearance: dark, light",
-      "deprecated": "kotlin",
-      "deprecation_note": "Compose keyboard appearance is system-controlled."
+      "enum": [
+        "default",
+        "yes",
+        "no",
+        "on",
+        "off",
+        "true",
+        "false"
+      ],
+      "valueAliases": {
+        "on": "yes",
+        "true": "yes",
+        "off": "no",
+        "false": "no"
+      },
+      "description": "Auto-correction type. UIKit's vocabulary; `on`/`true` and `off`/`false` are accepted alias spellings of yes/no. `default` means \"leave it to the platform\" — web deliberately emits nothing for it."
     },
     "clearButtonMode": {
       "type": "string",
@@ -1847,11 +1928,9 @@
       "platform": "swift",
       "mode": "swiftui"
     },
-    "placeholderColor": {
-      "type": "string",
-      "description": "Deprecated on swift.",
-      "deprecated": "swift",
-      "deprecation_note": "SwiftUI TextField placeholder cannot be color-styled."
+    "hintLineHeightMultiple": {
+      "type": "number",
+      "description": "Placeholder line height multiplier. Declared from the implementation, which already read it: sjui textfield_converter.rb:153 and textview_converter.rb:93,117 (EditText/Input follow via _alias_of) (plan 51-E)."
     }
   },
   "TextView": {
@@ -1892,7 +1971,7 @@
     },
     "hintAttributes": {
       "type": "object",
-      "description": "Hint styling attributes"
+      "description": "Hint styling attributes. The nested keys win over the flat spellings (hintColor / hintFont / hintFontSize): a bag scoped to the hint is the more specific statement. That is the ordinary cascade rule and what all four readers do (rjui label_converter, kjui text_component, sjui Label and SelectBox) - it was unwritten until 2026-08-05, when the one converter that had it backwards was found by contradicting its own comment."
     },
     "hideOnFocused": {
       "type": "boolean",
@@ -1985,7 +2064,15 @@
     },
     "lineBreakMode": {
       "type": "string",
-      "description": "Line break mode"
+      "enum": [
+        "Char",
+        "Clip",
+        "Word",
+        "Head",
+        "Middle",
+        "Tail"
+      ],
+      "description": "Truncation mode. Same vocabulary as Label.lineBreakMode — the two were the same concept declared twice, once enumerated and once as a bare string."
     },
     "dataDetectorTypes": {
       "type": "string",
@@ -2001,7 +2088,41 @@
     },
     "keyboardType": {
       "type": "string",
-      "description": "Keyboard type"
+      "enum": [
+        "default",
+        "asciiCapable",
+        "alphabet",
+        "number",
+        "numberPad",
+        "decimal",
+        "decimalPad",
+        "phone",
+        "phonePad",
+        "email",
+        "emailAddress",
+        "URL",
+        "webURL",
+        "webSearch",
+        "search",
+        "namePhonePad",
+        "twitter",
+        "text",
+        "numeric",
+        "numbersAndPunctuation"
+      ],
+      "valueAliases": {
+        "alphabet": "asciiCapable",
+        "numberPad": "number",
+        "decimalPad": "decimal",
+        "phonePad": "phone",
+        "numeric": "phone",
+        "numbersAndPunctuation": "number",
+        "emailAddress": "email",
+        "webURL": "URL",
+        "search": "webSearch",
+        "text": "default"
+      },
+      "description": "Soft-keyboard type. The canonical token of each pair is the one all three converters accept: `number` rather than UIKit's numberPad (Compose only matches `number` and would fall back to a plain text keyboard), likewise decimal/phone/email. `namePhonePad` and `twitter` reach iOS only; the other platforms fall back to their default keyboard."
     },
     "onTextChange": {
       "type": "string",
@@ -2097,10 +2218,11 @@
       "platform": "react"
     },
     "edgeInset": {
-      "type": "string",
-      "description": "Deprecated on kotlin.",
-      "deprecated": "kotlin",
-      "deprecation_note": "Compose Text has no edgeInset; use padding* instead."
+      "type": [
+        "number",
+        "array"
+      ],
+      "description": "The UIKit spelling of containerInset (content inset). Same accepted shapes: a single number, or an array of 1/2/4 numbers. Was declared deprecated on kotlin (\"Compose Text has no edgeInset\"); retracted 2026-08-05 because Label.edgeInset maps to .padding() on Compose in both the codegen and the dynamic renderer. Unimplemented on the Compose TextView path, not impossible."
     }
   },
   "EditText": {
@@ -2151,10 +2273,6 @@
         "hilightColor"
       ]
     },
-    "hilightColor": {
-      "type": "string",
-      "description": "Highlight color - hex string or color name from colors.json (typo alias)"
-    },
     "tapBackground": {
       "type": "string",
       "description": "Background when tapped - hex string or color name from colors.json"
@@ -2202,6 +2320,105 @@
         "binding"
       ],
       "description": "Font weight (e.g., 'bold', 'semibold', '500', 600, or binding)"
+    },
+    "fontFamily": {
+      "type": [
+        "string",
+        "binding"
+      ],
+      "description": "Font family name (e.g., 'Noto Sans JP'). Passed as the `family` field of `FontSpec` to `Configuration.Font.fontProvider`. Coexists with `font` (weight) and `fontSize` which are passed in the same FontSpec. Declared from the implementation, which already read it: sjui button_converter.rb:173-178 (plan 51-E)."
+    },
+    "partialAttributes": {
+      "type": "array",
+      "description": "Partial text styling: apply font/size/color/underline/shadow to a substring selected by 'range' (a [start, end] pair, a text pattern, or a binding), and optionally make it tappable with 'onclick'. This is the supported way to get emphasis or a link inside a Label, since 'text' is plain text and markdown is not interpreted, and it is the portable way to express a cross-reference: the handler navigates (and scrolls to the target) in host code, so the same layout works everywhere, where a URL-based link would only work on web. All three platforms resolve partials at RUNTIME against the resolved string, so a pattern range and a localized or bound 'text' both work. Semantics, identical across platforms and verified against each runtime: an array range is [start, end) with the end exclusive; a string range is the FIRST occurrence and the partial is skipped (not an error) when the pattern is absent; a range that is out of bounds or inverted is skipped; partials apply in declaration order and MERGE where they overlap, later declarations winning per property. Declared from the implementation, which already read it: sjui button_converter.rb:68-129 (plan 51-E).",
+      "items": {
+        "type": "object",
+        "properties": {
+          "font": {
+            "type": "string",
+            "description": "Font name"
+          },
+          "fontSize": {
+            "type": "number",
+            "description": "Font size"
+          },
+          "fontColor": {
+            "type": "string",
+            "description": "Font color - hex string or color name from colors.json"
+          },
+          "lineSpacing": {
+            "type": "number",
+            "description": "Line spacing"
+          },
+          "lineHeightMultiple": {
+            "type": "number",
+            "description": "Line height multiplier"
+          },
+          "lineBreakMode": {
+            "type": "string",
+            "enum": [
+              "Char",
+              "Clip",
+              "Word",
+              "Head",
+              "Middle",
+              "Tail"
+            ],
+            "description": "Line break mode"
+          },
+          "textAlign": {
+            "type": "string",
+            "enum": [
+              "Left",
+              "Right",
+              "Center"
+            ],
+            "description": "Text alignment"
+          },
+          "underline": {
+            "type": "object",
+            "properties": {
+              "lineStyle": {
+                "type": "string",
+                "enum": [
+                  "Single",
+                  "Double",
+                  "Thick",
+                  "None"
+                ],
+                "description": "Underline style"
+              },
+              "color": {
+                "type": "string",
+                "description": "Underline color - hex string or color name from colors.json"
+              },
+              "lineOffset": {
+                "type": "number",
+                "description": "Baseline offset"
+              }
+            }
+          },
+          "textShadow": {
+            "type": "string",
+            "description": "Text shadow"
+          },
+          "range": {
+            "type": [
+              "array",
+              "string"
+            ],
+            "description": "Range [start, end], text pattern string, or binding expression"
+          },
+          "onclick": {
+            "type": "string",
+            "description": "Click handler for this range (selector-based, lowercase)"
+          },
+          "onClick": {
+            "type": "binding",
+            "description": "Click handler for this range (camelCase) - binding only (@{functionName})"
+          }
+        }
+      }
     }
   },
   "Image": {
@@ -2259,7 +2476,10 @@
         "Left",
         "Right"
       ],
-      "description": "Content mode (binding supported)"
+      "valueAliases": {
+        "ScaleToFill": "fill"
+      },
+      "description": "Content mode (binding supported). ScaleToFill is a declared synonym of fill (the stretch — see attribute_semantics.json#semantics.image); the normalizer folds it, fixtures are generated for the canonical spelling only."
     },
     "renderingMode": {
       "type": "string",
@@ -2326,6 +2546,10 @@
       "description": "Pinch-zoom lower bound.",
       "platform": "swift",
       "mode": "swiftui"
+    },
+    "defaultImage": {
+      "type": "string",
+      "description": "Default image name. Declared from the implementation, which already read it: sjui image_converter.rb:36,42 (defaultImage || errorImage || loadingImage) (plan 51-E)."
     }
   },
   "NetworkImage": {
@@ -2341,7 +2565,10 @@
         "string",
         "binding"
       ],
-      "description": "Image URL (alias, can be data binding)"
+      "description": "Image URL (alias, can be data binding). `source` folds here (sjui network_image_converter.rb:14 reads `url || source || src`).",
+      "aliases": [
+        "source"
+      ]
     },
     "hint": {
       "type": "string",
@@ -2421,6 +2648,18 @@
       "description": "HTTP headers for the image request (Coil 3: httpHeaders(NetworkHeaders) on ImageRequest.Builder).",
       "platform": "kotlin",
       "mode": "compose"
+    },
+    "renderingMode": {
+      "type": "string",
+      "enum": [
+        "original",
+        "template"
+      ],
+      "description": "Rendering mode. Declared from the implementation, which already read it: sjui network_image_converter.rb:67-68 (plan 51-E).",
+      "platform": [
+        "swift",
+        "kotlin"
+      ]
     }
   },
   "SelectBox": {
@@ -2443,14 +2682,6 @@
       ],
       "description": "Hint text color - hex string or color name from colors.json (binding supported)"
     },
-    "text": {
-      "type": [
-        "string",
-        "binding"
-      ],
-      "description": "Display text (binding supported)",
-      "platform": "swift"
-    },
     "items": {
       "type": [
         "array",
@@ -2481,15 +2712,17 @@
         "binding"
       ],
       "description": "Selected item value (two-way binding)",
-      "platform": "swift",
-      "mode": "uikit"
+      "platform": [
+        "swift",
+        "kotlin"
+      ]
     },
     "selectedDate": {
       "type": [
         "string",
         "binding"
       ],
-      "description": "Initial selected date (yyyy-MM-dd format, two-way binding)"
+      "description": "Initial selected date (yyyy-MM-dd format, two-way binding). No `default`: when it is absent no initial selection has been stated, and the closed face shows the prompt / hint / placeholder rather than today's date. Full ruling in attribute_semantics.json -> selectBoxDate."
     },
     "datePickerMode": {
       "type": "string",
@@ -2500,7 +2733,10 @@
         "dateAndTime",
         "countDown"
       ],
-      "description": "Date picker mode"
+      "valueAliases": {
+        "datetime": "dateAndTime"
+      },
+      "description": "Date picker mode. datetime is a declared synonym of dateAndTime and the normalizer folds it: sjui and rjui accept both spellings (selectbox_converter.rb case arms; rjui downcases), but KotlinJsonUI's DateSelectBox matches \"dateAndTime\" literally and datetime would silently fall to the date-only branch — so the UIKit spelling is canonical, same reasoning as gradientDirection's capitalised canon."
     },
     "datePickerStyle": {
       "type": "string",
@@ -2516,7 +2752,10 @@
     },
     "dateStringFormat": {
       "type": "string",
-      "description": "Date string format"
+      "description": "Date string format. `dateFormat` folds here (sjui selectbox_converter.rb:132 reads `dateFormat || dateStringFormat`).",
+      "aliases": [
+        "dateFormat"
+      ]
     },
     "minimumDate": {
       "type": [
@@ -2807,10 +3046,6 @@
       "platform": "swift",
       "mode": "uikit"
     },
-    "onToggle": {
-      "type": "binding",
-      "description": "Toggle handler function - binding only (@{functionName}). Alias of onValueChange."
-    },
     "onValueChange": {
       "type": "binding",
       "description": "Value change handler - binding only (@{functionName})",
@@ -2854,9 +3089,43 @@
     },
     "trackTintColor": {
       "type": "string",
-      "description": "Deprecated on swift.",
-      "deprecated": "swift",
-      "deprecation_note": "SwiftUI Toggle uses unified tint only."
+      "description": "Colour of the switch track - hex string or color name from colors.json. Deprecation retracted with the Slider pair; a SwiftUI Toggle is not limited to a unified tint any more than Progress is."
+    },
+    "fontColor": {
+      "type": [
+        "string",
+        "binding"
+      ],
+      "description": "Text color - hex string or color name from colors.json (binding supported). Declared from the implementation, which already read it: sjui toggle_converter.rb:62-63,71-72 (plan 51-E)."
+    },
+    "toggleStyle": {
+      "type": "string",
+      "enum": [
+        "switch",
+        "button",
+        "checkbox",
+        "default"
+      ],
+      "description": "Which control shape the Switch is drawn as. A SwiftUI-only concept (the ToggleStyle protocol); an unrecognised value falls back to the platform default rather than erroring. Declared from the implementation, which already read it: sjui toggle_converter.rb:92-104 (plan 51-E).",
+      "platform": "swift",
+      "mode": "swiftui"
+    },
+    "label": {
+      "type": [
+        "string",
+        "binding"
+      ],
+      "description": "Switch label (can be data binding). Same shape CheckBox and Radio already declare: `label` is the canonical row and `text` folds into it. Declared from the implementation, which already read it: sjui toggle_converter.rb:21 (text || label) (plan 51-E).",
+      "aliases": [
+        "text"
+      ]
+    },
+    "fontSize": {
+      "type": [
+        "number",
+        "binding"
+      ],
+      "description": "Font size (binding supported). Declared from the implementation, which already read it: sjui toggle_converter.rb hands the whole component to the shared apply_font_modifiers helper, so the size was honoured with no declaration behind it (plan 51-E)."
     }
   },
   "Toggle": {
@@ -2874,30 +3143,32 @@
         "number",
         "binding"
       ],
-      "description": "Initially selected index (binding for two-way)",
-      "binding_direction": "two-way"
+      "description": "Initially selected index (binding for two-way). `selectedTabIndex` folds here (sjui segment_converter.rb:16), matching the alias TabView already declares.",
+      "binding_direction": "two-way",
+      "aliases": [
+        "selectedTabIndex"
+      ]
     },
     "tintColor": {
       "type": "string",
-      "description": "Tint color - hex string or color name from colors.json"
+      "description": "Accent color of the SELECTED segment - a background fill on ios/web, the indicator on Compose. Hex string or color name from colors.json. `selectedSegmentTintColor` folds here (sjui segment_converter.rb:128 reads `selectedSegmentTintColor || tintColor`).",
+      "aliases": [
+        "selectedSegmentTintColor"
+      ]
     },
-    "normalColor": {
-      "type": [
-        "string",
-        "binding"
-      ],
-      "description": "Normal state color - hex string or color name from colors.json (binding supported)",
-      "platform": "swift",
-      "mode": "swiftui"
+    "fontColor": {
+      "type": "string",
+      "description": "Label color of the UNSELECTED segments - hex string or color name from colors.json",
+      "aliases": [
+        "normalColor"
+      ]
     },
-    "selectedColor": {
-      "type": [
-        "string",
-        "binding"
-      ],
-      "description": "Selected state color - hex string or color name from colors.json (binding supported)",
-      "platform": "swift",
-      "mode": "swiftui"
+    "selectedFontColor": {
+      "type": "string",
+      "description": "Label color of the selected segment, falling back to fontColor - hex string or color name from colors.json",
+      "aliases": [
+        "selectedColor"
+      ]
     },
     "valueChange": {
       "type": "string",
@@ -2929,41 +3200,29 @@
       "description": "Current value (binding for two-way)",
       "binding_direction": "two-way"
     },
-    "minValue": {
-      "type": [
-        "number",
-        "binding"
-      ],
-      "description": "Minimum value (binding supported)"
-    },
     "minimum": {
       "type": [
         "number",
         "binding"
       ],
-      "description": "Minimum value (alias for minValue) (binding supported)",
+      "description": "Minimum value (binding supported). `minValue` / `minimumValue` are accepted alias spellings. Defaults to 0: with no bounds declared the range is 0 .. 1, this SSoT's convention for a unitless value on a track (compare Progress.progress and opacity, both declared min 0 / max 1). Full ruling in attribute_semantics.json -> sliderRange.",
       "aliases": [
         "minimumValue",
         "minValue"
-      ]
-    },
-    "maxValue": {
-      "type": [
-        "number",
-        "binding"
       ],
-      "description": "Maximum value (binding supported)"
+      "default": 0
     },
     "maximum": {
       "type": [
         "number",
         "binding"
       ],
-      "description": "Maximum value (alias for maxValue) (binding supported)",
+      "description": "Maximum value (binding supported). `maxValue` / `maximumValue` are accepted alias spellings. Defaults to 1: with no bounds declared the range is 0 .. 1, this SSoT's convention for a unitless value on a track (compare Progress.progress and opacity, both declared min 0 / max 1). Full ruling in attribute_semantics.json -> sliderRange.",
       "aliases": [
         "maximumValue",
         "maxValue"
-      ]
+      ],
+      "default": 1
     },
     "tintColor": {
       "type": "string",
@@ -2995,15 +3254,15 @@
     },
     "progressTintColor": {
       "type": "string",
-      "description": "Deprecated on swift.",
-      "deprecated": "swift",
-      "deprecation_note": "SwiftUI Slider uses unified tint only."
+      "description": "Colour of the filled portion of the track - hex string or color name from colors.json. Was declared deprecated on swift (\"SwiftUI Slider uses unified tint only\"); retracted 2026-08-05 because Progress, also SwiftUI, maps the same attribute to .tint(). Unimplemented on the Slider path, not impossible."
     },
     "trackTintColor": {
       "type": "string",
-      "description": "Deprecated on swift.",
-      "deprecated": "swift",
-      "deprecation_note": "SwiftUI Slider uses unified tint only."
+      "description": "Colour of the unfilled track - hex string or color name from colors.json. Deprecation retracted with progressTintColor: SwiftUI Progress reaches the same result through .background()."
+    },
+    "range": {
+      "type": "array",
+      "description": "Both bounds at once, as [minimum, maximum] — a shorthand for declaring `minimum` and `maximum` separately. It is NOT an alias: one spelling carries two values, so the normalizer cannot fold it. Read only when it is a two-element array; anything else leaves `minimum` / `maximum` to speak for themselves. Declared from the implementation, which already read it: sjui slider_converter.rb:16-19 (plan 51-E)."
     }
   },
   "Progress": {
@@ -3136,16 +3395,30 @@
     },
     "gradient": {
       "type": "array",
-      "description": "Gradient colors",
-      "platform": "swift",
-      "mode": "uikit"
+      "description": "Gradient colors Wins over `background` when both are declared on the same view; see attribute_semantics.json -> backgroundFill.",
+      "platform": "swift"
     },
     "gradientDirection": {
-      "type": "string",
-      "description": "Gradient direction",
-      "platform": "swift",
-      "mode": "uikit"
-    },
+        "type": "string",
+        "enum": [
+          "Vertical",
+          "Horizontal",
+          "Oblique",
+          "LeftToRight",
+          "TopToBottom",
+          "Diagonal",
+          "RightToLeft",
+          "BottomToTop"
+        ],
+        "valueAliases": {
+          "LeftToRight": "Horizontal",
+          "TopToBottom": "Vertical",
+          "Diagonal": "Oblique"
+        },
+        "default": "Vertical",
+        "description": "Gradient direction. Canon copied from GradientView.gradientDirection, which declared the enum for the same concept while this spelling stayed a bare string. Vertical is the fallback on all three. CASE MATTERS on ios: sjui matches 'Horizontal'/'Oblique' literally (modifier_helper.rb:16) without downcasing, while Compose and web downcase — so the capitalised spellings are canonical and the aliases normalise to them before any converter sees the value. RightToLeft and BottomToTop are declared without an alias on purpose: they are reversed directions web implements (gradient_view_converter.rb:88,90) and the other two have no equivalent, so folding them into Horizontal/Vertical would silently reverse the gradient rather than preserve it.",
+        "platform": "swift"
+      },
     "locations": {
       "type": "array",
       "description": "Gradient color stop locations",
@@ -3154,7 +3427,7 @@
     },
     "safeAreaInsetPositions": {
       "type": "array",
-      "description": "Safe area inset positions (SafeAreaView only)",
+      "description": "Which edges reserve the safe area. Declared here as well as on SafeAreaView on purpose: SafeAreaView is its own definition section and does not inherit View's, and every platform honours the attribute on a PLAIN view too (sjui base_view_converter.rb#apply_safe_area_insets_to_bag runs for every component; rjui view_converter.rb#safe_area_edges emits env(safe-area-inset-*) padding). The two declarations are the same concept reaching two routing paths, not a duplicate.",
       "items": {
         "type": "string",
         "enum": [
@@ -3216,15 +3489,11 @@
     "_comment": "Sparse by design, not an alias: only the Kotlin dynamic runtime dispatches CircleView (DynamicCircleViewComponent, CircleShape clip) - P18 audit 2026-08-01. Everything it renders beyond child/children comes from common. component_metadata.json carries the per-platform truth.",
     "child": {
       "type": "array",
-      "description": "Child component(s)",
-      "platform": "swift",
-      "mode": "uikit"
+      "description": "Child component(s)"
     },
     "children": {
       "type": "array",
-      "description": "Child components (alias for child)",
-      "platform": "swift",
-      "mode": "uikit"
+      "description": "Child components (alias for child)"
     }
   },
   "ScrollView": {
@@ -3388,6 +3657,19 @@
       ],
       "description": "Scroll behavior animation",
       "platform": "react"
+    },
+    "horizontalScroll": {
+      "type": "boolean",
+      "description": "Enable horizontal scroll. Declared from the implementation, which already read it: sjui scrollview_converter.rb:39 (plan 51-E)."
+    },
+    "defaultScrollAnchor": {
+      "type": "string",
+      "enum": [
+        "top",
+        "center",
+        "bottom"
+      ],
+      "description": "Initial scroll position anchor. Sets where the scroll view starts. Declared from the implementation, which already read it: sjui scrollview_converter.rb:207-215. Scope is deliberately all three platforms: the anchor is a portable concept and the declaration says an attribute EXISTS, not which face has caught up — the coverage ledger carries the android and web gaps. The \"(iOS 17+)\" note this description was copied with belonged to Collection's ios implementation, not to the contract, and has been dropped here (plan 51-E, raised by C)."
     }
   },
   "Collection": {
@@ -3434,7 +3716,10 @@
     },
     "lineSpacing": {
       "type": "number",
-      "description": "Spacing between rows"
+      "description": "Spacing between rows. `sectionSpacing` folds here (sjui collection_converter.rb:799,960 read `sectionSpacing || lineSpacing || 8`).",
+      "aliases": [
+        "sectionSpacing"
+      ]
     },
     "horizontalScroll": {
       "type": "boolean",
@@ -3579,7 +3864,7 @@
     },
     "scrollTo": {
       "type": "binding",
-      "description": "PassthroughSubject<Int, Never> for programmatic scrolling to cell index"
+      "description": "Binding that requests a programmatic scroll. The declared DATA CLASS is a plain value — `String` when cellIdProperty is set (scroll to that cell id), `Int` otherwise (scroll to that index). It is deliberately NOT `PassthroughSubject<Int, Never>`, which this description used to prescribe: PassthroughSubject is a Combine type, and naming a Swift transport in the cross-platform SSoT is what made consumers write it into their data section, where kjui's map_to_kotlin_type passes unknown classes through verbatim and the Kotlin build dies on it. How the request is delivered is each platform's own business — iOS wraps the value in a publisher so a repeated send re-scrolls, Compose reads the String directly, web keys a useEffect on it. STATUS 2026-08-05, after B landed the derivation (jsonui-cli 8c41e3e): the CODEGEN side of all three platforms now takes the plain value — sjui emits `.onChange(of: data.<prop>)` with no publisher and no throttle, Compose keys a LaunchedEffect on it, web a useEffect. The remaining gap is the SwiftUI DYNAMIC renderer: CollectionConverter.swift:127 still resolves the binding as `data[propName] as? PassthroughSubject<Int, Never>` and gets nil for a plain value, so the scroll silently never fires there (it does not crash, it does nothing). Consequence for fixtures: a Collection.scrollTo fixture is now declarable and no longer kills the Kotlin build, and Collection.scrollAnchor is measurable on the codegen path — but ios codegen and ios dynamic will disagree until the dynamic resolver accepts the value, so expect a parity finding there rather than a render failure. Owner of the remainder: the SwiftJsonUI dynamic lane. Note also that the vendored CollectionAttributes.swift still carries the old publisher wording in its doc comment; it is generated from this description and will pick the correction up at the next re-vendor."
     },
     "scrollAnchor": {
       "type": "string",
@@ -3588,7 +3873,8 @@
         "center",
         "bottom"
       ],
-      "description": "Anchor point for scroll target (default: bottom)"
+      "default": "bottom",
+      "description": "Anchor point for the scrollTo target. Measured 2026-08-05: ios (sjui collection_converter.rb:1138), web (rjui build_command.rb:768) and the Compose GRID path (kjui collection_component.rb:313) all fall back to bottom, so bottom is the declared default. The Compose LIST path emits no anchor offset unless the attribute is explicitly declared, which lands the target at top - that is a divergence in that one path, not a second default."
     },
     "defaultScrollAnchor": {
       "type": "string",
@@ -3624,17 +3910,16 @@
       "description": "Enable/disable scrolling (binding supported)"
     },
     "onItemAppear": {
-      "type": "callback",
-      "description": "Called with the cell index (Int) when a cell appears on screen. Use for pagination by checking index against total count in ViewModel."
+      "type": [
+        "string",
+        "binding"
+      ],
+      "description": "Called with the cell index (Int) when a cell appears on screen. Use for pagination by checking index against total count in ViewModel. Declared `binding` because that is what a layout actually carries: the author writes `@{handlerName}`, a STRING, and every reader matches it as one (kjui collection_component.rb:364 `json_data['onItemAppear'].match(/@\\{([^}]+)\\}/)`, and the binding validators infer `((Int) -> Unit)?` from that spelling). It was `type: \"callback\"` — the only callback-typed attribute in the whole SSoT — and attr-codegen skips that type as \"function-valued, not extractable from JSON\". True of a function; not true of the `@{...}` string a JSON layout can hold, so the attribute had no row in any generated table and no platform could read it typed (2026-08-05, plan 49-E, raised by A)."
     },
     "currentPage": {
       "type": "binding",
       "description": "Current page index for paging collections (binding supported)"
     },
-    "onPageChanged": {
-      "type": "callback",
-      "description": "Called with the new page index (Int) when the user swipes to a different page"
-    },
     "containerInset": {
       "type": "array",
       "description": "Container-level insets applied outside of individual cells.",
@@ -3657,6 +3942,29 @@
         "onValueChanged",
         "onPageChanged"
       ]
+    },
+    "cellWidth": {
+      "type": "number",
+      "description": "Fixed width for every cell, in pt / dp / px. Applied to the cell view AFTER it is built, so it overrides whatever width the cell layout asked for; leave it out to let each cell size itself. Declared from the implementation, which already read it: sjui collection_converter.rb:256,282,315,650 (plan 51-E)."
+    },
+    "cellHeight": {
+      "type": "number",
+      "description": "Fixed height for every cell, in pt / dp / px. Applied to the cell view AFTER it is built, so it overrides whatever height the cell layout asked for; leave it out to let each cell size itself. Declared from the implementation, which already read it: sjui collection_converter.rb:260,286,318,402 (plan 51-E)."
+    },
+    "hideSeparator": {
+      "type": "boolean",
+      "description": "Hide the row separators a list draws between cells. A NO-OP where the container draws no separators (a grid-shaped Collection has none) — that is the contract, not an unimplemented gap, and it does not license switching the container to a List. No CODEGEN face reads it, so the coverage row is runtime-only. Full ruling in attribute_semantics.json -> collectionSeparators."
+    },
+    "listStyle": {
+      "type": "string",
+      "enum": [
+        "plain",
+        "grouped",
+        "insetGrouped",
+        "sidebar"
+      ],
+      "default": "plain",
+      "description": "Which list chrome the collection is drawn with. Enumerated from the only implementation that reads it (SwiftJsonUI TableConverter.applyListStyle); an unrecognised value falls back to plain. ORTHOGONAL to hideSeparator — that one hides the separators, this one picks the chrome, and neither overrides the other. No CODEGEN face reads it, so the coverage row is runtime-only: sjui collection_converter.rb:213 hardcodes PlainListStyle instead. Full ruling in attribute_semantics.json -> collectionSeparators."
     }
   },
   "Radio": {
@@ -3698,16 +4006,15 @@
         "selected_icon"
       ]
     },
-    "selected_icon": {
-      "type": "string",
-      "description": "Selected icon name (underscore alias)"
-    },
     "checked": {
       "type": [
         "boolean",
         "binding"
       ],
-      "description": "Initial checked state (can be binding)"
+      "description": "Seeds the group's INITIAL selection — it is not the live state, and it is not two-way. The state a radio group carries is `selectedValue`; `checked` only says which option starts selected when nothing else has said. Precedence, and all three platforms implement it in this order: a BOUND `selectedValue` wins outright (the group's own two-way state), then a LITERAL `selectedValue` (a group-level statement naming the starting option), then this option's `checked`. So a radio group that binds selectedValue ignores `checked` entirely, which is what stops a seed from freezing a group that the user can no longer change. The bound form of `checked` seeds the glyph rather than the state, since a property initialiser cannot read the data map: it selects only while the group has made no choice yet (sjui radio_converter.rb:88-103, and the same rule in RadioConverter.swift). CONTRAST with CheckBox.checked and Switch.checked, which look identical and are not: those ARE the control's state and carry binding_direction two-way. A radio has no state of its own — the group does. Declared 2026-08-05 (plan 49-E) from the implementations; the previous description said only \"Initial checked state\", which was true and told nobody what happens when both are declared. `isOn` folds here (sjui radio_converter.rb:88,102 read both the literal and the bound form as `checked || isOn`).",
+      "aliases": [
+        "isOn"
+      ]
     },
     "value": {
       "type": "any",
@@ -3783,6 +4090,13 @@
     "onValueChange": {
       "type": "binding",
       "description": "Value change handler - binding only (@{functionName})"
+    },
+    "items": {
+      "type": [
+        "array",
+        "binding"
+      ],
+      "description": "List of items for normal picker (can be template variable). Declared from the implementation, which already read it: sjui radio_converter.rb:13 — the option list a radio GROUP renders; with it the converter emits a group, without it a single radio (plan 51-E)."
     }
   },
   "CheckBox": {
@@ -3882,14 +4196,22 @@
     },
     "onValueChange": {
       "type": "binding",
-      "description": "Value change handler - binding only (@{functionName})"
+      "description": "Value change handler - binding only (@{functionName}). Legacy handler spellings fold here (sjui checkbox_converter.rb:122 reads `onValueChange || onClick || action || onValueChanged`; `onClick` stays common).",
+      "aliases": [
+        "action",
+        "onValueChanged"
+      ]
     },
     "checkedColor": {
       "type": "color",
-      "description": "Color when checked.",
+      "description": "Color when checked. Legacy accent spellings fold here (sjui checkbox_converter.rb:98 and kjui checkbox_component.rb:211 both read the same four spellings for this one colour). `tintColor` is deliberately NOT in the alias list: it is already declared on `common`, and an alias that is also a declared row is a silent no-op (test_no_alias_is_cancelled_by_a_declaration_of_its_own_name). On a CheckBox the common tint IS the checked colour - that is what both converters implement - so it needs no alias row. Declaring the other two also settles a live divergence: ios reads `checkedColor` first, android reads `checkColor` first, so a layout setting both drew two different colours until the normalizer began folding them (plan 51-E).",
       "platform": [
         "swift",
         "kotlin"
+      ],
+      "aliases": [
+        "checkColor",
+        "onTintColor"
       ]
     },
     "uncheckedColor": {
@@ -3915,6 +4237,16 @@
         "swift",
         "kotlin"
       ]
+    },
+    "fontWeight": {
+      "type": [
+        "string",
+        "number"
+      ],
+      "description": "Font weight (e.g., 'bold', 'semibold', '500', 600). Canonical name matches Label and Button; the legacy `fontStyle` spelling folds here. Declared from the implementation, which already read it: sjui checkbox_converter.rb:74-76, which reads `fontStyle` and emits `fontWeight:` (plan 51-E).",
+      "aliases": [
+        "fontStyle"
+      ]
     }
   },
   "Check": {
@@ -3922,6 +4254,18 @@
     "_comment": "Component alias of CheckBox. Resolved by the L1 normalizer type rewrite and by every validator/codegen consumer - do not add attribute copies here."
   },
   "Indicator": {
+    "animating": {
+      "type": [
+        "boolean",
+        "binding"
+      ],
+      "default": true,
+      "description": "Whether the indicator is spinning. Defaults to true: an Indicator with nothing declared animates. `false` stops it, and hidesWhenStopped then decides whether the stopped indicator keeps its space or collapses out of the layout \u2014 which is why hidesWhenStopped is only ever read on this branch (sjui indicator_converter.rb:23, kjui indicator_component.rb:13).",
+      "platform": [
+        "swift",
+        "kotlin"
+      ]
+    },
     "indicatorStyle": {
       "type": "string",
       "enum": [
@@ -3937,13 +4281,16 @@
         "string",
         "binding"
       ],
-      "description": "Indicator color - hex string or color name from colors.json (binding supported)",
+      "description": "Indicator color - hex string or color name from colors.json (binding supported). `tint` folds here (sjui indicator_converter.rb:77 reads `color || tintColor || tint`).",
       "platform": "swift",
-      "mode": "swiftui"
+      "mode": "swiftui",
+      "aliases": [
+        "tint"
+      ]
     },
     "hidesWhenStopped": {
       "type": "boolean",
-      "description": "Hide when stopped",
+      "description": "Hide when stopped. Decides SPACE: `true` collapses the stopped indicator out of the layout, `false` keeps it drawn AND laid out. Full ruling in attribute_semantics.json -> indicatorStopped.",
       "platform": "swift",
       "mode": "swiftui"
     }
@@ -3951,7 +4298,10 @@
   "GradientView": {
     "gradient": {
       "type": "array",
-      "description": "Gradient colors"
+      "description": "Gradient colors. `colors` folds here (sjui gradient_view_converter.rb:52,66 read `colors || gradient`). On GradientView the gradient is the component's own fill, so the backgroundFill precedence question does not arise.",
+      "aliases": [
+        "colors"
+      ]
     },
     "gradientDirection": {
       "type": "string",
@@ -3965,6 +4315,54 @@
     "locations": {
       "type": "array",
       "description": "Color stop locations (0.0-1.0)"
+    },
+    "child": {
+      "type": "array",
+      "description": "Child component(s). Declared from the implementation, which already read it: sjui gradient_view_converter.rb:16 (plan 51-E)."
+    },
+    "children": {
+      "type": "array",
+      "description": "Child components (alias for child). Declared from the implementation, which already read it: sjui gradient_view_converter.rb:16 (child || children) (plan 51-E)."
+    },
+    "startPoint": {
+      "type": [
+        "array",
+        "object"
+      ],
+      "description": "Unit coordinates in the view's own box for where the gradient starts: [x, y] or {\"x\": x, \"y\": y}, with 0 = leading/top, 0.5 = centre/middle, 1 = trailing/bottom. THREE faces read this key three incompatible ways today: sjui gradient_view_converter.rb:107-109 wants an OBJECT ({x, y}), rjui gradient_view_converter.rb:72-73 destructures an ARRAY ([x, y]), and kjui gradientview_component.rb:58-59 expects a STRING edge name ('top'). The two coordinate forms are declared because both are real coordinate spellings of the same thing; the android string form is NOT declared - it is `gradientDirection` semantics written under the wrong key, and is filed as a defect rather than blessed here. Declaring BOTH startPoint and endPoint replaces gradientDirection entirely; declaring only one is ignored and gradientDirection still decides (plan 51-E).",
+      "items": {
+        "type": "number"
+      },
+      "properties": {
+        "x": {
+          "type": "number",
+          "description": "0 = leading, 0.5 = centre, 1 = trailing"
+        },
+        "y": {
+          "type": "number",
+          "description": "0 = top, 0.5 = middle, 1 = bottom"
+        }
+      }
+    },
+    "endPoint": {
+      "type": [
+        "array",
+        "object"
+      ],
+      "description": "Unit coordinates in the view's own box for where the gradient ends: [x, y] or {\"x\": x, \"y\": y}, with 0 = leading/top, 0.5 = centre/middle, 1 = trailing/bottom. THREE faces read this key three incompatible ways today: sjui gradient_view_converter.rb:107-109 wants an OBJECT ({x, y}), rjui gradient_view_converter.rb:72-73 destructures an ARRAY ([x, y]), and kjui gradientview_component.rb:58-59 expects a STRING edge name ('top'). The two coordinate forms are declared because both are real coordinate spellings of the same thing; the android string form is NOT declared - it is `gradientDirection` semantics written under the wrong key, and is filed as a defect rather than blessed here. Declaring BOTH startPoint and endPoint replaces gradientDirection entirely; declaring only one is ignored and gradientDirection still decides (plan 51-E).",
+      "items": {
+        "type": "number"
+      },
+      "properties": {
+        "x": {
+          "type": "number",
+          "description": "0 = leading, 0.5 = centre, 1 = trailing"
+        },
+        "y": {
+          "type": "number",
+          "description": "0 = top, 0.5 = middle, 1 = bottom"
+        }
+      }
     }
   },
   "Blur": {
@@ -3984,6 +4382,14 @@
         "kotlin",
         "react"
       ]
+    },
+    "child": {
+      "type": "array",
+      "description": "Child component(s). Declared from the implementation, which already read it: sjui blur_converter.rb:16 (plan 51-E)."
+    },
+    "children": {
+      "type": "array",
+      "description": "Child components (alias for child). Declared from the implementation, which already read it: sjui blur_converter.rb:16 (child || children) (plan 51-E)."
     }
   },
   "IconLabel": {
@@ -3999,7 +4405,10 @@
         "boolean",
         "binding"
       ],
-      "description": "Selected state (binding supported). Chooses icon_on over icon_off and selectedFontColor over fontColor, so every platform declaring those needs this too."
+      "description": "Selected state (binding supported). Chooses icon_on over icon_off and selectedFontColor over fontColor, so every platform declaring those needs this too. `isOn` folds here — the legacy spelling for the same state. IconLabelConverter.swift:145-151 says so in as many words (\"Pre-SSoT layouts that spelled it `isOn` keep working\") and reads it out of rawData because no typed slot existed; sjui icon_label_converter.rb:130 reads the canonical `selected` (plan 51-E).",
+      "aliases": [
+        "isOn"
+      ]
     },
     "font": {
       "type": "string",
@@ -4045,6 +4454,13 @@
     "iconMargin": {
       "type": "number",
       "description": "Icon-text spacing"
+    },
+    "iconSize": {
+      "type": [
+        "number",
+        "array"
+      ],
+      "description": "Icon size. A number sizes both edges; a two-element [width, height] sizes them separately (rjui icon_label_converter.rb:130-138 reads both, and its spec covers both). NOT the same shape as CheckBox.iconSize, which is a square glyph and takes a number only. sjui icon_label_converter.rb:50-51 interpolates the value straight into `iconSize:`, so the array form is web-only today — declared here because the attribute's value space is a property of the attribute, not of whichever face lags (plan 51-E)."
     }
   },
   "Web": {
@@ -4070,8 +4486,8 @@
       "platform": "swift"
     },
     "sandbox": {
-      "type": "string",
-      "description": "Iframe sandbox attribute",
+      "type": "boolean",
+      "description": "Iframe sandboxing kill-switch. `false` emits no sandbox attribute at all; otherwise the permission list is built from the other Web attributes (javaScriptEnabled, javaScriptCanOpenWindowsAutomatically, allowPopupsToEscapeSandbox, allowModals, ...) rather than from a value written here.",
       "platform": "react"
     },
     "allow": {
@@ -4091,7 +4507,10 @@
     },
     "safeAreaInsetPositions": {
       "type": "array",
-      "description": "Safe area edges",
+      "description": "Safe area edges. `edges` is an accepted alias spelling: the Compose SafeAreaView builder reads it (kjui compose_builder.rb:722 `json_data['edges'] || json_data['safeAreaInsetPositions']`) while no declaration named it, so iOS and web silently ignored a layout that used it. Declaring the alias normalizes it to the canonical spelling and makes it reach all three platforms.",
+      "aliases": [
+        "edges"
+      ],
       "items": {
         "type": "string",
         "enum": [
@@ -4111,6 +4530,34 @@
     "children": {
       "type": "array",
       "description": "Child components (alias for child)"
+    },
+    "direction": {
+      "type": "string",
+      "enum": [
+        "topToBottom",
+        "bottomToTop",
+        "leftToRight",
+        "rightToLeft",
+        "none"
+      ],
+      "description": "Layout direction. Declared from the implementation, which already read it: sjui view_converter.rb:140 (SafeAreaView routes through the View converter) (plan 51-E)."
+    },
+    "gradient": {
+      "type": "array",
+      "description": "Gradient colors. Declared from the implementation, which already read it: sjui view_converter.rb:456 (plan 51-E).",
+      "platform": "swift"
+    },
+    "spacing": {
+      "type": [
+        "number",
+        "binding"
+      ],
+      "description": "Space between children (binding supported). Declared from the implementation, which already read it: sjui view_converter.rb:181 (plan 51-E).",
+      "mode": [
+        "swiftui",
+        "compose",
+        "react"
+      ]
     }
   },
   "TabView": {
@@ -4195,10 +4642,6 @@
       "default": true,
       "description": "Whether to show tab labels (default: true)"
     },
-    "onTabChange": {
-      "type": "binding",
-      "description": "Tab change handler - binding only (@{functionName})"
-    },
     "onValueChange": {
       "type": [
         "string",