From cbabc542731308ad2cf1cceb81d77b5ccac4023c Mon Sep 17 00:00:00 2001
From: "DESKTOP-I1T6TF3\\Q" <2291969160@qq.com>
Date: Wed, 3 Jun 2026 03:51:58 +0800
Subject: [PATCH] chore(engine): log worldSetting and storyBible at session
 start
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

Two lines in startSession: the full worldSetting being fed to the
Architect, and the resulting logline/genreTags/synopsis it produced.
Cheap to keep — fires once per session — and makes it possible to tell
at a glance whether a "story unrelated to my input" report is a frontend
transport bug, a worldSetting layout problem, or the LLM ignoring the
seed.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
---
 lib/engine/orchestrator.ts | 6 ++++++
 1 file changed, 6 insertions(+)

diff --git a/lib/engine/orchestrator.ts b/lib/engine/orchestrator.ts
index f5df2f8..5f930fc 100644
--- a/lib/engine/orchestrator.ts
+++ b/lib/engine/orchestrator.ts
@@ -53,9 +53,15 @@ export async function startSession(
   // bible BEFORE the first scene. Serial by necessity (the opening Writer
   // reads session.storyState), but it gives the whole story a spine from beat
   // one — the latency is offset by the director's portrait/voice overlap win.
+  console.log(
+    `[start] worldSetting (${session.worldSetting.length} chars):\n${session.worldSetting}`,
+  );
   const tArchitect = Date.now();
   session.storyState = await runArchitect(config.text, session);
   tlog("[start] Architect", tArchitect);
+  console.log(
+    `[start] storyBible: logline="${session.storyState.logline}" | genreTags="${session.storyState.genreTags}" | synopsis="${session.storyState.synopsis}"`,
+  );
 
   const { scene, sceneImageUrl, characters, storyState } = await directScene(
     config,