Migrate rv CLI from TypeScript to Rust

[DarrenBaldwin07]

Summary

• replace the Bun/TypeScript application and provider SDKs with a native Rust crate
• preserve the existing CLI commands, aliases, and ~/.rv.json config format
• implement a shared async review API for GitHub, GitLab, and Bitbucket
• validate and persist GitLab and Bitbucket token authentication
• correctly parse nested GitLab project namespaces such as frayt/platform/core
• document Rust build, authentication, command, and development workflows

Testing

• cargo fmt --all -- --check
• cargo clippy --all-targets --all-features -- -D warnings
• cargo test --all-targets
• exercised top-level and provider-specific --help output

Want tembo to make any changes? Add a comment with @tembo and i'll get back to work!

      

[cursor]

Cursor Bugbot has reviewed your changes using default effort and found 4 potential issues.

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.}

^{Reviewed by Cursor Bugbot for commit 62f2f18. Configure here.}

[cursor]

Bitbucket resolve uses wrong method

High Severity

Resolving a Bitbucket comment sends PUT to /comments/{id}/resolve. Bitbucket Cloud expects POST on that path, so resolve_comment fails instead of resolving the thread.

 

^{Reviewed by Cursor Bugbot for commit 62f2f18. Configure here.}

[cursor]

GitHub lists issue comments only

Medium Severity

get_comments and get_comment call the issues comment endpoints, so they return conversation comments and miss inline review comments. GitLab and Bitbucket include inline comments in the same APIs, and the previous GitHub client used pulls review-comment routes.

 

^{Reviewed by Cursor Bugbot for commit 62f2f18. Configure here.}

[cursor]

GitLab lists only the first page

Medium Severity

Notes and discussions are fetched once with per_page 100 and no follow-up pages. Larger merge requests lose comments and threads, and resolve_comment can fail to find a note that exists on a later page.

Additional Locations (1)

• src/client/gitlab.rs#L218-L229

 

^{Reviewed by Cursor Bugbot for commit 62f2f18. Configure here.}

[cursor]

PR URLs with extra path segments fail

Medium Severity

URL parsing requires an exact path (/pull/123, /pull-requests/123, or /-/merge_requests/123) and rejects common suffixes such as /files, /diffs, or /commits. github view and setup then fail on normal browser address-bar URLs.

 

^{Reviewed by Cursor Bugbot for commit 62f2f18. Configure here.}