notebooks: PRT work pt1

[validbeck]

Pull Request Description

What and why?

sc-15850

Updating the notebooks to reflect the new PRT functionality in parts. This part covers mainly conceptual edits of the notebooks, primarily the tutorials and quickstarts that get surfaced in guides in the documentation.

Important

Refer to "What needs special review?" for the parts that have yet to be updated.

Terminology refresh examples

Almost every notebook had its prose normalized:

• "model risk management" → "risk management"
• "model documentation" → "documentation"
• "documenting models" → "documenting records such as models"
• "model validators" → "validators"

Directory & file renames

• notebooks/tutorials/model_development/ → notebooks/tutorials/development/
• notebooks/tutorials/model_validation/ → notebooks/tutorials/validation/
• notebooks/use_cases/model_validation/ → notebooks/use_cases/validation/
• notebooks/quickstart/quickstart_model_documentation.{ipynb,Rmd} → quickstart_documentation.{ipynb,Rmd}
• notebooks/quickstart/quickstart_model_validation.{ipynb,Rmd} → quickstart_validation.{ipynb,Rmd}
• notebooks/how_to/tests/run_tests/1_run_dataset_based_tests.ipynb → 1-run_dataset-based_tests.ipynb
• notebooks/how_to/tests/run_tests/2_run_comparison_tests.ipynb → 2-run_comparison_tests.ipynb
• notebooks/tutorials/validation/3-developing_challenger_model.ipynb → 3-developing_potential_challenger.ipynb

All associated PNGs/GIFs and lr_model_champion.pkl / xgb_model_champion.pkl moved with their notebooks.

Repo-side updates to match the renames

• .gitignore — updated !notebooks/... allowlist entries for the moved .pkl fixtures.
• scripts/run_e2e_notebooks.py — updated quickstart_model_documentation.ipynb paths to quickstart_documentation.ipynb (in both NOTEBOOKS_TO_RUN and DATA_TEMPLATE_NOTEBOOKS).
• README.md, README.pypi.md, r/validmind/README.md — updated the R .Rmd filenames and added a pointer to the PII detection how‑to notebook.

Stale URL fixes

Any existing renames from the documentation side have been updated in this PR to clean up redirects out to the guides.

How to test

Pull the PR down and spot check some notebooks, keeping in mind the special review section.

What needs special review?

• Notebooks I've already thoroughly edited got a more thorough pass of terminology. If you notice a notebook looks incomplete, it's probably because it's still on the list for style/accuracy edits.
• KEY CONCEPTS HAS NOT BEEN UPDATED IN ANY NOTEBOOK YET. I need to update them in the docs site side to make things consistent before replicating in notebooks. Story is tracked under 15992 in Shortcut.

Dependencies, breaking changes, and deployment notes

• Notebooks pulled into JupyterHub here (needs a quick deploy): https://github.com/validmind/demo-environment/pull/28
• Notebooks pulled into documentation here: docs: Models > Records — Developer portal, quickstarts, & training documentation#1328

Release notes

n/a

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)

[jamadriz]

Nice work! My agent helped me check with these comments 😄

---

Must-fix (blocking or near-blocking)

1. README typo: “PPI” instead of “PII”
   The new link text says “Enable PPI detection”; it should be PII (personally identifiable information).
   README.md
   Lines 70-70
   For an extended guide, refer to our how-to notebook: Enable PPI detection

Should-fix (quality / consistency)
2. Double space after “collaborate on”
Many notebooks/templates now contain collaborate on documentation (two spaces). That almost certainly comes from replacing “model documentation” with “documentation” while leaving an extra space. It reads as a typo in rendered HTML and shows up in many files (quickstarts, templates, how-tos, use cases). A repo-wide replace of on documentation → on documentation (or a fuller phrase like “on documentation for your records”) would clean this up.

3. GitHub “bidirectional / hidden Unicode” warning
   GitHub flagged hidden or bidirectional Unicode in at least one file in the PR thread. Worth running a targeted scan (or opening the flagged file in an editor that shows hidden characters) so nothing odd ships in prose or URLs.

Nice-to-have / pre-existing
4. application_scorecard_demo.ipynb in DATA_TEMPLATE_NOTEBOOKS
scripts/run_e2e_notebooks.py still points at notebooks/use_cases/credit_risk/application_scorecard_demo.ipynb, which does not exist in the tree (only application_scorecard_full_suite.ipynb, _with_ml, etc.). That path is already wrong on main; this PR did not introduce it. Still worth a separate small fix so e2e template runs do not reference a missing notebook.

[jamadriz]

please see comment

[validbeck]

@jamadriz Fixes applied in commit #c0206e6

All four review items from PR #509's comment are applied. Summary of the diff (54 files):

Item	Files	Change
1. PPI → PII	README.md	Link text fix on line 70
2. Double-space collapse	51 notebooks + Rmd	on documentation → on documentation (one-occurrence-per-file replacement; all 51 hits were the same "collaborate on documentation. Together,…" sentence)
3. Hidden Unicode	notebooks/tutorials/development/4-finalize_testing_documentation.ipynb	Removed single U+200B before **ValidMind Insights** on line 909
4. Missing scorecard demo	scripts/run_e2e_notebooks.py	application_scorecard_demo.ipynb → application_scorecard_full_suite.ipynb in DATA_TEMPLATE_NOTEBOOKS