CLI direction

The proposed CLI is an operator and developer companion for inspecting access, validating safe fixtures, and reviewing workflow evidence from a terminal.

No CLI is distributed today. There is no approved package, binary, installer, authentication command, or executable command contract. This page defines product expectations for a future release.

Intended job families

Job	Expected behaviour	Availability
Access inspection	Explain the active environment and workspace without printing credentials.	Design direction
Fixture validation	Run deterministic checks against a local synthetic or redacted file.	Design direction
Workflow inspection	Read authorised state and evidence without implying provider execution.	Design direction
Operational mutation	Require a published contract, explicit scope, idempotency, and confirmation.	Unavailable

Security requirements

Credentials belong in an operating-system or deployment secret store, never command history or config committed to source control.
Human-readable output must avoid customer data and secret material by default.
Machine-readable output needs a versioned schema and non-zero exit codes for failures.
Destructive or provider-visible actions must be clearly distinguished from reads and previews.
Environment and workspace scope must be visible before any consequential confirmation.

Release checklist

A future CLI page must publish signed distribution channels, supported platforms, checksums, version compatibility, installation and upgrade paths, authentication setup, complete command reference, output stability, telemetry behaviour, and support lifecycle before commands are presented as usable.

Until then, use the public contract for schema semantics and the access guide for private-preview boundaries.