Check if these issues are valid — if so, understand the root cause of each and fix them.


<file name="packages/core/lib/v3/agent/tools/v3-dragAndDrop.ts">

<violation number="1" location="packages/core/lib/v3/agent/tools/v3-dragAndDrop.ts:12">
P2: Schema allows arrays of any length but code assumes exactly 2 elements. Use `z.tuple([z.number(), z.number()])` to enforce the expected structure and provide better validation errors if the AI model sends malformed input.</violation>
</file>

<file name="packages/core/lib/v3/agent/tools/v3-type.ts">

<violation number="1" location="packages/core/lib/v3/agent/tools/v3-type.ts:24">
P2: The `coordinates` schema allows arrays of any length but the code expects exactly 2 elements. Consider using `z.tuple([z.number(), z.number()])` to enforce the expected structure and get proper TypeScript typing.</violation>
</file>

<file name="packages/core/lib/v3/agent/tools/v3-scroll.ts">

<violation number="1" location="packages/core/lib/v3/agent/tools/v3-scroll.ts:71">
P2: The `coordinates` array schema doesn&#39;t enforce length. If fewer than 2 elements are provided, `coordinates[1]` will be `undefined`, causing `processCoordinates` to return NaN values. Consider using `z.tuple([z.number(), z.number()])` to ensure exactly 2 coordinates are provided.</violation>
</file>

<file name="packages/core/lib/v3/agent/prompts/agentSystemPrompt.ts">

<violation number="1" location="packages/core/lib/v3/agent/prompts/agentSystemPrompt.ts:47">
P2: The `clickAndHold` tool is available for hybrid mode (per the tools/index.ts registration) but is not documented in the hybrid mode tools section. The agent won&#39;t be aware this tool exists.</violation>
</file>

<file name="packages/core/lib/v3/agent/tools/v3-fillFormVision.ts">

<violation number="1" location="packages/core/lib/v3/agent/tools/v3-fillFormVision.ts:75">
P2: Missing Google provider delay after click. The `v3-type.ts` tool adds a 1000ms delay for Google models after clicking before typing, but this logic is missing here. This could cause typing issues when using Google models with the fillFormVision tool.</violation>
</file>

<file name="packages/core/lib/v3/tests/agent-hybrid-mode.spec.ts">

<violation number="1" location="packages/core/lib/v3/tests/agent-hybrid-mode.spec.ts:234">
P2: Test assertion doesn&#39;t match the comment and instruction. The comment says &#39;Should include screenshot&#39; and the instruction explicitly asks the agent to &#39;Take a screenshot&#39;, but the assertion only verifies `close` was called. Consider adding an assertion to verify screenshot was used, or update the comment if screenshot verification is intentionally omitted.</violation>
</file>

<file name="packages/core/lib/v3/agent/tools/v3-clickAndHold.ts">

<violation number="1" location="packages/core/lib/v3/agent/tools/v3-clickAndHold.ts:19">
P2: The coordinates schema allows arrays of any length but the code assumes exactly 2 elements. Consider using `.length(2)` to validate the array size, or use a tuple schema for stronger typing: `z.tuple([z.number(), z.number()])`.</violation>
</file>

<file name="packages/core/lib/v3/agent/tools/v3-click.ts">

<violation number="1" location="packages/core/lib/v3/agent/tools/v3-click.ts:23">
P2: The coordinates schema `z.array(z.number())` doesn&#39;t enforce exactly 2 elements. If an LLM returns an empty or single-element array, `coordinates[1]` will be `undefined`, causing issues in `processCoordinates`. Use `z.tuple([z.number(), z.number()])` to enforce the expected (x, y) pair.</violation>
</file>

<file name="packages/core/lib/v3/agent/tools/index.ts">

<violation number="1" location="packages/core/lib/v3/agent/tools/index.ts:50">
P1: Missing `delete filtered.act;` in hybrid mode. According to the PR description, `act` is a DOM-only tool and should not be available in hybrid mode. Currently only `fillForm` is removed, leaving `act` incorrectly available.</violation>
</file>