fix(sockets): add zod as direct sockets server dep

[icecrasher321]

Summary

Prevent confusion with optional marking of nextenv-js for Zod since sockets server directly uses it.

Type of Change

• Bug fix

Testing

Will test in staging environment

Checklist

• Code follows project style guidelines
• Self-reviewed my changes
• Tests added/updated and passing
• No new warnings introduced
• I confirm that I have read and agree to the terms outlined in the Contributor License Agreement (CLA)

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Review	Updated (UTC)
docs	Ready	Preview, Comment	Dec 16, 2025 4:21am

[greptile-apps]

Greptile Overview

Greptile Summary

Added zod (^3.24.2) as a direct dependency at the root package.json level. This prevents dependency confusion since the sockets server directly imports and uses zod for runtime validation (ZodError and WorkflowOperationSchema), but it was only available transitively through @t3-oss/env-nextjs. Making it explicit ensures the dependency is properly resolved for the socket server workspace.

• Verified zod is used in socket-server/validation/schemas.ts for defining operation schemas
• Verified zod is used in socket-server/handlers/operations.ts for runtime validation and error handling
• Note: apps/sim/package.json already has zod listed at line 138, so this ensures it's available at workspace root level

Confidence Score: 5/5

• This PR is safe to merge with no risk - it only adds an explicit dependency declaration
• The change is minimal, well-justified, and follows best practices for explicit dependency management. It prevents potential issues where transitive dependencies might not be reliably available.
• No files require special attention

Important Files Changed

File Analysis

Filename	Score	Overview
package.json	5/5	Added zod as direct dependency at root level to prevent confusion with @t3-oss/env-nextjs optional marking

Sequence Diagram

sequenceDiagram
    participant Client
    participant SocketServer
    participant ValidationSchemas
    participant ZodLib

    Client->>SocketServer: workflow-operation event
    SocketServer->>ValidationSchemas: WorkflowOperationSchema.parse(data)
    ValidationSchemas->>ZodLib: validate with zod schemas
    alt Valid Operation
        ZodLib-->>ValidationSchemas: validated data
        ValidationSchemas-->>SocketServer: validated operation
        SocketServer->>SocketServer: persist & broadcast
        SocketServer-->>Client: operation-confirmed
    else Invalid Operation
        ZodLib-->>ValidationSchemas: ZodError
        ValidationSchemas-->>SocketServer: ZodError thrown
        SocketServer-->>Client: operation-error/operation-failed
    end

Loading

[greptile-apps]

_{1 file reviewed, no comments}

_{Edit Code Review Agent Settings | Greptile}