[MS-1145] Visual sync button responsiveness optimization

[alex-vt]

JIRA ticket
Will be released in: 2025.3.0

Root cause analysis (for bugfixes only)

First known affected version: 2025.3.0 dev only

• The forceEventSync and toggleImageSync invoke sync purely on the data layer, so the UI was remaining unaware of the forced sync command until data-driven evidence of sync was starting to appear. This could take seconds on slow devices.

Notable changes

• Each forced sync, invoked by forceEventSync and toggleImageSync, immediately reshapes the flow of events: At first we immediately emit a sync state that is forcefully marked as in progress, for events or images separately. And we start ignoring sync states that happen before the true progress in data layer appears. Once the true progress in data layer starts, we keep showing that true progress. Additionally, an initial progress is emitted on start, before any forced sync invocations - to prevent getting stuck on start.

Testing guidance

• Record and image sync buttons react immediately when used to start the sync.

Additional work checklist

• Effect on other features and security has been considered
• Design document marked as "In development" (if applicable)
• External (Gitbook) and internal (Confluence) Documentation is up to date (or ticket created)
• Test cases in Testiny are up to date (or ticket created)
• Other teams notified about the changes (if applicable)

[BurningAXE]

Would forceEventSyncProgress() be more precise here?

[alex-vt]

As this is resolved too, and nothing else to resolve - I'll merge.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
93.9% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[luhmirin-s]

IMO, only this paragraph is relevant; the rest can be pruned.

Also, this is not a KDoc comment, so it should not have the double star at the beginning.

[alex-vt]

Removed the double star, but let's stay a bit more descriptive than usual about this non-trivial feature. There's been a history of more comments requested in similar situations rather than less.