publishedAt field issues

[busbyk]

1. If you change the publishedAt date and save a draft, the publishedAt field is cleared
2. If you unpublish, the publishedAt field should be cleared and is cleared in the database but it still shows the old value in the UI. Maybe a regression of fix(ui): properly reflects hook changes in ui payloadcms/payload#10268?
3. The Pages collection's publishedAt field shows description "Set when this page was or should be published. This affects the page's visibility and can be used for scheduling future publications." but this is not true, we do not respect this for whether or not a page will render or show a 404.
4. We're using three slightly different field configs for publishedAt in homePages, posts, and pages.

homePages, posts, and pages have custom publishedAt fields. The only things we use publishedAt fields for in the (frontend) is sorting [example] and the displaying of dates (optionally based on showDates) for posts.

Why don't we just use updatedAt for those things instead and do away with the publishedAt field completely?

updatedAt is a payload-managed field and in combination with status could easily serve the purpose of publishedAt.