synthesisui 0.16.153 → 0.16.155

package/dist/skill-init.js

@@ -32,20 +32,22 @@ visual, semantic and functional parity, without supposing and without inventing
 
 ## THE SHAPE OF THIS RUN, AND WHY IT IS THIS SHAPE
 
-Four questions, asked before anything that needs an answer. Then silence, then four lines.
+Five questions, asked before anything that needs an answer. Then silence, then four lines.
 
 \`\`\`
 1  environment      which agent they work in - and what that agent can actually get
 2  authorisation    may we optimise after importing, and which parts
 3  project          WHICH folder becomes the system (the only unavoidable choice)
 4  identity         name, primary, theme - each already answered by the census
+5  intent           adopting the system, or migrating design INTO it
+                    (+ where absorbed values live, only if they are migrating)
 ---- nobody waits from here on ----
-   import v1  ->  freeze v1  ->  apply what they authorised  ->  four lines
-5  offer            put the tokens back into their code
+   init  ->  import  ->  freeze  ->  apply what they authorised  ->  four lines
+6  offer            the two lines that wire it up
 \`\`\`
 
 **Every question is asked before the work, and the work starts during the questions.** A person who
-answers four things in ninety seconds and then watches one bar has had a good four minutes; the same
+answers five things in ninety seconds and then watches one bar has had a good four minutes; the same
 person interrupted twice mid-silence has had a bad twenty (dono, 01/08).
 
 **What runs in parallel, precisely.** The UNSCOPED census - \`npx synthesisui import --dry\` - needs no
@@ -161,6 +163,59 @@ in the \`sui-import-ds\` skill; do not reinvent it here, and do not ask anything
 
 ---
 
+## 5. INTENT
+
+The one question the census cannot answer, and the only one whose answer changes what a later command
+puts first.
+
+\`\`\`
+What are you doing with this system?
+
+  Adopting it (recommended)   make the code use the system. The doctor leads with the
+                              values your system already names - those have a one-line
+                              fix, and \`doctor --fix\` does them.
+  Migrating into it           you are moving design out of your apps and into the shared
+                              package. The doctor leads with the values your system does
+                              NOT name yet, by frequency - those are the tokens the
+                              library still has to absorb.
+\`\`\`
+
+Both lists exist in both modes. The answer decides the ORDER, and the order decides what somebody
+does first - measured on a real monorepo (dono, 06/08): with no intent declared, four of the five
+suggestions came out of a consumer app, led by a colour that does not belong to the system's palette
+at all. The same number is noise under one intent and the strongest candidate in the repo under the
+other.
+
+Pass the answer straight through:
+
+\`\`\`
+npx synthesisui@latest init --intent adopt      (or --intent migrate)
+\`\`\`
+
+**One follow-up, and ONLY when they chose migrating.** Absorbing is what a migration does; asking an
+adopter where absorbed values would go is asking about a command they will not run this month.
+
+\`\`\`
+When your system absorbs a value, where should it live?
+
+  In the system (recommended)   it becomes a token of the design system, and the
+                                tokens.css it generates starts emitting it
+  In your own CSS               we hand you the block and you paste it into your
+                                vocabulary; the next import reads it back as a
+                                token you declared
+\`\`\`
+
+Then \`--absorb system\` or \`--absorb code\` on the same \`init\`. Both answers are real: the second exists
+because in some teams the canonical vocabulary IS their stylesheet, and in that case our part is to hand
+over the snippet - never to write in their file.
+
+**Run \`init\` even when nothing else needs it.** It writes \`_synthesisui/config.json\` - the committed
+file that holds \`target\`, \`pagesDir\`, \`componentsDir\`, \`styles\` and this intent - and until 06/08 this
+run never called it: a full first run left no config at all, so \`template\` and \`component\` fell back to
+defaults and the intent had nowhere to live (dono, 06/08).
+
+---
+
 ## THE SILENT PART
 
 Now nobody is asked anything.
@@ -209,46 +264,46 @@ answers 400, and a 400 in a first run reads as a broken product.
 
 ---
 
-## 5. THE FOUR LINES
+## 6. THE FOUR LINES
 
-This is the whole point of the run. Four lines, their numbers, no adjectives.
+This is the whole point of the run, and **it is not yours to compose.** Run this and print nothing
+else:
 
 \`\`\`
-SignalUI is yours - 275 components and 92 of your own tokens, read out of packages/ui.
-
-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 v2 is one click: /dashboard/mine/signalui/publish
+npx synthesisui@latest summary <slug> --base <base> --draft <draft> --fixes <how many>
 \`\`\`
 
-**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.
+It prints their component count, their own token count, where the system was read from, the two
+versions with the way back, and the one thing to do next. The numbers for \`--base\` and \`--draft\` come
+from the \`optimize\` RESPONSE - never invented here, because the platform is what numbers a version.
 
-**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.
+**Why a command instead of four lines you write.** The last screen of this run has ended long, more
+than once - up to four hundred words, with three of its four paragraphs about the AGENT rather than
+about their system: notes from a previous session, a generator that had been deleted and rebuilt, a
+regression stripped by hand. Two of those notes were also out of date, which is worse than verbose: it
+warned somebody about defects that no longer existed (dono, 06/08).
 
-**What must always be there:** the count of their components, the count of their own tokens, and the
-way back.
+The pull to report your own work at the end of a long job beats a rule written sixty lines earlier. So
+the rule became a program. What you have in hand when the run ends - your notes, your retries, your
+repairs - has no way into a block that a command prints.
 
-## 6. THE OFFER
+**Anything you think belongs on that screen and is not in the command's output does not belong on that
+screen.** If it is a real finding, it is already in the report or in the causes screen; if it is about
+what you did, it is not theirs.
 
-One question, and only if there is something to offer - the doctor already knows the number.
+## 7. THE OFFER
 
-\`\`\`
-340 hand-written values in your code have a token in your system now.
-Want me to replace them? It only touches values your system names, and you read the diff.
+There is exactly one thing to offer, and it is not the fix: it is the two lines that wire the system
+up. Until a stylesheet imports the tokens and an element carries \`data-ds\`, none of the tokens reach
+the browser.
 
-    npx synthesisui@latest doctor --fix
-\`\`\`
+\`summary\` already prints both. Say nothing more about them.
 
-If the number is zero, say nothing. An offer with no subject is noise, and this run ends better
-short.
+**Never offer \`doctor --fix\` here.** It was offered for a while, with the number of values that have a
+token - and on an unwired project that swap points hundreds of literals at variables the browser
+cannot resolve, so the declarations are dropped and the page changes (dono, 06/08: 210 values, in a
+project where neither line was in place). The doctor itself now refuses in that state, and it is the
+right place for the offer: it can see the wiring, and this run cannot see what they do after it ends.
 
 ---
 
@@ -261,6 +316,10 @@ short.
 - **Never applies an optimisation without a frozen v1**, and never reports one without the way back.
 - **Never claims parity between agents.** The post-write check exists in one of them. Saying
   otherwise is the kind of sentence that ends a trial.
-- **Never ends long.** If the last screen needs scrolling, the run failed at the last step.
+- **Never ends long.** If the last screen needs scrolling, the run failed at the last step. The last
+  screen is \`summary\`'s output and nothing else - see section 6 for why that stopped being a rule and
+  became a command.
+- **Never offers a fix that the wiring blocks.** A swap to tokens that do not reach the browser
+  changes the page, and it would be our command that changed it.
 `;
 export const INIT_SKILL_PATH = ".claude/skills/sui-init/SKILL.md";

package/package.json

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