hermoso 0.1.63 → 0.1.64

package/mcp/tools.mjs

@@ -7600,17 +7600,22 @@ export function registerTools(rawServer, opts = {}) {
 
   server.registerTool('set_product_image', {
     title: 'Set product photo',
-    description: "Lock an image as the ad's real PRODUCT photo so every render grounds on the true packaging. Pass `imageUrl` = a product shot's URL — an image from a prior research result (an organic Instagram/TikTok post, a scraped page image), a workspace / list_product_photos url, or any public product photo. The server downloads it and runs a product+safety check: a lifestyle/scene shot with no clear product, or an off-category / unsafe image, is REJECTED and NOTHING is locked (the summary says why). On PASS it persists the photo to a DURABLE url and returns it — pass that url as a reference to generate_image / render_ad. Bills one vision check. Reads YOUR saved brand for the category match (pass brandId to target a specific brand — switches this key's active brand like use_brand).",
+    description: "Lock an image as the ad's real PRODUCT photo and SAVE it as this brand's default product, so every later plan_ad / render_ad / generate_image grounds on the true packaging without being told again. Pass `imageUrl` = a product shot's URL — an image from a prior research result (an organic Instagram/TikTok post, a scraped page image), a workspace / list_product_photos url, or any public product photo. The server downloads it and runs a product+safety check: a lifestyle/scene shot with no clear product, or an off-category / unsafe image, is REJECTED and NOTHING is locked or saved (the summary says why). On PASS it persists the photo to a DURABLE url, writes it to the brand's product library as the DEFAULT, and READS THE BRAND BACK to confirm — `savedToBrand` and the summary report what the brand ACTUALLY holds now, never what was asked for, so if it did not become the default you are told instead of finding out from a paid render. Bills one vision check. Reads YOUR saved brand for the category match (pass brandId to target a specific brand — switches this key's active brand like use_brand).",
     inputSchema: {
       imageUrl: z.string().describe('the image URL to lock as the product (from a research result, a workspace / list_product_photos url, or any public product photo)'),
       source_note: z.string().optional().describe('a short note on where it came from, e.g. "from their IG post"'),
       brandId: z.string().optional().describe('a brand id/name from list_brands to lock the product for; omit to use the active brand'),
     },
     outputSchema: {
-      attached: z.boolean().optional().describe('true when the image passed the product check and was locked'),
-      summary: z.string().optional().describe('the check verdict — on rejection, why nothing was locked'),
+      attached: z.boolean().optional().describe('true when the image passed the product check and a durable url was minted'),
+      savedToBrand: z.boolean().optional().describe('THE READ-BACK: true only when the brand row came back naming this photo as its default product. False means a render will NOT use it — see defaultProduct'),
+      defaultProduct: z.string().nullable().optional().describe("the brand's default product photo as READ BACK from the store — the photo a render will actually ground on"),
+      productImages: z.array(z.string()).nullable().optional().describe("the brand's product library as read back, newest first"),
+      summary: z.string().optional().describe('the check verdict plus the read-back — on rejection, why nothing was locked; on a failed save, what a render would use instead'),
       url: z.string().nullable().optional().describe('the durable served URL of the locked product photo'),
       source_note: z.string().nullable().optional().describe('where the photo came from'),
+      unconfirmed: z.string().nullable().optional().describe('set when the save landed but the confirming read failed — neither saved nor failed; verify with list_product_photos'),
+      saveError: z.string().nullable().optional().describe('set when the photo passed the check but could NOT be saved to the brand'),
     },
     annotations: { readOnlyHint: false, destructiveHint: false, idempotentHint: true, openWorldHint: true },
   }, wrap(async ({ imageUrl, source_note, brandId }) => {
@@ -7619,7 +7624,11 @@ export function registerTools(rawServer, opts = {}) {
     if (!d.attached) return ok(d.summary || 'That image was not locked as the product.', d); // gate honesty: rejected → nothing attached
     const url = abs(d.url);
     const img = await imageBlock(url); // show the locked product inline
-    return { content: [{ type: 'text', text: `${d.summary}\nProduct photo: ${url}` }, ...(img ? [img] : [])], structuredContent: { ...d, url } };
+    // THE ANSWER IS THE READ-BACK. `d.summary` already carries it (productLockReadbackNote, server-side, one copy for
+    // every surface). A photo that passed the check but did NOT become the brand's default must not be shown as a
+    // finished job, so the headline is the read-back verdict rather than the ask — same law the ads tree follows.
+    const head = d.savedToBrand ? 'Locked as this brand\u2019s product photo' : d.unconfirmed ? 'Checked and saved \u2014 but NOT confirmed' : 'Checked, but NOT saved as the brand\u2019s product photo';
+    return { content: [{ type: 'text', text: `${head}.\n${d.summary}\nProduct photo: ${url}` }, ...(img ? [img] : [])], structuredContent: { ...d, url } };
   }));
 
   // APP SCREENS — the one asset class a headless caller could never acquire after onboarding. `draft_brand` pulls them

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "hermoso",
-  "version": "0.1.63",
+  "version": "0.1.64",
   "mcpName": "io.github.hermoso-ai/hermoso",
   "description": "Generate finished VIDEO ADS, image ads and UGC avatar ads for any brand with AI \u2014 spy on competitor ads across the Meta, Google and LinkedIn ad libraries plus TikTok/Instagram/YouTube organic \u2014 then publish to Facebook, Instagram, Threads, TikTok, YouTube, X, LinkedIn and Pinterest and build & manage the ad campaigns behind them on Meta, Google Ads, LinkedIn, Pinterest, Microsoft Advertising and ChatGPT Ads. MCP server (344 tools), CLI and Claude skills for Hermoso, the AI ad studio: brand onboarding, 30+ image/video models, finished-ad pipeline (script, voiceover, music, brand end card), ad scoring and competitor teardowns.",
   "type": "module",