Make test task forward BATS targets correctly

[junior-ricon]

During caller-cwd follow-up verification, mise run test test/merge-driver.bats did not target just that file. The current test task shape effectively runs bats test/ "$@", so passing an explicit file starts the whole suite plus the extra arg; in my local run it printed the full suite and timed out at 300s around the merge-driver block.

Expected shape is the fold notes/bats-tool-testing.md pattern: a single test task that forwards args to BATS, defaults to test/ when no target is given, and supports direct file/bare-suite targeting.

Why it matters: targeted verification is part of review/debug workflow. If the task ignores or misinterprets file targets, agents either waste time on full suites or route around the real task path.

Observed while resolving modules#27; full mise run test later passed 107/107 after unrelated test fixes.

[olavostauros]

This was resolved by PR #31 ("Keep tracked modules on local branches," merged May 18, 2026). The .mise/tasks/test file was rewritten to include a proper BATS target resolver that forwards scoped arguments without also running the full test/ directory. A follow-up fix in commit 0ced723 ("fix: clear inherited usage defaults") handled the empty-arg edge case. The current task correctly supports mise run test init, mise run test test/init.bats, and mise run test -- --filter <pattern>. Closing as completed.