Property 'rag_model' is missing in type '{ id: number; image_name: string; image_path: string; ocr_model: string; correction_model: string; llm_model: string; ocr_text: string; corrected_text: string; rag_context: string[]; llm_response: string; prompt: string; final_prompt: string; note: string; created_at: string; }' but required in type 'Translation'.

Property 'rag_model' is missing in type '{ id: number; image_name: string; image_path: string; ocr_model: string; correction_model: string; llm_model: string; ocr_text: string; corrected_text: string; rag_context: string[]; llm_response: string; prompt: string; final_prompt: string; note: string; created_at: string; }' but required in type 'Translation'.

Property 'rag_model' is missing in type '{ id: number; image_name: string; image_path: string; ocr_model: string; correction_model: string; llm_model: string; ocr_text: string; corrected_text: string; rag_context: string[]; llm_response: string; prompt: string; final_prompt: string; note: string; created_at: string; }' but required in type 'Translation'.

Property 'rag_model' is missing in type '{ id: number; image_name: string; image_path: string; ocr_model: string; correction_model: string; llm_model: string; ocr_text: string; corrected_text: string; rag_context: string[]; llm_response: string; prompt: string; final_prompt: string; note: string; created_at: string; }' but required in type 'Translation'.

Property 'rag_model' is missing in type '{ ocr_text: null; corrected_text: null; rag_context: never[]; llm_response: null; note: null; id: number; image_name: string; image_path: string; ocr_model: string; correction_model: string; llm_model: string; prompt: string; final_prompt: string; created_at: string; }' but required in type 'Translation'.

Property 'rag_model' is missing in type '{ id: number; image_name: string; image_path: string; ocr_model: string; correction_model: string; llm_model: string; ocr_text: string; corrected_text: string; rag_context: string[]; llm_response: string; prompt: string; final_prompt: string; note: string; created_at: string; }' but required in type 'Translation'.

Property 'rag_model' is missing in type '{ id: number; image_name: string; image_path: string; ocr_model: string; correction_model: string; llm_model: string; ocr_text: string; corrected_text: string; rag_context: string[]; llm_response: string; prompt: string; final_prompt: string; note: string; created_at: string; }' but required in type 'Translation'.

Unexpected any. Specify a different type

Unexpected any. Specify a different type

Unexpected any. Specify a different type

Unexpected any. Specify a different type

Unexpected any. Specify a different type

Unexpected any. Specify a different type

Unexpected any. Specify a different type

Unexpected any. Specify a different type

Unexpected any. Specify a different type

Unexpected any. Specify a different type

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-node@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Using `<img>` could result in slower LCP and higher bandwidth. Consider using `<Image />` from `next/image` or a custom image loader to automatically optimize images. This may incur additional usage or cost from your provider. See: https://nextjs.org/docs/messages/no-img-element

Using `<img>` could result in slower LCP and higher bandwidth. Consider using `<Image />` from `next/image` or a custom image loader to automatically optimize images. This may incur additional usage or cost from your provider. See: https://nextjs.org/docs/messages/no-img-element

Using `<img>` could result in slower LCP and higher bandwidth. Consider using `<Image />` from `next/image` or a custom image loader to automatically optimize images. This may incur additional usage or cost from your provider. See: https://nextjs.org/docs/messages/no-img-element

Using `<img>` could result in slower LCP and higher bandwidth. Consider using `<Image />` from `next/image` or a custom image loader to automatically optimize images. This may incur additional usage or cost from your provider. See: https://nextjs.org/docs/messages/no-img-element

Using `<img>` could result in slower LCP and higher bandwidth. Consider using `<Image />` from `next/image` or a custom image loader to automatically optimize images. This may incur additional usage or cost from your provider. See: https://nextjs.org/docs/messages/no-img-element

Using `<img>` could result in slower LCP and higher bandwidth. Consider using `<Image />` from `next/image` or a custom image loader to automatically optimize images. This may incur additional usage or cost from your provider. See: https://nextjs.org/docs/messages/no-img-element

'afterEach' is defined but never used

'beforeEach' is defined but never used

'toast' is defined but never used