Add user and brewery address tables

Auth and Emails land together since Auth's registration/resend flows need
Emails to exist first. Service.Auth's four services (Register, Login,
Confirmation, Token) collapse into MediatR commands/queries in
Features.Auth; TokenService stays as a slice-internal service since
multiple handlers call it. Auth no longer references Emails directly —
it sends SendRegistrationEmailCommand/SendResendConfirmationEmailCommand
(defined in Shared.Application) which Features.Emails handles, so neither
slice has a project reference on the other.

Service.Emails' IEmailService becomes Features.Emails' IEmailDispatcher,
simplified to take (firstName, email, token) instead of a full UserAccount
since that's all it ever used. API.Specs' TestApiFactory/MockEmailService
are updated to swap in the relocated interface.

Also deletes Infrastructure.Repository now that Breweries, UserManagement,
and Auth have all moved their repos out of it, and replaces the two
now-dead docker-compose test services (repository.tests, service.auth.tests,
both pointing at deleted Dockerfiles) with a single unit.tests service that
runs every Features.*.Tests project via Dockerfile.tests.

.config/dotnet-tools.json

@@ -1,13 +0,0 @@
-{
-  "version": 1,
-  "isRoot": true,
-  "tools": {
-    "csharpier": {
-      "version": "1.2.1",
-      "commands": [
-        "csharpier"
-      ],
-      "rollForward": false
-    }
-  }
-}

.gitattributes

@@ -0,0 +1 @@
+archive/** linguist-vendored

.github/ISSUE_TEMPLATE/feature_request.md

@@ -7,6 +7,7 @@ assignees: []
 ---
 
 ## User Story
+
 **As a** (who wants to accomplish something)  
 **I want to** (what they want to accomplish)  
 **So that** (why they want to accomplish that thing)
@@ -15,29 +16,18 @@ assignees: []
 
 ### Scenario 1
 
-
+Given ... When ... Then ...
-Given ...
-When ...
-Then ...
-
 
 ### Scenario 2
 
-
+Given ... When ... Then ...
-Given ...
-When ...
-Then ...
-
 
 ### Scenario 3
 
-
+Given ... When ... Then ...
-Given ...
-When ...
-Then ...
-
 
 ## Subtasks
+
 - [ ] Task 1
 - [ ] Task 2
 - [ ] Task 3

README.md

@@ -1,40 +1,56 @@
 # The Biergarten App
 
-The Biergarten App is a multi-project monorepo with a .NET backend and an active React
+The Biergarten App is a full-stack directory and discovery platform for
-Router frontend in `src/Website`. The current website focuses on account flows, theme
+breweries. It features a robust user authentication system, a searchable
-switching, shared UI components, Storybook coverage, and integration with the API.
+database of brewery locations, and a custom offline data-generation pipeline
+that uses LLMs (Llama.cpp) and Wikipedia to synthesize realistic seed data.
 
-## Documentation
+It features:
 
-- [Getting Started](docs/getting-started.md) - Local setup for backend and active website
+- A .NET backend (Web API + database migrations/seed) under `web/backend/`
-- [Architecture](docs/architecture.md) - Current backend and frontend architecture
+- A server-rendered React website (React Router + Vite) under `web/frontend/`
-- [Docker Guide](docs/docker.md) - Container-based backend development and testing
+- A C++20 “pipeline” CLI for generating seed data under `tooling/pipeline/`
-- [Testing](docs/testing.md) - Backend and frontend test commands
+
-- [Environment Variables](docs/environment-variables.md) - Active configuration reference
+Specialized documentation (setup, architecture, docker, testing, diagrams, and
-- [Token Validation](docs/token-validation.md) - JWT validation architecture
+pipeline notes) lives under `docs/`.
-- [Legacy Website Archive](docs/archive/legacy-website-v1.md) - Archived notes for the old Next.js frontend
+
+## Documentation (Start Here)
+
+Website + backend (active stack):
+
+- [Getting Started](docs/website/getting-started.md)
+- [Architecture](docs/architecture.md)
+- [Docker Guide](docs/website/docker.md)
+- [Testing](docs/website/testing.md)
+- [Environment Variables](docs/website/environment-variables.md)
+- [Token Validation](docs/website/token-validation.md)
+
+Data generation pipeline (C++):
+
+- [Pipeline README](docs/pipeline/README.md)
+- [Ethics & Known Issues](docs/pipeline/ETHICS-AND-KNOWN-ISSUES.md)
 
 ## Diagrams
 
-- [Architecture](docs/diagrams-out/architecture.svg) - Layered architecture
+- [Architecture](docs/website/diagrams-out/architecture.svg)
-- [Deployment](docs/diagrams-out/deployment.svg) - Docker topology
+- [Deployment](docs/website/diagrams-out/deployment.svg)
-- [Authentication Flow](docs/diagrams-out/authentication-flow.svg) - Auth sequence
+- [Authentication Flow](docs/website/diagrams-out/authentication-flow.svg)
-- [Database Schema](docs/diagrams-out/database-schema.svg) - Entity relationships
+- [Database Schema](docs/website/diagrams-out/database-schema.svg)
 
 ## Current Status
 
 Active areas in the repository:
 
-- .NET 10 backend with layered architecture and SQL Server
+- .NET 10 backend (vertical-slice architecture with MediatR) + SQL Server
-- React Router 7 website in `src/Website`
+- React 19 website (React Router 7 + Vite)
-- Shared Biergarten theme system with a theme guide route
+- Shared Biergarten theme system + Storybook coverage
-- Storybook stories and browser-based checks for shared UI
+- Auth flows and account/email integration (local Mailpit in dev compose)
-- Auth demo flows for home, login, register, dashboard, logout, and confirmation
+- Data generation pipeline with C++ and Llama.cpp
-- Toast-based feedback for auth outcomes
 
-Legacy area retained for reference:
+Archived/reference areas:
 
-- `src/Website-v1` contains the archived Next.js frontend and is no longer the active website
+- `archive/next-js-web-app/` contains an older Next.js frontend retained for
+  reference
 
 ## Tech Stack
 
@@ -43,36 +59,43 @@ Legacy area retained for reference:
 - **UI Documentation**: Storybook 10, Vitest browser mode, Playwright
 - **Testing**: xUnit, Reqnroll (BDD), FluentAssertions, Moq
 - **Infrastructure**: Docker, Docker Compose
-- **Security**: Argon2id password hashing, JWT access/refresh/confirmation tokens
+- **Security**: Argon2id password hashing, JWT access/refresh/confirmation
+  tokens
+- **Data Pipeline**: C++20, CMake, Boost, libcurl, SQLite, llama.cpp
 
 ## Quick Start
 
-### Backend
+For full setup details, use [Getting Started](docs/website/getting-started.md).
+This section is the shortest path to a working dev environment.
+
+### Backend (Docker)
 
 ```bash
 git clone https://github.com/aaronpo97/the-biergarten-app
 cd the-biergarten-app
-cp .env.example .env.dev
+
-docker compose -f docker-compose.dev.yaml up -d
+cp web/.env.example web/.env.dev
+docker compose --env-file web/.env.dev -f web/docker-compose.dev.yaml up --build -d
 ```
 
 Backend access:
 
 - API Swagger: http://localhost:8080/swagger
 - Health Check: http://localhost:8080/health
+- Mailpit UI (dev SMTP): http://localhost:8025
 
-### Frontend
+### Frontend (Node)
 
 ```bash
-cd src/Website
+cd web/frontend
 npm install
-API_BASE_URL=http://localhost:8080 SESSION_SECRET=dev-secret npm run dev
+API_BASE_URL=http://localhost:8080 SESSION_SECRET=dev-secret-change-me npm run dev
 ```
 
 Optional frontend tools:
 
 ```bash
-cd src/Website
+cd web/frontend
 npm run storybook
 npm run test:storybook
 npm run test:storybook:playwright
@@ -81,62 +104,43 @@ npm run test:storybook:playwright
 ## Repository Structure
 
 ```text
-src/Core/          Backend projects (.NET)
+web/
-src/Website/       Active React Router frontend
+  backend/          .NET API: API.Core (host), Features.* (vertical slices),
-src/Website-v1/    Archived legacy Next.js frontend
+                     Shared.*, Domain.*, Infrastructure.*, Database.* projects
-docs/              Active project documentation
+  frontend/         React Router website + Storybook + Playwright/Vitest
-docs/archive/      Archived legacy documentation
+
+tooling/
+  pipeline/         C++20 seed-data generation CLI (CMake)
+
+docs/
+  architecture.md   High-level architecture overview
+  website/          Backend/frontend setup, docker, testing, diagrams
+  pipeline/         Pipeline docs, ethics notes, PlantUML diagrams
+
+archive/
+  next-js-web-app/  Older Next.js frontend (reference only)
 ```
 
-## Key Features
-
-Implemented today:
-
-- User registration and login against the API
-- JWT-based auth with access, refresh, and confirmation flows
-- SQL Server migrations and seed projects
-- Shared form components and auth screens
-- Theme switching with Lager, Stout, Cassis, and Weizen variants
-- Storybook documentation and automated story interaction tests
-- Toast feedback for auth-related outcomes
-
-Planned next:
-
-- Brewery discovery and management
-- Beer reviews and ratings
-- Social follow relationships
-- Geospatial brewery experiences
-- Additional frontend routes beyond the auth demo
-
 ## Testing
 
-Backend suites:
+Run the backend test stack with Docker:
-
-- `API.Specs` - integration tests
-- `Infrastructure.Repository.Tests` - repository unit tests
-- `Service.Auth.Tests` - service unit tests
-
-Frontend suites:
-
-- Storybook interaction tests via Vitest
-- Storybook browser regression checks via Playwright
-
-Run all backend tests with Docker:
 
 ```bash
-docker compose -f docker-compose.test.yaml up --abort-on-container-exit
+docker compose --env-file web/.env.test -f web/docker-compose.test.yaml up --abort-on-container-exit
 ```
 
-See [Testing](docs/testing.md) for the full command list.
+See [Testing](docs/website/testing.md) for the full command list.
 
 ## Configuration
 
 Common active variables:
 
-- Backend: `DB_SERVER`, `DB_NAME`, `DB_USER`, `DB_PASSWORD`, `ACCESS_TOKEN_SECRET`, `REFRESH_TOKEN_SECRET`, `CONFIRMATION_TOKEN_SECRET`
+- Backend/Docker: `DB_SERVER`, `DB_NAME`, `DB_USER`, `DB_PASSWORD`,
-- Frontend: `API_BASE_URL`, `SESSION_SECRET`, `NODE_ENV`
+  `ACCESS_TOKEN_SECRET`, `REFRESH_TOKEN_SECRET`, `CONFIRMATION_TOKEN_SECRET`,
+  `WEBSITE_BASE_URL`
+- Frontend runtime: `API_BASE_URL`, `SESSION_SECRET`, `NODE_ENV`
 
-See [Environment Variables](docs/environment-variables.md) for details.
+See [Environment Variables](docs/website/environment-variables.md) for details.
 
 ## Contributing
 
@@ -145,15 +149,3 @@ See [Environment Variables](docs/environment-variables.md) for details.
 3. Commit your changes (`git commit -m 'Add amazing feature'`)
 4. Push to the branch (`git push origin feature/amazing-feature`)
 5. Open a Pull Request
-
-### Development Workflow
-
-1. Start development environment: `docker compose -f docker-compose.dev.yaml up -d`
-2. Make changes to code
-3. Run tests: `docker compose -f docker-compose.test.yaml up --abort-on-container-exit`
-4. Rebuild if needed: `docker compose -f docker-compose.dev.yaml up -d --build api.core`
-
-## Support
-
-- **Documentation**: [docs/](docs/)
-- **Architecture**: See [Architecture Guide](docs/architecture.md)