synthesisui 0.16.139 → 0.16.140

package/dist/anatomy-read.js

@@ -65,9 +65,24 @@ const FRONTIERS = new Set(["component", "external"]);
  * its own box, because its styles already sit on the component's base.
  */
 const STRUCTURAL = /^(root|wrapper|base|el|outer)$/i;
-/** A pathological transcription of somebody's DOM, bounded. Six levels reaches
- *  any real component; past that it is layout divs all the way down. */
-const MAX_DEPTH = 6;
+/**
+ * A transcrição patológica do DOM de alguém, com teto - e o teto foi medido errado.
+ *
+ * "Seis níveis alcançam qualquer componente real; além disso são divs de layout até o fim" foi
+ * calibrado numa biblioteca de 36 componentes. Um app de 275 desmente: a leitura do
+ * `apps/web-dashboard` tem 64 nós além do 6, e a distribuição mostra que a cauda é fina e é
+ * CONTEÚDO (05/08):
+ *
+ *     nível  0    1    2    3    4    5    6    7   8  9
+ *     nós  923  935  871  609  405  231  139   50  12  2
+ *
+ * O que estava acontecendo com esses 64: `walk` retornava ali, então tudo abaixo do sexto nível era
+ * descartado em silêncio - a estrutura que o cliente escreveu, perdida sem uma linha de aviso.
+ *
+ * 10 cobre a população inteira com folga e mantém o teto contra recursão patológica, que é a razão
+ * de ele existir. Um número medido em vez de estimado.
+ */
+const MAX_DEPTH = 10;
 /**
  * The same ceiling the sketch measured, for the same reason.
  *

package/dist/skill-import.js

@@ -1189,6 +1189,21 @@ three biggest items so they know whether it is worth opening now.
 found in their code, a token that is not ramp-shaped, a name the document refused. Read them
 and pass on the ones that matter.
 
+**And the notes now judge YOUR reading, which nothing did before.** \`validate_recipes\` looks at
+the \`anatomy\` inside a recipe; the anatomy you author travels in \`reading.components[X].anatomy\`,
+and until 05/08 no one looked at it - so a note may name findings the batch validator never saw.
+Two kinds, and both are yours to act on:
+
+- **structure that does not survive the reader.** Nine of these landed on a real import, every one
+  the same shape: a \`button\` holding a \`stack\`. Only \`row\` and \`stack\` arrange, so the children are
+  hoisted out and become siblings - the nesting they wrote is gone. Fix it in the reading and send
+  again; the note tells you the component and the path.
+- **references pointing at components the system does not contain.** 215 of 660 on that same
+  import. This one is usually NOT a mistake of yours: their component composes something the gate
+  left out, or something outside the scope that was measured. Say the number to the person and name
+  the top few, because a specimen there draws the reference and nothing else - and if the missing
+  piece is central to their system, the answer is a wider \`--scope\`, not a rewritten reading.
+
 ### 6. Close the loop in their repo
 
 The system is only worth something once it governs the code it came from:

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "synthesisui",
-  "version": "0.16.139",
+  "version": "0.16.140",
   "description": "Bring SynthesisUI design systems into any project - tokens, typed components, whole pages and an agent-ready CLAUDE.md manifest.",
   "type": "module",
   "bin": {