Silent doc failures not being detected

Desired documentation content.

Building the docs currently only checks for complete failures and errors, however there are issues that can occur that do not cause the cell to completely fail, but can produce the wrong answer. A current example of this is additional_flight_phases.ipynb, where a number of runtime warnings pop up. This is both concerning for a user reading the docs who doesn't know if these warnings are serious or not, and could lead to a doc showing the incorrect answer for an example.

We need to start baking asserts and other checks similar to our unittests and benchmark tests into doc cells (probably separate hidden cells) so we immediately know if something changed

Is there any existing documentation on your requested topic? Please describe.

No response

Start by reproducing the documentation build and inspecting additional_flight_phases.ipynb, especially the cells that emit runtime warnings. Read the existing unittest and benchmark-test patterns mentioned in the issue to understand how checks are structured. Done means documentation examples detect incorrect or warning-producing results rather than silently passing.