Post scheduled in far future (year 4139) on self hosted

A user intended to publish a post on a self hosted site without Jetpack. The post was published in the future (Year 4139).

User might have tried to fetch revision history, which should be disabled on self hosted (no endpoint). Notice the call to wpcom endpoints and the site_id in the logs:

30 - [Jan-31 20:19 API] Volley error on https://public-api.wordpress.com/rest/v1.1/sites/0/post/4530/diffs/?locale=de_AT - exception: null 31 - [Jan-31 20:19 API] 
StackTrace: 
com.android.volley.ClientError at 
com.android.volley.toolbox.BasicNetwork.performRequest(BasicNetwork.java:199) at 
com.android.volley.NetworkDispatcher.processRequest(NetworkDispatcher.java:131) at 
com.android.volley.NetworkDispatcher.processRequest(NetworkDispatcher.java:111) at 
com.android.volley.NetworkDispatcher.run(NetworkDispatcher.java:90) 32 - [Jan-31 20:19 API] 

Dispatching action: PostAction-FETCHED_REVISIONS 33 - [Jan-31 20:19 API] Volley error on https://public-api.wordpress.com/rest/v1.1/sites/0/post/4530/diffs/?locale=de_AT - exception: null 34 - [Jan-31 20:19 API] 
StackTrace: 
com.android.volley.ClientError at 
com.android.volley.toolbox.BasicNetwork.performRequest(BasicNetwork.java:199) at 
com.android.volley.NetworkDispatcher.processRequest(NetworkDispatcher.java:131) at 
com.android.volley.NetworkDispatcher.processRequest(NetworkDispatcher.java:111) at 
com.android.volley.NetworkDispatcher.run(NetworkDispatcher.java:90)

Start by tracing the self-hosted post scheduling flow alongside the logged revision-history request to the WordPress.com diffs endpoint with site_id 0. Reproduce the far-future publication case and determine the expected behavior for revision fetching on self-hosted sites; done means the post is not scheduled for year 4139 and the invalid endpoint request is avoided.