Owner of one code-owned analysis session's canonical event batch and publication.

The trace owner supervises a combined run-state/event owner, guards construction until the builder marks it complete, retains the calling process as stable lifecycle owner, monitors the evaluation owner, and retains a finalized batch for close retries while that owner remains available. Finalization and batch handoff are one owner operation. Publication is atomic and no-clobber, and binds writes to a directory context whose filesystem identity matches the builder-bound destination; retrying never appends or emits another terminal event. Unexpected evaluation- or lifecycle-owner death gets one independent best-effort publication attempt before this trace owner stops; that path has no surviving caller-visible retry authority.