fix: --completion outputs wrong script name when run via Bun

[Paul-Goulpie]

fix: --completion outputs wrong script name when run via Bun

Problem

Running gitlab-ci-local --completion generated a bash completion
script referencing bun instead of gitlab-ci-local:

###-begin-bun-completions-###
...
mapfile -t type_list < <(bun --get-yargs-completions "${args[@]}")
...
complete -o bashdefault -o default -F _bun_yargs_completions bun
###-end-bun-completions-###

When run via bun run src/index.ts, yargs derives $0 from
process.argv[0], which resolves to the bun binary instead of
the command name. The handler.ts completion branch was creating
a fresh yargs instance without overriding this value.

Fix

Call .scriptName("gitlab-ci-local") on the yargs instance before
showCompletionScript() to explicitly set $0.

Test

Added a subprocess-based regression test. vi.spyOn(console, "log")
cannot intercept the output because Bun implements console.log
natively — the test runs the CLI via execSync and asserts the
generated script references gitlab-ci-local throughout.
The test is registered in the forks vitest pool and excluded from
threads to avoid worker initialisation failures.

---

Summary by cubic

Fixes --completion so the generated bash script uses gitlab-ci-local instead of bun when run via bun. Ensures the markers, function name, and complete directive reference the correct command.

• Bug Fixes
  • Set yargs.scriptName("gitlab-ci-local") before .showCompletionScript() to override $0 (which yargs derived from process.argv[0] as bun).
  • Added a subprocess regression test that runs the CLI via execSync and asserts all references use gitlab-ci-local; test runs in the forks pool and is excluded from threads.

^{Written for commit 1eb7b49. Summary will update on new commits.}

[cubic-dev-ai]

No issues found across 3 files