ANANSI → QYVORA TUI Architecture

[wsuits6]

I want to open a discussion around improving ANANSI and exploring how we can make better use of qyvora-tui across the QYVORA security tools. ANANSI could serve as the first tool we redesign and use as a reference implementation for the TUI experience, including navigation, configuration, task execution, live output, results, logging, errors, and overall usability. The goal is to keep each tool’s core functionality independent while providing a consistent terminal interface across the entire QYVORA tool ecosystem. We should discuss what functionality belongs in qyvora-tui, what should remain inside each individual tool, and how we can design the architecture so that improvements made for ANANSI can eventually be reused across the other tools without creating unnecessary coupling. The main objective is to make the tools more powerful, consistent, maintainable, and practical for real-world security research and offensive-security workflows.