Safe activation for background analytics projectors

Activate a background analytics projector behind three independent gates: cohort-bounded replay, baseline-consistent policy semantics, and deployment-order control.

Apply batch limits after filtering to records that can join the analytics cohort, or unrelated retryable history can starve newer evidence. Give latency-sensitive source families a separate bounded lane when older outcome evidence can remain retryable. If events may be committed later with earlier domain timestamps, carry the initial policy baseline through both projection and reporting.

Keep the schedule disabled until a compatible application build is active, then validate one real scheduled run. Infrastructure deployment is not job success. This does not justify unbounded replay, later-policy backdating, or operational-workflow mutation.