refactor(session): agent-scope rotation + accumulation; auto-register file artifacts

Sessions are already agent-scoped post-v34, but the code kept routing
rotation / accumulation / handoff through the task indirection. Heartbeat
runs (no task) silently skipped all three, letting taskless transcripts
grow past the model's context window — the 7M-token explosion.

- DB adds getSessionById(sessionId) — direct lookup bypassing
  tasks.active_session_id
- session-management-service: generateHandoff(session) is now agent-scoped,
  walking recent runs across tasks + heartbeats; getHandoffForAgent(agentId)
  is the canonical lookup, getHandoffContext(taskId) is a thin shim for
  callers that still hold a task id
- turn-context.ts::resolveSession drops the `if (!task)` early return:
  rotation evaluation runs on the agent session unconditionally
- run-finished-helpers.ts::accumulateAndRotateSession drops the `!task`
  gate: tokens accumulate and rotation fires for every run, keyed on the
  agent session, not the task
- Rotation evaluator contract: evaluatePreRunSessionRotation(agentId,
  connectorId) → { rotated, handoff, sessionId }; old (taskId, connectorId)
  signature removed

IPC contract tightening: ipc-support::emitEvent becomes a best-effort
sink. "Render frame was disposed" during renderer reload is a lifecycle
signal, not a logic error; silently drop it instead of letting it abort
downstream event emissions.

Artifact projection: pi's write/edit tool results now upsert a
`work_products` row via a new agent-runtime/artifact-projector.ts. No
more agents writing 54 files into the workspace that the UI never sees.
Migration v40 relaxes work_products.task_id to nullable so heartbeat
artifacts can register too.

File size: split agent-event-projection.ts out of runtime-bridge.ts to
keep the bridge under the 400-line cap after adding the projector hook.

Tests: 604 unit + integration green; generateHandoff callsites updated
for the single-argument signature; artifact-projector has pure-function
coverage via the projector module's own shape.

tests/integration/autonomous-chain/ceo-phased-prompts.spec.ts

@@ -24,8 +24,13 @@ describe("Step 2: CEO phased prompts", () => {
 
     const prompt = buildSystemPrompt(ctx);
     expect(prompt).toContain("Team Building Phase");
-    expect(prompt).toContain("Design the Organization Structure");
-    expect(prompt).toContain("Submit Org Strategy for Approval");
+    // The rewritten prompt uses "Design a minimal org" instead of the
+    // old "Design the Organization Structure" header. Check for both
+    // the stable Step-2 marker and the new ordering guarantee that
+    // blocks the self-loop the earlier prompt enabled.
+    expect(prompt).toContain("Design a minimal org");
+    expect(prompt).toContain("HIRES FIRST. STRATEGY APPROVAL LAST.");
+    expect(prompt).toContain("Submit org strategy");
     expect(prompt).not.toContain("Awaiting Org Approval");
     expect(prompt).not.toContain("Goal Decomposition");
   });

tests/integration/process-recovery.spec.ts

@@ -472,8 +472,8 @@ describe("Process Recovery -- Context Preservation (D-02)", () => {
     expect(rotationResult.shouldRotate).toBe(true);
     expect(rotationResult.reason).toBe("max_runs");
 
-    // Generate handoff markdown
-    const handoff = sessionService.generateHandoff(taskId, session!);
+    // Generate handoff markdown (agent-scoped, single-argument signature).
+    const handoff = sessionService.generateHandoff(session!);
     expect(handoff).toContain("# Session Handoff");
     expect(handoff).toContain("Session stats:");
   });