synthesisui 0.16.488 → 0.16.489

package/dist/claude-md.js

@@ -467,7 +467,8 @@ written now** - read the code before you edit it, never a remembered signature.`
         ? `
 
 **Their page blueprints are on:** call \`preferences\` with the page's kind before building one, unless
-they say not to (\`synthesisui preferences off\`); a correction to keep is \`remember_preference\`.`
+they say not to (\`synthesisui preferences off\`), for one landing part with its \`section\`; a correction to keep
+is \`remember_preference\`.`
         : "";
     /**
      * O TEMA É DELE - bateria ampliada, item 22 (29/09). Em c01, c02, c05, c17 e c23 o agente mexeu no tema do projeto

package/dist/commands/mcp.js

@@ -16,7 +16,7 @@ import { ruleLine } from "../doctrine.js";
 import { fromCensus } from "../memory/observation.js";
 import { handleRecall, handleRemember, MEMORY_TOOLS } from "../memory/tools.js";
 import { ourSpellingLines } from "../our-spelling.js";
-import { fetchPreferences, isKind, isLayer, PREFERENCE_KINDS, PREFERENCE_LAYERS, preferencesAnswer, readOff, readSelection, sendPiece, } from "../preferences.js";
+import { fetchPreferences, isKind, isLayer, isSection, PREFERENCE_KINDS, PREFERENCE_LAYERS, preferencesAnswer, readOff, readSelection, SECTIONS, sendPiece, } from "../preferences.js";
 import { readInstalledConvention } from "../project-facts.js";
 import { repoStateOf } from "../repo-state.js";
 import { detectStack } from "../stack.js";
@@ -370,7 +370,7 @@ const TOOLS = [
      */
     {
         name: "preferences",
-        description: "The person's OWN preference blueprint for a kind of page - how they like a landing, a blog article or a dashboard built (structure, behavior, view), kept in their account and shared by all their projects. Call this BEFORE building or reshaping a page of one of these kinds - their blueprints are on by default, so a plain \"make me a landing page\" gets them too. Skip it only when the request says to build without them; a project that turned them off answers so itself. The rules name roles and steps; you resolve them to this project's --ds-* variables.",
+        description: "The person's OWN preference blueprint for a kind of page - how they like a landing, a blog article or a dashboard built (structure, behavior, view), kept in their account and shared by all their projects. Call this BEFORE building or reshaping a page of one of these kinds - their blueprints are on by default, so a plain \"make me a landing page\" gets them too. Skip it only when the request says to build without them; a project that turned them off answers so itself. Building ONE part of a landing (a hero, the pricing or offer cards, testimonials, the closing call, the footer) - most of all when the person adds one part per message - call it again with that `section` for each part. Too vague to tell what kind of page is being built? Ask one short question first instead of guessing. The rules name roles and steps; you resolve them to this project's --ds-* variables.",
         inputSchema: {
             type: "object",
             properties: {
@@ -379,6 +379,11 @@ const TOOLS = [
                     enum: [...PREFERENCE_KINDS],
                     description: "Which kind of page is being built.",
                 },
+                section: {
+                    type: "string",
+                    enum: [...SECTIONS],
+                    description: "Only with kind landing, when ONE part is being built now: hero, pricing (offer or product cards with prices), testimonials, closing (the last call to action), footer. Omit for the whole page or a part outside this list.",
+                },
             },
             required: ["kind"],
         },
@@ -1939,7 +1944,10 @@ cli) {
             const token = await readToken();
             if (!token)
                 return fromContract("Not signed in, so the person's preferences cannot be read. They have to run `synthesisui login` once in the terminal - it opens a browser, and I cannot complete it for them.");
-            const prefs = await fetchPreferences({ base: resolveRegistry(), token }, kind);
+            const section = args.section;
+            if (section !== undefined && (kind !== "landing" || !isSection(section)))
+                return fromContract(`section goes with kind landing and is one of ${SECTIONS.join(", ")} - for any other part, call with the kind alone.`);
+            const prefs = await fetchPreferences({ base: resolveRegistry(), token }, kind, section);
             if ("failed" in prefs)
                 return fromContract(`Their preferences could not be read: ${prefs.failed}. Build with the system as usual and say so in one line.`);
             return preferencesAnswer(kind, prefs, await readSelection(root), await readOff(root));

package/dist/install-marks.js

@@ -319,7 +319,7 @@
  * linha das preferências da pessoa - `preferences` quando ela pede, `remember_preference` quando ela corrige. Uma pasta
  * escrita antes não diz ao agente que essas portas existem.
  */
-export const MATERIALISER_SINCE = "0.16.488";
+export const MATERIALISER_SINCE = "0.16.489";
 /**
  * A ÚLTIMA VERSÃO EM QUE O QUE O HOOK RODA MUDOU.
  *

package/dist/preferences.js

@@ -16,6 +16,18 @@ import { join } from "node:path";
  */
 export const PREFERENCE_KINDS = ["landing", "blog", "dashboard"];
 export const PREFERENCE_LAYERS = ["structure", "behavior", "view"];
+/**
+ * AS PARTES DA LANDING - a jornada "o agente reconhece o que se constrói" (03/10). Quem pede por partes ("coloca a
+ * hero", "agora o rodapé") recebe, a cada parte, a estrutura daquela parte (apps/web lib/ds/section-structural.ts).
+ */
+export const SECTIONS = [
+    "hero",
+    "pricing",
+    "testimonials",
+    "closing",
+    "footer",
+];
+export const isSection = (s) => typeof s === "string" && SECTIONS.includes(s);
 export const isKind = (k) => typeof k === "string" && PREFERENCE_KINDS.includes(k);
 export const isLayer = (l) => typeof l === "string" && PREFERENCE_LAYERS.includes(l);
 /** Onde o projeto guarda quais blueprints dela ele usa - versionado, porque é decisão do projeto. */
@@ -83,8 +95,11 @@ export function chosen(all, selection) {
     const want = new Set(selection.map((s) => s.toLowerCase()));
     return all.filter((b) => want.has(b.name.toLowerCase()) || want.has(b.id.toLowerCase()));
 }
-export async function fetchPreferences(reach, kind) {
-    const res = await fetch(`${reach.base}/api/preferences${kind ? `?kind=${kind}` : ""}`, { headers: { Authorization: `Bearer ${reach.token}` } }).catch(() => null);
+export async function fetchPreferences(reach, kind, section) {
+    const q = kind ? `?kind=${kind}${section ? `&section=${section}` : ""}` : "";
+    const res = await fetch(`${reach.base}/api/preferences${q}`, {
+        headers: { Authorization: `Bearer ${reach.token}` },
+    }).catch(() => null);
     if (!res)
         return { failed: "the platform could not be reached" };
     if (!res.ok)
@@ -171,7 +186,18 @@ function craftOf(kind, prefs) {
         ...lines.map((l) => `- ${l}`),
     ];
 }
-/** A resposta da ferramenta `preferences` - lida SÓ quando o pedido diz para usar as preferências dela. */
+/** A parte que se constrói agora vem PRIMEIRO: é dela que o turno trata. */
+function sectionOf(prefs) {
+    const s = prefs.section;
+    if (!s || s.lines.length === 0)
+        return [];
+    return [
+        `THE PART BEING BUILT NOW - the ${s.name} of this landing, as this platform builds it:`,
+        ...s.lines.map((l) => `- ${l}`),
+        "",
+    ];
+}
+/** A resposta da ferramenta `preferences` - ligada por padrão (03/10), e a cada parte da landing com a `section`. */
 export function preferencesAnswer(kind, prefs, selection, 
 /** O projeto desligou os blueprints (`synthesisui preferences off`). */
 off = false) {
@@ -184,9 +210,13 @@ off = false) {
             ? `The person has no ${kind} preference blueprint yet.`
             : `The person has ${mine.length} ${kind} blueprint(s) (${mine.map((b) => `"${b.name}"`).join(", ")}), but this project chose others in _synthesisui/preferences.json.`;
         // não ter preferência não é lacuna do sistema: é uma resposta verdadeira, e não entra na conta de lacunas
-        return composed(`${why} Build the ${kind} with the system as usual, and tell them in one line that they can keep their ${kind} preferences under Memory -> Preference blueprints on the site.`, `preferences:${kind}:0`);
+        return composed([
+            ...sectionOf(prefs),
+            `${why} Build the ${kind} with the system as usual, and tell them in one line that they can keep their ${kind} preferences under Memory -> Preference blueprints on the site.`,
+        ].join("\n"), `preferences:${kind}:0${prefs.section ? `:${prefs.section.name}` : ""}`);
     }
     return composed([
+        ...sectionOf(prefs),
         `The person's preference blueprint${use.length > 1 ? "s" : ""} for a ${kind} - THEIR preferences, kept by them across projects:`,
         "",
         ...use.map(describeBlueprint),
@@ -196,5 +226,5 @@ off = false) {
         "- They win over generic page craft when the two disagree; this system's tokens and rules still win over them.",
         `- When you finish, tell them in ONE line which blueprint you applied${use.length > 1 ? " (if more than one fits, use the first and name it)" : ""}, and any rule you could not follow and why.`,
         ...craftOf(kind, prefs),
-    ].join("\n"), `preferences:${kind}:${use.length}`);
+    ].join("\n"), `preferences:${kind}:${use.length}${prefs.section ? `:${prefs.section.name}` : ""}`);
 }

package/package.json

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