Runtime smoke test

This page runs a one-line lab in Python and JS to verify the in-browser runtime works. If the Run button is broken on a real module page, start here: this page strips away every module-specific concern (KaTeX, flavor CSS, gate logic) so a failure here points at the runtime itself rather than the module.

Expected outcome: a green ✓ 2 tests passed pill after you press Run. If you see a red pill or no pill at all, the diagnostics panel below shows which load step is failing.

Diagnose whether the in-browser runtime is healthy. — press Run; expect "2 tests passed"; — if anything goes wrong, the diagnostics below show why. # Trivial smoke test — proves the Python runtime executes and the # test reporter parses `N tests passed` from stdout. def add(a, b): return a + b assert add(2, 3) == 5 assert add(-1, 1) == 0 print("All 2 tests passed (python runtime smoke)") // Trivial smoke test — proves the JS runtime executes and the // test reporter parses `N tests passed` from stdout. function add(a, b) { return a + b; } console.assert(add(2, 3) === 5, "2 + 3 should be 5"); console.assert(add(-1, 1) === 0, "-1 + 1 should be 0"); console.log("All 2 tests passed (js runtime smoke)");

Diagnostics

Updated automatically as the page loads and as you press Run.

… flavor-boot.js applied ?
… runtime.js loaded (window.NeuralForge present)
… <code-lab> custom element registered
… forge.state readable from localStorage
… forge.state.labs["smoke-test"] = pass (after Run)

Cross-ref: runtime tier explainer · AI Tutor setup (the Ask Tutor button on a failure pill needs the proxy running).