synthesisui 0.16.145 → 0.16.147

package/dist/skill-import.js

@@ -172,6 +172,16 @@ file to pick between. Nothing is sent by \`--dry\`. Read the file.
 
 ### 2. Walk them through the decisions - ALL of them, before any reading
 
+**WHEN \`sui-init\` SENT YOU HERE, THESE ARE ALREADY ANSWERED. Ask nothing.**
+
+The first-run skill collects source, name, primary, theme, canvas, architecture and \`standards\`
+before it hands over, precisely so this step is silent. Asking again is not thoroughness - it is the
+same six questions twice in one conversation, which reads as a tool that forgot what it was told, and
+it is the single fastest way to make a first run feel long. Take the answers, skip to step 3, and
+confirm nothing.
+
+If any of them is missing from the handover, ask ONLY that one.
+
 **Every question this skill asks is answerable from the census you just took.** Source, name,
 primary, theme, canvas, architecture - the numbers behind all six are in the file on their disk,
 and none of them needs the anatomy.

package/dist/skill-init.js

@@ -150,13 +150,34 @@ in the \`sui-import-ds\` skill; do not reinvent it here, and do not ask anything
 
 ## THE SILENT PART
 
-Now nobody is asked anything. In order:
+Now nobody is asked anything.
 
+**Steps 1 to 3 are NOT described here. Invoke the \`sui-import-ds\` skill and let it drive them.**
+
+That skill owns the import: the double measurement and why a library measured alone reports no laws,
+the \`--scope\` versus \`--usage\` split and the two mistakes it exists to prevent, the whole shape of the
+reading - anatomy, rules with \`kind\`/\`applies\`/\`fact\`, \`typeRoles\`, themes read from the switch rather
+than from the palette - the single batched \`validate_recipes\` call, and what to do with a 401. It is
+over a thousand lines of specifics, every one of them paid for by something that went wrong.
+
+Paraphrasing three of those lines here is how the two files start describing different pipelines, and
+the paraphrase always loses: an agent following a summary does a shallow import and nobody can see
+which document was wrong. So this skill asks the questions and hands the answers over:
+
+\`\`\`
+Invoke: sui-import-ds
+Already decided, do not ask again:
+  source   <the folder they picked in question 3>
+  usage    <the apps the CLI named, if any>
+  name · primary · theme · canvas · architecture   <what they answered in question 4>
+  standards   none, if they have a component library of their own
+Then come back here for step 4.
 \`\`\`
-1  npx synthesisui import --scope <theirs> --usage <apps…>     measures with the answers
-2  the reading                                                  anatomy, rules, roles
-3  send it                                                      their v1 exists
-4  POST /api/registry/ds/<slug>/optimize                        freeze v1, apply what they said yes to
+
+Then, and only then, the part that belongs to this skill:
+
+\`\`\`
+4  POST /api/registry/ds/<slug>/optimize      freeze v1, apply what they authorised
        { "categories": ["tokens", "spacing", "typography"] }
 \`\`\`
 
@@ -182,13 +203,19 @@ This is the whole point of the run. Four lines, their numbers, no adjectives.
 \`\`\`
 SignalUI is yours - 275 components and 92 of your own tokens, read out of packages/ui.
 
-v1 is frozen: your system exactly as your code has it today. It never moves.
-v2 is what you are looking at - the same system with 118 deterministic fixes: contrast on
+v2 is frozen: your system exactly as your code has it today. It never moves.
+v3 is what you are looking at - the same system with 118 deterministic fixes: contrast on
 text only, lengths onto your own scale, near-identical colours unified.
 
-Back to v1 is one click: /dashboard/mine/signalui/publish
+Back to v2 is one click: /dashboard/mine/signalui/publish
 \`\`\`
 
+**THE VERSION NUMBERS COME FROM THE RESPONSE, NEVER FROM THIS EXAMPLE.** \`optimize\` answers with
+\`base\` and \`draft\`, and those are the two numbers to print. Writing "v1" here would have been wrong:
+a system already publishes its baseline at birth, so an import writes into v2 and the freeze produces
+v3. Proved against production before this skill ever ran (05/08) - and a first screen that points at
+the wrong version to restore is worse than no version at all.
+
 **What must never be in those lines:** how many files we scanned, how long it took, which readers
 ran, what the ledger says. All of that is in the report and none of it is what somebody wants in the
 first minute of owning a system.

package/package.json

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