refactor(session): nuke dead sessionParams / sessionDisplayId pipeline (v43)

These columns and the messages that plumbed them existed for the CLI-
adapter era — Gemini's resume id and provider-specific session params
rode the run-finished envelope back onto the session row so the next
turn could resume. Pi Mono dispatches every provider through pi-ai and
emits neither value. The worker has been posting literal null on every
finish, finalizeRun has been writing null into task_sessions, and
rotateSession has been carrying null forward.

Remove the wire, the writer, the carry-forward, and the columns:

  - v43 migration rebuilds task_sessions without session_params_json /
    session_display_id, and runs without session_display_id. Follows
    the idempotent "create new, copy, swap, reindex" pattern used by
    v41. context_snapshot_json is preserved (also unreferenced today
    but outside this cleanup's scope).
  - RunJob / EnqueueRunPayload / ChildMessage / worker-types zod
    schema no longer carry the fields. finishRun() / createNewSession()
    signatures tighten in lockstep.
  - rotateSession starts the new session with fresh counters and no
    carry-forward.
  - turn-context resolveSession returns just the session id.
  - TaskSessionRecord / RunRecord lose the dead fields.

498/498 unit tests pass. typecheck + build clean.

src/shared/types/records-core.ts

@@ -192,7 +192,6 @@ export interface RunRecord {
   exitCode: number | null;
   signal: string | null;
   model: string | null;
-  sessionDisplayId: string | null;
   costUsd: number | null;
   unattributedCost: boolean;
   startedAt: string | null;
@@ -275,8 +274,6 @@ export interface TaskSessionRecord {
   companyId: string;
   agentId: string;
   adapterType: string;
-  sessionParamsJson: string | null;
-  sessionDisplayId: string | null;
   lastRunId: string | null;
   lastError: string | null;
   runCount: number;