All versions since [0.4.1]

[0.4.1]

Sep 6, 2026

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).

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.

Sep 7, 2026

job start --wait and template run --wait now wait for the resulting Job to reach a terminal state and exit non-zero when it does not complete successfully. --timeout limits the wait while leaving the Job running.

Sep 8, 2026

Step-by-step Job composition (#49). job create --name NAME now creates an empty Job to compose, --processing-step keeps the one-shot RapidSetupJob behaviour, and --parent JOB [--inherit-folder] creates a sub-job; a flag the chosen Action has no property for is a usage error before anything is sent.
job select-processing, job configure, job set-input, and job clear-input select a Job’s ProcessingStep, configure its parameters, and assign, source from a folder (--folder PATH [--no-recursive]), or clear the WorkData on one input DataSlot. job configure --param is typed against the Action’s own schema, falling back to the selected ProcessingStep’s parameter schema.
Input DataSlots are addressed by 0-based index or case-insensitive name, on job set-input / clear-input and on the Template verbs, and job show and template show now list the index.

Actions on sub-entities such as DataSlots stay reachable through the Bound verbs above rather than the generic action command (ADR-0006).