@slatesvideo/shared 0.5.4 → 0.5.6

package/dist/prompts/reference-rules.d.ts

@@ -20,8 +20,25 @@ export declare const IDENTITY_LIGHTING = "flat, even, shadowless lighting";
  * crushes hair and wardrobe silhouettes.** A deep neutral grey holds both.
  */
 export declare const IDENTITY_PLATE_HEX = "#3a3a3c";
-export declare const IDENTITY_BACKGROUND = "a plain, deep neutral-grey background (#3a3a3c)";
-export declare const IDENTITY_LIGHTING_CLAUSE = "Render on a plain, deep neutral-grey background (#3a3a3c) with flat, even, shadowless lighting so the sheet captures the character's identity, not scene lighting.";
+/**
+ * 🚨 THE HEX IS EMITTED WITHOUT ITS `#` AND THAT IS LOAD-BEARING (2026-07-30).
+ *
+ * `#` is a REFERENCE-TOKEN SIGIL in the desktop's prompt composer
+ * (`slate/src/shared/promptComposition.ts` — `/([@#])([\w-]+)/g`), and an
+ * unresolved `#token` is SILENTLY DELETED. So `#3a3a3c` never survived to any
+ * model: fal echoed back `deep neutral-grey background ()` on a real 2026-07-30
+ * request. The plate value has been doing nothing since the composer shipped.
+ *
+ * Writing it bare keeps the value in the prompt. `IDENTITY_PLATE_HEX` keeps its
+ * `#` because it is a colour constant and may have non-prompt consumers.
+ *
+ * GENERAL RULE FOR THIS FILE: never emit `#` or `@` into prompt text. Both are
+ * sigils downstream and both mangle silently — no error, no log, just missing
+ * words. HOW YOU'D KNOW THIS IS BEATEN: the composer stops treating bare
+ * `#hex` as a token, or starts leaving unresolved tokens intact.
+ */
+export declare const IDENTITY_BACKGROUND: string;
+export declare const IDENTITY_LIGHTING_CLAUSE: string;
 /**
  * Craft clauses every identity reference wants — the eye and skin detail that
  * survives downstream, plus the two "reads literally" guards. Crushed-black

package/dist/prompts/reference-rules.js

@@ -30,9 +30,9 @@ export const REFERENCE_RULES = [
     },
     {
         id: 'identity-name-as-one-entity',
-        title: 'One identity sheet per character — NAME whatever you attach as one entity',
-        rule: 'Attach the character\'s single identity sheet (dominant portrait + body panels) rather than a pile of views — fewer competing renderings of a face is always better, because the model cannot tell which is authoritative and averages them. When a character DOES carry a second bound sheet (an explicit expression range, or a legacy turnaround+expression pair), NAME both inline as the SAME subject ("Marcus (images 1 and 2)") — that shared name is what tells the model they are ONE person. Do NOT inject a role essay ("use for identity, ignore the outfit/lighting, render neutral"): the user\'s prompt owns wardrobe, expression, and lighting.',
-        why: 'Naming both images as one entity IS each model\'s OWN official consistency lever — NB2 "assign a distinct name to each character/object"; Seedance "Reference <Subject_N> in <Image_N>"; Kling "reuse a fixed label verbatim". The old heavy role-essay was the OFF-doctrine part: telling the model to "use for identity" while injecting "ignore the outfit" dragged the studio-lit sheet\'s wardrobe + lighting into scenes that explicitly wanted otherwise (the movie-still injection failure). The close-ups still carry far more facial signal (eyes, skin, teeth, bone structure) than a turnaround\'s postage-stamp faces, so attach both — the NAME, not an instruction, is what makes many refs work. The trend is MORE references (video/audio/3D into Seedance-class models), all addressed by name.',
+        title: 'One identity sheet per character, named inline',
+        rule: 'Attach the character\'s single identity sheet (dominant portrait + body panels) rather than a pile of views — fewer competing renderings of a face is better, because the model cannot tell which is authoritative and averages them. Cite it inline as the subject ("Marcus (image 1)"). Do not inject a role essay ("use for identity, ignore the outfit/lighting, render neutral"): the user\'s prompt owns wardrobe, expression, and lighting.',
+        why: 'Distinct inline naming is each model\'s own consistency lever — NB2 "assign a distinct name to each character/object"; Seedance "Reference <Subject_N> in <Image_N>"; Kling "reuse a fixed label verbatim". One canonical identity image removes same-role competition before it starts.',
         grade: 'Eric-test',
     },
     {
@@ -96,7 +96,24 @@ export const IDENTITY_LIGHTING = 'flat, even, shadowless lighting';
  * crushes hair and wardrobe silhouettes.** A deep neutral grey holds both.
  */
 export const IDENTITY_PLATE_HEX = '#3a3a3c';
-export const IDENTITY_BACKGROUND = `a plain, deep neutral-grey background (${IDENTITY_PLATE_HEX})`;
+/**
+ * 🚨 THE HEX IS EMITTED WITHOUT ITS `#` AND THAT IS LOAD-BEARING (2026-07-30).
+ *
+ * `#` is a REFERENCE-TOKEN SIGIL in the desktop's prompt composer
+ * (`slate/src/shared/promptComposition.ts` — `/([@#])([\w-]+)/g`), and an
+ * unresolved `#token` is SILENTLY DELETED. So `#3a3a3c` never survived to any
+ * model: fal echoed back `deep neutral-grey background ()` on a real 2026-07-30
+ * request. The plate value has been doing nothing since the composer shipped.
+ *
+ * Writing it bare keeps the value in the prompt. `IDENTITY_PLATE_HEX` keeps its
+ * `#` because it is a colour constant and may have non-prompt consumers.
+ *
+ * GENERAL RULE FOR THIS FILE: never emit `#` or `@` into prompt text. Both are
+ * sigils downstream and both mangle silently — no error, no log, just missing
+ * words. HOW YOU'D KNOW THIS IS BEATEN: the composer stops treating bare
+ * `#hex` as a token, or starts leaving unresolved tokens intact.
+ */
+export const IDENTITY_BACKGROUND = `a plain, deep neutral-grey background (hex ${IDENTITY_PLATE_HEX.replace('#', '')})`;
 export const IDENTITY_LIGHTING_CLAUSE = `Render on ${IDENTITY_BACKGROUND} with ${IDENTITY_LIGHTING} so the sheet captures the character's identity, not scene lighting.`;
 /**
  * Craft clauses every identity reference wants — the eye and skin detail that