Required vs optional arguments are clear

deploy target env tells the user nothing about which argument is required, which is optional, or what the default is. They guess, hit an error, guess again, and eventually give up. Unclear argument signatures also break automated documentation and API-shaped wrappers that parse help output. When a missing required argument triggers a stack trace instead of Error: missing argument <target>, users interpret the tool as unstable and stop using it in CI.

Use angle brackets for required arguments and square brackets for optional ones in command signatures, and pass show_default=True (or equivalent) so defaults appear in --help. In src/cli/commands/deploy.ts:

program
  .command('deploy <target> [environment]')
  .description('Deploy to target (environment defaults to production)')
  .option('-p, --port <number>', 'Port to use', '3000')