Sub-ticket of PLUTO-459 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. · pluto