Can I vibecode TinyPNG Pro?

You are building a production-ready software product named “Squooshbox”, a deliberately focused alternative to TinyPNG Pro. Build a complete, usable vertical slice—not a landing page, static mockup, or disconnected collection of components.

WORKING AGREEMENT
Before writing implementation code, produce a short technical plan that names the routes or pages, server actions or endpoints, data tables, important state transitions, authorization boundaries, background jobs, and external adapters. Resolve contradictions in favor of the narrow audience and non-goals below. Prefer a small, legible architecture over speculative abstraction, but do not omit persistence, validation, error handling, or tests.

PRODUCT BRIEF
Primary user: a designer compressing batches of web images.
Primary outcome: compress common image formats locally and make the savings obvious.
Product principle: optimize the exact workflow below instead of copying the full breadth of TinyPNG Pro. A first-time user should understand what to do from the interface itself, without a tour or documentation.

END-TO-END USER JOURNEYS
Implement all of these flows through the real interface and persistent data layer:
1. The user drops a mixed batch of images, watches each file validate and compress locally, then compares original and result sizes.
2. The user selects one image, adjusts output format and quality, examines a split preview, and applies those settings to selected files.
3. The user downloads one optimized image or a ZIP with predictable names, while unsupported and failed files remain clearly identified.

SCREENS AND INFORMATION ARCHITECTURE
Build these as coherent responsive views. Each screen must specify its primary action, secondary actions, visible status, validation feedback, empty state, loading or pending state, success confirmation, and recoverable failure state.
1. Workspace: prominent drop zone, file picker, privacy statement, batch list, overall bytes saved, clear-all, and download-all controls.
2. Image row: thumbnail, source and output format, dimensions, original bytes, result bytes, savings percentage, state, and remove action.
3. Inspector: zoomable before-and-after split view, format, quality, resize controls, metadata policy, and live recompression indicator.
4. Completion state: summary by success and failure, ZIP size, filenames, and a reminder that refreshing discards all local work.

CORE CAPABILITIES
1. drag-and-drop or file picker for multiple images
2. quality controls with sensible per-format defaults
3. before and after dimensions, bytes, and percentage saved
4. side-by-side preview for the selected image
5. download one file or all results as a ZIP

DETAILED BEHAVIOR AND BUSINESS RULES
Treat these as server-enforced product requirements, not interface suggestions:
1. Process files entirely in the browser, revoke object URLs after use, and never send image bytes to analytics or a server.
2. Preserve aspect ratio by default, prevent accidental upscaling, enforce pixel and memory limits, and explain unsupported browser capabilities.
3. Never replace the original file in place; produce a deterministic suffix and resolve duplicate output names inside ZIP downloads.
4. Run a bounded number of compression jobs concurrently so a large batch keeps the interface responsive and can be canceled.

DATA MODEL AND LIFECYCLE
Design a small relational schema centered on local ProcessingJob and ImageResult objects only. Before implementing it, document:
1. Each table’s purpose, primary key, ownership or tenant boundary, timestamps, status fields, and important attributes.
2. Foreign keys, uniqueness constraints, check constraints, indexes needed by the named screens, and transaction boundaries for multi-record changes.
3. The allowed lifecycle or state transitions, who may trigger each transition, which transitions are terminal or reversible, and what audit history must remain immutable.
4. Archive, retention, and deletion behavior, including what happ...