Rust CLI Delivery

Treat the command-line interface as a stable user protocol rather than embedding business logic directly in main. Complete an end-to-end loop from contract confirmation, implementation to real process verification.

Confirm Constraints

Before making changes, confirm requirements, existing help text, scripts, READMEs, tests, and release configurations:

• Command name, subcommands, arguments, defaults, mutual exclusions, compatibility requirements;
• Human output format versus machine output (quiet mode, verbose, JSON, colorless);
• Input priority for stdin, files, and arguments; stdout/file write destinations;
• Exit codes corresponding to success, usage errors, data errors, transient failures;
• Supported platforms, shells, TTY/pipes environments, MSRV, dependency versions;
• Configuration file precedence over environment variables over command-line options.

If critical contracts are missing, infer the minimal compatible solution from existing behavior and tests while explicitly stating assumptions. Do not arbitrarily alter flags, output text, or exit codes.

Workflow