-
Notifications
You must be signed in to change notification settings - Fork 0
Closed
Labels
cliCommand-line interfaceCommand-line interfaceinterfaceUser/API interfacesUser/API interfacesphase-3Scenario Execution phaseScenario Execution phasetiger-styleTiger Style philosophy complianceTiger Style philosophy compliance
Description
Description
Implement command-line interface per CLI_INTERFACE.md
Phase
Set up development infrastructure with Tiger Style discipline
Test-First Requirements
⚠️ Write tests BEFORE implementation
- Test argument parsing
- Test all commands with valid/invalid inputs
- Test exit codes
Acceptance Criteria
- Commands:
run,replay,analyze,diff,validate,version,help - Command
run: execute scenario, output results - Command
replay: verify deterministic replay - Command
analyze: recompute metrics from event log - Command
diff: compare two runs - Command
validate: check scenario file - Argument parsing using
claplibrary - Output formats: summary (default), JSON, CSV
- Progress indicators (live mode)
- Signal handling: SIGINT (graceful shutdown)
- Exit codes: 0 (success), 1 (assertion failure), 2 (config error), 3 (runtime error)
- Minimum 2 assertions per function
- >85% test coverage
- All tests pass
Dependencies
- TASK-300
- TASK-301
Files to Create/Modify
src/main.zig
src/cli.zig
tests/unit/cli_test.zig
tests/integration/cli_test.sh
Estimated Effort
32 hours
Tiger Style Requirements:
- Minimum 2 assertions per function
- All loops are bounded
- Explicit error handling (no silent failures)
- Code formatted with
zig fmt - Pre-commit hook passes
- All tests pass
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
cliCommand-line interfaceCommand-line interfaceinterfaceUser/API interfacesUser/API interfacesphase-3Scenario Execution phaseScenario Execution phasetiger-styleTiger Style philosophy complianceTiger Style philosophy compliance