ok fine bugbot wants tests, let's do it:
ok fine bugbot wants tests, let's do it:
/Users/paul/.claude/worktrees/cli/linear-brewing-cocke
ok fine bugbot wants tests, let's do it:
New behavior is introduced via ValidArgsFunction/completeContextNames (annotated context-name tab completion), but there’s no unit test coverage for it even though this file already has tests. Adding a small test for completeContextNames would help lock in the expected output format (name + description, and "(active)" marker) and verify errors are swallowed as intended.
Go lint is clean. The shellcheck failure is pre-existing in mise-tasks/release — unrelated to my change (I only touched a Go test file).
Done. Added two tests to cmd/entire/cli/auth_context_test.go:
TestCompleteContextNames— records two contexts (one active), verifies the completion output format:name\tdescriptionwith handle + core URL, exactly one(active)marker on the current context, theNoFileCompdirective, and that passing an existing positional arg returns(nil, NoFileComp).TestCompleteContextNames_NoContexts— verifies the empty/error path swallows cleanly to empty completions.
Both pass; follows the existing t.Setenv + tokenstore.UseFileBackendForTesting setup used by the other tests in the file.
push
I'll commit and push.
you stuck?
No, just waiting on you — the commit got rejected (looks like you declined the tool call). Want me to retry the commit + push, or change something first?