[
  {
    "path": "load/loading-1.svg",
    "registry_name": "action/loading",
    "visual_signature": "open circular arc (loading ring with a gap), rotates in component",
    "affordance_category": "informational",
    "synonyms_en": [
      "loading",
      "spinner",
      "progress",
      "busy",
      "in progress"
    ],
    "synonyms_zh": [
      "加载中",
      "等待",
      "进行中"
    ],
    "when_to_use": "indicate an in-flight async operation; e.g. button spinner during form submit, table loading state",
    "notes": "manifest tags ['spinner','progress']. Classified informational despite manifest category 'action' — visually a status indicator, not a user-triggered action.",
    "figma_component_key": "fc410f9dfa5596a8f044e02649deef2d76372514",
    "figma_name": "icon/load/loading 1",
    "figma_node_id": "1202:4100"
  },
  {
    "path": "load/loading-2.svg",
    "registry_name": "action/loading-2",
    "visual_signature": "twelve-spoke radial spinner made from short bars around a center point",
    "affordance_category": "informational",
    "synonyms_en": [
      "loading",
      "spinner",
      "progress",
      "busy",
      "processing",
      "in progress"
    ],
    "synonyms_zh": [
      "加载中",
      "等待",
      "处理中",
      "进行中"
    ],
    "when_to_use": "indicate an in-flight async operation when a denser radial spinner is preferred; e.g. loading button, panel refresh, or async table state",
    "notes": "cross-category-override: action. SVG is visually identical to existing done registry action/loading (icon/load/loading 1 raw IconLoading), so propose action/loading-2 to keep load spinner family beside existing action/loading rather than splitting into status/loading-2.",
    "figma_component_key": "50a9f3342c9cc38646e7101402920d4740ed1816",
    "figma_name": "icon/load/loading 2",
    "figma_node_id": "1202:4149"
  },
  {
    "path": "load/refresh.svg",
    "registry_name": "action/refresh",
    "visual_signature": "clockwise circular arrow wrapping around an implied loop, with arrowhead at upper right",
    "affordance_category": "action",
    "synonyms_en": [
      "refresh",
      "reload",
      "retry",
      "sync",
      "update",
      "re-fetch"
    ],
    "synonyms_zh": [
      "刷新",
      "重新加载",
      "重试",
      "同步",
      "更新"
    ],
    "when_to_use": "trigger reloading, retrying, or synchronizing data; e.g. refresh list, retry failed fetch, or resync status",
    "notes": "cross-category-override: action. Although source folder is load and batch default is status, the glyph is a command affordance (refresh/retry) rather than a passive state indicator.",
    "figma_component_key": "6a3fadaf85377a5417eb53ea0eb3acb4baa9b67e",
    "figma_name": "icon/load/refresh",
    "figma_node_id": "1202:4182"
  },
  {
    "path": "load/wait.svg",
    "registry_name": "status/wait",
    "visual_signature": "wait indicator shaped like a small cup or timer-like container with a handle and baseline",
    "affordance_category": "informational",
    "synonyms_en": [
      "wait",
      "waiting",
      "pending",
      "standby",
      "queued",
      "hold"
    ],
    "synonyms_zh": [
      "等待",
      "待处理",
      "排队中",
      "待命",
      "暂停等待"
    ],
    "when_to_use": "communicate a waiting, pending, or queued state without implying user-triggered refresh; e.g. delayed job, standby state, or queued operation",
    "notes": "Uses batch default status because the glyph communicates a passive wait/pending state. Low confidence: visual resembles a cup/timer hybrid, so user should confirm the intended affordance before Phase C merge.",
    "figma_component_key": "a93c330788866aa910ba757aac86baec8c14349c",
    "figma_name": "icon/load/wait",
    "figma_node_id": "1202:4239"
  }
]