fix: Submit/confirm prediction button disabled state

[dwesolow]

Summary

1. The issue is that mapLocalAnnotationsToServer don't include confidences: null when there is no confidence - causing isEqual to be true.
2. One minor issue that when annotation is invalid but subset is changed user is allowed to submit.

How to test

Checklist

• The PR title and description are clear and descriptive
• I have manually tested the changes
• All changes are covered by automated tests
• All related issues are linked to this PR (if applicable)
• Documentation has been updated (if applicable)

[github-actions]

⏱️ Backend import time — app.main

Accelerator	Cumulative (s)	Self (s)
cpu	4.104	0.003
xpu	4.394	0.003
cuda	4.630	0.003

[Copilot]

Pull request overview

Fixes an annotator submit/confirm button disabled-state regression in the UI by ensuring annotation “confidence” data is normalized consistently between server DTOs and local models, and by tightening the submit-disable logic when annotations are invalid.

Changes:

• Normalize mapLocalAnnotationsToServer to always include confidences (as null when absent) to avoid false “changed” comparisons.
• Add unit/regression tests covering confidence round-tripping and canSubmit behavior on initial load.
• Centralize submit-disable logic in getIsSubmitDisabled, preventing submission when annotations are invalid even if subset selection changes.

Reviewed changes

Copilot reviewed 6 out of 6 changed files in this pull request and generated no comments.

Show a summary per file

File	Description
application/ui/src/shared/annotator/annotation-mappers.ts	Always emits confidences (null when no probabilities) to match backend DTO shape and stabilize equality checks.
application/ui/src/shared/annotator/annotation-mappers.test.ts	Adds unit tests for confidence mapping and DTO round-trip equality (new test file).
application/ui/src/shared/annotator/annotation-actions-provider.test.tsx	Adds regression coverage for canSubmit on initial load when server annotations include confidences: null.
application/ui/src/features/dataset/media-preview/secondary-toolbar/util.ts	Introduces getIsSubmitDisabled to encapsulate submit-disable rules across modes and invalid states.
application/ui/src/features/dataset/media-preview/secondary-toolbar/util.test.ts	Adds unit tests validating getIsSubmitDisabled behavior for annotation vs prediction modes and saving/loading flags.
application/ui/src/features/dataset/media-preview/secondary-toolbar/secondary-toolbar.component.tsx	Switches submit-disable computation to getIsSubmitDisabled and includes invalid-annotation signal from actions provider.

[github-actions]

📊 Test coverage report

Metric	Coverage
Lines	60.2%
Functions	56.9%
Branches	51.8%
Statements	59.8%

[github-actions]

🐳 Docker image sizes

Device	Size
cpu	4002.9 MB (3.91 GB)
xpu	10791.5 MB (10.54 GB)
cuda	10198.1 MB (9.96 GB)

[jpggvilaca]

why not useIsSubmitDisabled and call useAnnotationActions there since here we're just passing them around from 1 hook to an util

[dwesolow]

No strong reason, we still need to call useAnnotationActions to get submitAnnotations, submitPredictions, initialAnnotations, initialPredictions. But we can move to hook itself as well if you find it better.

[jpggvilaca]

yeah i know, but here the method is just used as a bridge, we can just get it directly if it becomes a hook

[dwesolow]

Updated, thanks