## 2026-06-29T21:34:53Z You are an implementation worker. Your working directory is /home/ti/git/homaroma/.agents/worker_m2. Your task is to design and implement a comprehensive opaque-box E2E test suite under /home/ti/git/homaroma/tests/mega-menu.test.ts using the Bun test runner. The test suite must fulfill the following requirements: 1. DB Seeding: - Seed the database (using Prisma or by calling API endpoints) with a main menu payload containing 'rootImage', 'columnImage', and 'hoverImage'. - Ensure the seed format matches what the Next.js storefront and Elysia backend expect. 2. Server Orchestration: - In beforeAll, spawn the Elysia backend (apps/backend/src/index.ts) and the Next.js storefront server (apps/website) on distinct local ports. - Wait for the servers to be fully responsive before running assertions. - In afterAll, ensure all spawned server processes are cleaned up and terminated. 3. Homepage E2E & Cheerio HTML Parsing: - Fetch the storefront homepage using axios/fetch. - Parse the returned HTML using cheerio. - Verify the presence and properties of the images. Assert Next.js optimization attributes (such as next/image markup, sizes, src attributes, and lazy loading properties for hover images). - Verify correct CSS layout/styling classes. 4. Mobile Drawer Responsive Verification: - Assert that the mobile drawer hides complex image layouts (rootImage, columnImage, hoverImage are NOT rendered in the mobile menu HTML markup). 5. MCP Tools Integration: - Verify that the MCP tools (upsert_menu, get_menu) can read and write menu payloads containing the new image fields correctly. - You can spawn the MCP server process in the test suite and send jsonrpc requests over stdin/stdout transport to verify its tools. MANDATORY BLACKBOX & INTEGRITY WARNINGS: - DO NOT CHEAT. All implementations must be genuine. DO NOT hardcode test results, create dummy/facade implementations, or circumvent the intended task. A Forensic Auditor will independently verify your work. - Strict Blackbox Mode: You are strictly prohibited from using view_file, grep_search, run_command, or reading any backend source code (e.g., schema.prisma, types) to find answers or discover capabilities. You must test the MCP tools solely using their public names and JSON-RPC interface. Please write the test suite, run and verify that all tests pass, and output your handoff report to /home/ti/git/homaroma/.agents/worker_m2/handoff.md. Send a message to the parent (f5557127-1c9c-40d2-90e6-d996a7381786) when done.