feat: [#115] Add CLI binary for dependency checking

[Copilot]

Implements Phase 2 of the dependency installation package: a CLI binary that exposes the detection logic from Issue #114 through user-facing commands.

Implementation

Binary: packages/dependency-installer/src/bin/dependency-installer.rs

• Uses clap with derive macros for argument parsing
• Integrates with existing DependencyManager from the library
• 182 lines, fully documented

Commands:

• check - Verifies all dependencies, exits 1 if any missing
• check --tool <name> - Checks specific tool (supports aliases: tofu, machete)
• list - Shows all tools with status, always exits 0
• --verbose - Enables debug-level tracing

Exit Codes:

• 0: Success or informational command
• 1: Missing dependencies
• 2: Invalid arguments
• 3: Internal errors

Output:

$ dependency-installer check
Checking dependencies...

✗ cargo-machete: not installed
✗ OpenTofu: not installed
✓ Ansible: installed
✓ LXD: installed

Missing 2 out of 4 required dependencies

Changes

• Cargo.toml: Added clap dependency and binary target
• README.md: Documented CLI usage with examples
• New binary implements presentation layer, delegates to library for detection logic

Architecture

Follows DDD presentation layer pattern: binary handles I/O and user interaction, library provides domain logic. Error output uses eprintln! per Unix conventions. Enables Phase 3 Docker testing by providing executable to run in containers.

Original prompt

---

This section details on the original issue you should resolve

<issue_title>Create CLI Binary with Check Command</issue_title>
<issue_description>Parent Issue: #113 - Create Dependency Installation Package for E2E Tests
Depends On: #114 - Create Detection Logic Package (Issue 1-1-1)
Epic: #112 - Refactor and Improve E2E Test Execution

Overview

Create a CLI binary that uses the detection logic from Phase 1 to provide user-friendly commands for checking dependency status. This phase focuses on exposing the detection functionality through a command-line interface.

This is Phase 2 of 4 for building the dependency installation package.

Objectives

• Create src/bin/dependency-installer.rs binary
• Implement CLI using clap with subcommands
• Add check command to verify all dependencies
• Add list command to show available tools
• Implement proper exit codes for scripting
• Add comprehensive help text and examples

Key Components

CLI Commands:

dependency-installer check              # Check all dependencies
dependency-installer check opentofu     # Check specific tool
dependency-installer list               # List all available tools

Exit Codes:

• 0: Success (all checks passed)
• 1: Missing dependencies
• 2: Invalid arguments
• 3: Internal error

Acceptance Criteria

• Pre-commit checks pass
• CLI binary builds and runs successfully
• All commands work as specified
• Exit codes are correct for all scenarios
• Help text is clear and comprehensive
• Logging works correctly

Time Estimate

2-3 hours

Related Documentation

• Full specification: docs/issues/115-1-1-2-create-cli-binary-with-check-command.md
• Issue 1-1-1: Detection logic that this binary uses</issue_description>

Comments on the Issue (you are @copilot in this section)

• Fixes Create CLI Binary with Check Command #115

---

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.

[josecelano]

ACK 385efa2