Save button color mismatch on Soft constraints tab (tc05_forms_derived)

Description

When navigating to the "Soft constraints" tab in project tester-ws-1/tc05_forms_derived, the fields correctly show the soft-constraint warning state (yellow). The form's Save button, however, remains green instead of reflecting the warning state (yellow). The Save button color does not match the field-level warning state and may mislead users about whether soft constraints are active.

Environment
Staging

Application (+ app version, build, operating system)

• Mergin Maps Mobile app: 2025.7.0 (build 721011)
• Project: tester-ws-1 / tc05_forms_derived
• Device / OS: (please add device model and OS/version used for testing)

Steps to reproduce

1. Open Mergin Maps Mobile and download/open project tester-ws-1 / tc05_forms_derived.
2. Record a new feature in the Bears layer.
3. Open feature form and nap to the Soft constraints tab.
4. The fields display a yellow warning state (soft constraint).
5. Observe the Save button color on the form.

Actual results

• The fields show a yellow warning state (soft constraint).
• The Save button remains green (success/primary color), which does not match the field warning state.

Expected results

• When one or more fields are in a soft-constraint (warning) state, the Save button should visually indicate that by matching the warning color (yellow) or otherwise providing consistent visual feedback that soft constraints are active.
• The inconsistency between field warnings and Save button color can mislead users about the current validation state.

Conclusion
This is a visual/UX inconsistency where the Save control doesn't reflect the soft-constraint warning state shown on the form fields. It would improve clarity and reduce user confusion if the Save button used a matching warning styling or provided a clear visual indicator when soft constraints are present.

Created by GitHub Copilot and supervised by a human test analyst.

Reproduce the issue in Mergin Maps Mobile using tester-ws-1/tc05_forms_derived, then start from the form's Soft constraints tab and inspect how the Save button reflects field validation state. Done means the Save control provides warning-consistent visual feedback when soft constraints are active; no source file or test is named in the issue.