Live contract tests for the ProcessingStep name resolution, run against a real JMA with PINEXQ_LIVE_TESTS=1 uv run pytest -m live (they are skipped otherwise), so a mismatch between what the CLI sends and how the JMA filters is caught (#71).
Fixed
processing-step show <name> and <name>@<version> (and every Bound verb that takes such a reference) reported an existing ProcessingStep as not found. The name lookup sent the JMA’s ShowDeprecated and ShowPrerelease filters as true to include those versions, but the JMA reads true as “only these”, so the two together matched nothing. The lookup now sends no such filter, so deprecated, prerelease, and hidden versions all resolve (#71).
When a pinned version does not exist, the error now says which half failed: no ProcessingStep named <name>, or <name> has no version <version> followed by the versions that do exist (#71).
--hidden on job list, workdata list, and processing-step list, and --deprecated / --prerelease on processing-step list, now include those Resources as documented. They used to return only those Resources, for the same reason. processing-step list also excludes deprecated ProcessingSteps and prerelease versions by default now, as its help text always said.
