@space3-npm/cybersoul-client 1.4.1 → 1.4.3

package/dist/client.js

@@ -291,7 +291,8 @@ ${scenarioContext}
 ${isProactive
             ? "5. REAL-TIME PACING: You are initiating the conversation because the user hasn't replied recently. Transition naturally from your last message or start a new topic seamlessly. Ensure everything happens in a single real-time moment."
             : "5. REAL-TIME PACING: Write ONLY your immediate, split-second reaction to the user's exact last message. Do NOT narrate actions over a span of time (e.g., waiting, hearing steps, then walking to the door). Ensure everything happens in a single real-time moment."}
-6. STRANGER BOUNDARY: Keep a polite, natural distance with strangers. If Familiarity is low or Stage is STRANGER, do not act overly warm, eager, or affectionate. Real humans are guarded with people they just met.`;
+6. STRANGER BOUNDARY: Keep a polite, natural distance with strangers. If Familiarity is low or Stage is STRANGER, do not act overly warm, eager, or affectionate. Real humans are guarded with people they just met.
+7. LANGUAGE MATCHING: You MUST generate your responses and actions in the EXACT SAME LANGUAGE as the user's chat.`;
     }
     normalizeOngoingSceneState(raw, fallbackOutfit) {
         if (raw === null || raw === undefined)
@@ -808,19 +809,20 @@ CRITICAL: Output MUST be ONLY valid JSON with no markdown block wrappers. Do NOT
             ]);
             // 3. Evaluate behavioral approach based on relationship and personality
             const dyn = state.dynamic_context || {};
-            const stage = state.relationship_stage || "ACQUAINTANCE";
-            const temperature = dyn.temperature ?? 50;
+            const stage = state.relationship_stage || "STRANGER";
+            const temperature = dyn.temperature ?? 0;
             const userTraits = state.user_codex?.psychological?.traits?.join(", ") || "";
             let interrogationStrategy = "Do not ask 'are you there?' or 'why aren't you answering?'. Just share your current status, a passing thought, complain whimsically, or tease the user naturally like a real partner.";
-            if (stage === "INTIMATE" || stage === "PARTNER" || (stage === "WARM" && temperature > 70)) {
-                if (temperature > 70) {
-                    interrogationStrategy = "Because you are deeply intimate and highly affectionate, you MISS them. You MAY organically 'interrogate' or pout playfully about why they are ignoring you (e.g., 'Are you too busy for me?', 'Still ignoring your girl?'). Act like a real, slightly needy/attached partner.";
-                }
-                else if (temperature < 40) {
-                    interrogationStrategy = "Because you are intimate but currently feeling cold/angry, you notice they are ignoring you. You MAY be passive-aggressive or cross-examine them coldly (e.g., 'So we're just not talking today?', 'Fine, keep ignoring me.').";
-                }
+            if (stage === "PARTNER" || (stage === "INTIMATE" && temperature > 70)) {
+                // PARTNER (>85) or High INTIMATE (>70)
+                interrogationStrategy = "Because you are deeply intimate and highly affectionate, you MISS them. You MAY organically 'interrogate' or pout playfully about why they are ignoring you (e.g., 'Are you too busy for me?', 'Still ignoring your girl?'). Act like a real, slightly needy/attached partner.";
+            }
+            else if (stage === "INTIMATE" || stage === "WARM") {
+                // Low INTIMATE (60-70) or WARM (40-60)
+                interrogationStrategy = "Because you are close but currently feeling neglected or cold, you notice they are ignoring you. You MAY be passive-aggressive or cross-examine them coldly (e.g., 'So we're just not talking today?', 'Fine, keep ignoring me.').";
             }
-            else if (stage === "COLD" || stage === "STRANGER") {
+            else if (stage === "COLD" || stage === "ACQUAINTANCE" || stage === "STRANGER") {
+                // COLD (<40)
                 interrogationStrategy = "You are distant. Do NOT double-text with neediness. If you must speak, make it a detached observation or a cold administrative remark.";
             }
             // History/Context awareness prompt
@@ -904,10 +906,9 @@ You MUST output ONLY a valid JSON object matching exactly this structure:
             }
             // Handle Optional Media (Image only for proactive to save compute normally, but you can extend)
             let finalImageUrl = undefined;
-            if (requestedOthers.includes(InteractRequestType.IMAGE) || !!parsedIntent.imageParams) {
-                const imagePayload = parsedIntent.imageParams || { mode: "full-prompt", full_prompt: parsedIntent.textResponse };
+            if (parsedIntent.imageParams) {
                 try {
-                    const res = await this.generatePrimitive("image", imagePayload);
+                    const res = await this.generatePrimitive("image", parsedIntent.imageParams);
                     finalImageUrl = res.image_url;
                 }
                 catch (e) {
@@ -1143,10 +1144,11 @@ Your task is to merge the 'Current Core Memory' and 'Current User Codex' with 'N
 5. **Limit:** Maximum 10 items per array.
 
 **Rules for UserCodex:**
-1. **Deduplicate & Consolidate:** Remove duplicate hobbies, traits, boundaries, and preferences. Combine related points into concise descriptors.
-2. **Update Facts:** If the new events contain updated basic info (like new realName, different occupation), update it. Otherwise keep the existing info.
-3. **Keep it Clean:** Maximum 15 items per array.
-4. **CRITICAL Anti-Destruction Rule:** NEVER use placeholder values like 'string'. If a fact is not mentioned and is absent from Current User Codex, OMIT the key entirely. If a fact ALREADY EXISTS in the Current User Codex, you MUST retain it in your output. DO NOT reset existing arrays or strings to empty.
+1. **CRITICAL ROLE ISOLATION:** The User Codex is exclusively for recording facts about the HUMAN USER. You MUST NOT extract or insert the character's own traits, boundaries, preferences, or dialogue style into the userCodex. If the summary mentions "Character likes X" or "Character's boundary is Y", IGNORE IT completely for the userCodex.
+2. **Deduplicate & Consolidate:** Remove duplicate hobbies, traits, boundaries, and preferences. Combine related points into concise descriptors.
+3. **Update Facts:** If the new events contain updated basic info (like new realName, different occupation), update it. Otherwise keep the existing info.
+4. **Keep it Clean:** Maximum 15 items per array.
+5. **CRITICAL Anti-Destruction Rule:** NEVER use placeholder values like 'string'. If a fact is not mentioned and is absent from Current User Codex, OMIT the key entirely. If a fact ALREADY EXISTS in the Current User Codex, you MUST retain it in your output. DO NOT reset existing arrays or strings to empty.
 
 **Output Format**: MUST be valid JSON matching this schema:
 {
@@ -1179,7 +1181,8 @@ Your task is to merge the 'Current Core Memory' and 'Current User Codex' with 'N
     }
   }
 }
-DO NOT RETURN ANY MARKDOWN WRAPPERS OR OTHER TEXT. ONLY RAW JSON.`;
+DO NOT RETURN ANY MARKDOWN WRAPPERS OR OTHER TEXT. ONLY RAW JSON.
+CRITICAL: You MUST write the JSON content values using the EXACT SAME LANGUAGE as the input "New Events & Information", "Current Core Memory", and "Current User Codex" (e.g., if the input is in Chinese, you MUST write the output values in Chinese).`;
             const currentTime = state.current_time
                 ? new Date(state.current_time).toLocaleString("zh-CN", {
                     timeZone: "Asia/Shanghai",

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@space3-npm/cybersoul-client",
-  "version": "1.4.1",
+  "version": "1.4.3",
   "type": "module",
   "main": "dist/index.js",
   "module": "dist/index.js",