feat: add crud api

[Leetfs]

No description provided.

[Copilot]

Pull Request Overview

This PR adds a comprehensive CRUD API for managing clients and their associated logs, built on top of a Nitro server framework. The API provides endpoints for creating, reading, updating, and deleting clients, as well as retrieving and clearing client logs, with integrated chat completion functionality.

Key changes:

• Complete CRUD API implementation with TypeScript type definitions
• Client management endpoints with validation and error handling
• Log management system with pagination and filtering capabilities
• Chat completion proxy functionality using @llamakit/core

Reviewed Changes

Copilot reviewed 12 out of 20 changed files in this pull request and generated 6 comments.

Show a summary per file

File	Description
packages/server/test-api-fixed.js	Comprehensive test script to validate all API endpoints
packages/server/server/types/api.ts	TypeScript type definitions for API requests and responses
packages/server/server/api/test.get.ts	Simple test endpoint for server health checks
packages/server/server/api/log/[client]/index.get.ts	Get logs endpoint with pagination and filtering
packages/server/server/api/log/[client]/index.delete.ts	Clear logs endpoint for specific clients
packages/server/server/api/client/index.get.ts	List clients endpoint with pagination
packages/server/server/api/client/create.post.ts	Create client endpoint with validation
packages/server/server/api/client/[id].put.ts	Update client endpoint
packages/server/server/api/client/[id].delete.ts	Delete client endpoint with cleanup
packages/server/server/api/client/[client]/completions/index.post.ts	Chat completion proxy with logging
packages/server/package.json	Added @llamakit/core dependency
packages/server/nitro.config.ts	Updated configuration with Redis storage and WASM support

Files not reviewed (1)

• pnpm-lock.yaml: Language not supported

[Copilot]

Using new URL() for validation and ignoring the result with eslint-disable is unclear. Consider using a more explicit validation approach like URL.canParse() if available, or assign the result to a variable to make the intent clearer.

Suggested change

	// eslint-disable-next-line no-new
	new URL(body.baseUrl)
	if (!URL.canParse(body.baseUrl)) {
	throw new Error('Invalid URL')
	}

[Copilot]

The log ID generation using Date.now() and Math.random() could potentially create collisions in high-concurrency scenarios. Consider using a more robust unique ID generator like randomUUID() from Node.js crypto, which is already imported in other files.

Suggested change

	const logId = `${Date.now()}-${Math.random().toString(36).slice(2, 11)}`
	const logId = randomUUID()

[Copilot]

Using console.error for handling storage errors provides minimal debugging information. Consider using a more informative error logging approach that includes context about the failed operation, such as the client ID and operation type.

Suggested change

	storage.setItem(`client:${clientId}:logs`, updatedLogs).catch(console.error)
	storage.setItem(`client:${clientId}:logs`, updatedLogs).catch((error) => {
	console.error(`Failed to update logs for client: ${clientId}. Operation: setItem. Key: client:${clientId}:logs. Error:`, error);
	})