Issue 1: Restore a clean, passing build and test baseline

[Nanle-code]

Summary
The project currently does not compile cleanly in its existing state. Several unresolved imports, broken argument paths, and outdated helper references are preventing contributors from building or testing the repository reliably.

Why this matters
A failing baseline blocks all meaningful development work, slows down onboarding for new contributors, and makes pull-request reviews difficult. Establishing a stable build and test baseline is the first prerequisite for advancing the project safely.

Proposed work
Fix current compile-time errors across the CLI and test suite
Resolve missing or broken dependency references
Validate command handlers and argument wiring
Ensure cargo test and the main build path pass consistently
Expected outcome
The repository builds successfully with a clean compiler result
The test suite runs without unresolved errors
Contributors can start working from a reliable, reproducible baseline
Acceptance criteria
cargo test completes successfully
cargo build completes successfully
No unresolved imports or broken command references remain in the main project flow

[Ejirowebfi]

@Ejirowebfi has applied to work on this issue as part of the Stellar Wave Program's 5th wave.

Full stacks
Hi, I'd like to apply for this issue.

I'm a full stack developer (3–5 years) comfortable across the entire stack — from database schema and API design to React/TypeScript frontend and deployment. I regularly work on features that touch both layers, so I'm used to tracing bugs that cross the frontend/backend boundary.

For this specific issue, I plan to: [e.g. audit the API response shape, fix the mismatch on the server side, then update the frontend to handle the corrected structure and add a test for both layers]. I've worked with [technologies mentioned in the issue].

My availability is [X hrs/week]. Estimated completion: [X hours/days].

ℹ️ Repo Maintainers: To accept this application, review their application or assign @Ejirowebfi to this issue.

[nonso7]

@nonso7 has applied to work on this issue as part of the Stellar Wave Program's 5th wave.

Can i work on this issue

ℹ️ Repo Maintainers: To accept this application, review their application or assign @nonso7 to this issue.

[drips-wave]

Congratulations, @nonso7! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on June 2, 2026.

🧑‍💻 @nonso7: Please resolve the issue such that the repo's maintainers have enough time to review your contribution before the due date. You'll earn Points for completing the issue on-time, which will make you eligible for a share of the Stellar Wave Program's reward pool.

Warning

When opening a PR, please link it to this issue to ensure it gets tracked accurately. Points are awarded when this issue is marked as completed by the maintainer.

🤠 Repo maintainers: Please keep an eye on the contributor's progress and review their work before the due date. You can manage this issue, including adjusting its complexity and points, here.

🌊 Happy Wave 🌊