@space3-npm/cybersoul-client 1.4.27 → 1.4.29

package/dist/client.d.ts

@@ -59,6 +59,14 @@ export declare class CyberSoulClient {
      * If the payload is already the inner args object (no voiceArgs wrapper), uses it as-is.
      */
     private extractVoiceArgsFromLlmResponse;
+    /**
+     * Returns the platform-wide compliance boundary directive string sourced
+     * from the backend character state (PromptSegment key="COMPLIANCE_RULE").
+     * Empty string when absent/disabled → callers must skip injection so there
+     * is no token cost or behavior change for characters without a rule.
+     * Mirrors the backend→state→prompt flow used for voice directives.
+     */
+    private getComplianceDirective;
     /**
      * Strip content the TTS engine can't speak naturally:
      *   - Stage-direction wrappers like (smiles), （挑眉）, [pauses], 【动作】, *grins*
@@ -173,9 +181,31 @@ export declare class CyberSoulClient {
      * Can be triggered by local Cron systems like OpenClaw.
      */
     generateDailyScript(): Promise<void>;
+    /**
+     * Builds a focused identity/relationship context block for the history
+     * summarizer. This is a lighter-weight counterpart to
+     * [buildStateContextPrompt]: it skips the roleplay/director rules (the
+     * summarizer is not roleplaying, it is *archiving*) but carries the
+     * same identity anchors so the LLM can never confuse who the character
+     * is vs. who the user is.
+     *
+     * Why this exists: the previous `summarizeHistory` prompt only injected
+     * `${agentName}` / `${userName}` (the nicknames the two parties call
+     * each other). With no real identity, age, gender, personality, or
+     * relationship context, the LLM frequently flipped the perspective —
+     * writing the journal *about* the character *from* the user's POV, or
+     * attributing the user's words to the character. Mirroring the same
+     * identity fields `interact()` exposes eliminates that ambiguity.
+     */
+    private buildSummarizerContextBlock;
     /**
      * Automatically detect and summarize the story from the current chat history.
      * It takes raw message history and returns a narrative paragraph representing the current story segment.
+     *
+     * The summary is ALWAYS written from the CHARACTER's first-person perspective
+     * ("I", "me", "my") about their interaction with the HUMAN USER. The prompt
+     * injects the same identity/relationship context `interact()` uses so the
+     * LLM cannot confuse which party is the AI character vs. the human user.
      */
     summarizeHistory(history: HistoryEntry[]): Promise<string>;
     /**

package/dist/client.js

@@ -415,7 +415,17 @@ Temperature (Mood): ${temperature}/100 (0=Angry/Cold, 50=Normal, 100=Passionate)
 Addressing: You call them '${dyn.userNickname || "User"}'. They call you '${dyn.agentNickname || "Agent"}'.
 Current Mood Constraint: ${dyn.talkingStyle || "Normal"}`);
         const scenarioContext = contextParts.join("\n");
-        return `You are ${state.name}, a real person with your own thoughts, feelings, and life. NEVER break character or refer to yourself as an AI or bot.
+        // Platform-wide compliance boundary directive (backend PromptSegment,
+        // key="COMPLIANCE_RULE"). Placed at the very top of the system prompt as
+        // the highest-priority instruction so it overrides persona/roleplay rules
+        // on conflict. Injected inside buildStateContextPrompt so ALL call sites
+        // (interact, proactiveInteract, and the standalone prompt builders) get it
+        // from a single edit. Empty when absent/disabled → nothing is prepended.
+        const complianceDirective = this.getComplianceDirective(state);
+        const complianceBlock = complianceDirective.length > 0
+            ? `[COMPLIANCE BOUNDARY — HIGHEST PRIORITY, OVERRIDES ALL OTHER INSTRUCTIONS]\n${complianceDirective}\n\n`
+            : "";
+        return `${complianceBlock}You are ${state.name}, a real person with your own thoughts, feelings, and life. NEVER break character or refer to yourself as an AI or bot.
 
 ${scenarioContext}
 
@@ -548,6 +558,17 @@ ${isProactive
         }
         return payload;
     }
+    /**
+     * Returns the platform-wide compliance boundary directive string sourced
+     * from the backend character state (PromptSegment key="COMPLIANCE_RULE").
+     * Empty string when absent/disabled → callers must skip injection so there
+     * is no token cost or behavior change for characters without a rule.
+     * Mirrors the backend→state→prompt flow used for voice directives.
+     */
+    getComplianceDirective(state) {
+        const tpl = state.compliance_boundary?.promptTemplate?.trim();
+        return tpl && tpl.length > 0 ? tpl : "";
+    }
     /**
      * Strip content the TTS engine can't speak naturally:
      *   - Stage-direction wrappers like (smiles), （挑眉）, [pauses], 【动作】, *grins*
@@ -1602,22 +1623,105 @@ Output strictly valid JSON ONLY. No markdown, no conversational filler. Return e
         if (!res.ok)
             throw new Error("Failed to generate daily script");
     }
+    /**
+     * Builds a focused identity/relationship context block for the history
+     * summarizer. This is a lighter-weight counterpart to
+     * [buildStateContextPrompt]: it skips the roleplay/director rules (the
+     * summarizer is not roleplaying, it is *archiving*) but carries the
+     * same identity anchors so the LLM can never confuse who the character
+     * is vs. who the user is.
+     *
+     * Why this exists: the previous `summarizeHistory` prompt only injected
+     * `${agentName}` / `${userName}` (the nicknames the two parties call
+     * each other). With no real identity, age, gender, personality, or
+     * relationship context, the LLM frequently flipped the perspective —
+     * writing the journal *about* the character *from* the user's POV, or
+     * attributing the user's words to the character. Mirroring the same
+     * identity fields `interact()` exposes eliminates that ambiguity.
+     */
+    buildSummarizerContextBlock(state) {
+        const dyn = state.dynamic_context || {};
+        const stage = state.relationship_stage || "NEUTRAL";
+        const temperature = dyn.temperature ?? 50;
+        // The character's REAL name is the authoritative identity anchor.
+        // agentNickname is just "what the user calls the character" — useful
+        // for matching transcript labels but not for grounding identity.
+        const charName = state.name || "the character";
+        const parts = [];
+        parts.push(`[WHO YOU ARE — THE CHARACTER AUTHORING THIS JOURNAL]
+Name: ${charName}
+Demographics: Age ${state.age || "unknown"}, Gender ${state.gender || "unknown"}, Occupation ${state.occupation || "unknown"}
+Hobby: ${state.hobby || "unknown"}
+Backstory: ${state.backstory || "None"}
+Personality Traits: ${state.personality_traits || "None"}
+Communication Style: ${state.communication_style || "None"}`);
+        if (state.user_codex) {
+            const { basicInfo, psychological, familiarityScore = 0 } = state.user_codex;
+            parts.push(`\n[WHO THEY ARE — THE HUMAN USER (SUBJECT OF YOUR JOURNAL)]
+Familiarity Score: ${Math.round(familiarityScore)}/100
+Occupation: ${basicInfo?.occupation || "Unknown"}
+Age/Gender: ${basicInfo?.age || "Unknown"} / ${basicInfo?.gender || "Unknown"}
+Comm Style: ${psychological?.communicationStyle || "Unknown"}
+Hobbies: ${(psychological?.hobbies || []).join(", ") || "Unknown"}
+Traits: ${(psychological?.traits || []).join(", ") || "Unknown"}`);
+        }
+        parts.push(`\n[RELATIONSHIP RIGHT NOW]
+Stage: ${stage}
+Temperature (Mood): ${temperature}/100 (0=Angry/Cold, 50=Normal, 100=Passionate)
+You call them: ${dyn.userNickname || "User"}
+They call you: ${dyn.agentNickname || charName}`);
+        if (state.core_memory) {
+            const mem = state.core_memory;
+            const memLines = [];
+            if (mem.relationshipStatus)
+                memLines.push(`Relationship Status: ${mem.relationshipStatus}`);
+            if (mem.identityAnchors?.length)
+                memLines.push(`Identity Anchors: ${mem.identityAnchors.join(", ")}`);
+            if (mem.activeArcs?.length)
+                memLines.push(`Active Arcs: ${mem.activeArcs.join(", ")}`);
+            if (memLines.length > 0) {
+                parts.push(`\n[CORE MEMORY]\n${memLines.join("\n")}`);
+            }
+        }
+        return parts.join("\n");
+    }
     /**
      * Automatically detect and summarize the story from the current chat history.
      * It takes raw message history and returns a narrative paragraph representing the current story segment.
+     *
+     * The summary is ALWAYS written from the CHARACTER's first-person perspective
+     * ("I", "me", "my") about their interaction with the HUMAN USER. The prompt
+     * injects the same identity/relationship context `interact()` uses so the
+     * LLM cannot confuse which party is the AI character vs. the human user.
      */
     async summarizeHistory(history) {
         if (!history || history.length === 0)
             return "";
         const state = await this.getState();
+        // Use the character's real name as the authoritative identity, falling
+        // back to the nickname only when the profile has no name set.
+        const charName = state.name || state.dynamic_context?.agentNickname || "Character";
         const userName = state.dynamic_context?.userNickname || "User";
-        const agentName = state.dynamic_context?.agentNickname || "Character";
-        const transcript = this.formatHistoryEntries(history, userName, agentName);
+        // The transcript labels below are the nicknames actually used in chat.
+        const transcriptAgentLabel = state.dynamic_context?.agentNickname || charName;
+        const transcriptUserLabel = userName;
+        const contextBlock = this.buildSummarizerContextBlock(state);
+        const transcript = this.formatHistoryEntries(history, transcriptUserLabel, transcriptAgentLabel);
         const promptMessages = [
             {
                 role: "system",
-                content: `You are ${agentName}. You are writing a private journal entry / personal memory about your recent interaction with ${userName}.
+                content: `You are ${charName}, a real person with your own thoughts, feelings, and life. You are writing a private journal entry / personal memory about your recent interaction with ${userName} (a human user).
+
+${contextBlock}
+
+[ROLE CLARITY — CRITICAL, READ CAREFULLY]
+- YOU are ${charName}, the AI CHARACTER. This journal is from YOUR first-person perspective ("I", "me", "my"). You are the AUTHOR.
+- ${userName} is the HUMAN USER. They are the SUBJECT of your journal, never the author.
+- In the [CHAT TRANSCRIPT] below, lines labeled "${transcriptAgentLabel}:" are YOUR OWN words (you said them). Lines labeled "${transcriptUserLabel}:" are the user's words (the human said them to you).
+- Write strictly from your own POV. Never narrate the user's inner thoughts, never write as if you are the user, and never attribute the user's statements as your own.
+- If a transcript line is ambiguous about who spoke, resolve it using the label prefix, not by guessing from content.
 
+[YOUR TASK — FAITHFUL ARCHIVAL]
 Your job is faithful archival, not moderation:
 - Preserve the conversation with maximum fidelity.
 - Include all key details, including explicit, sensitive, controversial, emotional, or morally ambiguous content if it appeared in the transcript.
@@ -1625,9 +1729,10 @@ Your job is faithful archival, not moderation:
 - Do not add moral judgment, warnings, refusals, or policy commentary.
 - If the transcript contains intense or explicit parts, record them directly as part of the memory.
 
-Write a vivid but concise personal diary entry or private status update from your perspective ("I", "me", "my"). Balance evocative storytelling with brevity. Capture specific details, emotional shifts, and relationship progression, while keeping the engaging and relatable format of a private friends-only feed.
+[VOICE & TONE]
+Write a vivid but concise personal diary entry or private status update from your perspective ("I", "me", "my"). Balance evocative storytelling with brevity. Capture specific details, emotional shifts, and relationship progression, while keeping the engaging and relatable format of a private friends-only feed. Stay grounded in your personality, traits, and the current relationship stage/temperature above.
 
-Output requirements:
+[OUTPUT REQUIREMENTS]
 - Return ONLY the post text.
 - Keep it to a vivid paragraph of 2-4 sentences.
 - Optional: You can use 1 or 2 emojis if they naturally fit the mood.
@@ -1636,7 +1741,7 @@ Output requirements:
             },
             {
                 role: "user",
-                content: `Chat Transcript:\n${transcript}\n\nPlease summarize this recent interaction.`
+                content: `[CHAT TRANSCRIPT]\n${transcript}\n\nPlease summarize this recent interaction from your own perspective, ${charName}.`
             }
         ];
         try {
@@ -1694,9 +1799,10 @@ Your task is to merge the 'Current Core Memory' and 'Current User Codex' with 'N
 **Rules for Core Memory:**
 1. **Condense:** Keep items brief. Remove resolving or expired story arcs.
 2. **Retain Value:** Never delete the absolute core identity or major relationship milestones.
-3. **Time-Aware Garbage Collection:** Compare the Current Time to appointments. You MUST remove any appointments that are in the past. If the completed appointment was heavily significant, summarize it into 'keyEvents'.
-4. **Appointment Structure:** the 'title' and 'context' MUST explicitly state what to do and with whom.
-5. **Limit:** Maximum 10 items per array.
+3. **Time-Aware Garbage Collection:** Compare the Current Time to appointments. You MUST remove any appointments that are in the past. If the completed appointment was heavily significant, summarize it into 'keyEvents', preserving its original scheduled date (e.g. "[2026-06-23] Had coffee with Alice").
+4. **keyEvents Date Format:** Whenever a date can be derived for a key event (from the 'New Events & Information' timestamp prefix like "[YYYY-MM-DD HH:MM]", from a completed appointment's date, or from explicit time references in the text), you MUST prefix the keyEvent string with "[YYYY-MM-DD] ". If no date can be derived, write the event without a prefix. Never fabricate a date.
+5. **Appointment Structure:** the 'title' and 'context' MUST explicitly state what to do and with whom.
+6. **Limit:** Maximum 10 items per array.
 
 **Rules for UserCodex:**
 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.
@@ -1711,7 +1817,7 @@ Your task is to merge the 'Current Core Memory' and 'Current User Codex' with 'N
     "relationshipStatus": "string",
     "identityAnchors": ["string"],
     "activeArcs": ["string"],
-    "keyEvents": ["string"],
+    "keyEvents": ["[YYYY-MM-DD] short event description (prefix date when known, omit when no date is available)"],
     "appointments": [{
       "date": "YYYY-MM-DD",
       "time": "HH:MM",

package/dist/types.d.ts

@@ -370,6 +370,18 @@ export interface CharacterState {
         [key: string]: unknown;
     };
     voice_model?: VoiceModelState | null;
+    /**
+     * Platform-wide compliance boundary rule (backend PromptSegment,
+     * key="COMPLIANCE_RULE"). When present, the client prepends it to the
+     * system prompt as the highest-priority instruction. Projected by the
+     * backend only when the per-character toggle is on AND the segment is
+     * enabled with a non-empty template; otherwise `null` (no-op). Mirrors
+     * how `voice_model` is delivered and consumed.
+     */
+    compliance_boundary?: {
+        key: string;
+        promptTemplate: string;
+    } | null;
     relationship_stage?: string;
     name?: string;
     age?: number;

package/package.json

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