Meeting Security Hardening & Stability Fixes

Security

• Fixes an issue where past meeting records could be created against meetings not owned by the requesting project or committee, preventing unauthorized cross-project associations.
• Prevents past meeting records from being moved to a different project or committee on update, ensuring meeting ownership cannot be transferred without proper authorization.
• Ensures recording and transcript access levels always reflect the latest host settings by using the parent past meeting record as the authoritative source, rather than stale creation-time snapshots.

Stability

• Resolves a service instability where unbounded recurrence rule (RRULE) expansion on recurring meetings could exhaust available memory or CPU, causing pod restarts. Expansion is now strictly bounded to protect against large or malformed recurring series.