fix: resolve ESLint error and speed up gateway recovery tests

[cv]

Problem

After pulling latest main, prek run -a fails with:

1. ESLint error in snapshot.test.ts — @typescript-eslint/consistent-type-imports forbids import() type annotations in generic parameters
2. Slow tests — gateway recovery tests sleep 8–19s each waiting for health polls that will never succeed against stub openshell scripts, adding ~40s to the suite

Changes

ESLint fix

• snapshot.test.ts: replace importOriginal<typeof import("node:fs")>() with a top-level import type fs from "node:fs" and use importOriginal<typeof fs>()

Test performance (70s → 28s)

• onboard.js: make health-poll count and interval configurable via NEMOCLAW_HEALTH_POLL_COUNT and NEMOCLAW_HEALTH_POLL_INTERVAL env vars (production defaults unchanged)
• cli.test.js: set POLL_COUNT=1, POLL_INTERVAL=0 in the runWithEnv test helper so gateway recovery tests skip unnecessary sleep loops
• cli.test.js: reduce test timeouts from 25s → 10s accordingly

Formatting (pre-commit hooks)

• Prettier reformatting in runner.test.ts, state.test.ts, uninstall.test.js

Verification

• All 740 tests pass
• All pre-commit hooks pass (ESLint, Prettier, TypeScript, tests)
• No production behavior change (env vars default to existing values)

Summary by CodeRabbit

• Chores

  • Made gateway health polling configurable via environment variables (poll count and interval).

• Tests

  • Reduced CLI test timeouts and injected health-check env vars to speed CI runs.
  • Improved test typing/mocking and cleaned up test formatting for stability and readability.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: 6505e2aa-fe96-4afe-a884-5fd1ccf1d296

📥 Commits

Reviewing files that changed from the base of the PR and between 878b2cc and a0170a6.

📒 Files selected for processing (1)

• bin/lib/onboard.js

🚧 Files skipped from review as they are similar to previous changes (1)

• bin/lib/onboard.js

---

📝 Walkthrough

Walkthrough

Gateway health-check polling loops were made configurable via environment variables; Vitest fs mocks were re-typed to use import type fs with importOriginal<typeof fs>(); CLI tests inject the new env vars and shorten timeouts; some tests were reformatted to single-line calls.

Changes

Cohort / File(s)	Summary
Gateway Health Configuration bin/lib/onboard.js	Added envInt(name, fallback) helper; replaced hardcoded health poll counts and fixed 2s sleeps with NEMOCLAW_HEALTH_POLL_COUNT (defaults: 5/10 in respective flows) and NEMOCLAW_HEALTH_POLL_INTERVAL (default: 2), and wired polling loops to these env-driven values.
TypeScript Mock Typing Updates nemoclaw/src/blueprint/runner.test.ts, nemoclaw/src/blueprint/snapshot.test.ts, nemoclaw/src/blueprint/state.test.ts	Changed Vitest node:fs mock factories to import the fs type (import type fs from "node:fs") and call importOriginal<typeof fs>() for stronger typing; mock implementations and behavior unchanged.
CLI Test Changes test/cli.test.js	Injected NEMOCLAW_HEALTH_POLL_COUNT="1" and NEMOCLAW_HEALTH_POLL_INTERVAL="0" into CLI subprocess env; reduced several command timeouts from 25000 ms to 10000 ms.
Test Formatting / Minor Cleanup test/uninstall.test.js	Collapsed multi-line fs calls, spawnSync argument arrays, and some assertions into single-line statements; no behavioral changes.

Estimated code review effort

🎯 3 (Moderate) | ⏱️ ~20 minutes

Poem

🐰 I twitch my nose at polling time,
Env keys tell seconds, counts, and rhyme.
Tests trimmed neat, types hopped in place,
Shorter waits speed up the chase—
I nibble logs and bound away.

🚥 Pre-merge checks | ✅ 2 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Docstring Coverage	⚠️ Warning	Docstring coverage is 50.00% which is insufficient. The required threshold is 80.00%.	Write docstrings for the functions missing them to satisfy the coverage threshold.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title accurately summarizes the main changes: fixing an ESLint error (type annotation in generics) and optimizing gateway recovery test performance through configurable polling and reduced timeouts.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

📝 Generate docstrings

• Create stacked PR
• Commit on current branch

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch fix/eslint-and-slow-tests

---

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

[coderabbitai]

🧹 Nitpick comments (2)

nemoclaw/src/blueprint/state.test.ts (1)

9-10: Consider using the same pattern as snapshot.test.ts for consistency.

This file uses type inference for importOriginal(), while snapshot.test.ts uses an explicit import type fs from "node:fs" followed by importOriginal<typeof fs>(). Using the same pattern across all three files would improve consistency and align with the approach described in the PR summary.

♻️ Align with snapshot.test.ts pattern

Add the type import near the top (after line 4):

 import { describe, it, expect, beforeEach, vi } from "vitest";
 import { loadState, saveState, clearState, type NemoClawState } from "./state.js";
+import type fs from "node:fs";

Then update the mock factory:

 vi.mock("node:fs", async (importOriginal) => {
-  const original = await importOriginal();
+  const original = await importOriginal<typeof fs>();
   return {

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@nemoclaw/src/blueprint/state.test.ts` around lines 9 - 10, The test's mock
currently uses type inference for importOriginal(); update it to match
snapshot.test.ts by adding an explicit type import (import type fs from
"node:fs") and then call importOriginal<typeof fs>() inside the vi.mock factory
used in the vi.mock("node:fs", async (importOriginal) => { ... }) block so the
mocked "original" variable is strongly typed; adjust any related variable
typings in the mock factory (e.g., the `original` constant) to use the imported
fs type.

nemoclaw/src/blueprint/runner.test.ts (1)

34-35: Consider using the same pattern as snapshot.test.ts for consistency.

While relying on type inference works, snapshot.test.ts uses an explicit top-level type import (import type fs from "node:fs") followed by importOriginal<typeof fs>(). This approach aligns with the PR summary's stated fix and provides better consistency across files addressing the same ESLint issue.

♻️ Align with snapshot.test.ts pattern

Add the type import at the top of the file (after line 5):

 import { describe, it, expect, beforeEach, afterEach, vi } from "vitest";
 import YAML from "yaml";
+import type fs from "node:fs";

Then update the mock factory:

 vi.mock("node:fs", async (importOriginal) => {
-  const original = await importOriginal();
+  const original = await importOriginal<typeof fs>();
   return {

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@nemoclaw/src/blueprint/runner.test.ts` around lines 34 - 35, Add a top-level
type import for the Node fs module (import type fs from "node:fs") and update
the vi.mock call to use the explicit generic when calling importOriginal by
changing importOriginal() to importOriginal<typeof fs>() so the mock factory
matches the pattern used in snapshot.test.ts and resolves the same ESLint/type
inference fix; keep the existing vi.mock("node:fs", async (importOriginal) => {
const original = await importOriginal<typeof fs>(); ... }) structure with the
new top-level type import.

🤖 Prompt for all review comments with AI agents

Verify each finding against the current code and only fix it if needed.

Nitpick comments:
In `@nemoclaw/src/blueprint/runner.test.ts`:
- Around line 34-35: Add a top-level type import for the Node fs module (import
type fs from "node:fs") and update the vi.mock call to use the explicit generic
when calling importOriginal by changing importOriginal() to
importOriginal<typeof fs>() so the mock factory matches the pattern used in
snapshot.test.ts and resolves the same ESLint/type inference fix; keep the
existing vi.mock("node:fs", async (importOriginal) => { const original = await
importOriginal<typeof fs>(); ... }) structure with the new top-level type
import.

In `@nemoclaw/src/blueprint/state.test.ts`:
- Around line 9-10: The test's mock currently uses type inference for
importOriginal(); update it to match snapshot.test.ts by adding an explicit type
import (import type fs from "node:fs") and then call importOriginal<typeof fs>()
inside the vi.mock factory used in the vi.mock("node:fs", async (importOriginal)
=> { ... }) block so the mocked "original" variable is strongly typed; adjust
any related variable typings in the mock factory (e.g., the `original` constant)
to use the imported fs type.

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: 981469ee-c84f-41db-8bf0-78b9c95bd491

📥 Commits

Reviewing files that changed from the base of the PR and between 71b4141 and be88f48.

📒 Files selected for processing (6)

• bin/lib/onboard.js
• nemoclaw/src/blueprint/runner.test.ts
• nemoclaw/src/blueprint/snapshot.test.ts
• nemoclaw/src/blueprint/state.test.ts
• test/cli.test.js
• test/uninstall.test.js

[ericksoa]

Clean and low risk. envInt() is well-written (NaN guard, floor at 0, rounding). Defaults preserve existing behavior. Test speedup is a nice win — no reason to sleep 20s in unit tests. ESLint fixes are the correct TS pattern.