docs: Add screenshot and comprehensive release documentation

- Add home.png screenshot to README header
- Complete release.md with all v1.0.0 features
- Document Image Gallery with full feature list
- Include all bug fixes and improvements
- Ready for v1.0.0 release

Author: theabbie

.gitignore

@@ -140,8 +140,9 @@ vite.config.ts.timestamp-*
 
 # Chrome Extension
 *.crx
-*.pem
+privatekey.pem
 chaos-tab-*.zip
+chaos-tab-temp/
 web-ext-artifacts/
 .web-extension-id
 

README.md

@@ -1,6 +1,8 @@
 # Chaos Tab
 
-Transform your new tab into a mesmerizing double pendulum physics simulation with powerful productivity tools. Watch chaos theory unfold in real-time while managing your notes, tasks, and bookmarks—all in one beautiful interface.
+![Chaos Tab Screenshot](home.png)
+
+Transform your new tab into a mesmerizing double pendulum physics simulation with powerful productivity tools. Watch chaos theory unfold in real-time while managing your notes, tasks, bookmarks, custom widgets, and image gallery—all in one beautiful interface.
 
 ## Features
 

SIGNING.md

@@ -0,0 +1,140 @@
+# 🔐 Verified CRX Signing Guide
+
+This document explains how to sign Chaos Tab for verified CRX uploads to Chrome Web Store.
+
+## 📋 Prerequisites
+
+- OpenSSL installed
+- Google Chrome installed
+- Private key (`privatekey.pem`) - **KEEP THIS SAFE!**
+
+## 🔑 Key Management
+
+### Your Keys
+
+**Private Key:** `privatekey.pem`
+- ⚠️ **NEVER commit to Git** (already in .gitignore)
+- ⚠️ **NEVER share with anyone**
+- ✅ Store in encrypted location
+- ✅ Keep offline backup on USB drive
+- ✅ Store encrypted backup in password manager
+
+**Public Key:** Used for Chrome Web Store verification
+```bash
+openssl rsa -in privatekey.pem -pubout
+```
+
+### If You Lose the Private Key
+
+❌ **You CANNOT update your extension anymore!**
+- You'll need to publish as a new extension
+- All users and reviews will be lost
+- **BACKUP YOUR KEY IMMEDIATELY**
+
+## 🚀 Signing Process
+
+### Option 1: Use the Script (Recommended)
+
+```bash
+./sign-extension.sh
+```
+
+This will:
+1. Check for private key
+2. Pack and sign the extension
+3. Create `chaos-tab-v1.0.0.crx`
+
+### Option 2: Manual Signing
+
+```bash
+# On macOS
+/Applications/Google\ Chrome.app/Contents/MacOS/Google\ Chrome \
+  --pack-extension=. \
+  --pack-extension-key=privatekey.pem
+
+# On Linux
+google-chrome --pack-extension=. --pack-extension-key=privatekey.pem
+
+# On Windows
+"C:\Program Files\Google\Chrome\Application\chrome.exe" ^
+  --pack-extension=. ^
+  --pack-extension-key=privatekey.pem
+```
+
+## 📤 Upload to Chrome Web Store
+
+### First Time Setup
+
+1. Go to [Chrome Web Store Developer Dashboard](https://chrome.google.com/webstore/devconsole)
+2. Navigate to your extension → **Package** tab
+3. Find **Verified CRX Uploads** section
+4. Click **Opt In**
+5. Paste your public key:
+   ```bash
+   openssl rsa -in privatekey.pem -pubout
+   ```
+6. Click **Save**
+
+### For Each Update
+
+1. Run `./sign-extension.sh` to create signed CRX
+2. Go to Developer Dashboard
+3. Click **Upload New Package**
+4. Upload the `.crx` file (NOT the `.zip`)
+5. Submit for review
+
+## 🔒 Security Best Practices
+
+### DO:
+- ✅ Keep private key in encrypted storage
+- ✅ Backup to multiple secure locations
+- ✅ Use password manager for backup
+- ✅ Store offline copy on USB drive
+- ✅ Verify .gitignore includes `*.pem`
+
+### DON'T:
+- ❌ Commit to Git/GitHub
+- ❌ Email or message the key
+- ❌ Store in cloud unencrypted
+- ❌ Share with anyone
+- ❌ Store in Google Account
+
+## 🆘 Backup Checklist
+
+Before publishing, ensure you have:
+
+- [ ] Private key backed up in password manager
+- [ ] Private key on encrypted USB drive
+- [ ] Private key in secure cloud storage (encrypted)
+- [ ] Public key saved (can regenerate from private)
+- [ ] Tested signing process works
+
+## 📝 Verification
+
+After opting in, your extension will show:
+- ✅ "Verified" badge on Chrome Web Store
+- ✅ Cryptographic verification of updates
+- ✅ Protection against package tampering
+
+## 🔄 Regenerating Keys (Emergency Only)
+
+If you lose your key, you CANNOT update the existing extension. You must:
+
+1. Create new extension listing
+2. Generate new key pair
+3. Lose all existing users and reviews
+4. Start from scratch
+
+**This is why backup is critical!**
+
+## 📞 Support
+
+If you have issues:
+- Check Chrome version is up to date
+- Verify OpenSSL is installed
+- Ensure private key has correct permissions
+- Contact: abhishek7gg7@gmail.com
+
+---
+
+**Remember: Your private key is irreplaceable. Treat it like a password to your bank account!**