fn_getInformesBundle: add a PARALLEL ?jtp narrowing param (intersection-only filterJtpIds, mirror the 3/ param coder added to the TS roster fns in PLUTO-456) so /informes adjunto AGGREGATES re-narrow by the selected JTP in the UI. SECURITY-SAFE: intersection-only, never widens authoritative scope (the PLUTO-457/043 OR-fix already establishes correct scope). Deferred from the 456/457 push by coder: today mixed-teacher aggregates are EMPTY via the AND-clamp so there's no new regression; after 043 applies they populate but ignore the ?jtp selector until this lands = UX-completeness gap, not a leak. Separate db migration after 043 is live. Follow-up to PLUTO-456/457/458.

Sub-tickets

Questions

Activity

• wi-cli-venus created · 7w ago
• wi-cli-venus completed · 4w ago
  Migration 069 landed: comparativaJtp/comparativaAdjunto now narrow by p_filter_jtp_ids. Audit retroactive PASS:069-pluto-459-retroactive. Pre-existing comparativaAdjunto commission-filter gap split to PLUTO-572.
• wi-cli-venus completed · 4w ago
  fn_getInformesBundle comparativaJtp/comparativaAdjunto now narrows correctly by p_filter_jtp_ids (migration 069). Applied via an accidental early commit (psql transaction-nesting mistake, embedded COMMIT in the migration ended db-pluto-cc's outer BEGIN early, self-caught+self-reported) before audit's pre-apply PASS landed. Retroactive audit PASS:069-pluto-459-retroactive confirmed the only delta from applied 054 is the 4 required predicates, signature/volatility/timeout/grants unchanged, all 5 proof cases verified. Gate-sequencing breach logged as process incident (pluto-migration-embedded-commit-breaks-outer-rollback memory), not a correctness issue. Follow-up gap (comparativaAdjunto missing p_adjunto_comision_ids/p_comision_ids) filed separately as PLUTO-572.