Prepare Repository for Chrome Web Store Build and Packaging

[cadudotdev]

The WorkLog Chrome extension repository needs to be prepared for generating a production-ready build suitable for Chrome Web Store publication. This issue focuses on configuring the Vite build process, generating the dist directory correctly, and ensuring the repository is structured for packaging, using React, TypeScript, TailwindCSS, and Chrome Extension Manifest V3.

Key Requirements:

• Configure Vite Build: Update vite.config.ts to ensure the build outputs a production-ready dist directory with minified assets and a correctly structured manifest.json at the root.
• Optimize Manifest: Review and update manifest.json to include minimal permissions (e.g., only those needed for time tracking and API integration) and set an initial version (e.g., 0.0.1) for future updates.
• Exclude Unnecessary Files: Ensure the dist directory excludes development files (e.g., .gitignore, .git, node_modules, vite.config.ts) and only includes necessary assets (e.g., manifest.json, compiled JS/CSS, icons).
• Verify Build Output: Test the dist directory in Chrome Developer Mode (chrome://extensions/) to confirm functionality of the time calculation sheet and compatibility with planned features (e.g., time tracking screen).
• Add Build Documentation: Update the README with clear instructions for generating the dist directory using npm run build.
• Automate Build Process: Optionally, set up a GitHub Action to automate the build process and verify the dist output on push or pull request events.
• Ensure Asset Compatibility: Verify that static assets (e.g., icons in public/) meet Chrome Web Store requirements (e.g., 128x128 icon) and are included in the dist directory.