🎨📝 web-api: New batch of improved user-facing messages

[pcrespov]

What do these changes do?

Introduces a new batch of user-facing messages, generated with the help of AI prompts and manually reviewed for accuracy.

Workflow

1. Annotate user-facing messages in the web server using the user_message function.
2. Generate suggestions via the AI prompt.
3. Manually review and correct outputs as needed.
4. Iteratively refine the prompt to prevent recurrence of identified issues.

Related issue/s

How to test

It is important to audit the outputs

• please check randomly some message and assess whether they comply with docs/user-messages-guidelines.md

Dev-ops

None

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 87.78%. Comparing base (0571243) to head (0e93266).
Report is 1 commits behind head on master.

Additional details and impacted files

@@            Coverage Diff             @@
##           master    #7944      +/-   ##
==========================================
- Coverage   87.84%   87.78%   -0.06%     
==========================================
  Files        1849     1423     -426     
  Lines       71335    59152   -12183     
  Branches     1250      626     -624     
==========================================
- Hits        62663    51926   -10737     
+ Misses       8310     7016    -1294     
+ Partials      362      210     -152     

Flag	Coverage Δ
integrationtests	64.29% <100.00%> (+0.04%)	⬆️
unittests	86.09% <100.00%> (-0.35%)	⬇️

Components	Coverage Δ
api	∅ <ø> (∅)
pkg_aws_library	∅ <ø> (∅)
pkg_celery_library	∅ <ø> (∅)
pkg_dask_task_models_library	∅ <ø> (∅)
pkg_models_library	∅ <ø> (∅)
pkg_notifications_library	∅ <ø> (∅)
pkg_postgres_database	∅ <ø> (∅)
pkg_service_integration	∅ <ø> (∅)
pkg_service_library	71.54% <ø> (ø)
pkg_settings_library	∅ <ø> (∅)
pkg_simcore_sdk	85.10% <ø> (-0.06%)	⬇️
agent	96.29% <ø> (ø)
api_server	92.64% <ø> (ø)
autoscaling	96.03% <ø> (ø)
catalog	92.29% <ø> (ø)
clusters_keeper	99.13% <ø> (ø)
dask_sidecar	91.79% <ø> (ø)
datcore_adapter	97.94% <ø> (ø)
director	76.73% <ø> (ø)
director_v2	91.12% <ø> (ø)
dynamic_scheduler	96.69% <ø> (ø)
dynamic_sidecar	90.09% <ø> (ø)
efs_guardian	89.65% <ø> (ø)
invitations	93.60% <ø> (ø)
payments	92.57% <ø> (ø)
resource_usage_tracker	89.00% <ø> (ø)
storage	86.27% <ø> (-0.21%)	⬇️
webclient	∅ <ø> (∅)
webserver	87.70% <100.00%> (+0.10%)	⬆️

---

Continue to review full report in Codecov by Sentry.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 0571243...0e93266. Read the comment docs.

🚀 New features to boost your workflow:

• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[pcrespov]

@mergify queue

[mergify]

queue

🛑 The pull request could not be merged

This could be related to an activated branch protection or ruleset rule that prevents us from merging. (details: 2 of 6 required status checks are expected.)

[sanderegg]

maybe search for "studies" as well

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

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

See analysis details on SonarQube Cloud

[matusdrobuliak66]

Nice 👍

[mergify]

This pull request has been removed from the queue for the following reason: pull request dequeued.

Pull request #7944 has been dequeued. The pull request could not be merged. This could be related to an activated branch protection or ruleset rule that prevents us from merging. (details: 2 of 6 required status checks are expected.).

You should look at the reason for the failure and decide if the pull request needs to be fixed or if you want to requeue it.
If you do update this pull request, it will automatically be requeued once the queue conditions match again.
If you think this was a flaky issue instead, you can requeue the pull request, without updating it, by posting a @mergifyio requeue comment.