Krzysztof kuhy Rudnicki 37cc00fa21 Say which jupyter problem it is, and regenerate the status table ... `_works jupyter || _blocked "needs jupyter"` collapsed two different problems into one message. "needs jupyter" and "jupyter is on PATH but does not run" send you to different fixes -- install it, versus work out why the shim's interpreter is gone -- and a status table is only worth keeping if it says which. `_require_working` checks presence and then execution, and reports them separately. The wording is now what DOCS-runnability.md already said for twm_4 and PBAD, except the probe produces it rather than someone having typed it. Regenerating the table changed those two rows and nothing else, which is the useful part: the run guard, the two new .venv directories under PSD and ERSMS-project, and the tex entry-point change left all 44 courses' status exactly as it was. One thing worth knowing for the next regeneration: the answer depends on PATH. jupyter lives in ~/.local/bin, so a shell without it reports "needs jupyter" and one with it reports the dead shim. Regenerate from a login shell. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>		2026-08-29 08:44:02 +02:00
..
known-incomplete.txt	Run all 33 safe courses; fix what that broke	2026-08-28 18:52:31 +02:00
runnability-local.tsv	Say which jupyter problem it is, and regenerate the status table	2026-08-29 08:44:02 +02:00
vendored.txt	Hold the coursework to the same lint bar as the tooling	2026-08-28 19:53:04 +02:00