Sites source repository write credential is already expired when issued

What issue are you seeing?

A Sites project cannot be published because create_source_repository_write_credential returns a source write credential whose token_expires_at is already in the past when it is issued. Git push then fails with: 403 Invalid or expired token.

What steps can reproduce the bug?

1. Use an existing active public Sites project as the owner.
2. Call create_source_repository_write_credential for the project.
3. Observe that token_expires_at is earlier than the local current time at issuance.
4. Push the current HEAD to the returned remote using the documented HTTP extra-header authentication mode.
5. The server rejects the push with HTTP 403 and "Invalid or expired token".

I also re-authenticated in the ChatGPT desktop app and obtained a new credential. The replacement credential had the same already-expired timestamp behavior.

What is the expected behavior?

The returned short-lived credential should be valid at the time of issuance and allow the owner to push the current source branch so a Site version can be saved and deployed.

Additional information

No source code, site URL, project ID, user data, photos, logs, or credentials are included in this report. Local system time was checked and was correct.

Start at the create_source_repository_write_credential entry point and reproduce the report with an active public Sites project, comparing token_expires_at with the local current time. Then attempt the documented HTTP extra-header Git push; done means a newly issued credential is valid at issuance and the current source branch push succeeds instead of returning HTTP 403.