eval: evaluate_pyro_annotator omits transitive core deps (tubes.py, types.py, ...)

evaluate_pyro_annotator in eval/dvc.yaml declares fewer ../core deps than evaluate@train/@val, but reaches the missing ones transitively at runtime: inference.py imports .tubes/.types/.logistic_calibrator, and model.py imports .package/.tubes/.types. Missing from the dep list: tubes.py, types.py, logistic_calibrator.py, sequences.py, package.py, temporal_classifier.py.

Consequence: a change that touches only e.g. core/tubes.py (tube linking — exactly what the pyro-annotator scoring exercises) leaves the stage's lock untouched and dvc repro declares it up to date, so the stage the retrain runbook designates as the acceptance gate can report metrics produced by different code than reviewed. The v4.1.0 run wasn't affected only because model.zip changed too.

Fix: align the dep list with evaluate@train/@val (or factor the shared list). Noticed in the PR #65 review; kept out of that PR to avoid scope creep.

Start in eval/dvc.yaml by comparing evaluate_pyro_annotator with evaluate@train and @val. Check the dependency entries for the six named core files, then verify that a change to one of them causes the evaluation stage to be considered out of date by DVC. Done means the pyro-annotator stage tracks the same relevant dependencies as the other evaluation stages.