What is the problem or goal you're trying to solve or accomplish?
API consumers, and especially AI agents, need to build valid dashboard layouts, including tabs. Nothing tells them which parent/child combinations are allowed (for example, that a TAB takes ROW/COLUMN/MARKDOWN/HEADER/DIVIDER/TABS, never GRID). They don't know which fields are required either (parents chain, meta.text, DASHBOARD_VERSION_KEY).
How are you solving it currently?
Guessing the structure, or copying from exports of UI-built dashboards.
What is your recommended solution?
Document the exact required schema for TABS nodes ( component IDs, meta fields, nesting rules ) so API consumers can build them correctly.