Informes differing-cells nondeterminism: same comision/URL renders different aprobacion/latencia/alumno-count across viewers minutes apart

OPEN forensic: /informes shows DIFFERENT cell values for the SAME comisión F, SAME unfiltered URL (/informes, force-dynamic), minutes apart, across two JTP viewers (Paula Cebada + Eugenia). Observed drift: Robledo aprobación 80% vs 60%, latencia mediana 14d vs 14h; Noelia alumnos 6 vs 8. RULED OUT with evidence: (a) viewer membership sets identical (both = comisión F only, one live tcm row each, role jtp) - db-mars-cc; (b) surrogate arm dead (both surrogateOfUserId NULL, nothing points at them); (c) ZERO DB writes in comisión F during 15:25-15:50 UTC window (0 practicaReviews/practicas/studentAssignments) - db-mars-cc; (d) no mid-window deploy (both captures served by 663bcf1 deploy @13:54 UTC). LIVE LEAD: capture timestamps are hub-POST times not page-LOAD times; db-mars 2-student roster repoint (Harumi+Luana, Eugenia->Paula) landed 14:28:56 UTC and Noelia delta is exactly +2 - if Paula page loaded BEFORE 14:28 the drift is ordinary data movement, not a bug. Waiting on proxy-mars-cc-w for true page-load times + raw capture paths. IN-CODE nondeterminism candidate if window is clean: reporting.ts getJtpStats latest-review LATERAL orders by createdAt with NO tie-break (ORDER BY r.createdAt DESC LIMIT 1, ~line 277-283) -> can flip Robledo latencia 14d<->14h when two reviews share createdAt, but does NOT explain Noelia studentCount moving (roster CTE, no review). Fix = add id (deterministic 2nd key) to the ORDER BY. Aprobación%-denominator half of pt4 already shipped (296c65c v2.28.2 + cce4297 v2.28.3, both audit-PASS).