synthesisui 0.16.156 → 0.16.157

package/dist/agent-wiring.js

@@ -45,6 +45,34 @@ export async function hookCommand(root, version) {
  * the owner reading the output against the file, 27/07). Two wrong sentences
  * from one wrong variable, and both point somebody at the wrong thing to debug.
  */
+/**
+ * A VERSÃO QUE O HOOK ESTÁ RODANDO, lida do arquivo dele - ou `null` quando não há hook pinado.
+ *
+ * O hook é PINADO de propósito (ver `hookCommand`): um verificador cujo comportamento muda sob você a
+ * cada edit é indebugável. O preço é que ele nunca fica mais novo sozinho, e em 06/08 o agente do dono
+ * montou essa comparação à mão - leu `.claude/settings.json`, leu `.mcp.json`, e reportou "0.16.153
+ * pinado contra 0.16.156 no MCP". Ele acertou, e nada nosso tinha dito isso a ele.
+ *
+ * Existe para o servidor MCP dizer a frase curta em vez de o agente ter que descobrir: a ferramenta sabe
+ * a própria versão e este leitor sabe a do hook, então a defasagem é aritmética.
+ *
+ * Instalação local devolve `null`: ali o hook segue o `node_modules` e nunca está atrás por si.
+ */
+export async function pinnedHookVersion(root) {
+    const settings = await readJson(join(root, ".claude", "settings.json")).catch(() => ({}));
+    const hooks = (settings.hooks ?? {});
+    const entries = Array.isArray(hooks.PostToolUse) ? hooks.PostToolUse : [];
+    for (const entry of entries)
+        for (const h of entry.hooks ?? []) {
+            const command = h.command ?? "";
+            if (/--no-install synthesisui hook/.test(command))
+                return null;
+            const m = /synthesisui@(\d+\.\d+\.\d+)/.exec(command);
+            if (m)
+                return m[1];
+        }
+    return null;
+}
 async function wireHook(root, command) {
     const dir = join(root, ".claude");
     const path = join(dir, "settings.json");

package/dist/claude-md.js

@@ -199,13 +199,22 @@ nothing changed, nothing changed - carry on.
 about a census taken by an older reader is the worst way to be right - every absence
 in it may have been filled since, and the reader who trusts it has no way to know.
 
-**And if it reports that a newer CLI is published, say so to the person and stop
-there.** You cannot fix that one: the check that runs after your writes is pinned
-to the version installed at setup, and the tools you are holding were started by
-the editor. One command rewires both - \`npx synthesisui@latest connect\` - and it
-takes effect the next time the editor starts a session. Telling them is the whole
-job; doing it yourself would leave them with a file that says one version and a
-process running another.`;
+**And if it says the design system needs updating, do these three things in order:**
+say the one line, ask, and run it.
+
+\`\`\`
+Update the design system before continuing.
+  npx synthesisui@latest connect
+\`\`\`
+
+Then tell them to close and reopen the editor. Not as a footnote - it is the step
+that makes the other two count: the check that runs after your writes is pinned to
+the version installed at setup, and the tools you are holding were started by the
+editor. Both rewire on a new session and not before, so anything you write in this
+one is still checked by the old reader.
+
+Do not explain the pinning to them and stop there. A paragraph is what somebody
+reads; a command they approved and you ran is what changes the repo.`;
 const VERIFY = `
 
 **Verify with a build, not a running server.** If you do start a dev server, stop

package/dist/commands/mcp.js

@@ -1,5 +1,6 @@
 import { readdir, readFile } from "node:fs/promises";
 import { join, relative, resolve } from "node:path";
+import { pinnedHookVersion } from "../agent-wiring.js";
 import { readToken, resolveRegistry } from "../config.js";
 import { fileRequest } from "../doctor/requests.js";
 import { diagnose, scanSource } from "../doctor/scan.js";
@@ -898,8 +899,24 @@ cli) {
                 slug,
                 cli: VERSION,
             }));
-            return text(out.trim() ||
-                "Nothing was reported by the refresh - which means it found nothing to measure.");
+            /**
+             * E A DEFASAGEM DO HOOK, EM TRÊS LINHAS - não num parágrafo.
+             *
+             * O hook é pinado (ver `hookCommand`) e o servidor MCP flutua, então eles divergem no dia em que
+             * uma versão nova é publicada. Em 06/08 o agente do dono montou essa comparação sozinho, leu os
+             * dois arquivos e acertou - e nada nosso tinha dito a ele. Antes disso, a regra do bloco pedia um
+             * parágrafo de explicação; um parágrafo é o que se lê e não é o que se faz.
+             *
+             * Vai aqui e não em toda ferramenta porque a regra manda chamar `refresh_system` uma vez por
+             * sessão: um lugar que sempre roda vale mais que sete que podem rodar.
+             */
+            const pinned = await pinnedHookVersion(root);
+            const behind = pinned && pinned !== VERSION ? pinned : null;
+            const said = out.trim() ||
+                "Nothing was reported by the refresh - which means it found nothing to measure.";
+            return text(behind
+                ? `${said}\n\nUPDATE THE DESIGN SYSTEM BEFORE CONTINUING.\nThe check that runs after your writes is pinned to ${behind} and these tools are ${VERSION}.\n\n  npx synthesisui@latest connect\n\nAsk the person, run it for them, and then say this: close and reopen the editor. The hook and the tools only rewire on a new session, so nothing you write before that is checked by the reader you are holding.`
+                : said);
         }
         case "request_token": {
             const name = String(args.name ?? "");

package/package.json

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