docs: add a getting started guide to the main README

[EmperorOrokuSaki]

• add a getting started guide to the main readme that covers how to use the CLI, and also the TUI through the cli
  • Basic usage is either adding --tui to the end of a obfuscate in cli, or using azoth obfuscate ... --emit-debug file and azoth tui debug_file
• add a description of the commands available on the cli but not in as much depth as the cli readme itself, link to that for more info

@claude

[claude]

Claude finished @EmperorOrokuSaki's task in 1m 46s —— View job • claude/issue-123-20251217-1411 • Create PR ➔

---

Getting Started guide added successfully

Tasks Completed

• Read current README.md structure
• Explore CLI documentation and commands
• Research TUI functionality
• Draft Getting Started section
• Update README.md
• Commit and push changes
• Provide PR creation link

Summary

I've successfully added a comprehensive Getting Started guide to the main README. The new section includes:

Installation

• Clear build instructions for the CLI

Basic Usage covering all commands:

• decode - Convert bytecode to assembly
• strip - Extract runtime bytecode
• cfg - Generate control flow graphs
• obfuscate - Apply obfuscation transforms with examples
• analyze - Measure obfuscation quality

TUI Usage with both methods:

• Option 1: Direct launch using --tui flag with obfuscate command
• Option 2: Two-step process using --emit-debug to save debug file, then azoth tui debug.json to view it

Additional Resources

• Link to detailed CLI documentation for advanced usage

The guide provides practical examples for each command and explains the two different ways to access the TUI functionality as requested.

--- |