As I understand from your links, the most recent ballot SC-081v3: Introduce Schedule of Reducing Validity and Data Reuse Periods among the Certification Authority/Browser Forum members is yet awaiting official publication.
A quick count shows that of ~30 participants, about 20% abstained while ~80% approved of the following schedule to further reduce acceptable certificate validity:
The maximum certificate lifetime is going down:
- From today until March 15, 2026, the maximum lifetime for a TLS certificate is 398 days.
- As of March 15, 2026, the maximum lifetime for a TLS certificate will be 200 days.
- As of March 15, 2027, the maximum lifetime for a TLS certificate will be 100 days.
- As of March 15, 2029, the maximum lifetime for a TLS certificate will be 47 days.
It remains to be seen how quick client software - web browsers, in particular - would implement respective changes, and how they would deal with a valid certificate that only exceeds the validity threshold.
Apple OSs current refusal to acknowledge otherwise valid certificates if their validity is above 825 days already has prompted a discussion, but that didn't trigger any changes, as OP reported that SSL/TLS access started working for them (see HTTPS nutzen - Bitte um Hilfe - #13 by DL6ER).
In that topic, @DL6ER's main concern when reducing certificate validity was about automatically renewing Pi-hole's self-signed certificate, as Pi-hole would need a method to tell certificates it created itself from third-party certificates. Maybe remembering the exact timestamp of creation could help with that?