Add OpenCode provider support for discover

[vadika]

Summary

• add a new OpenCode session provider for rtk discover that reads command history from ~/.local/share/opencode/opencode.db (with OPENCODE_DB_PATH override)
• add --provider auto|claude|opencode to rtk discover and make auto prefer OpenCode when available
• improve discover signal quality by ignoring multiline/comment script snippets and normalizing absolute RTK binary paths (for example: /home/user/.cargo/bin/rtk ...) before classification

Validation

• cargo check
• cargo test test_classify_ -- --nocapture
• cargo run --quiet -- discover --provider opencode --all --since 30 --limit 5 --format text

Notes

• this preserves existing Claude behavior while enabling OpenCode-first workflows without requiring Claude session logs

[pszymkowiak]

Hi! Thanks for the contribution! Since March 6, all PRs should target the develop branch instead of master (see CONTRIBUTING.md).

Could you update the base branch? Click Edit at the top right of this PR and change it from master to develop.

Thanks!

[pszymkowiak]

Thanks for this @vadika! The SessionProvider trait integration is clean and the absolute-path RTK detection is a nice touch.

A few issues to address before we can merge:

Must fix:

1. String comparison for provider label (discover/mod.rs:63) — provider_label == "claude" is fragile. If the label string changes, the CWD encoding silently breaks. Use the DiscoverProvider enum directly or a boolean flag instead.

2. test_classify_sqlite3 references a non-existent command (registry.rs:1485) — there is no rtk sqlite3 rule or implementation. This test will fail. Either remove it or add the corresponding rule.

3. from_str shadows the FromStr trait (provider.rs:43) — clippy will warn about this. Consider using clap::ValueEnum on DiscoverProvider instead, which also fixes the silent fallback to Auto on typos (e.g. --provider opnecode).

Nice to fix:

4. DB opened N+1 times — discover_sessions opens the DB, then extract_commands opens it again for each session. Consider caching the path or connection.

5. LIKE injection in SQL (provider.rs:313) — % and _ in the project filter are not escaped, so paths containing those characters will over-match.

[vadika]

Thanks for the detailed review — great catches.

I retargeted the PR base branch to develop.

I’ve now addressed all points you listed:

1. Replaced fragile provider-label string checks with DiscoverProvider-driven logic.
2. Removed the sqlite3 discover tests that didn’t match expected behavior.
3. Switched provider parsing to clap ValueEnum so typos fail fast instead of silently falling back to Auto.
4. Removed the OpenCode DB N+1 open pattern by reusing a connection inside the provider.
5. Escaped % / _ for the OpenCode SQL LIKE project filter and added explicit ESCAPE handling.

Also added tests for provider parsing and LIKE escaping behavior.

I ran fmt + clippy + full test suite locally; cargo test --all is passing.

[CLAassistant]

All committers have signed the CLA.

[aeppling]

Hey

We are cleaning up the codebase and improving the project structure for better onboarding. As part of this effort, PR #826 reorganizes src/ from a flat layout into subfolders.

No logic changes — only file moves and import path updates.

What you need to do

Rebase your branch on develop when receiving this comment:

git fetch origin && git rebase origin/develop

Git detects renames automatically. If you get import conflicts, update the paths:

use crate::git;        // now: use crate::cmds::git::git;
use crate::tracking;   // now: use crate::core::tracking;
use crate::config;     // now: use crate::core::config;
use crate::init;       // now: use crate::hooks::init;
use crate::gain;       // now: use crate::analytics::gain;

Need help rebasing? Tag @aeppling