CodeRabbit Generated Unit Tests: Add unit tests

[coderabbitai]

Unit test generation was requested by @BillChirico.

• fix(web): show all guild categories in dashboard selector #477 (comment)

The following files were modified:

• tests/api/utils/configValidation.test.js
• tests/modules/cli-process.test.js
• tests/modules/triage-config.test.js
• tests/utils/anthropicClient.test.js

[changeset-bot]

⚠️ No Changeset found

Latest commit: 3570667

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[coderabbitai]

Important

Review skipped

This PR was authored by the user configured for CodeRabbit reviews. CodeRabbit does not review PRs authored by this user. It's recommended to use a dedicated user account to post CodeRabbit review feedback.

⚙️ Run configuration

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Pro

Run ID: 98bf2062-c647-4978-a72b-ad5a99185e88

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[railway-app]

🚅 Deployed to the volvox-bot-pr-537 environment in volvox-bot

Service	Status	Web	Updated (UTC)
web	✅ Success (View Logs)		Apr 18, 2026 at 9:35 pm
bot	❌ Build Failed (View Logs)	Web	Apr 18, 2026 at 9:35 pm

[sonarqubecloud]

Quality Gate failed

Failed conditions
2 Security Hotspots
17.5% Duplication on New Code (required ≤ 3%)

See analysis details on SonarQube Cloud

[greptile-apps]

Greptile Summary

This PR adds four Vitest test files covering configValidation, triage-config, cli-process, and anthropicClient. The tests are well-structured with good happy-path and error-case coverage, but several files test against source modules that either do not exist or have diverged from the tests.

• src/utils/anthropicClient.js and src/modules/cli-process.js are missing — both test files will error out entirely at the dynamic import, meaning 0 of their ~60 combined tests run.
• triage-config.test.js asserts streaming, tokenRecycleLimit, and a thinkingTokens default of 4096 — none of which match the current resolveTriageConfig source.
• configValidation.test.js (the new triage describe block) tests triage.streaming and triage.tokenRecycleLimit which are absent from CONFIG_SCHEMA.triage.properties.

Confidence Score: 2/5

Not safe to merge — two test files import non-existent source modules and two others have assertions that contradict the live implementation, meaning the test suite will fail on CI.

Four distinct P1 failures span all four changed files. Two source files are completely absent (anthropicClient.js, cli-process.js), and the triage tests have wrong default values and missing schema fields.

All four test files need attention: tests/utils/anthropicClient.test.js and tests/modules/cli-process.test.js require their source modules to be created; tests/modules/triage-config.test.js requires resolveTriageConfig to be updated; tests/api/utils/configValidation.test.js requires streaming and tokenRecycleLimit added to CONFIG_SCHEMA.triage.

Important Files Changed

Filename	Overview
tests/utils/anthropicClient.test.js	Tests for Anthropic SDK singleton client — entire file will fail at import because src/utils/anthropicClient.js does not exist in the repository.
tests/modules/cli-process.test.js	Comprehensive 1,300-line test suite for CLIProcess/AsyncQueue — all tests will fail at the dynamic import because src/modules/cli-process.js is absent from the repository.
tests/modules/triage-config.test.js	Tests for resolveTriageConfig, isChannelEligible, getDynamicInterval — source file exists but tests assert streaming, tokenRecycleLimit, and thinkingTokens defaults that don't match the current implementation.
tests/api/utils/configValidation.test.js	Extensive schema validation tests — the majority are correct against the live source, but the new triage describe block tests two properties (streaming, tokenRecycleLimit) missing from CONFIG_SCHEMA.triage.

Flowchart

%%{init: {'theme': 'neutral'}}%%
flowchart TD
    A[tests/api/utils/configValidation.test.js] -->|imports| B[src/api/utils/configValidation.js ✅ exists]
    C[tests/modules/triage-config.test.js] -->|imports| D[src/modules/triage-config.js ✅ exists]
    E[tests/modules/cli-process.test.js] -->|imports| F[src/modules/cli-process.js ❌ missing]
    G[tests/utils/anthropicClient.test.js] -->|imports| H[src/utils/anthropicClient.js ❌ missing]
    B --> B1{triage.streaming in schema?}
    B1 -->|No ❌| B2[triage-new-fields block FAILS]
    B1 -->|Yes ✅| B3[All other configValidation tests PASS]
    D --> D1{streaming / tokenRecycleLimit / thinkingTokens default correct?}
    D1 -->|No ❌| D2[triage-config default tests FAIL]
    D1 -->|Yes ✅| D3[channel eligibility + interval tests PASS]
    F --> F1[Dynamic import throws MODULE_NOT_FOUND]
    F1 --> F2[All 40+ cli-process tests FAIL]
    H --> H1[Dynamic import throws MODULE_NOT_FOUND]
    H1 --> H2[All 9 anthropicClient tests FAIL]

Loading

Comments Outside Diff (1)

1. tests/modules/triage-config.test.js, line 13-18 (link)

   Three assertions mismatch the current source implementation

   The current resolveTriageConfig in src/modules/triage-config.js:

   1. Does not return a tokenRecycleLimit field at all — so result.tokenRecycleLimit is undefined, not 20000 (line 18).
   2. Does not return a streaming field — so result.streaming is undefined, not false (line 22-24).
   3. Defaults thinkingTokens to 0 (triageConfig.thinkingTokens ?? 0), not 4096 (line 27-29).

   All three assertions will fail against the live source unless the source is updated to match.

   Prompt To Fix With AI

   This is a comment left during a code review.
   Path: tests/modules/triage-config.test.js
   Line: 13-18
   
   Comment:
   **Three assertions mismatch the current source implementation**
   
   The current `resolveTriageConfig` in `src/modules/triage-config.js`:
   
   1. Does **not** return a `tokenRecycleLimit` field at all — so `result.tokenRecycleLimit` is `undefined`, not `20000` (line 18).
   2. Does **not** return a `streaming` field — so `result.streaming` is `undefined`, not `false` (line 22-24).
   3. Defaults `thinkingTokens` to `0` (`triageConfig.thinkingTokens ?? 0`), not `4096` (line 27-29).
   
   All three assertions will fail against the live source unless the source is updated to match.
   
   How can I resolve this? If you propose a fix, please make it concise.

Prompt To Fix All With AI

This is a comment left during a code review.
Path: tests/utils/anthropicClient.test.js
Line: 16-18

Comment:
**Source module does not exist — all tests will fail**

`src/utils/anthropicClient.js` does not exist in the repository. The dynamic import on line 16 will throw a module-not-found error at runtime, causing every test in this file to fail before any assertion runs. The file needs to be created (or the correct path resolved) before these tests can pass.

How can I resolve this? If you propose a fix, please make it concise.

---

This is a comment left during a code review.
Path: tests/modules/cli-process.test.js
Line: 68-70

Comment:
**Source module does not exist — all tests will fail**

`src/modules/cli-process.js` does not exist in the repository. The dynamic import on line 68 will throw a module-not-found error, making the entire 1,300-line test file dead on arrival. All 40+ test cases will error out before any assertion is reached.

How can I resolve this? If you propose a fix, please make it concise.

---

This is a comment left during a code review.
Path: tests/modules/triage-config.test.js
Line: 13-18

Comment:
**Three assertions mismatch the current source implementation**

The current `resolveTriageConfig` in `src/modules/triage-config.js`:

1. Does **not** return a `tokenRecycleLimit` field at all — so `result.tokenRecycleLimit` is `undefined`, not `20000` (line 18).
2. Does **not** return a `streaming` field — so `result.streaming` is `undefined`, not `false` (line 22-24).
3. Defaults `thinkingTokens` to `0` (`triageConfig.thinkingTokens ?? 0`), not `4096` (line 27-29).

All three assertions will fail against the live source unless the source is updated to match.

How can I resolve this? If you propose a fix, please make it concise.

---

This is a comment left during a code review.
Path: tests/api/utils/configValidation.test.js
Line: 486-538

Comment:
**`triage.streaming` and `triage.tokenRecycleLimit` are absent from `CONFIG_SCHEMA`**

The entire `describe('triage schema — new fields (streaming, tokenRecycleLimit)', ...)` block will fail. In the current `src/api/utils/configValidation.js`, the `triage` object's `properties` map has no `streaming` or `tokenRecycleLimit` entries. As a result:

- `validateSingleValue('triage.streaming', true)` returns `['Unknown config path: triage.streaming']`, not `[]`.
- Every `validateSingleValue('triage.tokenRecycleLimit', ...)` call also returns the unknown-path error.
- `CONFIG_SCHEMA.triage.properties.streaming` is `undefined`, so the `toHaveProperty` / `toEqual` assertions on lines 530-537 fail.

The schema needs `streaming: { type: 'boolean' }` and `tokenRecycleLimit: { type: 'number', min: 0, max: 1000000 }` added to the `triage` properties before these tests can pass.

How can I resolve this? If you propose a fix, please make it concise.

---

This is a comment left during a code review.
Path: tests/modules/cli-process.test.js
Line: 809-819

Comment:
**Test doesn't actually verify the retry-limit behavior**

The test body only asserts `typeof cli.restart === 'function'`, which will always be true regardless of whether the max-retry cap is wired up correctly. The comment explains the real behavior but the assertion doesn't exercise it — this test can never catch a regression in the cap logic.

How can I resolve this? If you propose a fix, please make it concise.

_{Reviews (1): Last reviewed commit: "CodeRabbit Generated Unit Tests: Add uni..." | Re-trigger Greptile}

[greptile-apps]

Source module does not exist — all tests will fail

src/utils/anthropicClient.js does not exist in the repository. The dynamic import on line 16 will throw a module-not-found error at runtime, causing every test in this file to fail before any assertion runs. The file needs to be created (or the correct path resolved) before these tests can pass.

Prompt To Fix With AI

This is a comment left during a code review.
Path: tests/utils/anthropicClient.test.js
Line: 16-18

Comment:
**Source module does not exist — all tests will fail**

`src/utils/anthropicClient.js` does not exist in the repository. The dynamic import on line 16 will throw a module-not-found error at runtime, causing every test in this file to fail before any assertion runs. The file needs to be created (or the correct path resolved) before these tests can pass.

How can I resolve this? If you propose a fix, please make it concise.

[greptile-apps]

Source module does not exist — all tests will fail

src/modules/cli-process.js does not exist in the repository. The dynamic import on line 68 will throw a module-not-found error, making the entire 1,300-line test file dead on arrival. All 40+ test cases will error out before any assertion is reached.

Prompt To Fix With AI

This is a comment left during a code review.
Path: tests/modules/cli-process.test.js
Line: 68-70

Comment:
**Source module does not exist — all tests will fail**

`src/modules/cli-process.js` does not exist in the repository. The dynamic import on line 68 will throw a module-not-found error, making the entire 1,300-line test file dead on arrival. All 40+ test cases will error out before any assertion is reached.

How can I resolve this? If you propose a fix, please make it concise.

[greptile-apps]

triage.streaming and triage.tokenRecycleLimit are absent from CONFIG_SCHEMA

The entire describe('triage schema — new fields (streaming, tokenRecycleLimit)', ...) block will fail. In the current src/api/utils/configValidation.js, the triage object's properties map has no streaming or tokenRecycleLimit entries. As a result:

• validateSingleValue('triage.streaming', true) returns ['Unknown config path: triage.streaming'], not [].
• Every validateSingleValue('triage.tokenRecycleLimit', ...) call also returns the unknown-path error.
• CONFIG_SCHEMA.triage.properties.streaming is undefined, so the toHaveProperty / toEqual assertions on lines 530-537 fail.

The schema needs streaming: { type: 'boolean' } and tokenRecycleLimit: { type: 'number', min: 0, max: 1000000 } added to the triage properties before these tests can pass.

Prompt To Fix With AI

This is a comment left during a code review.
Path: tests/api/utils/configValidation.test.js
Line: 486-538

Comment:
**`triage.streaming` and `triage.tokenRecycleLimit` are absent from `CONFIG_SCHEMA`**

The entire `describe('triage schema — new fields (streaming, tokenRecycleLimit)', ...)` block will fail. In the current `src/api/utils/configValidation.js`, the `triage` object's `properties` map has no `streaming` or `tokenRecycleLimit` entries. As a result:

- `validateSingleValue('triage.streaming', true)` returns `['Unknown config path: triage.streaming']`, not `[]`.
- Every `validateSingleValue('triage.tokenRecycleLimit', ...)` call also returns the unknown-path error.
- `CONFIG_SCHEMA.triage.properties.streaming` is `undefined`, so the `toHaveProperty` / `toEqual` assertions on lines 530-537 fail.

The schema needs `streaming: { type: 'boolean' }` and `tokenRecycleLimit: { type: 'number', min: 0, max: 1000000 }` added to the `triage` properties before these tests can pass.

How can I resolve this? If you propose a fix, please make it concise.