v0.21.0-rc.1

This release candidate delivers the Phase 3 operator-intake output contract and the canonical Alteryx One Job Library command family.

The binary’s own Cargo package version is 0.21.0-rc.1 — it matches the v0.21.0-rc.1 tag exactly, so ayx --version on this candidate is honest and ayx self update can later move an RC install forward to the final 0.21.0 release.

Breaking: --output json-full and --error-format removed

--output json-full and --error-format are gone. The compact ayx.output.v1 envelope (schema_version/kind) no longer exists; --output json now always emits the full, recursively redacted envelope that json-full used to produce. If a script was told by the 0.18.0 or 0.20.0 notes to use json-full for the lossless envelope, switch it to plain json — running with the retired flags now exits 2 with a usage error instead of succeeding.

Every JSON envelope that carries a descriptor also reports command as a top-level field again, naming the exact invocation that produced the result (e.g. one.jobs.detail), so a caller can correlate a result or a failure with the command that produced it without inferring it from context.

Job Library commands

Use the new Jobs surface for aggregate Job Library entries and their child runs:

ayx one jobs <JOB-ID>
ayx one jobs runs <JOB-ID>
ayx one jobs execute --body request.json

jobs runs shows the complete lifecycle, status, timing, warning/error, and execution metadata returned for every child run. JSON remains recursively redacted and retains the provider response without presentation-only labels.

ayx one job-groups remains callable as a hidden compatibility namespace for this release cycle. It is intentionally excluded from help, catalog, and normal discovery. There is no singular child-run detail command: the vendor exposes a child-run collection and a status-only direct child route, not a complete child record endpoint.

Output and operator intake

• Text and JSON use aligned canonical command labels.
• Human output includes remediation and timestamp precision suitable for operators; machine output retains exact redacted timestamps.
• Named output collections remain explicit opt-in projections.
• Agent Assets remains hidden because its API contract does not support bearer authentication for the supported credential profiles.

Validation

The RC is gated by formatting, generated command-surface validation, locked workspace Clippy and nextest, audit, release builds, and a live Alteryx One read sweep from the packaged Windows artifact. The live check includes a Job Library entry with multiple child runs.