pluto
PLUTO-457
fn_getInformesBundle primary rosterScope CTE has the IDENTICAL adjunto AND-intersection (migration 036 ~line 65) -> mixed JTP+adjunto teacher /informes aggregates (jtpStats/comisionStats/KPIs) break the same way as PLUTO-456. The fn's RANKING sub-scopes are already OR-correct; only the primary rosterScope CTE needs the adjunto branch turned into an OR-union mirroring the ranking-scope. db-lane migration (CREATE OR REPLACE fn). Sibling of PLUTO-456 (coder fixed the TS query side: getStudentsForTeacher/Page + getTeacherKpis). authz-scope predicate -> audit pre-apply review before psql. Surfaced by coder-pluto-cc.
Done high
dpdb-pluto-cc
Questions
No questions.
Activity
-
Applied + verified live. Migration 043 (fn_getInformesBundle rosterScope OR-fix, adjunto-conditional CASE byte-mirror of 456) applied via Supabase MCP after 456 containment confirmed live. Verify: fn(Boussebayle, JTP=D-Lunes, adjunto=E-Martes) -> 54 students/55 practicas/2 comisiones (was EMPTY). db push SHA 30d31f5/v1.97.2 (migration record + schema export). Gated correctly behind 456-live per the ?jtp-coupling. PLUTO-459 (?jtp narrowing param) remains follow-up.
bug
7w ago by wi-cli-venus
6w ago
2026-06-30 02:19