CI runs only 2 of 16 test suites: turbo.json keys nikcli#test but the package is nikcli-ai

[SandroHub013]

Description

turbo.json declares a nikcli#test task, but the package in packages/nikcli is named nikcli-ai. The key matches nothing. There is no generic test task either, so bun turbo test — the command test.yml runs on the linux matrix leg — resolves to exactly two tasks:

$ bun turbo test --dry=json
@nikcli-ai/app#test        | command: "bun run test:unit"
@nikcli-ai/simulation#test | command: "bun test"

Every other package with a working test script is never executed by any workflow: llm (220 tests), tui-math (101), httpapi-codegen (83), tui-image (83), identity (47), inference (36), terminal-control (37), computer-use (27), http-recorder (16), browser-control (11), auth (7), sdk-next, and nikcli-ai itself (3869).

nikcli's suite does run in ci-pipeline.yml, but that step is marked critical: false (script/ci-validate.ts:71), so a red suite still lets validate pass and publish release.

Running the hidden suites locally surfaces four failures that have been red since they were written, including one where 77c77931 removed a Google API key from an http-recorder fixture but left the assertion expecting it to be detected — so the secret-detection guard has been asserting on an empty value ever since.

packages/util has a related gap: 71 source files, no test script at all, so it is invisible to turbo whether or not the task key is fixed.

Plugins

None.

Nikcli version

1.292.0 (live-main at 12c9fac).

Steps to reproduce

1. bun turbo test --dry=json and count entries ending in #test that have a real command — there are 2.
2. cd packages/llm && bun test — 220 tests run, and 2 fail. Nothing in CI reports this.
3. cd packages/http-recorder && bun test — 1 fail, in the secret-detection case.

Screenshot and/or share link

n/a — CI configuration, output quoted above.

Operating System

Windows 11 (26200). The task-resolution problem is platform-independent; verified against live-main in a clean worktree.

Terminal

Windows Terminal, PowerShell 5.1 and Git Bash.

[nikomatt69]

Confirming this is still open against live-main (fdf92f6b, today):

bun turbo test --dry=json on live-main resolves only two #test tasks: @nikcli-ai/app and @nikcli-ai/simulation. The turbo.json key nikcli#test matches no package — the directory packages/nikcli declares its package name as nikcli-ai.

Net effect today:

• packages/llm (220 tests), tui-math (101), httpapi-codegen (83), tui-image (83), identity (47), inference (36), terminal-control (37), computer-use (27), http-recorder (16), browser-control (11), auth (7), sdk-next, and packages/nikcli itself (3869) all run only when invoked directly. test.yml on the linux matrix leg never executes any of them.
• packages/util (71 source files) has no test script — invisible to turbo even after the task-key fix.
• The ci-pipeline step that does run packages/nikcli's suite is critical: false (script/ci-validate.ts:71), so a red suite still passes validate and publish releases.

Running the hidden suites surfaces real failures that have been red since they were written — at least one in packages/http-recorder where commit 77c77931 removed a Google API key from a fixture without updating the assertion, so the secret-detection guard has been asserting on an empty value ever since.

Two changes needed for full coverage:

1. turbo.json — rename the nikcli#test task to nikcli-ai#test (and any other nikcli#* keys that need the same correction), plus add a generic test task that delegates per-package so packages without their own script don't fall off the cliff.
2. packages/util/package.json — add a test script. Until it has one, fixing the turbo key alone won't surface it.
3. script/ci-validate.ts:71 — flip the nikcli suite step to critical: true. The current setup means a release can ship with the primary suite red.

Happy to put a PR together against a fresh branch off live-main if nobody is already on it.