Merge staging into prod — 26.04 release

[nrichers]

Pull Request Description

What and why?

This PR releases our 26.04 docs to production.

How to test

What needs special review?

Dependencies, breaking changes, and deployment notes

Release notes

Checklist

• What and why
• Screenshots or videos (Frontend)
• How to test
• What needs special review
• Dependencies, breaking changes, and deployment notes
• Labels applied
• PR linked to Shortcut
• Unit tests added (Backend)
• Tested locally
• Documentation updated (if required)
• Environment variable additions/changes documented (if required)

[github-actions]

PR Summary

This pull request introduces a series of changes primarily focused on documentation and instructional materials across multiple notebooks, tutorials, release notes, and workflow configuration files. The main changes are:

1. Python Version Recommendation Update: Many code cells and alert messages have been updated to change the recommended Python version ranges from "Python 3.8 <= x <= 3.11" (or "3.9 <= x <= 3.11") to "Python 3.8 <= x <= 3.14." This ensures that users are directed to use a newer version that is verified with the code.

2. Nomenclature Standardization: Several instances of the term "User Action v2" have been replaced with "User Action" to simplify and unify the naming conventions across workflow steps and configuration files.

3. UI and Link Updates: Minor adjustments in release notes and support documents include an update to a broken/deprecated link for accessing the "Breaking changes & deprecations" documentation and adds missing anchor spans for consistent navigation in training and troubleshooting sections.

4. Minor Formatting and Consistency Updates: Additional changes include the removal of extraneous markdown comments, adjustments in sidebar and contents navigation markers, and minor tweaks in workflow configuration examples.

The changes do not alter the core functionality of the code but help improve clarity, consistency, and up-to-date guidance for developers and users interacting with the ValidMind platform and its documentation.

Test Suggestions

• Open and run several notebooks (e.g. quickstart_model_documentation.Rmd, quickstart_model_validation.Rmd, and corresponding .ipynb files) to validate that the updated recommended Python version messages display correctly.
• Verify that navigation anchors and link updates (especially for 'User Action' and 'Breaking changes & deprecations') work as expected in the rendered HTML documentation and on the ValidMind Platform.
• Confirm that workflow configuration files correctly reference the updated step terminology without breaking any automated process.
• Test that the upgrade instructions in the _how-to-upgrade.qmd file render correctly and that the troubleshooting page includes the upgraded content.

[github-actions]

Lighthouse check results

⚠️ WARN: Average accessibility score is 0.87 (required: >0.9) — Check the workflow run

Show Lighthouse scores

Folder depth level checked: 0

Commit SHA: 31f6178

Modify the workflow to check a different depth:

• 0: Top-level navigation only — /index.html, /guide/guides.html, ...
• 1: All first-level subdirectories — /guide/.html, /developer/.html, ...
• 2: All second-level subdirectories — /guide/attestation/*.html, ...

Page	Accessibility	Performance	Best Practices	SEO
/developer/validmind-library.html	0.85	0.66	1.00	0.82
/get-started/get-started.html	0.85	0.70	1.00	0.73
/guide/guides.html	0.81	0.70	1.00	0.82
/index.html	0.93	0.68	1.00	0.82
/releases/all-releases.html	0.86	0.68	1.00	0.73
/support/support.html	0.91	0.70	1.00	0.82
/training/training.html	0.85	0.66	0.96	0.73

[github-actions]

Execute training notebooks for PRs

✓ INFO: Live previews are available —

• Open model development series
• Open model validation series

[github-actions]

Validate docs site

✓ INFO: A live preview of the docs site is available — Open the preview