Changelog entry disappears from dashboard + created date gets corrupted when scheduling a future publish date via API

Summary Calling the changelog update endpoint with draft: false and a future scheduled Unix timestamp does not schedule the entry correctly. Instead, the entry enters a broken state: it stays retrievable via the API (not live, enabled: 0), but disappears entirely from the dashboard (not found via dashboard search, doesn't appear under any status tab), and its created timestamp gets overwritten with an unrelated, incorrect date. Steps to reproduce Create or take an existing draft changelog entry. Call the update endpoint with draft: false and scheduled: <future unix timestamp> (e.g. 1787644800 = 2026-08-25 08:00 UTC). Fetch the entry again via the API. Observed behavior The entry is no longer findable in the dashboard (tested via dashboard search for the entry's title) — confirmed independently on two separate entries (changelog IDs 58645 and 58295). Via the API, the entry still returns fully (title, description, etc.), with draft: false, scheduled: true (only a boolean is returned, never the actual timestamp), and enabled: 0 (not live). The created field is silently rewritten to a date that matches neither the original creation date nor the requested scheduled date. Example: entry 58295 was created 2026-07-29; after setting scheduled to 2026-08-25 08:00 UTC, created became 2026-08-10 04:00:00 — a value unrelated to any input. A separate earlier incident (entry 58645, July 2026): calling the same combination (draft: false + future scheduled) caused the entry to publish immediately instead of queuing for the future, and the dashboard then showed the message "Published entries can be backdated, not moved into the future" when trying to correct it. Expected behavior Setting draft: false with a future scheduled timestamp should queue the entry for automatic publish at that time, remain visible in the dashboard (ideally under a "Scheduled" filter/tab), and leave created untouched or set it to the actual action timestamp — not an unrelated date. Workaround found Setting draft: true on the affected entry restores it to a normal, dashboard-visible draft state (and also resets created to the current date). No API-based method was found to reliably schedule a future publish date — we now schedule manually in the dashboard UI instead. Environment: accessed via the Sleekplan MCP server tools (create\changelog / update\changelog), which appear to call the same backend as the dashboard.