26.02 release

[nrichers]

Pull Request Description

What and why?

This PR releases our 26.02 docs to prod.

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)

[CLAassistant]

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.
3 out of 4 committers have signed the CLA.

✅ validbeck
✅ github-actions[bot]
✅ nrichers
❌ cachafla
_{You have signed the CLA already but the status is still pending? Let us recheck it.}

[github-actions]

Pull requests must include at least one of the required labels: internal (no release notes required), highlight, enhancement, bug, deprecation, documentation. Except for internal, pull requests must also include a description in the release notes section.

[github-actions]

PR Summary

This PR is a massive update that adds a standard ValidMind copyright and licensing notice to a large number of files across the repository. Changes include:

• Adding a copyright block (with a reference to the LICENSE file and SPDX identifier) in the YAML frontmatter of Quarto (.qmd) files, YAML (.yml/.yaml) files, and even files starting with _ requiring special handling.
• Introduction of two helper scripts: add_copyright.py to add the copyright header to files and verify_copyright_qmd.py to verify that all documentation files have the required copyright header.
• Inclusion of a separate file copyright.txt containing the authoritative copyright/licensing text.
• Updates to the training/troubleshooting, support, internal testing, and reference files to include the new copyright notice.

The changes affect frontmatter in documentation source files as well as configuration and deployment files, ensuring that legal notices are consistently embedded across the project. These modifications help with compliance and ensure that all published documentation carries the required copyright and license information.

Test Suggestions

• Run the provided scripts (e.g., python site/scripts/add_copyright.py and python site/scripts/verify_copyright_qmd.py) to confirm that all files have the correct copyright header.
• Manually inspect a sample of .qmd and YAML files to verify that the header is present and properly formatted.
• Use the CI pipeline (if available) to check for failures in copyright verification with the make verify-copyright target.

[github-actions]

Validate docs site

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

[github-actions]

Execute training notebooks for PRs

✓ INFO: Live previews are available —

• Open model development series
• Open model validation series