chore: added cursor indexing and spectory

.cursorindexingignore

@@ -0,0 +1,3 @@
+
+# Don't index SpecStory auto-save files, but allow explicit context inclusion via @ references
+.specstory/**

.specstory/.gitignore

@@ -0,0 +1,4 @@
+# SpecStory project identity file
+/.project.json
+# SpecStory explanation file
+/.what-is-this.md

.specstory/history/2025-10-22_16-12Z-why-didn-t-this-work.md

@@ -0,0 +1,165 @@
+<!-- Generated by SpecStory, Markdown v2.0.0 -->
+
+<!-- cursor Session dd6194ca-82f0-470d-9cb5-eeae2e15f0e5 (2025-10-22 16:12Z) -->
+
+# Why didn't this work? (2025-10-22 16:12Z)
+
+_**User (2025-10-22 16:12Z)**_
+
+Why didn't this work?
+
+---
+
+_**Agent (model default, mode Agent)**_
+
+Looking at the terminal output, I can see the build is failing due to missing environment variables. Let me examine the project structure and configuration to understand what's happening.
+
+
+---
+
+<tool-use data-tool-type="read" data-tool-name="read_file">
+<details><summary>Tool use: **read_file** • Read file: /home/nicholai/Documents/dev/united-tattoo/lib/env.ts</summary>
+
+</details>
+</tool-use>
+
+---
+
+Could not find file '/home/nicholai/Documents/dev/united-tattoo/.env.local' in the workspace.
+
+---
+
+Could not find file /home/nicholai/Documents/dev/united-tattoo/.env.example in the workspace.
+
+---
+
+<tool-use data-tool-type="generic" data-tool-name="list_dir">
+<details>
+            <summary>Tool use: **list_directory** • Listed directory undefined • **0** results</summary>
+        
+No results found
+</details>
+</tool-use>
+
+---
+
+<tool-use data-tool-type="generic" data-tool-name="glob_file_search">
+<details>
+<summary>Tool use: **glob_file_search** • Searched codebase ".env*" • **1** result in **1** directory</summary>
+
+Directory: **/home/nicholai/Documents/dev/united-tattoo** (1 file)
+
+</details>
+</tool-use>
+
+---
+
+Now I understand the issue! The build is failing because you're missing the required environment variables. Looking at the error message and the `lib/env.ts` file, I can see that the application requires several environment variables to be set:
+
+**The build failed because these required environment variables are missing:**
+
+1. `DATABASE_URL` - Database connection string
+2. `NEXTAUTH_URL` - NextAuth.js base URL
+3. `NEXTAUTH_SECRET` - NextAuth.js secret key
+4. `AWS_ACCESS_KEY_ID` - AWS/R2 access key
+5. `AWS_SECRET_ACCESS_KEY` - AWS/R2 secret key
+6. `AWS_REGION` - AWS region
+7. `AWS_BUCKET_NAME` - S3/R2 bucket name
+
+The application uses Zod validation in `lib/env.ts` to validate these environment variables at startup, and when they're missing, it throws the error you're seeing.
+
+**To fix this, you need to:**
+
+1. **Create a `.env.local` file** in your project root with the required variables:
+
+```bash
+# Database
+DATABASE_URL="your_database_url_here"
+
+# Authentication
+NEXTAUTH_URL="http://localhost:3000"
+NEXTAUTH_SECRET="your_nextauth_secret_here"
+
+# AWS/R2 Storage
+AWS_ACCESS_KEY_ID="your_access_key"
+AWS_SECRET_ACCESS_KEY="your_secret_key"
+AWS_REGION="your_region"
+AWS_BUCKET_NAME="your_bucket_name"
+```
+
+2. **For development**, you can use placeholder values or set up the actual services:
+   - For `DATABASE_URL`: Set up a local database or use a cloud database
+   - For `NEXTAUTH_SECRET`: Generate a random string (you can use `openssl rand -base64 32`)
+   - For AWS/R2: Set up Cloudflare R2 or AWS S3 for file storage
+
+3. **Make sure `.env.local` is in your `.gitignore`** (which it should be by default in Next.js projects)
+
+The reason this happens during the build process is that Next.js tries to collect page data at build time, which includes running API routes that depend on these environment variables.
+
+Would you like me to help you set up the environment variables or create a template `.env.local` file?
+
+---
+
+_**User (2025-10-22 16:12Z)**_
+
+created my .env.local - still having an issue
+
+---
+
+_**Agent (model default, mode Agent)**_
+
+Great! I can see the build is now working successfully - the Next.js build completed without errors and the OpenNext build finished. The issue now is that `wrangler` command is not found.
+
+The error `bash: wrangler: command not found` means that the Cloudflare Wrangler CLI is not installed on your system.
+
+Let me check your package.json to see if it's listed as a dependency:
+
+
+---
+
+<tool-use data-tool-type="read" data-tool-name="read_file">
+<details><summary>Tool use: **read_file** • Read file: /home/nicholai/Documents/dev/united-tattoo/package.json</summary>
+
+</details>
+</tool-use>
+
+---
+
+Perfect! I can see that `wrangler` is listed as a dev dependency (line 139), but it's not installed globally on your system. The issue is that you're trying to run `wrangler dev` directly, but it should be run through npm/npx.
+
+Here are the solutions:
+
+**Option 1: Use npx to run wrangler (Recommended)**
+```bash
+npm run pages:build && npx wrangler dev
+```
+
+**Option 2: Use the existing npm script**
+Looking at your package.json, you already have a script for this:
+```bash
+npm run dev:wrangler
+```
+
+**Option 3: Install wrangler globally**
+```bash
+npm install -g wrangler
+```
+
+**Option 4: Use the preview command instead**
+```bash
+npm run preview
+```
+
+The reason this happens is that `wrangler` is installed as a local dev dependency in your project, but when you run `wrangler dev` directly in the terminal, your shell looks for a globally installed version of the command.
+
+I'd recommend using **Option 1** or **Option 2** since they use the locally installed version of wrangler that matches your project's requirements.
+
+Try running:
+```bash
+npm run pages:build && npx wrangler dev
+```
+
+This should work since the build already completed successfully!
+
+---
+