Add unit tests for CLI

[zipdoki]

Background

The CLI was originally written in Kotlin, then converted to Go for easier distribution. We used AI for the conversion. It works, but honestly, we are not confident in Go—we do not know if the code is idiomatic or follows best practices.

We need help from Go developers. If you see something wrong or weird, please tell us.

The `internal/util` package has only one test file (`truncate_test.go`), which was also written by AI.

Tasks

Each item can be submitted as a separate PR.

• `util/filters.go` (12 LOC, Easy)
• `util/formatter.go` (~50 LOC, Easy)
• `util/strings.go` (~30 LOC, Easy)
• `util/arguments.go` (110 LOC, Medium)
• `util/table_printer.go` (~80 LOC, Medium)

How to Contribute

1. Comment below to claim an item
2. Branch: `test/cli-util-`
3. PR title: `test(cli): add tests for util/`
4. One file per PR
5. Run `cd cli && make test`

Done When

• Test file at `cli/internal/util/_test.go`
• Public functions covered
• Tests pass

Notes

Code improvements are welcome—open a separate issue or include in your PR."
Create CLI util tests umbrella issue

[thatnerdjosh]

I'm in the process to work on this - note that I did vibe code the tests, but I also have extensive go experience, so before I create the PR's I will make sure to thoroughly review by hand.

CC: @zipdoki

[zipdoki]

@thatnerdjosh
Thanks for your interest! Looking forward to your PR. Vibe coding is fine—I appreciate you taking the time to review by hand. Feel free to ask if you have any questions!

[em3s]

As mentioned in #90: Your approach—AI-assisted with hand review—is exactly what we're looking for. Thanks!
@thatnerdjosh

[thatnerdjosh]

Just a heads up this is on my list to go through in the next 1-2 weeks (or less) - currently at a meditation retreat