[maximusunc]

What

1. Bumps the HelmsDeep pin in requirements-runners.txt from v0.4.0 to v0.5.0.
2. Renames the sweep example targets from aragorn / arax / bte to shepherd-aragorn / shepherd-arax / shepherd-bte, and documents why the name matters.

Why

HelmsDeep v0.5.0

v0.5.0 stops counting an ARA's refusal of a query type it doesn't support as a load failure. BTE answers every Pathfinder query with a 500 saying "BTE does not support Pathfinder type queries.", so the mixed (aras_mixed) run against BTE failed every checkpoint on Pathfinder errors.

On the sync path, HelmsDeep now treats such a refusal as unsupported instead of failed. That covers a 501, or a "does not support" / "not supported" / "not implemented" message in the response's status, description or error-level logs. An unsupported answer:

• adds no error and no latency sample
• isn't sent again for the rest of the run, so that class's users sit idle
• isn't judged in that class's checkpoint
• is reported in the run's summary output and summary.json

The ARS path is unaffected. A related Shepherd change, BioPack-team/shepherd#200, makes BTE return 501 for Pathfinder. HelmsDeep handles either form, so this pin doesn't depend on it.

Sweep target names

The sweep passes each target's NAME to --target. With the default --trapi_version auto, the version is looked up in SmartAPI as infores:<NAME>. The Shepherd-hosted ARAs are registered as infores:shepherd-aragorn, infores:shepherd-arax and infores:shepherd-bte. A sweep using the bare names read the wrong entries, or none: when nothing is found it falls back to 2.0.0 with only a log warning. As a result, Aragorn and BTE were sent TRAPI 2.0 while SmartAPI lists them at 1.6.0.

Updated:

• README.md
• the test_harness/sweep.py docstring and --help
• deploy/cronjob.example.yaml
• deploy/helm/test-harness/values.example.yaml
• the chart's sweep.targets error message

The README and the --target / NAME help now say the name must be the infores the service is registered under in SmartAPI. They also say what else the name controls: each target's output directory and filename prefix, and the agent the Information Radiator reports under.

Testing

• The first CI run failed only at pip install, because the v0.5.0 tag didn't exist yet. It now exists on HelmsDeep main (merge of Don't score an ARA's "not supported" refusal as a load failure HelmsDeep#23).
• Locally on Python 3.11 with HelmsDeep 0.5.0 installed: pytest passes (205 tests) and black --check . is clean.

🤖 Generated with Claude Code

https://claude.ai/code/session_01S2yuRAujys2XXK6YPjSay3