jui-tools-mcp-server 2.12.3 → 2.12.5

package/data/attribute_definitions.json

@@ -2994,29 +2994,31 @@
     },
     "caretAttributes": {
       "type": "object",
-      "description": "Caret/arrow styling attributes",
-      "platform": "swift",
-      "mode": "uikit",
+      "description": "Caret/arrow styling for the closed select. Absent: every face keeps its native indicator at its native inset (the picture each face drew before 1.8.101), so existing layouts do not move. Present: the face draws the caret itself from these keys, on every platform and mode — this object was UIKit-only (SJUISelectBox) until 1.8.101; SwiftUI codegen/dynamic, Compose codegen/dynamic and the web <select> now honour it too. `src` is optional: when it is absent the face draws its own default chevron glyph, so `{\"rightMargin\": 12}` alone moves the native-looking arrow away from the trailing edge. Not inherited from any other object; the multiple/list-box and Date modes have no closed-state caret and ignore it.",
       "properties": {
         "src": {
           "type": "string",
-          "description": "Caret image name"
+          "description": "Caret image asset name. Optional — absent means the face's default chevron glyph."
         },
         "width": {
           "type": "number",
-          "description": "Caret width"
+          "description": "Caret width (pt / dp / px). Absent: the face's default glyph size."
         },
         "height": {
           "type": "number",
-          "description": "Caret height"
+          "description": "Caret height (pt / dp / px). Absent: the face's default glyph size."
         },
         "tintColor": {
           "type": "string",
-          "description": "Caret tint color - hex string or color name from colors.json"
+          "description": "Caret tint color - hex string or color name from colors.json. Applies to the default glyph and to a template `src`."
         },
         "background": {
           "type": "string",
-          "description": "Caret background color - hex string or color name from colors.json"
+          "description": "Caret background color - hex string or color name from colors.json. Fills the caret's own box (width x height), not the select."
+        },
+        "rightMargin": {
+          "type": "number",
+          "description": "Distance from the select's trailing edge to the caret's trailing edge (pt / dp / px). Absent: 0, which is the UIKit contract this object came from (the caret sits flush against the edge)."
         }
       }
     },
@@ -4758,7 +4760,7 @@
         "string",
         "binding"
       ],
-      "description": "Unselected tab color - hex string or color name from colors.json (binding supported). SCOPE: this is the colour of an unselected TAB ITEM, so it only concerns TabView used as a tab bar. A TabView carrying .tabViewStyle(.page) is a PAGER and has no tab items at all, so nothing here applies to it - measured 2026-09-15 across two consumer faces, where all four TabView uses were .page pagers and the exposure to this key was zero. iOS 26 AND LATER DO NOT HONOUR THIS, on either iOS face, and there is no replacement: SwiftUI exposes no per-item tint for a tab bar (the whole tab/toolbar modifier surface was enumerated from the iOS 27 SDK swiftinterface - tabBarMinimizeBehavior, tabViewCustomization, tabViewSearchActivation and eleven toolbar* modifiers, none of which reaches an item), so both faces route through the UIKit appearance proxy UITabBar.appearance().unselectedItemTintColor. Measured 2026-09-15 on iPhone 16 Pro / iOS 26.5: the fixture renders 0 differing pixels from its control while tabBarBackground renders 223110 and tintColor 4553 on the same capture. The proxy is not being cleared - reading it back immediately after the set and again one runloop later both return the assigned colour - iOS 26 simply ignores it for item tints, having replaced the tab bar. Three replacement routes were rendered and each measured 0: the legacy property, UITabBarAppearance item colours (stackedLayoutAppearance / inlineLayoutAppearance / compactInlineLayoutAppearance, assigned to standardAppearance and scrollEdgeAppearance) in onAppear, and the same set before the view is constructed; a build control injecting a red backgroundColor on that same path moved 223110 pixels, so the code demonstrably ran. NOT a v10.22.0 regression: conformance run 34849471695 shows it on iOS 26 before that tag existed, and the iOS 18 runs before it do not. The sibling keys are unaffected - tintColor, tabBarBackground (which also has a SwiftUI route) and the Slider / Switch / Segment appearance proxies are all still active on iOS 26, so this is one key, not the proxy as a whole. android and web are unaffected and still honour it."
+      "description": "Unselected tab color - hex string or color name from colors.json (binding supported). SCOPE: this is the colour of an unselected TAB ITEM, so it only concerns TabView used as a tab bar. A TabView carrying .tabViewStyle(.page) is a PAGER and has no tab items at all, so nothing here applies to it. iOS 26 AND LATER DO NOT HONOUR THIS, and there is no replacement: SwiftUI exposes no per-item tint for a tab bar (the whole tab/toolbar modifier surface was enumerated from the iOS 27 SDK swiftinterface - tabBarMinimizeBehavior, tabViewCustomization, tabViewSearchActivation and eleven toolbar* modifiers, none of which reaches an item), so the iOS render path routes through the UIKit appearance proxy UITabBar.appearance().unselectedItemTintColor. Measured 2026-09-15 on iPhone 16 Pro / iOS 26.5: the fixture renders 0 differing pixels from its control while tabBarBackground renders 223110 and tintColor 4553 on the same capture. The proxy is not being cleared - reading it back immediately after the set and again one runloop later both return the assigned colour - iOS 26 simply ignores it for item tints, having replaced the tab bar. Three replacement routes were rendered and each measured 0: the legacy property, UITabBarAppearance item colours (stackedLayoutAppearance / inlineLayoutAppearance / compactInlineLayoutAppearance, assigned to standardAppearance and scrollEdgeAppearance) in onAppear, and the same set before the view is constructed; a build control injecting a red backgroundColor on that same path moved 223110 pixels, so the code demonstrably ran. NOT a v10.22.0 regression: conformance run 34849471695 shows it on iOS 26 before that tag existed, and the iOS 18 runs before it do not. The sibling keys are unaffected - tintColor, tabBarBackground (which also has a SwiftUI route) and the Slider / Switch / Segment appearance proxies are all still active on iOS 26, so this is one key, not the proxy as a whole. android and web are unaffected and still honour it."
     },
     "tabBarBackground": {
       "type": [

package/data/coverage.json

@@ -1,6 +1,6 @@
 {
   "schemaVersion": 1,
-  "_comment": "Declared attributes no platform converter reads. Hand-maintained: close a gap by implementing it (then delete the entry) or by narrowing platform/mode in attribute_definitions.json. reason is one of: dynamic-key, legacy, platform-na, runtime-only, unimplemented.",
+  "_comment": "Declared attributes no platform converter reads. Hand-maintained: close a gap by implementing it (then delete the entry) or by narrowing platform/mode in attribute_definitions.json. reason is one of: dynamic-key, legacy, platform-na, runtime-only, unimplemented, unreviewed.",
   "entries": [
     {
       "component": "ScrollView",
@@ -17,7 +17,8 @@
       "platforms": [
         "android"
       ],
-      "reason": "unimplemented"
+      "reason": "unimplemented",
+      "note": "written by `coverage --update`; replace with a real reason and a note, or close the gap"
     },
     {
       "component": "common",

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "jui-tools-mcp-server",
-  "version": "2.12.3",
+  "version": "2.12.5",
   "description": "MCP server for JsonUI project management - wraps jui and jsonui-doc CLIs plus component spec lookup",
   "main": "dist/index.js",
   "scripts": {

package/scripts/fetch-definitions.js

@@ -44,7 +44,7 @@ const DATA_DIR = join(PROJECT_ROOT, "data");
 //   3. `npm run fetch-definitions` and commit the data/ diff together with
 //      this pin in one commit
 // JSONUI_CLI_RAW_BASE still overrides the whole base URL for manual testing.
-const JSONUI_CLI_TAG = "v1.8.85";
+const JSONUI_CLI_TAG = "v1.8.101";
 const BASE_URL =
   process.env.JSONUI_CLI_RAW_BASE ||
   `https://raw.githubusercontent.com/Tai-Kimura/jsonui-cli/${JSONUI_CLI_TAG}`;