feat(sbt): add SBT (Scala Build Tool) support

[randomBrainstormer]

Summary

• Adds rtk sbt test — ScalaTest output filtering with 90% token reduction (compact single-line on pass, failure details on fail)
• Adds rtk sbt compile — strips SBT noise, keeps errors with 75% token reduction (source count + time on success)
• Adds rtk sbt run — light filtering, strips SBT preamble, passes through program output
• Adds rtk sbt <other> — passthrough for any unsupported subcommand

Implementation

Follows the established go_cmd.rs pattern:

• lazy_static! regex for noise/summary/error line detection
• crate::tee::tee_and_hint for full output recovery on failure
• Exit code propagation for CI/CD compatibility
• Discovery rules updated (src/discover/rules.rs) with 80% savings estimate

Test plan

• 11 unit tests with token savings assertions (>=60% on test pass, >=40% on test fail, >=30% on compile error)
• 3 real-output fixtures: sbt_test_pass.txt, sbt_test_fail.txt, sbt_compile_error.txt
• cargo fmt --all --check — clean
• cargo clippy --all-targets — clean
• cargo test --all — 990 passed, 0 failed
• Manual: rtk sbt test in a real Scala project — pending, will validate on a Scala workspace

Documentation

• README.md — added rtk sbt to build commands section and command rewrite table
• CHANGELOG.md — added entry under [Unreleased]

Signed-off-by: Ivan Severino 4858703+randomBrainstormer@users.noreply.github.com

[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

[randomBrainstormer]

Hey, thanks for the heads-up! @aeppling , I've rebased on develop and adapted to the new structure. Let me know if anything looks off!

[Angel-O]

hey @aeppling any update on this ? do you think it can be merged ?

[dannylinden]

Please merge before my wallet getting empty due to our scala project :D

[pszymkowiak]

Hi @randomBrainstormer! Re-ran CI on the rebased branch and it hit two regressions from develop that landed after your last green build (2026-04-17):

1. Missing Debug derive on SbtCommands — Commands enum on develop now requires Debug on all sub-enums:

error[E0277]: `SbtCommands` doesn't implement `std::fmt::Debug`

2. Clippy 0.1.95 flags 5 unnecessary >= y + 1 patterns — clippy expanded that lint since you submitted. Should rewrite as x > y instead of x >= y + 1.

Could you push a quick fix? After that CI should go green and we can merge.

Full job log: https://github.com/rtk-ai/rtk/actions/runs/24583551517/job/76078806371

[randomBrainstormer]

@pszymkowiak Done! Rebased onto develop and pushed a fix for both:

• Added #[derive(Debug)] to SbtCommands
• The 5 int_plus_one warnings in stream.rs were already fixed by 1bc4713 on develop, they came in automatically with the rebase

CI should be green now. Let me know if anything else comes up before merge.

[pszymkowiak]

Thanks for the quick rebase fix — CI is green now (verified, 11 checks pass on all 3 OS).

I built the branch and tested rtk sbt against real Scala projects in a container. sbt compile and sbt run work well. One real gap on sbt test:

filter_sbt_test only recognizes ScalaTest output. Tested against typelevel/cats (kernelLawsJVM/test, 1701 tests) and a fresh munit project — both use munit (via discipline-munit), whose summary format is:

[info] Passed: Total 1701, Failed 0, Errors 0, Passed 1701

TEST_SUMMARY_RE does not match this, so has_summary stays false and the output falls back to sbt test: parse error (sbt_cmd.rs:409) — even though it then recovers the summary from the [error] lines. munit is the default test framework in many modern Scala 3 templates, so this is not an edge case.

Two suggestions:

1. Add a munit branch to filter_sbt_test (Total N, Failed N, Errors N, Passed N), and ideally specs2/ZIO Test later.
2. When the fallback does recover a summary, it should not print parse error — that header is misleading.

Minor: sbt update falls through to passthrough (run_other) — fine for now, but on a real project dependency resolution is very verbose and would benefit from a filter later.

compile/run are solid. Up to you whether you want to extend test framework coverage in this PR or land it as-is and follow up — your call.

[randomBrainstormer]

@pszymkowiak good catch on munit , it's the default in Scala 3 templates so definitely not an edge case. Fix was small enough to fold in here:

• Added MUNIT_SUMMARY_RE for the Passed: Total N, Failed N, Errors N, Passed N format. Maps succeeded = Passed, failed = Failed + Errors, sets has_summary = true. The *** FAILED *** detail blocks work the same as ScalaTest so those came for free. Added pass/fail fixtures to cover both frameworks.

• Also renamed the fallback label from parse error to errors, agreed it was misleading.

sbt update and specs2/ZIO Test I'll leave for a follow-up as you suggested.

[randomBrainstormer]

@pszymkowiak hey, just checking in — munit fix is in, CI is green. Any blockers on your end before this can be merged?

[max-leuthaeuser]

Thanks for this PR! I am a heavy Scala/SBT user and would really like to finally get this feature.

[randomBrainstormer]

Hi @pszymkowiak @aeppling , bumping this one. All your review points are addressed (munit fix in, last CI green). Anything still blocking, or is it good to merge?