Files
software-mansion__argent/packages/tool-server/test/utils/invalid-params.test.ts
filip131311 4975ff490c fix(debugger): cut debugger tool fail rate — structured not-connected results, classified CDP failures, narrow recovery (#610)
## Why

PostHog (30d) shows the debugger tool family is argent's least reliable
surface:

| tool | fail rate | dominant causes |
|---|---|---|
| `debugger-status` | **37%** | METRO_NO_TARGETS /
SERVICE_INITIALIZATION_FAILED / zod |
| `debugger-connect` | **24%** | SERVICE_INITIALIZATION_FAILED (~7k, >1k
users), METRO_NO_TARGETS |
| `debugger-log-registry` | 41.7% raw / 4.2% excl. storms | one user
retry-looped it **12,742×** on NO_TARGETS |

Three design issues drive this: (1) "app/Metro not ready yet" — an
expected precondition — is reported as a tool *error*, which both
inflates fail rates and invites agent retry storms; (2) every CDP
init/lifecycle fault lands in telemetry as the catch-all
`REGISTRY_SERVICE_INITIALIZATION_FAILED` with `error_kind=unknown`; (3)
~600 users/30d hit zod validation failures with zero visibility into
which parameter was wrong.

## What

**1. Classified failures** (`d71efa43`) — six former plain-`Error` sites
in `cdp-client.ts` / `target-selection.ts` now carry dedicated
`DEBUGGER_CDP_*` / `DEBUGGER_TARGET_DEVICE_MISMATCH` signals (messages
byte-identical). The registry's two causeless "terminating window"
`ServiceInitializationError`s get their own
`REGISTRY_SERVICE_TERMINATING` code.

**2. Narrow recovery** (`ff9c1955`) — `recoverable()` on both debugger
blueprints, scoped to windows where retry is provably safe: Metro
recovers only `DEBUGGER_CDP_NOT_CONNECTED` (request never left the host;
a detected socket death already self-heals for the *next* call via the
terminated cascade — recovering `CONNECTION_CLOSED` there would be dead
code, see the blueprint comment). Chromium also recovers
`CONNECTION_CLOSED` for the tab-switch reconnect window.
`REQUEST_TIMEOUT` stays unrecoverable (double-execution risk). A
reachability test proves the retry actually fires for a RUNNING node.

**3. Structured not-connected results** (`48b91ffd`) — `debugger-status`
and `debugger-log-registry` become factories that return `{ status:
"not_connected", reason, detail, guidance }` for classified
preconditions (`metro_not_running | no_app_connected | device_mismatch |
cdp_unreachable | stale_connection | reconnecting`) and still throw on
unexpected faults. `detail` preserves the original error text for
string-matching agents. `debugger-status` gains a socket-state gate
(Metro: dispose stale node; Chromium: report transient reconnect, no
dispose — the client belongs to the ChromiumCdp dependency).
log-registry keeps **no** gate on purpose: captured logs are readable
over a dead socket, and disposal would destroy the post-crash log file.
Flows/run-sequence map a not_connected result to a **failed step**
(mirrors `isUnmetUiWaitResult`) so recorded connectivity gates don't
silently pass. `debugger-evaluate` re-codes agent-expression throws as
`DEBUGGER_EVALUATE_EXPRESSION_THREW`.

**4. Telemetry + guidance + docs** (`7602a70d`) —
`tool:fail.invalid_params` (schema-declared names only; unknown keys →
literal `"unrecognized_keys"`; capped emit-side at 16), new
`debugger:tool_outcome` event (coded enum; joins
`tool:invoke`/`complete` via `tool_invocation_id` —
`ai_client`/`duration` live on the joined row), anti-retry-loop guidance
appended to the Metro discovery errors (first sentences verbatim —
skills match on them), six skills updated, Telemetry.md bumped to v1.03
with the new coded diagnostics disclosed.

## Dashboard migration note

`debugger-status` / `debugger-log-registry` precondition failures stop
emitting `tool:fail` — track them via `debugger:tool_outcome` (`outcome
!= 'connected'`). Per-AI-client breakdowns of those outcomes need a join
on `tool_invocation_id` against `tool:complete`.

## Testing

- Full suites green: tool-server 3,142, telemetry 290, registry 87. New
coverage: recoverable truth tables (incl. non-Error inputs), status
not-connected matrix
(Metro/Chromium/terminating-window/stale/dispose-side-effect/fall-through-rethrow),
log-registry rows, zod `invalid_params` derivation + emission-level
guard, flow gate, evaluate rewrap, sanitize-level enum checks.
- Live-tested against a booted iOS simulator + RN app and an Electron
target (details in PR comments).

Plan hardened through 3 adversarial review rounds (46 confirmed findings
addressed) before implementation.

🤖 Generated with [Claude Code](https://claude.com/claude-code)
2026-08-10 11:51:45 +02:00

100 lines
3.5 KiB
TypeScript

import { describe, it, expect } from "vitest";
import { z } from "zod";
import { deriveInvalidParams } from "../../src/utils/invalid-params";
function issuesFor(schema: z.ZodType, input: unknown): z.ZodError {
const res = schema.safeParse(input);
if (res.success) throw new Error("expected the input to fail validation");
return res.error;
}
describe("deriveInvalidParams", () => {
const declared = new Set(["port", "device_id", "steps", "count"]);
it("reports the top-level declared name for a simple type failure", () => {
const err = issuesFor(z.object({ count: z.number() }), { count: "nope" });
expect(deriveInvalidParams(err, declared)).toEqual(["count"]);
});
it("collapses a nested path to its top-level declared name, once", () => {
const schema = z.object({
steps: z.array(z.object({ tool: z.string(), args: z.object({ x: z.number() }) })),
});
const err = issuesFor(schema, {
steps: [
{ tool: 1, args: { x: "bad" } },
{ tool: 2, args: {} },
],
});
// Multiple issues under steps[0].tool / steps[0].args.x / steps[1].tool —
// all collapse to the single declared name "steps", deduped.
expect(deriveInvalidParams(err, declared)).toEqual(["steps"]);
});
it("reports the literal token for unrecognized_keys — never the user-typed key names", () => {
const schema = z.object({ port: z.number() }).strict();
const err = issuesFor(schema, { port: 1, ssn: "123-45-6789", passwd: "hunter2" });
const out = deriveInvalidParams(err, declared);
expect(out).toEqual(["unrecognized_keys"]);
expect(out.join(",")).not.toMatch(/ssn|passwd/);
});
it("dedups repeated names across issues", () => {
const schema = z.object({ port: z.number(), device_id: z.string() });
const err = issuesFor(schema, { port: "a", device_id: 5 });
const out = deriveInvalidParams(err, declared);
expect(out.sort()).toEqual(["device_id", "port"]);
expect(new Set(out).size).toBe(out.length);
});
it("filters names that are not schema-declared (defense in depth against key leakage)", () => {
// Forge a ZodError whose issue path names an undeclared key — must be
// dropped so only Argent's own schema vocabulary can reach telemetry.
const forged = new z.ZodError([
{
code: "invalid_type",
expected: "string",
path: ["users_home_dir"],
message: "x",
} as unknown as z.core.$ZodIssue,
{
code: "invalid_type",
expected: "number",
path: ["port"],
message: "x",
} as unknown as z.core.$ZodIssue,
]);
expect(deriveInvalidParams(forged, declared)).toEqual(["port"]);
});
it("drops issues with an empty path", () => {
const forged = new z.ZodError([
{
code: "custom",
path: [],
message: "whole-object refinement",
} as unknown as z.core.$ZodIssue,
]);
expect(deriveInvalidParams(forged, declared)).toEqual([]);
});
it("caps at 16 names (the sanitize arrayOf validator voids longer arrays wholesale)", () => {
const names = Array.from({ length: 20 }, (_, i) => `p${i}`);
const bigDeclared = new Set(names);
const forged = new z.ZodError(
names.map(
(name) =>
({
code: "invalid_type",
expected: "string",
path: [name],
message: "x",
}) as unknown as z.core.$ZodIssue
)
);
const out = deriveInvalidParams(forged, bigDeclared);
expect(out).toHaveLength(16);
expect(out).toEqual(names.slice(0, 16));
});
});