Fixed partial sync bug in social post account statuses

I fixed an issue where updating the status of a single social media account (Instagram, Facebook, TikTok) during a partial sync would accidentally overwrite the statuses of other accounts tied to the same post. This was causing some accounts to get stuck in “partial” or “retry” states, blocking the scheduler from progressing normally. Now, partial updates only modify the intended account rows without clobbering siblings.

Added scheduler lease recovery for stuck partial states

The scheduler now recognizes “partial” states at the account level as recoverable leases, allowing it to retry and recover from unexpected partial syncs that previously caused stuck posts. This helps keep the publishing workflow moving smoothly even when transient issues occur.

Improved test coverage for lease status resolution

I added tests to verify how lease statuses are interpreted during scheduler processing, ensuring that only valid states are accepted and that “partial” states are treated correctly for lease recovery.

Other improvements

• Updated database function to only expand missing account entries when fully replacing the status map, preventing unintended overwrites during partial updates.
• Documented this bug risk and ongoing investigation around account health detection and reconnect UX for auth failures in the tech debt log.