pinexq job logs <ref> prints the Log entries of a Job, oldest first, following the Job’s Logs link to the monitoring service and paging through the whole log. -o text|raw|json selects the line format (text colours the level on a TTY, JSON is NDJSON), --level, --search, and --tail filter in the CLI, and --no-color (or NO_COLOR) forces plain output.
pinexq job metrics <ref> shows the Metrics of the Worker that ran a Job: a header with status, duration, and peak CPU and memory, followed by terminal plots of both series. -o json and -o csv emit the full series instead.
actions and action on every Resource noun, executing the hypermedia Actions the JMA advertises instead of a hardcoded set. actions <ref> lists what a Resource offers right now with each parameter’s type; action <ref> <name> executes one by name in any spelling. --root targets the Resource type’s creation Actions. Parameters come from --set KEY=VALUE and --json, typed and validated against the Action’s schema before anything is sent, and --dry-run prints the request without sending it.
Bound verbs on every noun, each wrapping exactly one advertised Action with typed flags: job start, delete, hide, unhide, rename, tag, move, set-error, and create; wd delete (with --force for a WorkData whose deletion is not allowed yet), hide, unhide, rename, comment, tag, move, upload, and download; ps deprecate, restore, delete, hide, unhide, rename, tag, move, set-defaults, and clear-defaults; template run, delete, edit, tag --scope, set-params, clear-params, set-input, clear-input, and create; trigger enable, disable, delete, edit, set-templates, set-cron, set-window, and create; folder create, rename, move, delete, and clear.
The multi-reference Bound verbs act on several Resources at once, read references from stdin with - (so job list -q --state failed | job delete - -y works), report a reference that fails and continue with the rest, and exit 1 if any failed.
wd upload <file> creates a WorkData from a local file, guessing the media type from the extension and applying --tag and --folder afterwards; wd download <ref> streams the content to a file, a path, or stdout, and refuses to overwrite without --force.
job create builds a fully configured Job in one request: ProcessingStep, --param values typed against the Function’s own schema, --input WorkData assignments (several per slot assign a collection), tags, a Folder, and --start.
An Action the JMA marks Destructive asks for confirmation before it runs. --yes skips the prompt, and without a terminal the command refuses rather than hanging.
show in table output now ends with the names of the Actions the Resource offers, so the next step is on screen. JSON and CSV output of show are unchanged.
README sections for the Action verbs, every noun’s Bound verbs, job logs, and job metrics.
Changed
The root --help groups the Resource commands under a “Resources” panel, and each noun lists its Bound verbs in a panel of their own.
New runtime dependencies: jsonschema (parameter validation) and plotille (the job metrics plots).
