| Files | Last commit | Last update |
|---|---|---|
ci: run the Python unit tests on the GitCode test job The three Python test modules ran only on the GitHub mirror (wired in !603); the GitCode test job had zero Python steps (its seven python references all live in the package job's wheel pipeline), so record- mode, wrapper, and remote-facts regressions had no signal on the primary platform. Add the same explicit three-module unittest step the GitHub ubuntu job runs. This is deliberately added without setup-python: the PR's own GitCode CI run doubles as the codearts runner python3 availability probe (issue 630) - a green run proves availability and lands the wiring in one step; a command-not-found failure means setup-python needs adding instead. Step content is the contract suite's declared uncovered dimension, so the 21 mutation negatives pass unchanged; the 5.4 job table syncs the test row wording. Refs #630 Co-Authored-By: Claude Code <noreply@anthropic.com> | 12 days ago |