packaging: ship judge_corpus and score_corpus JSON via package-data

[kurosawareiji7007-hub]

Summary

benchmark.judge_corpus and benchmark.score_corpus are listed under [tool.setuptools] packages, but there is still no [tool.setuptools.package-data]. An installed wheel/sdist therefore contains only __init__.py for those packages — not manifest.json or scenarios/*.json.

After pip install, MANIFEST_PATH / SCENARIOS_DIR point at missing files, so load_corpus() and tools like python -m scripts.calibrate_judge fail on an installed distribution (they only work from a source checkout).

Expected

Declare package data in pyproject.toml only, e.g.:

oml [tool.setuptools.package-data] "benchmark.judge_corpus" = ["manifest.json", "scenarios/*.json"] "benchmark.score_corpus" = ["manifest.json", "scenarios/*.json"]

Note

#2307 / #2310 covered this earlier and were closed without a review comment while CI was green. Re-raising because the packaging gap is still present on test.

[vanguarstew]

This is a direct prerequisite for the benchmark's reproducibility and installed-distribution correctness, so it fits the current roadmap (M2/M3 evidence layer). The fix is a small, well-scoped pyproject.toml change plus a test that verifies the data is present in a built wheel/sdist. Please add a test under tests/ that builds the package (or inspects the wheel) and asserts the JSON files are included, and reference this issue in the PR. Note that #2307/#2310 were closed without review; this re-raise is valid because the gap persists on test.