Time at 00:00 or 01:00 March 29 broken, Daylight Savings likely

Capacities v1.60.1; Google Pixel; Android v16; Chrome WebView v146.0.7680.119 (WebKit v537.36); Mobile (Capacitor); 29/3/2026, 15:05:20; en (Europe/Dublin, UTC+1)

Using @ object creation for early hours of March 29 broken. Tested at around 15:06 on March 29 (today)

• "@0", no date recognized ❌
• "@1", incorrect datetime "March 29, 2026, 00:00" ❌
• "@2", incorrect datetime "March 29, 2026, 00:00" ❌
• "@3", correct datetime "March 29, 2026, 03:00" ✅
• "@march 29, 00", correct datetime "March 29, 2026, 00:00" ✅
• "@march 29, 01", incorrect datetime "March 29, 2026, 00:00" ❌
• "@march 29, 02", incorrect datetime "March 29, 2026, 00:00" ❌
• "@march 29, 03", correct datetime "March 29, 2026, 03:00" ✅
• "@march 28, 00", correct datetime "March 28, 2026, 00:00" ✅
• "@march 28, 01", correct datetime "March 28, 2026, 01:00" ✅
• "@march 28, 02", correct datetime "March 28, 2026, 02:00" ✅
• "@march 28, 03", correct datetime "March 28, 2026, 03:00" ✅

And so on, there are more possibilities but this set of cases suggest it related to daylight savings coming into effect.