feat: massively overhaul codebase

.cargo/config.toml

@@ -0,0 +1,9 @@
+# WASM targets for wasmtime.
+# wasm32-unknown-unknown is used by default (available on stable).
+# For full WASI support, install: rustup target add wasm32-wasi --toolchain nightly
+
+[target.wasm32-unknown-unknown]
+rustflags = ["-C", "target-feature=+atomics,+bulk-memory,+mutable-globals,+simd128"]
+
+[target.wasm32-wasi]
+rustflags = ["-C", "target-feature=+atomics,+bulk-memory,+mutable-globals,+simd128"]

.claude/rules/cleanup-downloads.md

@@ -0,0 +1,32 @@
+---
+description: Clean up any downloaded files after they are no longer needed.
+glob: "*"
+---
+
+# Clean Up Downloaded Files
+
+After downloading any files (archives, packages, binaries, datasets, temporary assets), remove them once they have served their purpose.
+
+## Rules
+
+1. After extracting an archive, delete the archive.
+2. After installing a package from a downloaded tarball, delete the tarball.
+3. After copying needed data from a downloaded file, delete the original download.
+4. After fetching a binary or tool for a one-time operation, delete it when done.
+
+## When to Clean
+
+Remove downloads immediately after:
+- Extracting an archive (`tar`, `unzip`, etc.)
+- Installing from a downloaded package
+- Copying data from a temporary file
+- Running a one-time tool or binary
+- Generating a build artifact that's already committed
+
+## What to Keep
+
+Do **not** delete:
+- Source code files
+- Configuration files
+- Build outputs that are part of the project
+- Files tracked by git

.claude/rules/commit-after-changes.md

@@ -0,0 +1,9 @@
+---
+description: Always commit after every meaningful code change before moving to the next task.
+glob: "*"
+---
+
+# Commit After Changes
+
+After every meaningful code change (fix, feature, config update), stage and commit the files before moving to the next task.
+Do not batch multiple changes into a single commit unless they are part of the same atomic fix.

.claude/rules/escape-at-signs.md

@@ -0,0 +1,15 @@
+---
+description: Escape @ symbols in commit messages and file content before committing to GitHub to prevent unwanted mentions.
+glob: "*"
+---
+
+# Escape @ Symbols Before Committing
+
+Always escape `@` symbols with a backslash (`\@`) in commit messages and any file content before committing to GitHub, to prevent GitHub from interpreting them as user or team mentions.
+
+Apply this to:
+- Commit messages
+- Markdown files
+- Any text that will be rendered by GitHub
+
+Example: `@username` → `\@username`

.claude/rules/playwright-verify.md

@@ -0,0 +1,70 @@
+---
+description: Verify all visual and behavioral changes using Playwright MCP before claiming success.
+glob: "*"
+---
+
+# Verify with Playwright MCP
+
+After making any visual or behavioral change, verify it works correctly using Playwright MCP browser tools. Never claim a feature works without confirming it in a real browser.
+
+## When to Verify
+
+Run Playwright verification after:
+- CSS/style changes
+- Component rewrites
+- Layout modifications
+- Adding or removing UI elements
+- Changing responsive behavior
+- Dark mode adjustments
+
+## Verification Steps
+
+1. **Navigate** to the affected page using `playwright_browser_navigate`
+2. **Snapshot** the page using `playwright_browser_snapshot` to verify structure
+3. **Screenshot** using `playwright_browser_take_screenshot` for visual confirmation
+4. **Interact** with the changed elements (click, type, hover) to confirm behavior
+5. **Compare** against expected appearance — if broken, fix immediately
+
+## Example Workflow
+
+```
+# After changing upload page styles
+1. playwright_browser_navigate → http://localhost:5173/upload
+2. playwright_browser_snapshot → verify component structure
+3. playwright_browser_take_screenshot → visual check
+4. playwright_browser_click → test interactive elements
+5. Confirm no regressions
+```
+
+## Golden Path + Edge Cases
+
+Test both:
+- **Golden path**: the main happy flow (e.g., select files → upload → share)
+- **Edge cases**: empty states, error states, loading states, mobile viewports
+
+## Responsive Testing
+
+After CSS changes, verify at multiple viewports:
+
+```
+1. playwright_browser_resize → 1920x1080 (desktop)
+2. playwright_browser_resize → 768x1024 (tablet)
+3. playwright_browser_resize → 375x667 (mobile)
+```
+
+## Dark Mode Testing
+
+After style changes, toggle dark mode and verify:
+
+```
+1. playwright_browser_evaluate → toggle .dark class on <html>
+2. playwright_browser_snapshot → verify dark styles
+3. Confirm no broken contrast or missing overrides
+```
+
+## What NOT to Do
+
+1. **Do NOT** claim a change works without browser verification
+2. **Do NOT** skip verification for "small" CSS changes
+3. **Do NOT** assume Tailwind classes work without confirming the output
+4. **Do NOT** skip responsive verification after layout changes