ci: run the test suite

[CybotTM]

Four suites under tests/ exist, pass, and nothing executes them — lint, validate and release never touch tests/. A test no pipeline runs is not a gate; it only looks like one.

This calls the reusable added in netresearch/skill-repo-skill#211, so a fix to the runner reaches every skill repo at once instead of being copied per repo.

Context: a fleet measurement found 27 of 33 skill repos shipping scripts had no test file at all, and none of the 20 reusable workflows ran tests/. This repo is the opposite case — the tests were already written, they were simply never wired to anything.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[Copilot]

Copilot was unable to review this pull request because the user who requested the review has reached their quota limit.

[CybotTM]

Closing: the premise was wrong. lint.yml already calls ci-python.yml with test-command: … python -m unittest discover -s tests -v, so these four suites have been gated all along — the Python / Test job on this very PR ran them.

My check grepped the workflows for tests/ with a slash and missed -s tests. A narrowing pattern of my own making produced a finding about the world.

Merging this would run the same four tests twice per PR for no added coverage. The reusable stays the right tool where shell tests exist, which ci-python.yml cannot reach — that is the case in skill-repo-skill and automated-assessment-skill, and it is not the case here.