Greptile Summary

This PR fixes an inconsistency in the PATCH /v1/account/sessions/:sessionId (updateSession) endpoint where expire and providerAccessTokenExpiry were returned in the internal DB datetime format (Y-m-d H:i:s.v) rather than ISO8601, unlike GET session and all create-session paths.

• Core fix (account.php): Both setAttribute('expire', ...) and setAttribute('providerAccessTokenExpiry', ...) in the PATCH handler now wrap DateTime::addSeconds() with DateTime::formatTz(), matching the pattern already used everywhere else in the file.
• Tests (AccountCustomClientTest.php): testRefreshEmailPasswordSession now asserts that the PATCH response and the follow-up GET both contain an ISO8601-formatted expire value, using both DatetimeValidator and DateTime::createFromFormat('Y-m-d\\TH:i:s.uP', ...).

Confidence Score: 5/5

Safe to merge — the change is a targeted two-line fix that aligns the update path with the already-established create-session pattern throughout the same file.

Both changed lines follow the exact same DateTime::formatTz(DateTime::addSeconds(...)) idiom used by every other session-creation path in account.php. The accompanying test explicitly validates the ISO8601 format for both the PATCH response and the subsequent GET.

Files Needing Attention: No files require special attention.

Important Files Changed

_{Reviews (2): Last reviewed commit: "Merge branch 'main' into fix-8447-sessio..." | Re-trigger Greptile}