Warning: This build has drifted.
The coverage report for this pull request build may be inaccurate because its base commit is no longer the HEAD of its target branch.
This means it includes changes from outside the original pull request, including, potentially, unrelated coverage changes.

    • Learn more: For more information on this, see Tracking coverage changes for pull request builds.
    • Fix now: For a quick fix, rebase this PR at GitHub. Your next report should be accurate.
    • Prevent going forward: To avoid this issue with future PRs, see these Recommended CI Configurations.

fix(processes): backfill start date when publishing immediate-start processes

A process created with an empty startDate ("start immediately") kept a zero
date in Mongo forever: the on-chain elections get StartTime=0 (start at the
mined block) but nothing wrote the actual start back, so the /processes list
and single read omitted startDate entirely and clients could not tell when
the process started.

Resolve the date in the publish worker once every question is confirmed
mined: keep a still-future requested date as-is, otherwise persist time.Now()
(within seconds of the mined block, no extra chain round-trip — an exact
single chain date does not exist anyway since the N per-question elections
can mine in different blocks across retry rounds). SetVotingProcessPublished
now takes the resolved date and sets it atomically with the published flag.