Summary
Improve CARLISLE wrapper CLI output so users can quickly understand current phase, status, and next actions.
Problem
Current wrapper output is functional but inconsistent in formatting and message intent, making it harder to scan during init/dryrun/run and harder to recover from errors quickly.
Scope
- Standardize user-facing output style (for example: INFO/STEP/WARN/ERROR/OK patterns)
- Make phase transitions explicit (preflight, dryrun, submission, completion/failure)
- Improve actionable error text for common setup/run failures
- Keep implementation in existing wrapper logic only
Requirement
No extra files should be created as part of implementation.
Acceptance Criteria
Summary
Improve CARLISLE wrapper CLI output so users can quickly understand current phase, status, and next actions.
Problem
Current wrapper output is functional but inconsistent in formatting and message intent, making it harder to scan during init/dryrun/run and harder to recover from errors quickly.
Scope
Requirement
No extra files should be created as part of implementation.
Acceptance Criteria