chore(engine): log worldSetting and storyBible at session start

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

@@ -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,