Club Calendar - Meeting events not displaying correctly

Meeting events for different dates are appearing stacked up on the same date on our Club Calendar. See attached pictures for how this appears on May/June/July. Also attached is our list of future agendas. No issues browsing to the various future agendas from the list.

Selecting any of the stray meeting instances behaves as though only the correct event is present; May 24th agenda, Memorial Day notice, July 19th agenda. Selecting a blank date for which an agenda exists (such as June 14th) displays the dialog box for adding a calendar event.

I noticed this immediately after adding a second meeting event to June 7th. I opened the calendar expecting to find two meetings on June 7th with the intent of verifying my new meeting event and deleting the previous one and found this issue. I don't know if the issue was present previous to this action. The last time I looked at the calendar may have been in early May when I populated the meeting events through the end of July.

I tried clearing cache/cookies and reloading the site from the server. Viewing it in Microsoft Edge and on mobile (Pixel 4/Android 11) shows the same behavior. If something I did caused the issue or if there's a way for me to fix it I haven't yet discovered what these are.

Thanks for your help!

I know what the cause is... I need to assess whether to roll-back the jQuery update or fix the calendar config.

Leaning towards the latter, but it will take some time that is in short supply at the moment.

We are having the same calendar problem at my two clubs as well. If this is not a universal fix for all clubs, would you kindly apply the solution to the following clubs as well:
Empire Statesmen Toastmasters Club #1427
empirestatesmen.toastmastersclubs.org/
and
Good Morning Syracuse Toastmasters Club #4885982
goodmorningsyracuse.toastmastersclubs.org/

Thank you very much,
Pat Costello

Calendar is back to normal Steve. Appreciate all your efforts!

Thank you Steve for fixing the problem right away and Thank you Richard for posting the problem!

Pat