v0.13.0

This release reorganizes the Alteryx One command tree and makes positional resource identifiers the stable interface.

Breaking changes

The ayx one namespace is now primitive-first. one platform {workspace,role,person,token} becomes one {workspace,role,person,token}; one platform auth login becomes one login; auth status/diagnosis moves to one auth; one platform user becomes one whoami; and the old status and platform inventory paths are removed or replaced by their current one forms. one doctor platform becomes one doctor identity, while one api remains available.

Required One resource identifiers are now positional. For example, use one flows detail <id>, one plans run <id>, one job-groups status <id>, and one connections detail <id>. Two-id operations take ordered positionals, connector metadata takes a connector slug, dataset detail uses positional ids, and one flows import takes its input positionally. There are no pre-release compatibility aliases; context selectors and payload controls remain flags.

Other changes

• Stable command help is backfilled. Server, SQL Server, Mongo, doctor, tools, license, and other stable families now have informative --help descriptions; the One subtree follows in v0.13.1.
• The project now states its independent status and trademark disclaimer in the README, NOTICE, and docs footer.
• Release and CI builds use --locked; the README documents Windows artifacts and the docs-site development command.
• one auto-insights and one desktop-exec were removed. They were configuration stubs that performed no One work and could fail on One-only profiles.
• CLI error and output contracts were hardened. Errors exit non-zero without appending stray text to JSON, required-argument errors classify as validation, output formats are constrained, and the OTP prompt flushes before reading input.
• One API coverage metadata was corrected for live flow, workspace, and IAM routes.