I'll build Shutter v0 - an ephemeral identity chat interface with hard reset capabilities. Let me first check the project structure, then create this minimal, honest implementation.

Now I'll build Shutter v0 with:

1. API routes for session management (start, message, shutter)
2. A clean chat interface with prominent reset button
3. Session indicator showing ephemeral state

Now let me create the chat UI component and the main page:

Shutter v0 is now live. Here's what I built:

Backend (3 API routes):

• /api/start - Creates a new ephemeral session
• /api/message - Handles messages with session-scoped context only
• /api/shutter - Hard delete + new identity (the core feature)

Frontend:

• Visible "Temporary session" indicator (always shown)
• "Start over as a stranger" button - no confirmation dialogs, no dark patterns
• Session ID displayed (truncated) so users can verify resets
• Clean chat interface with message count

Non-negotiable constraints enforced:

1. ✅ No silent persistence - in-memory only, no embeddings, no hidden logs
2. ✅ No cross-session inference - invalid session = denied
3. ✅ Reset is real - actual delete() on backend, not just UI clear
4. ✅ No friction - single click reset, no "are you sure?"

The session store uses a simple Map that dies with the server. When you click "Start over as a stranger", the old session is deleted and you get a completely new identity with no connection to the old one. Try sending a few messages, then reset - you'll feel the clean break.