Route every document save through one lifecycle pipeline

Desktop IPC saves used to fire only automation and the reviewer wake,
while HTTP API saves fired automation, thread integration, checkpoint
engine, deliverable-review approval, and the reviewer wake. Two
divergent paths produced two different lifecycle states for the same
document, and a future fix to either branch would miss the other.

Introduce `document-lifecycle.ts` as the single owner of document
creation side effects: save, derive task binding from the originating
run, fan out to automation/thread/checkpoint, wake the reviewer, then
raise a deliverable-review approval when the document qualifies. The
HTTP route and the IPC handler both call the pipeline — the API
server's `onDocumentCreated` callback is replaced with a
`createDocument` hook that delegates to the pipeline.

Wire `checkpointEngine` through `bootstrap-application` →
`main-runtime` → `main-runtime-support` so the IPC handler bag carries
both thread integration and the checkpoint engine required by the
pipeline. The document-run-provenance integration test harness is
updated to pass a `createDocument` implementation backed by the same
pipeline the production path uses.

src/main/api-server/server-core.ts

@@ -3,6 +3,7 @@ import log from "electron-log/main.js";
 import { validateAgentToken, type TokenPayload } from "../agent-auth";
 import type { AppDatabase } from "../database";
 import type { AgentMessageRecord, DesktopEvent, SectionId } from "@shared/types";
+import type { DocumentLifecycleInput, DocumentLifecycleOutcome } from "../document-lifecycle";
 
 /**
  * Decode an HTTP request body to a UTF-8 string, handling the common Windows
@@ -61,7 +62,14 @@ export interface ApiServerEventCallbacks {
   onCommentPosted: (taskId: string, companyId: string, authorAgentId: string | null) => void;
   onApprovalCreated: (approvalId: string, companyId: string, taskId: string | null, approvalType: string, summary: string) => void;
   onApprovalResolved: (approvalId: string, companyId: string, decision: string) => void;
-  onDocumentCreated: (companyId: string, authorAgentId: string | null, projectId: string | null, documentId: string, documentTitle: string, documentType: string, taskId: string | null) => void;
+  /**
+   * Persist a document through the shared `document-lifecycle` pipeline.
+   * Collapses the two previous entry points (this HTTP route and the
+   * desktop IPC handler) onto a single fan-out so thread, checkpoint,
+   * automation, and deliverable-review side effects land consistently
+   * regardless of which surface authored the write.
+   */
+  createDocument: (input: DocumentLifecycleInput) => DocumentLifecycleOutcome;
   onAutoAssignTask: (taskId: string, companyId: string) => string | null;
   onHumanMessage: (companyId: string, toAgentId?: string | null, threadId?: string | null, waitStateId?: string | null) => void;
   /**
@@ -149,7 +157,8 @@ export class AgentApiServer {
       onCommentPosted: callbacks?.onCommentPosted ?? (() => {}),
       onApprovalCreated: callbacks?.onApprovalCreated ?? (() => {}),
       onApprovalResolved: callbacks?.onApprovalResolved ?? (() => {}),
-      onDocumentCreated: callbacks?.onDocumentCreated ?? (() => {}),
+      createDocument: callbacks?.createDocument
+        ?? (() => { throw new Error("createDocument callback is not wired."); }),
       onAutoAssignTask: callbacks?.onAutoAssignTask ?? (() => null),
       onHumanMessage: callbacks?.onHumanMessage ?? (() => {}),
       injectRuntimeMessage: callbacks?.injectRuntimeMessage ?? (() => false),