523 changed files with 2286 additions and 123526 deletions
--- a/Webs.prompt.md
+++ b/Webs.prompt.md
@ -1,459 +0,0 @@
 # GitHub Copilot Instructions - BMC Webshop (Frontend)
 ## Project Overview
 BMC Webshop er en kunde-styret webshop løsning, hvor **BMC Hub** ejer indholdet, **API Gateway** (`apigateway.bmcnetworks.dk`) styrer logikken, og **Webshoppen** (dette projekt) kun viser og indsamler input.
 **Tech Stack**: React/Next.js/Vue.js (vælg én), TypeScript, Tailwind CSS eller Bootstrap 5
 ---
 ## 3-Lags Arkitektur
 ```
 ┌─────────────────────────────────────────────────────────┐
 │  TIER 1: BMC HUB (Admin System)                         │
 │  - Administrerer webshop-opsætning                       │
 │  - Pusher data til Gateway                               │
 │  - Poller Gateway for nye ordrer                         │
 │  https://hub.bmcnetworks.dk                              │
 └─────────────────────────────────────────────────────────┘
                      ▼ (Push config)
 ┌─────────────────────────────────────────────────────────┐
 │  TIER 2: API GATEWAY (Forretningslogik + Database)      │
 │  - Modtager og gemmer webshop-config fra Hub            │
 │  - Ejer PostgreSQL database med produkter, priser, ordrer│
 │  - Håndterer email/OTP login                             │
 │  - Beregner priser og filtrerer varer                    │
 │  - Leverer sikre API'er til Webshoppen                   │
 │  https://apigateway.bmcnetworks.dk                       │
 └─────────────────────────────────────────────────────────┘
                      ▲ (API calls)
 ┌─────────────────────────────────────────────────────────┐
 │  TIER 3: WEBSHOP (Dette projekt - Kun Frontend)         │
 │  - Viser logo, tekster, produkter, priser                │
 │  - Shopping cart (kun i frontend state)                  │
 │  - Sender ordre som payload til Gateway                  │
 │  - INGEN forretningslogik eller datapersistering        │
 └─────────────────────────────────────────────────────────┘
 ```
 ---
 ## Webshoppens Ansvar
 ### ✅ Hvad Webshoppen GØR
 - Viser kundens logo, header-tekst, intro-tekst (fra Gateway)
 - Viser produktkatalog med navn, beskrivelse, pris (fra Gateway)
 - Samler kurv i browser state (localStorage/React state)
 - Sender ordre til Gateway ved checkout
 - Email/OTP login flow (kalder Gateway's auth-endpoint)
 ### ❌ Hvad Webshoppen IKKE GØR
 - Gemmer INGEN data (hverken kurv, produkter, eller ordrer)
 - Beregner INGEN priser eller avance
 - Håndterer INGEN produkt-filtrering (Gateway leverer klar liste)
 - Snakker IKKE direkte med Hub eller e-conomic
 - Håndterer IKKE betalingsgateway (Gateway's ansvar)
 ---
 ## API Gateway Kontrakt
 Base URL: `https://apigateway.bmcnetworks.dk`
 ### 1. Login med Email + Engangskode
 **Step 1: Anmod om engangskode**
 ```http
 POST /webshop/auth/request-code
 Content-Type: application/json
 {
  "email": "kunde@firma.dk"
 }
 Response 200:
 {
  "success": true,
  "message": "Engangskode sendt til kunde@firma.dk"
 }
 ```
 **Step 2: Verificer kode og få JWT token**
 ```http
 POST /webshop/auth/verify-code
 Content-Type: application/json
 {
  "email": "kunde@firma.dk",
  "code": "123456"
 }
 Response 200:
 {
  "success": true,
  "token": "eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9...",
  "customer_id": 42,
  "expires_at": "2026-01-13T15:00:00Z"
 }
 ```
 ### 2. Hent Webshop Context (Komplet Webshop-Data)
 ```http
 GET /webshop/{customer_id}/context
 Authorization: Bearer {jwt_token}
 Response 200:
 {
  "customer_id": 42,
  "company_name": "Advokatfirma A/S",
  "config_version": "2026-01-13T12:00:00Z",
  "branding": {
    "logo_url": "https://apigateway.bmcnetworks.dk/assets/logos/42.png",
    "header_text": "Velkommen til vores webshop",
    "intro_text": "Bestil nemt og hurtigt direkte her.",
    "primary_color": "#0f4c75",
    "accent_color": "#3282b8"
  },
  "products": [
    {
      "id": 101,
      "ean": "5711045071324",
      "product_number": "FIRE-001",
      "name": "Cisco Firewall ASA 5506-X",
      "description": "Next-generation firewall med 8 porte",
      "unit": "stk",
      "base_price": 8500.00,
      "calculated_price": 9350.00,
      "margin_percent": 10.0,
      "currency": "DKK",
      "stock_available": true,
      "category": "Network Security"
    },
    {
      "id": 102,
      "ean": "5704174801740",
      "product_number": "SW-024",
      "name": "TP-Link 24-Port Gigabit Switch",
      "description": "Managed switch med VLAN support",
      "unit": "stk",
      "base_price": 2100.00,
      "calculated_price": 2310.00,
      "margin_percent": 10.0,
      "currency": "DKK",
      "stock_available": true,
      "category": "Switches"
    }
  ],
  "allowed_payment_methods": ["invoice", "card"],
  "min_order_amount": 500.00,
  "shipping_cost": 0.00
 }
 ```
 ### 3. Opret Ordre
 ```http
 POST /webshop/orders
 Authorization: Bearer {jwt_token}
 Content-Type: application/json
 {
  "customer_id": 42,
  "order_items": [
    {
      "product_id": 101,
      "quantity": 2,
      "unit_price": 9350.00
    },
    {
      "product_id": 102,
      "quantity": 5,
      "unit_price": 2310.00
    }
  ],
  "shipping_address": {
    "company_name": "Advokatfirma A/S",
    "street": "Hovedgaden 1",
    "postal_code": "1000",
    "city": "København K",
    "country": "DK"
  },
  "delivery_note": "Levering til bagsiden, ring på døren",
  "total_amount": 30250.00
 }
 Response 201:
 {
  "success": true,
  "order_id": "ORD-2026-00123",
  "status": "pending",
  "total_amount": 30250.00,
  "created_at": "2026-01-13T14:30:00Z",
  "message": "Ordre modtaget. Du vil modtage en bekræftelse på email."
 }
 ```
 ### 4. Hent Mine Ordrer (Optional)
 ```http
 GET /webshop/orders?customer_id=42
 Authorization: Bearer {jwt_token}
 Response 200:
 {
  "orders": [
    {
      "order_id": "ORD-2026-00123",
      "created_at": "2026-01-13T14:30:00Z",
      "status": "pending",
      "total_amount": 30250.00,
      "item_count": 7
    }
  ]
 }
 ```
 ---
 ## Frontend Krav
 ### Mandatory Features
 1. **Responsive Design**
   - Mobile-first approach
   - Breakpoints: 576px (mobile), 768px (tablet), 992px (desktop)
   - Brug CSS Grid/Flexbox eller framework grid system
 2. **Dark Mode Support**
   - Toggle mellem light/dark theme
   - Gem præference i localStorage
   - CSS Variables for farver
 3. **Shopping Cart**
   - Gem kurv i localStorage (persist ved page reload)
   - Vis antal varer i header badge
   - Real-time opdatering af total pris
   - Slet/rediger varer i kurv
 4. **Login Flow**
   - Email input → Send kode
   - Vis countdown timer (5 minutter)
   - Verificer kode → Få JWT token
   - Gem token i localStorage
   - Auto-logout ved token expiry
 5. **Product Catalog**
   - Vis produkter i grid layout (3-4 kolonner på desktop)
   - Filtrer produkter efter kategori (hvis Gateway leverer kategorier)
   - Søgning i produktnavn/beskrivelse
   - "Tilføj til kurv" knap med antal-vælger
 6. **Checkout Flow**
   - Vis kurv-oversigt
   - Leveringsadresse (kan være pre-udfyldt fra Gateway)
   - Leveringsnotat (textarea)
   - "Bekræft ordre" knap
   - Loading state under ordre-oprettelse
   - Success/error feedback
 ### Design Guidelines
 **Stil**: Minimalistisk, clean, "Nordic" æstetik (inspireret af BMC Hub's Nordic Top design)
 **Farver** (kan overskrives af Gateway's branding config):
 - Primary: `#0f4c75` (Deep Blue)
 - Accent: `#3282b8` (Bright Blue)
 - Success: `#27ae60`
 - Warning: `#f39c12`
 - Danger: `#e74c3c`
 **Typografi**:
 - Font: System font stack (`-apple-system, BlinkMacSystemFont, "Segoe UI", Roboto, ...`)
 - Headings: 500-600 weight
 - Body: 400 weight
 **Components**:
 - Cards med subtil shadow/border
 - Buttons med hover states
 - Input fields med focus outline
 - Loading spinners (ikke lange tekst-beskeder)
 ---
 ## State Management
 ### Local Storage Keys
 ```javascript
 // Authentication
 webshop_jwt_token          // JWT token fra Gateway
 webshop_customer_id        // Customer ID
 webshop_token_expires_at   // ISO timestamp
 // Shopping Cart
 webshop_cart               // JSON array af cart items
 webshop_theme              // "light" eller "dark"
 // Cache (optional)
 webshop_context            // Cached webshop context (TTL: 5 minutter)
 ```
 ### Cart Item Format
 ```javascript
 {
  product_id: 101,
  ean: "5711045071324",
  name: "Cisco Firewall ASA 5506-X",
  unit_price: 9350.00,
  quantity: 2,
  total: 18700.00
 }
 ```
 ---
 ## Error Handling
 ### Gateway API Errors
 ```javascript
 // Eksempel på error response fra Gateway
 {
  "success": false,
  "error": "invalid_code",
  "message": "Ugyldig engangskode. Prøv igen."
 }
 ```
 **Error Codes** (forventet fra Gateway):
 - `invalid_email` - Email ikke fundet eller ikke whitelisted
 - `invalid_code` - Forkert engangskode
 - `code_expired` - Engangskode udløbet (>5 min)
 - `token_expired` - JWT token udløbet
 - `unauthorized` - Manglende/ugyldig Authorization header
 - `product_not_found` - Produkt ID findes ikke
 - `min_order_not_met` - Ordre under minimum beløb
 - `out_of_stock` - Produkt ikke på lager
 **Handling**:
 - Vis brugervenlig fejlbesked i UI (ikke tekniske detaljer)
 - Log tekniske fejl til console (kun i development)
 - Redirect til login ved `token_expired` eller `unauthorized`
 ---
 ## Security
 1. **HTTPS Only**
   - Al kommunikation med Gateway over HTTPS
   - Ingen hardcoded credentials
 2. **JWT Token**
   - Gem i localStorage (ikke cookie)
   - Send i `Authorization: Bearer {token}` header
   - Check expiry før hver API call
   - Auto-logout ved expiry
 3. **Input Validation**
   - Validér email format (client-side)
   - Validér antal > 0 ved "Tilføj til kurv"
   - Validér leveringsadresse udfyldt ved checkout
   - Sanitize input (brug library som DOMPurify hvis nødvendigt)
 4. **CORS**
   - Gateway skal have `Access-Control-Allow-Origin` header
   - Webshoppen kalder altid Gateway (ikke Hub direkte)
 ---
 ## Deployment
 ### Environment Variables
 ```bash
 # .env.production
 NEXT_PUBLIC_API_GATEWAY_URL=https://apigateway.bmcnetworks.dk
 NEXT_PUBLIC_WEBSHOP_NAME="BMC Networks Webshop"
 ```
 ### Build Process
 ```bash
 # Development
 npm run dev
 # Production build
 npm run build
 npm run start
 # Docker (optional)
 docker build -t bmc-webshop .
 docker run -p 3000:3000 bmc-webshop
 ```
 ### Static Hosting (Anbefalet)
 - Vercel, Netlify, eller Cloudflare Pages
 - Deploy fra Git repository
 - Automatisk HTTPS og CDN
 - Environment variables i hosting provider UI
 ---
 ## Testing
 ### Manual Testing Checklist
 - [ ] Login med email/OTP virker
 - [ ] Token gemmes og bruges i efterfølgende API calls
 - [ ] Webshop context hentes og vises korrekt
 - [ ] Produkter vises i grid
 - [ ] "Tilføj til kurv" opdaterer cart badge
 - [ ] Cart viser korrekte varer og total pris
 - [ ] Checkout sender korrekt payload til Gateway
 - [ ] Success message vises ved succesfuld ordre
 - [ ] Error handling virker (test med ugyldig kode, udløbet token)
 - [ ] Dark mode toggle virker
 - [ ] Responsive design på mobil/tablet/desktop
 ---
 ## Common Pitfalls to Avoid
 1. **Gem IKKE data i Webshoppen** - alt kommer fra Gateway
 2. **Beregn IKKE priser selv** - Gateway leverer `calculated_price`
 3. **Snakker IKKE direkte med Hub** - kun via Gateway
 4. **Gem IKKE kurv i database** - kun localStorage
 5. **Hardcode IKKE customer_id** - hent fra JWT token
 6. **Valider IKKE produkter selv** - Gateway filtrerer allerede
 7. **Implementer IKKE betalingsgateway** - Gateway's ansvar
 ---
 ## Quick Reference
 ### API Endpoints
 ```
 POST   /webshop/auth/request-code         # Anmod engangskode
 POST   /webshop/auth/verify-code          # Verificer kode → JWT
 GET    /webshop/{customer_id}/context     # Hent webshop data
 POST   /webshop/orders                    # Opret ordre
 GET    /webshop/orders?customer_id={id}   # Hent mine ordrer
 ```
 ### Typical Flow
 ```
 1. User indtaster email → POST /auth/request-code
 2. User indtaster kode → POST /auth/verify-code → Gem JWT token
 3. App henter webshop context → GET /context (med JWT header)
 4. User browser produkter, tilføjer til kurv (localStorage)
 5. User går til checkout → POST /orders (med cart data)
 6. Gateway behandler ordre → Success message vises
 ```
 ---
 ## Support & Documentation
 **Hub Repository**: `/Users/christianthomas/DEV/bmc_hub_dev`
 **Hub API Docs**: `https://hub.bmcnetworks.dk/api/docs`
 **Gateway API Docs**: `https://apigateway.bmcnetworks.dk/docs` (når implementeret)
 **Kontakt**: ct@bmcnetworks.dk
--- a/.env.bak
+++ b/.env.bak
@ -34,37 +34,31 @@ LOG_FILE=logs/app.log
 # Repository: https://g.bmcnetworks.dk/ct/bmc_hub
 GITHUB_REPO=ct/bmc_hub
 # =====================================================
 # OLLAMA AI INTEGRATION
 # =====================================================
 OLLAMA_ENDPOINT=http://ai_direct.cs.blaahund.dk
 OLLAMA_MODEL=qwen2.5-coder:7b
 # =====================================================
 # e-conomic Integration (Optional)
 # =====================================================
 # Get credentials from e-conomic Settings -> Integrations -> API
 ECONOMIC_API_URL=https://restapi.e-conomic.com
-ECONOMIC_APP_SECRET_TOKEN=wy8ZhYBLsKhx8McirhvoBR9B6ILuoYJkEaiED5ijsA8
+ECONOMIC_APP_SECRET_TOKEN=your_app_secret_token_here
-ECONOMIC_AGREEMENT_GRANT_TOKEN=5AhipRpMpoLx3uklPMQZbtZ4Zw4mV9lDuFI264II0lE
+ECONOMIC_AGREEMENT_GRANT_TOKEN=your_agreement_grant_token_here
 # 🚨 SAFETY SWITCHES - Beskytter mod utilsigtede ændringer
 ECONOMIC_READ_ONLY=true   # Set to false ONLY after testing
 ECONOMIC_DRY_RUN=true     # Set to false ONLY when ready for production writes
-# =====================================================
+# vTiger CRM Integration (for Time Tracking Module)
 # vTiger Cloud Integration (Required for Subscriptions)
 # =====================================================
 VTIGER_URL=https://bmcnetworks.od2.vtiger.com
 VTIGER_USERNAME=ct@bmcnetworks.dk
 VTIGER_API_KEY=bD8cW8zRFuKpPZ2S
 # =====================================================
 # Simply-CRM / Old vTiger On-Premise (Legacy)
 # =====================================================
 # Old vTiger installation - leave empty if not used
 OLD_VTIGER_URL=https://bmcnetworks.simply-crm.dk
 OLD_VTIGER_USERNAME=ct
 OLD_VTIGER_API_KEY=b00ff2b7c08d591
 # =====================================================
 # Time Tracking Module Settings
-# =====================================================
+TIMETRACKING_DEFAULT_HOURLY_RATE=1200.00  # Standard timepris i DKK
 TIMETRACKING_DEFAULT_HOURLY_RATE=1200.00
 TIMETRACKING_AUTO_ROUND=true
 TIMETRACKING_ROUND_INCREMENT=0.5
 TIMETRACKING_ROUND_METHOD=up
@ -72,15 +66,6 @@ TIMETRACKING_ROUND_METHOD=up
 # Time Tracking Safety Switches
 TIMETRACKING_VTIGER_READ_ONLY=true
 TIMETRACKING_VTIGER_DRY_RUN=true
-TIMETRACKING_ECONOMIC_READ_ONLY=false
+TIMETRACKING_ECONOMIC_READ_ONLY=true
-TIMETRACKING_ECONOMIC_DRY_RUN=false
+TIMETRACKING_ECONOMIC_DRY_RUN=true
 # =====================================================
 # Simply-CRM (Separate CRM System)
 # =====================================================
 # Simply-CRM er et separat system fra vTiger Cloud
 # Find credentials i Simply-CRM: Settings → My Preferences → Webservices
 SIMPLYCRM_URL=https://bmcnetworks.simply-crm.dk
 SIMPLYCRM_USERNAME=ct
 SIMPLYCRM_API_KEY=b00ff2b7c08d591
 BACKUP_RESTORE_DRY_RUN=false
--- a/.env.bak2
+++ b/.env.bak2
@ -1,96 +0,0 @@
 # =====================================================
 # POSTGRESQL DATABASE - Local Development
 # =====================================================
 DATABASE_URL=postgresql://bmc_hub:bmc_hub@postgres:5432/bmc_hub
 # Database credentials (bruges af docker-compose)
 POSTGRES_USER=bmc_hub
 POSTGRES_PASSWORD=bmc_hub
 POSTGRES_DB=bmc_hub
 POSTGRES_PORT=5433
 # =====================================================
 # API CONFIGURATION
 # =====================================================
 API_HOST=0.0.0.0
 API_PORT=8001
 API_RELOAD=true
 # =====================================================
 # SECURITY
 # =====================================================
 SECRET_KEY=change-this-in-production-use-random-string
 CORS_ORIGINS=http://localhost:8000,http://localhost:3000
 # =====================================================
 # LOGGING
 # =====================================================
 LOG_LEVEL=INFO
 LOG_FILE=logs/app.log
 # =====================================================
 # GITHUB/GITEA REPOSITORY (Optional - for reference)
 # =====================================================
 # Repository: https://g.bmcnetworks.dk/ct/bmc_hub
 GITHUB_REPO=ct/bmc_hub
 # =====================================================
 # e-conomic Integration (Optional)
 # =====================================================
 # Get credentials from e-conomic Settings -> Integrations -> API
 ECONOMIC_API_URL=https://restapi.e-conomic.com
 ECONOMIC_APP_SECRET_TOKEN=wy8ZhYBLsKhx8McirhvoBR9B6ILuoYJkEaiED5ijsA8
 ECONOMIC_AGREEMENT_GRANT_TOKEN=5AhipRpMpoLx3uklPMQZbtZ4Zw4mV9lDuFI264II0lE
 # 🚨 SAFETY SWITCHES - Beskytter mod utilsigtede ændringer
 ECONOMIC_READ_ONLY=true   # Set to false ONLY after testing
 ECONOMIC_DRY_RUN=true     # Set to false ONLY when ready for production writes
 # =====================================================
 # vTiger Cloud Integration (Required for Subscriptions)
 # =====================================================
 VTIGER_URL=https://bmcnetworks.od2.vtiger.com
 VTIGER_USERNAME=ct@bmcnetworks.dk
 VTIGER_API_KEY=bD8cW8zRFuKpPZ2S
 # =====================================================
 # Simply-CRM / Old vTiger On-Premise (Legacy)
 # =====================================================
 # Old vTiger installation - leave empty if not used
 OLD_VTIGER_URL=https://bmcnetworks.simply-crm.dk
 OLD_VTIGER_USERNAME=ct
 OLD_VTIGER_API_KEY=b00ff2b7c08d591
 # =====================================================
 # Time Tracking Module Settings
 # =====================================================
 TIMETRACKING_DEFAULT_HOURLY_RATE=1200.00
 TIMETRACKING_AUTO_ROUND=true
 TIMETRACKING_ROUND_INCREMENT=0.5
 TIMETRACKING_ROUND_METHOD=up
 # Time Tracking Safety Switches
 TIMETRACKING_VTIGER_READ_ONLY=true
 TIMETRACKING_VTIGER_DRY_RUN=true
 TIMETRACKING_ECONOMIC_READ_ONLY=false
 TIMETRACKING_ECONOMIC_DRY_RUN=false
 # =====================================================
 # Simply-CRM (Separate CRM System)
 # =====================================================
 # Simply-CRM er et separat system fra vTiger Cloud
 # Find credentials i Simply-CRM: Settings → My Preferences → Webservices
 SIMPLYCRM_URL=https://bmcnetworks.simply-crm.dk
 SIMPLYCRM_USERNAME=ct
 SIMPLYCRM_API_KEY=b00ff2b7c08d591
 BACKUP_RESTORE_DRY_RUN=false
 # =====================================================
 # OFFSITE BACKUP - SFTP
 # =====================================================
 OFFSITE_ENABLED=true
 SFTP_HOST=sftp.acdu.dk
 SFTP_PORT=9022
 SFTP_USER=sftp_bmccrm
 SFTP_PASSWORD=9,Bg_U9,Bg_U9,Bg_U
 SFTP_REMOTE_PATH=/backups
--- a/.env.example
+++ b/.env.example
@ -22,20 +22,6 @@ ENABLE_RELOAD=false  # Set to true for live code reload (causes log spam in Dock
 SECRET_KEY=change-this-in-production-use-random-string
 CORS_ORIGINS=http://localhost:8000,http://localhost:3000
 # Telefoni (Yealink) callbacks security (MUST set at least one)
 # Option A: Shared secret token (recommended)
 TELEFONI_SHARED_SECRET=
 # Option B: IP whitelist (LAN only) - supports IPs and CIDRs
 TELEFONI_IP_WHITELIST=127.0.0.1
 # Shadow Admin (Emergency Access)
 SHADOW_ADMIN_ENABLED=false
 SHADOW_ADMIN_USERNAME=shadowadmin
 SHADOW_ADMIN_PASSWORD=
 SHADOW_ADMIN_TOTP_SECRET=
 SHADOW_ADMIN_EMAIL=shadowadmin@bmcnetworks.dk
 SHADOW_ADMIN_FULL_NAME=Shadow Administrator
 # =====================================================
 # LOGGING
 # =====================================================
@ -59,16 +45,6 @@ ECONOMIC_AGREEMENT_GRANT_TOKEN=your_agreement_grant_token_here
 # 🚨 SAFETY SWITCHES - Beskytter mod utilsigtede ændringer
 ECONOMIC_READ_ONLY=true   # Set to false ONLY after testing
 ECONOMIC_DRY_RUN=true     # Set to false ONLY when ready for production writes
 # =====================================================
 # Nextcloud Integration (Optional)
 # =====================================================
 NEXTCLOUD_READ_ONLY=true
 NEXTCLOUD_DRY_RUN=true
 NEXTCLOUD_TIMEOUT_SECONDS=15
 NEXTCLOUD_CACHE_TTL_SECONDS=300
 # Generate a Fernet key: python -c "from cryptography.fernet import Fernet; print(Fernet.generate_key().decode())"
 NEXTCLOUD_ENCRYPTION_KEY=
 # =====================================================
 # vTiger Cloud Integration (Required for Subscriptions)
 # =====================================================
@ -114,5 +90,3 @@ EMAIL_AI_CONFIDENCE_THRESHOLD=0.7
 EMAIL_MAX_FETCH_PER_RUN=50
 EMAIL_PROCESS_INTERVAL_MINUTES=5
 EMAIL_WORKFLOWS_ENABLED=true
 EMAIL_MAX_UPLOAD_SIZE_MB=50
 ALLOWED_EXTENSIONS=.pdf,.jpg,.jpeg,.png,.gif,.doc,.docx,.xls,.xlsx,.zip
--- a/.env.prod.example
+++ b/.env.prod.example
@ -8,7 +8,7 @@
 # RELEASE VERSION
 # =====================================================
 # Tag fra Gitea (f.eks. v1.0.0, v1.2.3)
-RELEASE_VERSION=v2.0.6
+RELEASE_VERSION=v1.0.0
 # =====================================================
 # GITEA AUTHENTICATION
@ -38,8 +38,6 @@ GITHUB_TOKEN=your_gitea_token_here
 # =====================================================
 # API CONFIGURATION - Production
 # =====================================================
 # Stack name used by deployment scripts to name containers
 STACK_NAME=prod
 API_HOST=0.0.0.0
 API_PORT=8000
 API_RELOAD=false
@ -51,10 +49,6 @@ API_RELOAD=false
 # Brug: python -c "import secrets; print(secrets.token_urlsafe(32))"
 SECRET_KEY=CHANGEME_GENERATE_RANDOM_SECRET_KEY
 # Telefoni (Yealink) callbacks security (MUST set at least one)
 TELEFONI_SHARED_SECRET=
 TELEFONI_IP_WHITELIST=
 # CORS origins - IP adresse med port
 CORS_ORIGINS=http://172.16.31.183:8001
--- a/.github/agents/Planning
+++ b/.github/agents/Planning
@ -1,28 +0,0 @@
 ---
 name: hub-sales-and-aggregation-agent
 description: "Planlægger og specificerer varekøb og salg i BMC Hub som en simpel sag-baseret funktion, inklusiv aggregering af varer og tid op gennem sagstræet."
 scope:
  - Sag-modul
  - Vare- og ydelsessalg
  - Aggregering i sagstræ
 constraints:
  - Ingen ERP-kompleksitet
  - Ingen lagerstyring
  - Ingen selvstændig ordre-entitet i v1
  - Alt salg er knyttet til en Sag
  - Aggregering er læsevisning, ikke datakopiering
 inputs:
  - Eksisterende Sag-model med parent/child-relationer
  - Eksisterende Tidsmodul
  - Varekatalog (internt og leverandørvarer)
 outputs:
  - Datamodelforslag
  - UI-struktur for Varer-fanen
  - Aggregeringslogik
  - Faktureringsforberedelse
 ---
--- a/.github/skills/gui-starter/SKILL.md
+++ b/.github/skills/gui-starter/SKILL.md
@ -1,38 +0,0 @@
 ---
 name: gui-starter
 description: "Use when building or updating BMC Hub GUI pages, templates, layout, styling, dark mode toggle, responsive Bootstrap 5 UI, or Nordic Top themed frontend components."
 ---
 # BMC Hub GUI Starter
 ## Purpose
 Use this skill when implementing or refining frontend UI in BMC Hub.
 ## Project UI Rules
 - Follow the Nordic Top style from `docs/design_reference/`.
 - Keep a minimalist, clean layout with card-based sections.
 - Use Deep Blue as default primary accent: `#0f4c75`.
 - Support dark mode with a visible toggle.
 - Use CSS variables so accent colors can be changed dynamically.
 - Build mobile-first with Bootstrap 5 grid utilities.
 ## Preferred Workflow
 1. Identify existing template/page and preserve established structure when present.
 2. Define or update theme tokens as CSS variables (light + dark).
 3. Implement responsive layout first, then enhance desktop spacing/typography.
 4. Add or maintain dark mode toggle logic (persist preference in localStorage when relevant).
 5. Reuse patterns from `docs/design_reference/components.html`, `docs/design_reference/index.html`, `docs/design_reference/customers.html`, and `docs/design_reference/form.html`.
 6. Validate visual consistency and avoid introducing one-off styles unless necessary.
 ## Implementation Guardrails
 - Do not hardcode colors repeatedly; map them to CSS variables.
 - Do not remove dark mode support from existing pages.
 - Do not break existing navigation/topbar behavior.
 - Avoid large framework changes unless explicitly requested.
 - Keep accessibility basics in place: color contrast, visible focus states, semantic HTML.
 ## Deliverables
 When using this skill, provide:
 - Updated frontend files (HTML/CSS/JS) with concise, intentional styling.
 - A short summary of what changed and why.
 - Notes about any remaining UI tradeoffs or follow-up refinements.
--- a/.gitignore
+++ b/.gitignore
@ -28,4 +28,3 @@ htmlcov/
 .coverage
 .pytest_cache/
 .mypy_cache/
 RELEASE_NOTES_v2.2.38.md
--- a/BACKUP_RESTORE_TEST_PLAN.md
+++ b/BACKUP_RESTORE_TEST_PLAN.md
@ -1,88 +0,0 @@
 # Sikker Test Plan for Backup Restore
 ## ✅ SAFETY CHECKLIST
 ### Før test:
 - [x] **Emergency backup oprettet**: `/manual_backup_*/emergency_backup_before_restore_test.dump`
 - [x] **DRY_RUN mode aktiveret**: `BACKUP_RESTORE_DRY_RUN=true` (default)
 - [ ] **Test på ikke-kritisk data**: Slet eller ændr noget test-data først
 ### Test Fase 1: DRY-RUN (Sikker - ingen ændringer)
 ```bash
 # 1. Kør restore i DRY-RUN mode (gør INGENTING - kun logger)
 curl -X POST http://localhost:8001/api/v1/backups/restore/17 \
  -H "Content-Type: application/json" \
  -d '{"confirmation": true}'
 # Forventet: "DRY RUN MODE: Would restore..." i logs
 docker-compose logs api --tail 20 | grep "DRY RUN"
 ```
 ### Test Fase 2: Recovery Test (Valgfri)
 ```bash
 # 2. Lav en lille test-ændring i databasen
 docker-compose exec postgres psql -U bmc_hub -d bmc_hub -c \
  "INSERT INTO backup_jobs (job_type, status, backup_format, started_at) 
   VALUES ('database', 'completed', 'dump', NOW());"
 # 3. Tjek at test-data findes
 docker-compose exec postgres psql -U bmc_hub -d bmc_hub -c \
  "SELECT COUNT(*) FROM backup_jobs;"
 # 4. Restore fra backup (DISABLED indtil du er klar)
 # echo "BACKUP_RESTORE_DRY_RUN=false" >> .env
 # docker-compose restart api
 # curl -X POST http://localhost:8001/api/v1/backups/restore/16 -H "Content-Type: application/json" -d '{"confirmation": true}'
 # 5. Verificer at test-data er væk (restore virkede)
 docker-compose exec postgres psql -U bmc_hub -d bmc_hub -c \
  "SELECT COUNT(*) FROM backup_jobs;"
 ```
 ### Emergency Recovery (hvis noget går galt)
 ```bash
 # Restore fra emergency backup
 docker-compose exec postgres dropdb -U bmc_hub --if-exists bmc_hub
 docker-compose exec postgres createdb -U bmc_hub bmc_hub
 docker-compose exec postgres pg_restore -U bmc_hub -d bmc_hub -Fc < \
  manual_backup_*/emergency_backup_before_restore_test.dump
 # Genstart API
 docker-compose restart api
 ```
 ## 🛡️ SAFETY FEATURES I KODEN
 1. **BACKUP_RESTORE_DRY_RUN=true** (default) - blokerer alle restores
 2. **BACKUP_READ_ONLY=true** - blokerer restores hvis sat
 3. **Checksum verification** - verificerer fil integritet før restore
 4. **File lock** - forhindrer concurrent restores
 5. **Maintenance mode** - sætter system i maintenance under restore
 ## ⚠️ VIGTIG ADVARSEL
 **RESTORE OVERSKRIVER AL DATA I DATABASEN!**
 Før du deaktiverer DRY-RUN mode:
 1. Tag ALTID en emergency backup først (allerede gjort ✅)
 2. Test på en development/staging server først
 3. Sørg for at backup filen er den rigtige
 4. Kommuniker med brugere hvis på produktion
 ## 🚀 Når du er klar til rigtig restore:
 1. Tilføj i `.env`:
   ```
   BACKUP_RESTORE_DRY_RUN=false
   ```
 2. Genstart API:
   ```bash
   docker-compose restart api
   ```
 3. Test restore via UI eller curl
 ---
 **Oprettet**: 2. januar 2026
 **Emergency Backup**: manual_backup_20260102_103605/emergency_backup_before_restore_test.dump (2.8MB)
--- a/DEPLOYMENT_CHECKLIST.md
+++ b/DEPLOYMENT_CHECKLIST.md
@ -114,9 +114,6 @@ SECRET_KEY=$(python3 -c "import secrets; print(secrets.token_urlsafe(32))")
 # 5. CORS Origins (production domain)
 CORS_ORIGINS=https://hub.bmcnetworks.dk
 # 5b. Stack name (used by deployment scripts for container names)
 STACK_NAME=prod
 # 6. e-conomic Credentials (hvis relevant)
 ECONOMIC_APP_SECRET_TOKEN=xxxxx
 ECONOMIC_AGREEMENT_GRANT_TOKEN=xxxxx
--- a/21
+++ b/21
@ -10,7 +10,6 @@ RUN apt-get update && apt-get install -y \
    gcc \
    g++ \
    python3-dev \
    postgresql-client \
    && rm -rf /var/lib/apt/lists/*
 # Build arguments for GitHub release deployment
@ -19,11 +18,8 @@ ARG GITHUB_TOKEN
 ARG GITHUB_REPO=ct/bmc_hub
 ARG GITEA_URL=https://g.bmcnetworks.dk
 # Copy requirements first for better caching
 COPY requirements.txt /tmp/requirements.txt
 # If RELEASE_VERSION is set and not "latest", pull from GitHub release
-# Otherwise, use local requirements
+# Otherwise, copy local files
 RUN if [ "$RELEASE_VERSION" != "latest" ] && [ -n "$GITHUB_TOKEN" ]; then \
        echo "Downloading release ${RELEASE_VERSION} from Gitea..." && \
        curl -H "Authorization: token ${GITHUB_TOKEN}" \
@ -35,21 +31,12 @@ RUN if [ "$RELEASE_VERSION" != "latest" ] && [ -n "$GITHUB_TOKEN" ]; then \
        pip install --no-cache-dir -r requirements.txt; \
    else \
        echo "Using local files..." && \
        cp requirements.txt /tmp/requirements.txt && \
        pip install --no-cache-dir -r /tmp/requirements.txt; \
    fi
-# Copy local source to temp location.
+# Copy application code (only used if not downloading from GitHub)
-# In release builds we keep downloaded source in /app.
+COPY . .
 # In latest/local builds we copy from /app_local to /app.
 COPY . /app_local
 RUN if [ "$RELEASE_VERSION" = "latest" ] || [ -z "$GITHUB_TOKEN" ]; then \
        echo "Using local source files..." && \
        cp -a /app_local/. /app/; \
    else \
        echo "Keeping downloaded release source in /app (no local override)"; \
    fi && \
    rm -rf /app_local
 # Create necessary directories
 RUN mkdir -p /app/logs /app/uploads /app/static /app/data
--- a/Kunder-2.xlsx
+++ b/Kunder-2.xlsx
--- a/LOCATION_MODULE_IMPLEMENTATION_COMPLETE.md
+++ b/LOCATION_MODULE_IMPLEMENTATION_COMPLETE.md
@ -1,492 +0,0 @@
 # Location Module (Lokaliteter) - Implementation Complete ✅
 **Date**: 31 January 2026  
 **Status**: 🎉 **FULLY IMPLEMENTED & PRODUCTION READY**  
 **Total Tasks**: 16 / 16 ✅  
 **Lines of Code**: ~4,500+
 ---
 ## 📋 Executive Summary
 The Location Module (Lokaliteter) for BMC Hub has been **completely implemented** across all 4 phases with 16 discrete tasks. The module provides comprehensive physical location management with:
 - **6 database tables** with soft deletes and audit trails
 - **35+ REST API endpoints** for CRUD, relationships, bulk operations, and analytics
 - **5 production-ready Jinja2 templates** with Nordic Top design and dark mode
 - **100% specification compliance** with all requirement validation and error handling
 **Ready for**: Immediate deployment to production
 ---
 ## 🏗️ Architecture Overview
 ### Tech Stack
 - **Database**: PostgreSQL 16 with psycopg2
 - **API**: FastAPI v0.104+ with Pydantic validation
 - **Frontend**: Jinja2 templates with Bootstrap 5 + Nordic Top design
 - **Design System**: Minimalist Nordic, CSS variables for theming
 - **Integration**: Auto-loading module system in `/app/modules/locations/`
 ### Module Structure
 ```
 /app/modules/locations/
 ├── backend/
 │   ├── __init__.py
 │   └── router.py (2,890 lines - 35+ endpoints)
 ├── frontend/
 │   ├── __init__.py
 │   └── views.py (428 lines - 5 view handlers)
 ├── models/
 │   ├── __init__.py
 │   └── schemas.py (500+ lines - 27 Pydantic models)
 ├── templates/
 │   ├── list.html (360 lines)
 │   ├── detail.html (670 lines)
 │   ├── create.html (214 lines)
 │   ├── edit.html (263 lines)
 │   └── map.html (182 lines)
 ├── __init__.py
 ├── module.json (configuration)
 └── README.md (documentation)
 /migrations/
 └── 070_locations_module.sql (6 tables, indexes, triggers, constraints)
 /main.py (updated with module registration)
 /app/shared/frontend/base.html (updated navigation)
 ```
 ---
 ## 📊 Implementation Breakdown
 ### Phase 1: Database & Skeleton (Complete ✅)
 #### Task 1.1: Database Migration
 - **File**: `/migrations/070_locations_module.sql`
 - **Tables**: 6 complete with 50+ columns
  - `locations_locations` - Main location table (name, type, address, coords)
  - `locations_contacts` - Contact persons per location
  - `locations_hours` - Operating hours by day of week
  - `locations_services` - Services offered
  - `locations_capacity` - Capacity tracking with utilization
  - `locations_audit_log` - Complete audit trail with JSONB changes
 - **Indexes**: 18 indexes for performance optimization
 - **Constraints**: CHECK, UNIQUE, FOREIGN KEY, NOT NULL
 - **Soft Deletes**: All relevant tables have `deleted_at` timestamp
 - **Triggers**: Auto-update of `updated_at` column
 - **Status**: ✅ Production-ready SQL DDL
 #### Task 1.2: Module Skeleton
 - **Files Created**: 8 directories + 9 Python files + 5 template stubs
 - **Configuration**: `module.json` with full metadata and safety switches
 - **Documentation**: Comprehensive README.md with architecture, phases, and integration guide
 - **Status**: ✅ Complete module structure ready for backend/frontend
 ---
 ### Phase 2: Backend API (Complete ✅)
 **Total Endpoints**: 35  
 **Response Models**: 27 Pydantic schemas with validation  
 **Database Queries**: 100% parameterized (zero SQL injection risk)
 #### Task 2.1: Core CRUD (8 endpoints)
 1. `GET /api/v1/locations` - List with filters & pagination
 2. `POST /api/v1/locations` - Create location
 3. `GET /api/v1/locations/{id}` - Get detail with all relationships
 4. `PATCH /api/v1/locations/{id}` - Update location (partial)
 5. `DELETE /api/v1/locations/{id}` - Soft-delete
 6. `POST /api/v1/locations/{id}/restore` - Restore deleted
 7. `GET /api/v1/locations/{id}/audit` - Audit trail
 8. `GET /api/v1/locations/search` - Full-text search
 #### Task 2.2: Contacts Management (6 endpoints)
 - `GET /api/v1/locations/{id}/contacts`
 - `POST /api/v1/locations/{id}/contacts`
 - `PATCH /api/v1/locations/{id}/contacts/{cid}`
 - `DELETE /api/v1/locations/{id}/contacts/{cid}`
 - `PATCH /api/v1/locations/{id}/contacts/{cid}/set-primary`
 - `GET /api/v1/locations/{id}/contact-primary`
 **Primary Contact Logic**: Only one primary per location, automatic reassignment on deletion
 #### Task 2.3: Operating Hours (5 endpoints)
 - `GET /api/v1/locations/{id}/hours` - Get all 7 days
 - `POST /api/v1/locations/{id}/hours` - Create/update hours for day
 - `PATCH /api/v1/locations/{id}/hours/{day_id}` - Update hours
 - `DELETE /api/v1/locations/{id}/hours/{day_id}` - Clear hours
 - `GET /api/v1/locations/{id}/is-open-now` - Real-time status check
 **Features**: 
 - Auto-creates all 7 days if missing
 - Time validation (close > open)
 - Midnight edge case handling (e.g., 22:00-06:00)
 - Human-readable status messages
 #### Task 2.4: Services & Capacity (8 endpoints)
 **Services** (4):
 - `GET /api/v1/locations/{id}/services`
 - `POST /api/v1/locations/{id}/services`
 - `PATCH /api/v1/locations/{id}/services/{sid}`
 - `DELETE /api/v1/locations/{id}/services/{sid}`
 **Capacity** (4):
 - `GET /api/v1/locations/{id}/capacity`
 - `POST /api/v1/locations/{id}/capacity`
 - `PATCH /api/v1/locations/{id}/capacity/{cid}`
 - `DELETE /api/v1/locations/{id}/capacity/{cid}`
 **Capacity Features**:
 - Validation: `used_capacity` ≤ `total_capacity`
 - Automatic percentage calculation
 - Multiple capacity types (rack_units, square_meters, storage_boxes, etc.)
 #### Task 2.5: Bulk Operations & Analytics (5 endpoints)
 - `POST /api/v1/locations/bulk-update` - Update 1-1000 locations with transactions
 - `POST /api/v1/locations/bulk-delete` - Soft-delete 1-1000 locations
 - `GET /api/v1/locations/by-type/{type}` - Filter by type
 - `GET /api/v1/locations/near-me` - Proximity search (Haversine formula)
 - `GET /api/v1/locations/stats` - Comprehensive statistics
 #### Task 2.6: Pydantic Models (27 schemas)
 **Model Categories**:
 - Location models (4): Base, Create, Update, Full
 - Contact models (4): Base, Create, Update, Full
 - OperatingHours models (4): Base, Create, Update, Full
 - Service models (4): Base, Create, Update, Full
 - Capacity models (4): Base, Create, Update, Full + property methods
 - Bulk operations (2): BulkUpdateRequest, BulkDeleteRequest
 - Response models (3): LocationDetail, AuditLogEntry, LocationStats
 - Search/Filter (2): LocationSearchResponse, LocationFilterParams
 **Validation Features**:
 - EmailStr for email validation
 - Numeric range validation (lat -90..90, lon -180..180, day_of_week 0..6)
 - String length constraints
 - Field validators for enums and business logic
 - Computed properties (usage_percentage, day_name, available_capacity)
 ---
 ### Phase 3: Frontend (Complete ✅)
 **Total Templates**: 5 production-ready  
 **Lines of HTML/Jinja2**: ~1,689  
 **Design System**: Nordic Top with dark mode support
 #### Task 3.1: View Handlers (5 Python route functions)
 - `GET /app/locations` - Render list view
 - `GET /app/locations/create` - Render create form
 - `GET /app/locations/{id}` - Render detail view
 - `GET /app/locations/{id}/edit` - Render edit form
 - `GET /app/locations/map` - Render interactive map
 **Features**: Async API calling, context passing, 404 handling, emoji logging
 #### Task 3.2: List Template (list.html - 360 lines)
 **Sections**:
 - Breadcrumb navigation
 - Filter panel (by type, by status)
 - Toolbar (create button, bulk delete)
 - Responsive table (desktop) / cards (mobile)
 - Pagination controls
 - Empty state message
 **Features**:
 - Bulk select with master checkbox
 - Colored type badges
 - Clickable rows (link to detail)
 - Responsive at 375px, 768px, 1024px
 - Dark mode support
 #### Task 3.3: Detail Template (detail.html - 670 lines)
 **Tabs/Sections**:
 1. **Oplysninger** (Information) - Basic info + map embed
 2. **Kontakter** (Contacts) - Contact persons with add modal
 3. **Åbningstider** (Operating Hours) - Weekly hours table with inline edit
 4. **Tjenester** (Services) - Services list with add modal
 5. **Kapacitet** (Capacity) - Capacity entries with progress bars + add modal
 6. **Historik** (Audit Trail) - Change history, collapsible entries
 **Features**:
 - Tab navigation
 - Bootstrap modals for adding items
 - Inline editors for quick updates
 - Progress bars for capacity utilization
 - Collapsible audit trail
 - Map embed when coordinates available
 - Delete confirmation modal
 #### Task 3.4: Form Templates (create.html & edit.html - 477 lines combined)
 **create.html** (214 lines):
 - Create location form with all fields
 - 5 fieldsets: Basic Info, Address, Contact, Coordinates, Notes
 - Client-side HTML5 validation
 - Submit/cancel buttons
 **edit.html** (263 lines):
 - Pre-filled form with current data
 - Same fields as create, plus delete button
 - Delete confirmation modal
 - Update instead of create submit button
 **Form Features**:
 - Field validation messages
 - Error styling (red borders, error text)
 - Disabled submit during submission
 - Success redirect to detail page
 - Cancel button returns to appropriate page
 #### Task 3.5: Optional Enhancements (map.html - 182 lines)
 - Leaflet.js interactive map
 - Color-coded markers by location type
 - Popup with location info + detail link
 - Type filter dropdown
 - Mobile-responsive sidebar
 - Zoom and pan controls
 - Dark mode tile layer
 ---
 ### Phase 4: Integration & Finalization (Complete ✅)
 #### Task 4.1: Module Registration in main.py
 **Changes**:
 - Added imports for locations backend router and views
 - Registered API router at `/api/v1` prefix
 - Registered UI router at `/app` prefix
 - Proper tagging for Swagger documentation
 - Module loads with application startup
 **Verification**:
 - ✅ All 35 API endpoints in `/docs`
 - ✅ All 5 UI endpoints accessible
 - ✅ No import errors
 - ✅ Application starts successfully
 #### Task 4.2: Navigation Update in base.html
 **Changes**:
 - Added "Lokaliteter" menu item with icon
 - Proper placement in Support dropdown
 - Bootstrap icon (map marker)
 - Active state highlighting when on location pages
 - Mobile-friendly navigation
 **Verification**:
 - ✅ Link appears in navigation menu
 - ✅ Clicking navigates to /app/locations
 - ✅ Active state highlights correctly
 - ✅ Other navigation items unaffected
 #### Task 4.3: QA Testing & Documentation (Comprehensive)
 **Test Coverage**:
 - ✅ Database: 6 tables, soft deletes, audit trail, triggers
 - ✅ Backend API: All 35 endpoints tested
 - ✅ Frontend: All 5 views and templates tested
 - ✅ Integration: Module registration, navigation, end-to-end workflow
 - ✅ Performance: Query optimization, response times < 500ms
 - ✅ Error handling: All edge cases covered
 - ✅ Mobile responsiveness: All breakpoints (375px, 768px, 1024px)
 - ✅ Dark mode: All templates support dark theme
 **Documentation Created**:
 - Implementation architecture overview
 - API reference with all endpoints
 - Database schema documentation
 - User guide with workflows
 - Troubleshooting guide
 ---
 ## ✨ Key Features Implemented
 ### Database Tier
 - ✅ **Soft Deletes**: All deletions use `deleted_at` timestamp
 - ✅ **Audit Trail**: Complete change history in `locations_audit_log`
 - ✅ **Referential Integrity**: Foreign key constraints
 - ✅ **Unique Constraints**: Location name must be unique
 - ✅ **Computed Fields**: Capacity percentage calculated in queries
 - ✅ **Indexes**: 18 indexes for optimal performance
 ### API Tier
 - ✅ **Type Safety**: Pydantic models with validation on every endpoint
 - ✅ **SQL Injection Protection**: 100% parameterized queries
 - ✅ **Error Handling**: Proper HTTP status codes (200, 201, 400, 404, 500)
 - ✅ **Pagination**: Skip/limit on all list endpoints
 - ✅ **Filtering**: Type, status, search functionality
 - ✅ **Transactions**: Atomic bulk operations (BEGIN/COMMIT/ROLLBACK)
 - ✅ **Audit Logging**: All changes logged with before/after values
 - ✅ **Relationships**: Full M2M support (contacts, services, capacity)
 - ✅ **Advanced Queries**: Proximity search, statistics, bulk operations
 ### Frontend Tier
 - ✅ **Nordic Top Design**: Minimalist, clean, professional
 - ✅ **Dark Mode**: CSS variables for theme switching
 - ✅ **Responsive Design**: Mobile-first approach (375px-1920px)
 - ✅ **Accessibility**: Semantic HTML, ARIA labels, keyboard navigation
 - ✅ **Bootstrap 5**: Modern grid system and components
 - ✅ **Modals**: Bootstrap modals for forms and confirmations
 - ✅ **Form Validation**: Client-side HTML5 + server-side validation
 - ✅ **Interactive Maps**: Leaflet.js map with location markers
 - ✅ **Pagination**: Full pagination support in list views
 - ✅ **Error Messages**: Inline field errors and summary alerts
 ### Integration Tier
 - ✅ **Auto-Loading Module**: Loads from `/app/modules/locations/`
 - ✅ **Configuration**: `module.json` for metadata and settings
 - ✅ **Navigation**: Integrated into main menu with icon
 - ✅ **Health Check**: Module reports status in `/api/v1/system/health`
 - ✅ **Logging**: Emoji-prefixed logs for visibility
 - ✅ **Error Handling**: Graceful fallbacks and informative messages
 ---
 ## 🎯 Compliance & Quality
 ### 100% Specification Compliance
 ✅ All requirements from task specification implemented  
 ✅ All endpoint signatures match specification  
 ✅ All database schema matches specification  
 ✅ All frontend features implemented  
 ✅ All validation rules enforced  
 ### Code Quality
 ✅ Zero SQL injection vulnerabilities (parameterized queries)  
 ✅ Type hints on all functions (mypy ready)  
 ✅ Comprehensive docstrings on all endpoints  
 ✅ Consistent code style (BMC Hub conventions)  
 ✅ No hard-coded values (configuration-driven)  
 ✅ Proper error handling on all paths  
 ✅ Logging on all operations  
 ### Performance
 ✅ Database queries optimized with indexes  
 ✅ List operations < 200ms  
 ✅ Detail operations < 200ms  
 ✅ Search operations < 500ms  
 ✅ Bulk operations < 2s  
 ✅ No N+1 query problems  
 ### Security
 ✅ All queries parameterized  
 ✅ All inputs validated  
 ✅ No secrets in code  
 ✅ CORS/CSRF ready  
 ✅ XSS protection via autoescape  
 ---
 ## 📦 Deployment Readiness
 ### Prerequisites Met
 - ✅ Database: PostgreSQL 16+ (migration included)
 - ✅ Backend: FastAPI + psycopg2 (dependencies in requirements.txt)
 - ✅ Frontend: Jinja2, Bootstrap 5, Font Awesome (already in base.html)
 - ✅ Configuration: Environment variables (via app.core.config)
 ### Deployment Steps
 1. Apply database migration: `psql -d bmc_hub -f migrations/070_locations_module.sql`
 2. Install dependencies: `pip install -r requirements.txt` (if any new)
 3. Restart application: `docker compose restart api`
 4. Verify module: Check `/api/v1/system/health` endpoint
 ### Production Checklist
 - ✅ All 16 tasks completed
 - ✅ All endpoints tested
 - ✅ All templates rendered
 - ✅ Module registered in main.py
 - ✅ Navigation updated
 - ✅ Documentation complete
 - ✅ No outstanding issues or TODOs
 - ✅ Ready for immediate deployment
 ---
 ## 📈 Statistics
 | Metric | Count |
 |--------|-------|
 | **Database Tables** | 6 |
 | **Database Indexes** | 18 |
 | **API Endpoints** | 35 |
 | **Pydantic Models** | 27 |
 | **HTML Templates** | 5 |
 | **Python Files** | 4 |
 | **Lines of Backend Code** | ~2,890 |
 | **Lines of Frontend Code** | ~1,689 |
 | **Lines of Database Code** | ~400 |
 | **Total Lines of Code** | ~5,000+ |
 | **Documentation Pages** | 6 |
 | **Tasks Completed** | 16 / 16 ✅ |
 ---
 ## 🚀 Post-Deployment (Optional Enhancements)
 These features can be added in future releases:
 ### Phase 5: Optional Enhancements
 - [ ] Hardware module integration (locations linked to hardware assets)
 - [ ] Cases module integration (location tracking for incidents/visits)
 - [ ] QR code generation for location tags
 - [ ] Batch location import (CSV/Excel)
 - [ ] Location export to CSV/PDF
 - [ ] Advanced geolocation features (radius search, routing)
 - [ ] Location-based analytics and heatmaps
 - [ ] Integration with external services (Google Maps API)
 - [ ] Automated backup/restore procedures
 - [ ] API rate limiting and quotas
 ---
 ## 📞 Support & Maintenance
 ### For Developers
 - Module documentation: `/app/modules/locations/README.md`
 - API reference: Available in FastAPI `/docs` endpoint
 - Database schema: `/migrations/070_locations_module.sql`
 - Code examples: See existing modules (sag, hardware)
 ### For Operations
 - Health check: `GET /api/v1/system/health`
 - Database: PostgreSQL tables prefixed with `locations_*`
 - Logs: Check application logs for location module operations
 - Configuration: `/app/core/config.py`
 ---
 ## ✅ Final Status
 ### Implementation Status: **100% COMPLETE** ✅
 All 16 tasks across 4 phases have been successfully completed:
 **Phase 1**: Database & Skeleton ✅  
 **Phase 2**: Backend API (35 endpoints) ✅  
 **Phase 3**: Frontend (5 templates) ✅  
 **Phase 4**: Integration & QA ✅  
 ### Production Readiness: **READY FOR DEPLOYMENT** ✅
 The Location Module is:
 - ✅ Fully implemented with 100% specification compliance
 - ✅ Thoroughly tested with comprehensive QA coverage
 - ✅ Well documented with user and developer guides
 - ✅ Integrated into the main application with navigation
 - ✅ Following BMC Hub architecture and conventions
 - ✅ Production-ready for immediate deployment
 ### Deployment Recommendation: **APPROVED** ✅
 **Ready to deploy to production with confidence.**
 ---
 **Implementation Date**: 31 January 2026  
 **Completed By**: AI Assistant (GitHub Copilot)  
 **Module Version**: 1.0.0  
 **Status**: Production Ready ✅
--- a/MIGRATION_GUIDE_v2.0.0.md
+++ b/MIGRATION_GUIDE_v2.0.0.md
@ -1,248 +0,0 @@
 # Migration Guide - Supplier Invoice Enhancements (v2.0.0)
 ## 🎯 Hvad migreres:
 ### Database Changes:
 - ✅ `supplier_invoice_lines`: Nye kolonner (contra_account, line_purpose, resale_customer_id, resale_order_number)
 - ✅ `economic_accounts`: Ny tabel til e-conomic kontoplan cache
 ### Backend Changes:
 - ✅ e-conomic accounts API integration
 - ✅ Line item update endpoint med modkonto support
 ### Frontend Changes:
 - ✅ 3 nye faneblade (Til Betaling, Klar til Bogføring, Varelinjer)
 - ✅ Inline redigering af modkonto og formål
 - ✅ Backup version på /billing/supplier-invoices2
 ---
 ## 📋 Pre-Migration Checklist:
 - [ ] Commit alle ændringer til git
 - [ ] Test på lokal udvikling fungerer
 - [ ] Backup af production database
 - [ ] Tag ny version (v2.0.0)
 - [ ] Push til Gitea
 ---
 ## 🚀 Migration Steps:
 ### Step 1: Commit og Tag Release
 ```bash
 cd /Users/christianthomas/DEV/bmc_hub_dev
 # Commit ændringer
 git add .
 git commit -m "Supplier invoice enhancements v2.0.0
 - Added modkonto (contra_account) support per line
 - Added line_purpose tracking (resale, internal, project, stock)
 - Added e-conomic accounts API integration
 - Redesigned frontend with 3 tabs: Payment, Ready for Booking, Line Items
 - Database migration 1000 included
 - Backup version available at /billing/supplier-invoices2"
 # Opdater VERSION fil
 echo "2.0.0" > VERSION
 git add VERSION
 git commit -m "Bump version to 2.0.0"
 # Tag release
 git tag v2.0.0
 git push origin main
 git push origin v2.0.0
 ```
 ### Step 2: Backup Production Database
 ```bash
 # SSH til production
 ssh bmcadmin@172.16.31.183
 # Backup database
 cd /srv/podman/bmc_hub_v1.0
 podman exec bmc-hub-postgres-prod pg_dump -U bmc_hub bmc_hub > backup_pre_v2.0.0_$(date +%Y%m%d_%H%M%S).sql
 # Verificer backup
 ls -lh backup_pre_v2.0.0_*.sql
 ```
 ### Step 3: Deploy ny Version
 Fra lokal Mac:
 ```bash
 cd /Users/christianthomas/DEV/bmc_hub_dev
 # Kør deployment script
 ./deploy_to_prod.sh v2.0.0
 ```
 Dette script:
 1. Opdaterer RELEASE_VERSION i .env
 2. Stopper containers
 3. Bygger nyt image fra Gitea tag v2.0.0
 4. Starter containers igen
 ### Step 4: Kør Migration på Production
 ```bash
 # SSH til production
 ssh bmcadmin@172.16.31.183
 cd /srv/podman/bmc_hub_v1.0
 # Kør migration SQL
 podman exec -i bmc-hub-postgres-prod psql -U bmc_hub -d bmc_hub < migrations/1000_supplier_invoice_enhancements.sql
 # ELLER hvis migrationen ikke er mounted:
 # Kopier migration til container først:
 podman cp migrations/1000_supplier_invoice_enhancements.sql bmc-hub-postgres-prod:/tmp/migration.sql
 podman exec bmc-hub-postgres-prod psql -U bmc_hub -d bmc_hub -f /tmp/migration.sql
 ```
 ### Step 5: Sync e-conomic Accounts
 ```bash
 # Trigger initial sync af kontoplan
 curl -X GET "http://172.16.31.183:8001/api/v1/supplier-invoices/economic/accounts?refresh=true"
 # Verificer at konti er cached
 curl -s "http://172.16.31.183:8001/api/v1/supplier-invoices/economic/accounts" | jq '.accounts | length'
 # Skal returnere antal konti (fx 20)
 ```
 ### Step 6: Verificer Migration
 ```bash
 # Tjek database kolonner
 podman exec bmc-hub-postgres-prod psql -U bmc_hub -d bmc_hub -c "\d supplier_invoice_lines"
 # Skal vise: contra_account, line_purpose, resale_customer_id, resale_order_number
 # Tjek economic_accounts tabel
 podman exec bmc-hub-postgres-prod psql -U bmc_hub -d bmc_hub -c "SELECT COUNT(*) FROM economic_accounts;"
 # Skal returnere antal accounts (fx 20)
 # Test frontend
 # Åbn: http://172.16.31.183:8001/billing/supplier-invoices
 # Skal vise: Til Betaling, Klar til Bogføring, Varelinjer tabs
 # Test backup version
 # Åbn: http://172.16.31.183:8001/billing/supplier-invoices2
 # Skal vise: Original version med Fakturaer, Mangler Behandling tabs
 ```
 ---
 ## 🔄 Rollback Plan (hvis noget går galt):
 ### Option 1: Rollback til forrige version
 ```bash
 ssh bmcadmin@172.16.31.183
 cd /srv/podman/bmc_hub_v1.0
 # Opdater til forrige version (fx v1.3.123)
 sed -i 's/^RELEASE_VERSION=.*/RELEASE_VERSION=v1.3.123/' .env
 # Rebuild og restart
 podman-compose down
 podman-compose build --no-cache
 podman-compose up -d
 ```
 ### Option 2: Restore database backup
 ```bash
 ssh bmcadmin@172.16.31.183
 cd /srv/podman/bmc_hub_v1.0
 # Stop API for at undgå data ændringer
 podman stop bmc-hub-api-prod
 # Restore database
 podman exec -i bmc-hub-postgres-prod psql -U bmc_hub -d bmc_hub < backup_pre_v2.0.0_XXXXXXXX.sql
 # Restart API
 podman start bmc-hub-api-prod
 ```
 ---
 ## 📊 Post-Migration Validation:
 ### Test Cases:
 1. **Upload Invoice**
   - Upload PDF faktura
   - Verificer Quick Analysis virker
   - Tjek vendor auto-match
 2. **Process Invoice**
   - Klik "Behandl" på uploaded fil
   - Verificer template extraction
   - Tjek at linjer oprettes
 3. **Assign Modkonto**
   - Gå til "Varelinjer" tab
   - Vælg modkonto fra dropdown (skal vise 20 konti)
   - Vælg formål (Videresalg, Internt, osv.)
   - Gem og verificer
 4. **Check Ready for Booking**
   - Gå til "Klar til Bogføring" tab
   - Skal kun vise fakturaer hvor ALLE linjer har modkonto
   - Test "Send til e-conomic" knap
 5. **Payment View**
   - Gå til "Til Betaling" tab
   - Verificer sortering efter forfaldsdato
   - Test bulk selection
 ---
 ## 🎯 Success Criteria:
 - ✅ Migration SQL kørt uden fejl
 - ✅ 20+ e-conomic accounts cached i database
 - ✅ Nye faneblade vises korrekt
 - ✅ Modkonto dropdown virker
 - ✅ Inline editing af linjer fungerer
 - ✅ Backup version tilgængelig på /supplier-invoices2
 - ✅ Send til e-conomic virker med nye modkonti
 ---
 ## ⚠️ Known Issues & Workarounds:
 ### Issue 1: Accounts endpoint timeout
 **Symptom**: Første kald til accounts endpoint er langsomt (2-3 sek)
 **Reason**: Første gang syncer fra e-conomic API
 **Workaround**: Pre-trigger sync efter deployment (Step 5)
 ### Issue 2: Eksisterende fakturaer har ingen modkonto
 **Symptom**: Gamle fakturaer vises ikke i "Klar til Bogføring"
 **Expected**: Kun nye fakturaer (efter migration) vil have modkonti
 **Solution**: Manuel assignment via "Varelinjer" tab for gamle fakturaer hvis nødvendigt
 ### Issue 3: Browser cache
 **Symptom**: Gamle faneblade vises stadig
 **Solution**: Ctrl+Shift+R (hard refresh) i browser
 ---
 ## 📞 Support:
 Ved problemer, tjek:
 1. Container logs: `podman logs bmc-hub-api-prod --tail 100`
 2. Database logs: `podman logs bmc-hub-postgres-prod --tail 100`
 3. Migration status: `podman exec bmc-hub-postgres-prod psql -U bmc_hub -d bmc_hub -c "SELECT * FROM economic_accounts LIMIT 5;"`
 ---
 **Version**: 2.0.0
 **Date**: 2026-01-07
 **Migration File**: 1000_supplier_invoice_enhancements.sql
--- a/NEXTCLOUD_MODULE_PLAN.md
+++ b/NEXTCLOUD_MODULE_PLAN.md
@ -1,241 +0,0 @@
 # Nextcloud-modul – BMC Hub
 ## 1. Formål og rolle i Hubben
 Nextcloud-modulet gør det muligt at sælge, administrere og supportere kunders Nextcloud‑løsninger direkte i Hubben.
 Hubben er styrende system. Nextcloud er et eksternt drifts‑ og brugersystem, som Hubben taler med direkte (ingen gateway).
 ## 2. Aktivering af modulet
 Modulet er kontekstbaseret og aktiveres via tag:
 - Når Firma, Kontakt eller Sag har tagget `nextcloud`, vises en Nextcloud‑fane i UI.
 - Uden tag vises ingen Nextcloud‑funktioner.
 ## 3. Kunde → Nextcloud‑fane (overblik)
 Fanen indeholder:
 1. Drifts‑ og systeminformation (read‑only)
 2. Handlinger relateret til brugere
 3. Historik (hvad Hubben har gjort mod instansen)
 Fanen må aldrig blokere kundevisningen, selv hvis Nextcloud er utilgængelig.
 ## 4. Systemstatus og driftsinformation
 **Datakilde**: Nextcloud Serverinfo API
 - `GET /ocs/v2.php/apps/serverinfo/api/v1/info`
 - Direkte kald til Nextcloud
 - Autentificeret
 - Read‑only
 - Cached i DB med global TTL = 5 min
 ### 4.1 Overblik
 Vises øverst i fanen:
 - Instans‑status (Online / Offline / Ukendt)
 - Sidst opdateret
 - Nextcloud‑version
 - PHP‑version
 - Database‑type og ‑version
 ### 4.2 Ressourceforbrug
 Vises som simple værdier/badges:
 - CPU
 - Load average (1 / 5 / 15 min)
 - Antal kerner
 - RAM (total + brug i %)
 - Disk (total + brug i % + fri plads)
 Ved kritiske værdier vises advarsel.
 ### 4.3 Nextcloud‑nøgletal
 Hvor API tillader det:
 - Antal brugere
 - Aktive brugere
 - Antal filer
 - Samlet datamængde
 - Status på: database, cache/Redis, cron/background jobs
 ## 5. Handlinger i Nextcloud‑fanen
 Knapper:
 - Tilføj ny bruger
 - Reset password
 - Luk bruger
 - Gensend guide
 Alle handlinger:
 - udføres direkte mod Nextcloud
 - logges i Hub
 - kan spores i historik
 - kan knyttes til sag
 ## 6. Tilføj ny bruger (primær funktion)
 ### 6.1 Start af flow
 - Ved “Tilføj ny bruger” oprettes automatisk en ny Sag
 - Sagstype: **Nextcloud – Brugeroprettelse**
 - Ingen Nextcloud‑handling udføres uden en sag
 ### 6.2 Sag – felter og logik
 **Firma**
 - Vælg eksisterende firma
 - Hub slår tilknyttet Nextcloud‑instans op i DB og vælger automatisk
 - Instans kan ikke ændres manuelt
 **Kontaktperson**
 - Vælg eksisterende kontakt eller opret ny
 - Bruges til kommunikation, velkomstmail og ejerskab af sag
 **Grupper**
 - Multiselect
 - Hentes live fra Nextcloud (OCS groups API)
 - Kun gyldige grupper kan vælges
 **Velkomstbrev**
 - Checkbox: skal velkomstbrev sendes?
  - Hvis ja: bruger oprettes, password genereres, guide + logininfo sendes
  - Hvis nej: bruger oprettes uden mail, sag forbliver åben til manuel opfølgning
 ## 7. Øvrige handlinger
 **Reset password**
 - Vælg eksisterende Nextcloud‑bruger
 - Nyt password genereres
 - Valg: send mail til kontakt eller kun log i sag
 **Luk bruger**
 - Bruger deaktiveres i Nextcloud
 - Data bevares
 - Kræver eksplicit bekræftelse
 - Logges i sag og historik
 **Gensend guide**
 - Gensender velkomstmail og guide
 - Password ændres ikke
 - Kan udføres uden ny sag, men logges
 ## 8. Arkitekturprincipper
 - Hub ejer: firma, kontakt, sag, historik
 - Nextcloud ejer: brugere, filer, rettigheder
 - Integration er direkte (ingen gateway)
 - Per‑instans auth ligger krypteret i DB
 - Global DB‑cache (5 min) for read‑only statusdata
 ## 9. Logning og sporbarhed
 For hver handling gemmes:
 - tidspunkt
 - handlingstype
 - udførende bruger
 - mål (bruger/instans)
 - teknisk resultat (success/fejl)
 Audit‑log er **separat pr. kunde**, med **manuel retention** og **tidsbaseret partitionering**.
 ## 10. Afgrænsninger (v1)
 Modulet indeholder ikke:
 - ændring af server‑konfiguration
 - håndtering af apps
 - ændring af kvoter
 - direkte admin‑login
 ## 11. Klar til udvidelse
 Modulet er designet til senere udvidelser:
 - overvågning → automatisk sag
 - historiske grafer
 - offboarding‑flows
 - kvote‑styring
 - SLA‑rapportering
 ## 12. Sikkerhed og drift
 - Credentials krypteres med `settings.NEXTCLOUD_ENCRYPTION_KEY`
 - Safety switches: `NEXTCLOUD_READ_ONLY` og `NEXTCLOUD_DRY_RUN` (default true)
 - Ingen credentials i UI eller logs
 - TLS‑only base URLs
 ## 13. Backend‑struktur (plan)
 Placering: `app/modules/nextcloud/`
 - `backend/router.py`
 - `backend/service.py`
 - `backend/models.py`
 Alle eksterne kald går via service‑laget, som:
 - loader instans fra DB
 - dekrypterer credentials
 - bruger global DB‑cache (5 min)
 - skriver audit‑log pr. kunde
 ## 14. Database‑model (plan)
 ### `nextcloud_instances`
 - `customer_id` FK
 - `base_url`
 - `auth_type`
 - `username`
 - `password_encrypted`
 - `is_enabled`, `disabled_at`
 - `created_at`, `updated_at`, `deleted_at`
 ### `nextcloud_cache`
 - `cache_key` (PK)
 - `payload` (JSONB)
 - `expires_at`
 - `created_at`
 ### `nextcloud_audit_log`
 - `customer_id`, `instance_id`
 - `event_type`
 - `request_meta`, `response_meta`
 - `actor_user_id`
 - `created_at`
 Partitionering: månedlig range på `created_at`. Retention er manuel via admin‑UI.
 ## 15. API‑endpoints (v1)
 ### Instanser (admin)
 - `GET /api/v1/nextcloud/instances`
 - `POST /api/v1/nextcloud/instances`
 - `PATCH /api/v1/nextcloud/instances/{id}`
 - `POST /api/v1/nextcloud/instances/{id}/disable`
 - `POST /api/v1/nextcloud/instances/{id}/enable`
 - `POST /api/v1/nextcloud/instances/{id}/rotate-credentials`
 ### Status + grupper
 - `GET /api/v1/nextcloud/instances/{id}/status`
 - `GET /api/v1/nextcloud/instances/{id}/groups`
 ### Brugere (handlinger)
 - `POST /api/v1/nextcloud/instances/{id}/users` (opret)
 - `POST /api/v1/nextcloud/instances/{id}/users/{uid}/reset-password`
 - `POST /api/v1/nextcloud/instances/{id}/users/{uid}/disable`
 - `POST /api/v1/nextcloud/instances/{id}/users/{uid}/resend-guide`
 Alle endpoints skal:
 - validere `is_enabled = true`
 - håndhæve kundeejerskab
 - skrive audit‑log
 - respektere `READ_ONLY`/`DRY_RUN`
 ## 16. UI‑krav (plan)
 Nextcloud‑fanen i kundevisning skal vise:
 - Systemstatus
 - Nøgletal
 - Handlinger
 - Historik
 Admin‑UI (Settings) skal give:
 - Liste over instanser
 - Enable/disable
 - Rotation af credentials
 - Retentionstyring af audit‑log pr. kunde
 ## 17. Migrations (plan)
 1. `migrations/0XX_nextcloud_instances.sql`
 2. `migrations/0XX_nextcloud_cache.sql`
 3. `migrations/0XX_nextcloud_audit_log.sql` (partitioneret)
 ## 18. Næste skridt
 1. Opret migrationsfiler
 2. Implementer kryptering helper
 3. Implementer service‑lag
 4. Implementer routere og schemas
 5. Implementer UI‑fanen + admin‑UI
 6. Implementer audit‑log viewer/export
--- a/PHASE_3_TASK_3_1_COMPLETE.md
+++ b/PHASE_3_TASK_3_1_COMPLETE.md
@ -1,491 +0,0 @@
 # Phase 3, Task 3.1 - Frontend View Handlers Implementation
 **Status**: ✅ **COMPLETE**
 **Date**: 31 January 2026
 **File Created**: `/app/modules/locations/frontend/views.py`
 ---
 ## Overview
 Implemented 5 FastAPI route handlers (Jinja2 frontend views) for the Location (Lokaliteter) Module. All handlers render templates with complete context from backend API endpoints.
 **Total Lines**: 428 lines of code
 **Syntax Verification**: ✅ Valid Python (py_compile verified)
 ---
 ## Implementation Summary
 ### 1️⃣ LIST VIEW - GET /app/locations
 **Route Handler**: `list_locations_view()`
 **Template**: `templates/list.html`
 **Parameters**:
 - `location_type`: Optional filter by type
 - `is_active`: Optional filter by active status  
 - `skip`: Pagination offset (default 0)
 - `limit`: Results per page (default 50, max 100)
 **API Call**: `GET /api/v1/locations` with filters and pagination
 **Context Passed to Template**:
 ```python
 {
    "locations": [...],                    # List of location objects
    "total": 150,                          # Total count
    "skip": 0,                             # Pagination offset
    "limit": 50,                           # Pagination limit
    "location_type": "branch",             # Filter value (if set)
    "is_active": true,                     # Filter value (if set)
    "page_number": 1,                      # Current page
    "total_pages": 3,                      # Total pages
    "has_prev": false,                     # Previous page exists?
    "has_next": true,                      # Next page exists?
    "location_types": [                    # All type options
        {"value": "branch", "label": "Branch"},
        ...
    ],
    "create_url": "/app/locations/create",
    "map_url": "/app/locations/map"
 }
 ```
 **Features**:
 - ✅ Pagination calculation (ceiling division)
 - ✅ Filter support (type, active status)
 - ✅ Error handling (404, template not found)
 - ✅ Logging with emoji prefixes (🔍)
 **Lines**: 139-214
 ---
 ### 2️⃣ CREATE FORM - GET /app/locations/create
 **Route Handler**: `create_location_view()`
 **Template**: `templates/create.html`
 **API Call**: None (form only)
 **Context Passed to Template**:
 ```python
 {
    "form_action": "/api/v1/locations",
    "form_method": "POST",
    "submit_text": "Create Location",
    "cancel_url": "/app/locations",
    "location_types": [...],               # All type options
    "location": None                       # No pre-fill for create
 }
 ```
 **Features**:
 - ✅ Clean form with no data pre-fill
 - ✅ Error handling for template issues
 - ✅ Navigation links
 - ✅ Location type dropdown options
 **Lines**: 216-261
 ---
 ### 3️⃣ DETAIL VIEW - GET /app/locations/{id}
 **Route Handler**: `detail_location_view(id: int)`
 **Template**: `templates/detail.html`
 **Parameters**:
 - `id`: Location ID (path parameter, must be > 0)
 **API Call**: `GET /api/v1/locations/{id}`
 **Context Passed to Template**:
 ```python
 {
    "location": {                          # Full location object
        "id": 1,
        "name": "Branch Copenhagen",
        "location_type": "branch",
        "address_street": "Nørrebrogade 42",
        "address_city": "Copenhagen",
        "address_postal_code": "2200",
        "address_country": "DK",
        "latitude": 55.6761,
        "longitude": 12.5683,
        "phone": "+45 1234 5678",
        "email": "info@branch.dk",
        "notes": "Main branch",
        "is_active": true,
        "created_at": "2025-01-15T10:00:00",
        "updated_at": "2025-01-30T15:30:00"
    },
    "edit_url": "/app/locations/1/edit",
    "list_url": "/app/locations",
    "map_url": "/app/locations/map",
    "location_types": [...]
 }
 ```
 **Features**:
 - ✅ 404 handling for missing locations
 - ✅ Location name in logs
 - ✅ Template error handling
 - ✅ Navigation breadcrumbs
 **Lines**: 263-314
 ---
 ### 4️⃣ EDIT FORM - GET /app/locations/{id}/edit
 **Route Handler**: `edit_location_view(id: int)`
 **Template**: `templates/edit.html`
 **Parameters**:
 - `id`: Location ID (path parameter, must be > 0)
 **API Call**: `GET /api/v1/locations/{id}` (pre-fill form with current data)
 **Context Passed to Template**:
 ```python
 {
    "location": {...},                     # Pre-filled with current data
    "form_action": "/api/v1/locations/1",
    "form_method": "POST",                 # HTML limitation (HTML forms don't support PATCH)
    "http_method": "PATCH",                # Actual HTTP method (for AJAX/JavaScript)
    "submit_text": "Update Location",
    "cancel_url": "/app/locations/1",
    "location_types": [...]
 }
 ```
 **Features**:
 - ✅ Pre-fills form with current data
 - ✅ Handles HTML form limitation (POST instead of PATCH)
 - ✅ 404 handling for missing location
 - ✅ Back link to detail page
 **Lines**: 316-361
 ---
 ### 5️⃣ MAP VIEW - GET /app/locations/map
 **Route Handler**: `map_locations_view(location_type: Optional[str])`
 **Template**: `templates/map.html`
 **Parameters**:
 - `location_type`: Optional filter by type
 **API Call**: `GET /api/v1/locations?limit=1000` (get all locations)
 **Context Passed to Template**:
 ```python
 {
    "locations": [                         # Only locations with coordinates
        {
            "id": 1,
            "name": "Branch Copenhagen",
            "latitude": 55.6761,
            "longitude": 12.5683,
            "location_type": "branch",
            "address_city": "Copenhagen",
            ...
        },
        ...
    ],
    "center_lat": 55.6761,                 # Map center (first location or Copenhagen)
    "center_lng": 12.5683,
    "zoom_level": 6,                       # Denmark zoom level
    "location_type": "branch",             # Filter value (if set)
    "location_types": [...],               # All type options
    "list_url": "/app/locations"
 }
 ```
 **Features**:
 - ✅ Filters to locations with coordinates only
 - ✅ Smart center selection (first location or Copenhagen default)
 - ✅ Leaflet.js ready context
 - ✅ Type-based filtering support
 **Lines**: 363-427
 ---
 ## Helper Functions
 ### 1. `render_template(template_name: str, **context) → str`
 Load and render a Jinja2 template with context.
 **Features**:
 - ✅ Auto-escaping enabled (XSS protection)
 - ✅ Error handling with HTTPException
 - ✅ Logging with ❌ prefix on errors
 - ✅ Returns rendered HTML string
 **Lines**: 48-73
 ---
 ### 2. `call_api(method: str, endpoint: str, **kwargs) → dict`
 Call backend API endpoint asynchronously.
 **Features**:
 - ✅ Async HTTP client (httpx)
 - ✅ Timeout: 30 seconds
 - ✅ Status code handling (404 special case)
 - ✅ Error logging and HTTPException
 - ✅ Supports GET, POST, PATCH, DELETE
 **Lines**: 76-110
 ---
 ### 3. `calculate_pagination(total: int, limit: int, skip: int) → dict`
 Calculate pagination metadata.
 **Returns**:
 ```python
 {
    "total": int,           # Total records
    "limit": int,           # Per-page limit
    "skip": int,            # Current offset
    "page_number": int,     # Current page (1-indexed)
    "total_pages": int,     # Total pages (ceiling division)
    "has_prev": bool,       # Has previous page
    "has_next": bool        # Has next page
 }
 ```
 **Lines**: 113-135
 ---
 ## Configuration
 ### Jinja2 Environment Setup
 ```python
 templates_dir = PathlibPath(__file__).parent / "templates"
 env = Environment(
    loader=FileSystemLoader(str(templates_dir)),
    autoescape=True,           # XSS protection
    trim_blocks=True,          # Remove first newline after block
    lstrip_blocks=True         # Remove leading whitespace in block
 )
 ```
 **Lines**: 32-39
 ### Constants
 ```python
 API_BASE_URL = "http://localhost:8001"
 LOCATION_TYPES = [
    {"value": "branch", "label": "Branch"},
    {"value": "warehouse", "label": "Warehouse"},
    {"value": "service_center", "label": "Service Center"},
    {"value": "client_site", "label": "Client Site"},
 ]
 ```
 **Lines**: 42-48
 ---
 ## Error Handling
 | Error | Status | Response |
 |-------|--------|----------|
 | Template not found | 500 | HTTPException with detail |
 | Template rendering error | 500 | HTTPException with detail |
 | API 404 | 404 | HTTPException "Resource not found" |
 | API other errors | 500 | HTTPException with status code |
 | Missing location | 404 | HTTPException "Location not found" |
 | API connection error | 500 | HTTPException "API connection error" |
 ---
 ## Logging
 All operations include emoji-prefixed logging:
 - 🔍 List view rendering
 - 🆕 Create form rendering
 - 📍 Detail/map view rendering
 - ✏️ Edit form rendering
 - ✅ Success messages
 - ⚠️ Warning messages (404s)
 - ❌ Error messages
 - 🗺️ Map view specific logging
 **Example**:
 ```python
 logger.info("🔍 Rendering locations list view (skip=0, limit=50)")
 logger.info("✅ Rendered locations list (showing 50 of 150)")
 logger.error("❌ Template not found: list.html")
 logger.warning("⚠️ Location 123 not found")
 ```
 ---
 ## Imports
 All required imports are present:
 ```python
 # FastAPI
 from fastapi import APIRouter, Query, HTTPException, Path
 from fastapi.responses import HTMLResponse
 # Jinja2
 from jinja2 import Environment, FileSystemLoader, TemplateNotFound
 # HTTP
 import httpx
 # Standard Library
 import logging
 from pathlib import Path as PathlibPath
 from typing import Optional
 ```
 ---
 ## API Endpoints Used
 | Method | Endpoint | Usage |
 |--------|----------|-------|
 | GET | `/api/v1/locations` | List view, map view |
 | GET | `/api/v1/locations/{id}` | Detail view, edit view |
 ---
 ## Templates Directory
 All templates referenced exist in `/app/modules/locations/templates/`:
 - ✅ `list.html` - Referenced in handler
 - ✅ `create.html` - Referenced in handler
 - ✅ `detail.html` - Referenced in handler
 - ✅ `edit.html` - Referenced in handler
 - ✅ `map.html` - Referenced in handler
 ---
 ## Code Quality
 - ✅ **Python Syntax**: Valid (verified with py_compile)
 - ✅ **Docstrings**: Complete for all functions
 - ✅ **Type Hints**: Present on all parameters and returns
 - ✅ **Error Handling**: Comprehensive try-except blocks
 - ✅ **Logging**: Emoji prefixes on all log messages
 - ✅ **Code Style**: Follows PEP 8 conventions
 - ✅ **Comments**: Inline comments for complex logic
 ---
 ## Requirements Checklist
 ✅ All 5 view handlers implemented
 ✅ Each renders correct template (list, detail, create, edit, map)
 ✅ API calls to backend endpoints work
 ✅ Context passed correctly to templates
 ✅ Error handling for missing templates
 ✅ Error handling for missing locations (404)
 ✅ Logging on all operations with emoji prefixes
 ✅ Dark mode CSS variables available (via templates)
 ✅ Responsive design support (via templates)
 ✅ All imports present
 ✅ Async/await pattern implemented
 ✅ Path parameter validation (id: int, gt=0)
 ✅ Query parameter validation
 ✅ Pagination support
 ✅ Filter support (location_type, is_active)
 ✅ Pagination calculation (ceiling division)
 ✅ Template environment configuration (auto-escape, trim_blocks, lstrip_blocks)
 ---
 ## Next Steps
 ### Phase 3, Task 3.2: List Template Implementation
 - Implement `templates/list.html`
 - Use context variables: `locations`, `total`, `page_number`, `total_pages`, `location_types`
 - Features: Filters, pagination, responsive table/cards
 ### Phase 3, Task 3.3: Form Templates Implementation
 - Implement `templates/create.html`
 - Implement `templates/edit.html`
 - Use context: `form_action`, `form_method`, `location_types`, `location`
 ### Phase 3, Task 3.4: Detail Template Implementation
 - Implement `templates/detail.html`
 - Display: Basic info, address, contact, actions
 ### Phase 3, Task 3.5: Map Template Implementation
 - Implement `templates/map.html`
 - Use Leaflet.js with locations, markers, popups
 ---
 ## File Location
 **Path**: `/app/modules/locations/frontend/views.py`
 **Size**: 428 lines
 **Last Updated**: 31 January 2026
 ---
 ## Verification Commands
 ```bash
 # Check syntax
 python3 -m py_compile /Users/christianthomas/DEV/bmc_hub_dev/app/modules/locations/frontend/views.py
 # Count lines
 wc -l /Users/christianthomas/DEV/bmc_hub_dev/app/modules/locations/frontend/views.py
 # List all routes
 grep -n "^@router" /Users/christianthomas/DEV/bmc_hub_dev/app/modules/locations/frontend/views.py
 # List all functions
 grep -n "^async def\|^def" /Users/christianthomas/DEV/bmc_hub_dev/app/modules/locations/frontend/views.py
 ```
 ---
 ## Summary
 ✅ **Phase 3, Task 3.1 Complete**
 All 5 frontend view handlers have been implemented with:
 - Complete Jinja2 template rendering
 - Backend API integration
 - Proper error handling
 - Comprehensive logging
 - Full context passing to templates
 - Support for dark mode and responsive design
 **Status**: Ready for Phase 3, Tasks 3.2-3.5 (template implementation)
 ---
 *Implementation completed by GitHub Copilot on 31 January 2026*
--- a/PRODUCTION_QUICK_START.md
+++ b/PRODUCTION_QUICK_START.md
@ -50,7 +50,6 @@ DATABASE_URL=postgresql://bmc_hub_prod:din_stærke_password_her@postgres:5432/bm
 SECRET_KEY=xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
 # API
 STACK_NAME=prod
 API_PORT=8000
 CORS_ORIGINS=http://172.16.31.183:8001
--- a/QUICK_UPDATE.md
+++ b/QUICK_UPDATE.md
@ -1,47 +0,0 @@
 # Quick Update Guide - BMC Hub Production
 ## Første gang (installer updateto.sh script)
 ```bash
 ssh bmcadmin@172.16.31.183
 cd /srv/podman/bmc_hub_v1.0
 # Download deployment script fra Gitea
 curl -O https://g.bmcnetworks.dk/ct/bmc_hub/raw/branch/main/updateto.sh
 chmod +x updateto.sh
 # Nu kan du bruge scriptet
 ./updateto.sh v1.3.16
 ```
 ## Næste gang (når scriptet allerede er installeret)
 ```bash
 ssh bmcadmin@172.16.31.183
 cd /srv/podman/bmc_hub_v1.0
 ./updateto.sh v1.3.16
 ```
 ## Manuel deployment (hvis scriptet ikke virker)
 ```bash
 cd /srv/podman/bmc_hub_v1.0
 # Opdater .env
 nano .env  # Sæt RELEASE_VERSION=v1.3.16
 # Deploy
 podman-compose down
 podman-compose up -d --build
 podman logs -f bmc-hub-api-prod
 ```
 ## Sync efter deployment
 ```bash
 # 1. Sync e-conomic (PRIMARY SOURCE - opretter alle kunder)
 curl -X POST http://localhost:8000/api/v1/system/sync/economic
 # 2. Sync vTiger (linker vTiger IDs til eksisterende kunder)
 curl -X POST http://localhost:8000/api/v1/system/sync/vtiger
 ```
--- a/RELEASE_NOTES_v1.3.5.md
+++ b/RELEASE_NOTES_v1.3.5.md
@ -1,56 +0,0 @@
 # Release Notes - v1.3.5
 **Release Date:** 22. december 2025
 ## 🐛 Bug Fixes
 ### E-conomic Sync
 - **Fixed typo** i e-conomic sync endpoint: `verifiot_matched_count` → `verified_count`
 - **Tilføjet `not_matched`** til return value for bedre feedback
 ## Deployment Instructions
 ### Production Server Update
 1. **SSH til serveren:**
   ```bash
   ssh bmcadmin@172.16.31.183
   ```
 2. **Naviger til projekt directory:**
   ```bash
   cd /path/to/bmc_hub  # Skal opdateres til korrekt sti
   ```
 3. **Pull ny version:**
   ```bash
   git pull origin main
   git checkout v1.3.5
   ```
 4. **Genstart containers:**
   ```bash
   docker-compose down
   docker-compose up -d --build
   ```
 5. **Verificer:**
   ```bash
   docker ps
   curl http://localhost:8001/health
   curl http://localhost:8001/settings
   ```
 ## Technical Details
 - **Git Tag:** v1.3.5
 - **Commit:** c5ce819
 - **Changed Files:** `app/system/backend/sync_router.py`
 ## Breaking Changes
 Ingen breaking changes i denne release.
 ## Notes
 Settings siden er verificeret at virke både lokalt og skal virke efter deployment på production.
--- a/RELEASE_NOTES_v1.3.75.md
+++ b/RELEASE_NOTES_v1.3.75.md
@ -1,161 +0,0 @@
 # Release Notes - v1.3.75
 **Release Date:** 2. januar 2026
 ## ✨ New Features
 ### SFTP Offsite Backup
 - **Implemented SFTP offsite backup** - Backups can now be uploaded to remote SFTP server
 - **Auto-upload support** - Backups can be automatically uploaded after creation
 - **Manual upload** - Backups can be manually uploaded via web UI
 - **Upload verification** - File size verification ensures successful upload
 - **Retry mechanism** - Failed uploads can be retried with error tracking
 ### Database Schema Updates
 - Added `offsite_status` column (pending, uploading, uploaded, failed)
 - Added `offsite_location` column for remote file path
 - Added `offsite_attempts` counter for retry tracking
 - Added `offsite_last_error` for error logging
 ## 🔧 Technical Improvements
 ### SFTP Implementation
 - Uses `paramiko` library for SFTP connections
 - Supports password authentication
 - Automatic directory creation on remote server
 - Progress tracking during upload
 - Connection timeout protection (30s banner timeout)
 ### Configuration
 - `OFFSITE_ENABLED` - Enable/disable offsite uploads
 - `SFTP_HOST` - Remote SFTP server hostname
 - `SFTP_PORT` - SFTP port (default: 22)
 - `SFTP_USER` - SFTP username
 - `SFTP_PASSWORD` - SFTP password
 - `SFTP_REMOTE_PATH` - Remote directory path
 ### Bug Fixes
 - Fixed infinite loop in `_ensure_remote_directory()` for relative paths
 - Fixed duplicate `upload_to_offsite()` method - removed redundant code
 - Fixed router method name mismatch (`upload_offsite` vs `upload_to_offsite`)
 - Added protection against empty/root path directory creation
 ## 📝 Files Changed
 - `app/backups/backend/service.py` - SFTP upload implementation
 - `app/backups/backend/router.py` - Offsite upload endpoint
 - `app/backups/templates/index.html` - Frontend offsite upload button
 - `app/core/config.py` - SFTP configuration settings
 - `migrations/052_backup_offsite_columns.sql` - Database schema migration
 - `.env` - SFTP configuration
 ## 🚀 Deployment Instructions
 ### Prerequisites
 - Ensure `.env` file contains SFTP credentials
 - Database migration must be applied
 ### Production Server Update
 1. **SSH til serveren:**
   ```bash
   ssh bmcadmin@172.16.31.183
   ```
 2. **Naviger til projekt directory:**
   ```bash
   cd /opt/bmc_hub  # Eller korrekt sti
   ```
 3. **Pull ny version:**
   ```bash
   git fetch --tags
   git checkout v1.3.75
   ```
 4. **Opdater .env fil med SFTP credentials:**
   ```bash
   nano .env
   # Tilføj:
   # OFFSITE_ENABLED=true
   # SFTP_HOST=sftp.acdu.dk
   # SFTP_PORT=9022
   # SFTP_USER=sftp_bmccrm
   # SFTP_PASSWORD=<password>
   # SFTP_REMOTE_PATH=SFTP_BMCCRM
   ```
 5. **Kør database migration:**
   ```bash
   docker-compose exec postgres psql -U bmcnetworks -d bmc_hub -f /migrations/052_backup_offsite_columns.sql
   # ELLER manuel ALTER TABLE:
   docker-compose exec postgres psql -U bmcnetworks -d bmc_hub -c "
   ALTER TABLE backup_jobs ADD COLUMN IF NOT EXISTS offsite_status VARCHAR(20) CHECK(offsite_status IN ('pending','uploading','uploaded','failed'));
   ALTER TABLE backup_jobs ADD COLUMN IF NOT EXISTS offsite_location VARCHAR(500);
   ALTER TABLE backup_jobs ADD COLUMN IF NOT EXISTS offsite_attempts INTEGER DEFAULT 0;
   ALTER TABLE backup_jobs ADD COLUMN IF NOT EXISTS offsite_last_error TEXT;
   "
   ```
 6. **Genstart containers:**
   ```bash
   docker-compose down
   docker-compose up -d --build
   ```
 7. **Verificer:**
   ```bash
   docker-compose logs -f api | grep -i offsite
   curl http://localhost:8001/health
   # Test offsite upload:
   curl -X POST http://localhost:8001/api/v1/backups/offsite/{job_id}
   ```
 ## 🧪 Testing
 ### Verify SFTP Connection
 ```bash
 # From inside API container:
 docker-compose exec api bash
 apt-get update && apt-get install -y lftp
 lftp -u sftp_bmccrm,'<password>' sftp://sftp.acdu.dk:9022 -e 'ls SFTP_BMCCRM; quit'
 ```
 ### Test Upload
 1. Create a backup via web UI: http://localhost:8001/backups
 2. Click "Upload to Offsite" button for the backup
 3. Check logs for "✅ Upload completed"
 4. Verify `offsite_uploaded_at` is set in database
 ## ⚠️ Breaking Changes
 None - this is a feature addition
 ## 📊 Database Migration
 **Migration File:** `migrations/052_backup_offsite_columns.sql`
 **Impact:** Adds 4 new columns to `backup_jobs` table
 - Safe to run on existing data (uses ADD COLUMN IF NOT EXISTS)
 - No data loss risk
 - Existing backups will have NULL values for new columns
 ## 🔐 Security Notes
 - SFTP password stored in `.env` file (not in repository)
 - Uses paramiko's `AutoAddPolicy` for host keys
 - File size verification prevents corrupt uploads
 - Connection timeout prevents indefinite hangs
 ## 📞 Support
 Ved problemer, kontakt Christian Thomas eller check logs:
 ```bash
 docker-compose logs -f api | grep -E "(offsite|SFTP|Upload)"
 ```
 ---
 **Git Tag:** v1.3.75  
 **Previous Version:** v1.3.74  
 **Tested on:** Local development environment (macOS Docker)
--- a/RELEASE_NOTES_v1.3.76.md
+++ b/RELEASE_NOTES_v1.3.76.md
@ -1,73 +0,0 @@
 # Release Notes - v1.3.76
 **Release Date:** 2. januar 2026
 ## 🐛 Bug Fixes
 ### Timetracking Wizard Approval
 - **Fixed approval endpoint** - Wizard approval nu virker korrekt
 - **Fixed parameter handling** - Router modtager nu body params korrekt som Dict
 - **Fixed missing fields** - Sender nu alle nødvendige felter til wizard.approve_time_entry():
  - `rounded_to` beregnes hvis auto-rounding er enabled
  - `approval_note` sendes med fra frontend
  - `billable` sættes til true som default
  - `is_travel` sendes med fra checkbox
 ### Technical Details
 - Ændret `/api/v1/timetracking/wizard/approve/{time_id}` endpoint
 - Modtager nu `request: Dict[str, Any]` i stedet for individuelle query params
 - Tilføjet `Dict, Any` imports i router
 - Beregner `rounded_to` baseret på TIMETRACKING_AUTO_ROUND setting
 ## 📝 Files Changed
 - `app/timetracking/backend/router.py` - Fixed approve_time_entry endpoint
 ## 🚀 Deployment Instructions
 ### Production Server Update
 1. **SSH til serveren:**
   ```bash
   ssh bmcadmin@172.16.31.183
   ```
 2. **Naviger til projekt directory:**
   ```bash
   cd /opt/bmc_hub
   ```
 3. **Pull ny version:**
   ```bash
   git fetch --tags
   git checkout v1.3.76
   ```
 4. **Genstart containers:**
   ```bash
   docker-compose restart api
   ```
 5. **Verificer:**
   ```bash
   curl http://localhost:8001/health
   # Test approval:
   # Gå til http://172.16.31.183:8000/timetracking/wizard
   # Godkend en tidsregistrering
   ```
 ## ⚠️ Breaking Changes
 None - this is a bug fix
 ## 📊 Impact
 - Timetracking wizard approval virker nu igen
 - Ingen database ændringer nødvendige
 - Ingen configuration ændringer nødvendige
 ---
 **Git Tag:** v1.3.76  
 **Previous Version:** v1.3.75  
 **Commit:** TBD
--- a/RELEASE_NOTES_v1.3.84.md
+++ b/RELEASE_NOTES_v1.3.84.md
@ -1,91 +0,0 @@
 # Release Notes - v1.3.84
 **Release Date:** 2. januar 2026
 ## 🔧 Database Migration
 ### Timetracking Approval Columns
 - **Added migration** for missing approval columns in `tmodule_times` table
 - **Required for production** - local development already has these columns
 ### Columns Added (if missing):
 - `approved_hours` DECIMAL(10,2) - Godkendte timer
 - `rounded_to` DECIMAL(10,2) - Afrundingsinterval brugt
 - `approval_note` TEXT - Godkendelsesnote
 - `billable` BOOLEAN DEFAULT TRUE - Skal faktureres
 - `is_travel` BOOLEAN DEFAULT FALSE - Indeholder kørsel
 - `approved_at` TIMESTAMP - Tidspunkt for godkendelse
 - `approved_by` INTEGER - Bruger der godkendte
 ### Indexes Added:
 - `idx_tmodule_times_status` - For hurtigere status queries
 - `idx_tmodule_times_approved_at` - For hurtigere approval queries
 ## 📝 Files Changed
 - `migrations/053_timetracking_approval_columns.sql` - New migration file
 ## 🚀 Deployment Instructions
 ### CRITICAL - Run Migration First!
 **På produktionsserveren:**
 1. **SSH til serveren:**
   ```bash
   ssh bmcadmin@172.16.31.183
   ```
 2. **Naviger til projekt:**
   ```bash
   cd /opt/bmc_hub
   git fetch --tags
   git checkout v1.3.84
   ```
 3. **Kør migration (VIGTIGT!):**
   ```bash
   # Med podman:
   podman exec bmc-hub-postgres psql -U bmcnetworks -d bmc_hub -f /app/migrations/053_timetracking_approval_columns.sql
   ```
   **ELLER kopier filen først hvis mounted wrong:**
   ```bash
   podman cp migrations/053_timetracking_approval_columns.sql bmc-hub-postgres:/tmp/
   podman exec bmc-hub-postgres psql -U bmcnetworks -d bmc_hub -f /tmp/053_timetracking_approval_columns.sql
   ```
 4. **Genstart API:**
   ```bash
   podman restart bmc-hub-api
   ```
 5. **Verificer:**
   ```bash
   # Test godkendelse i wizard
   # Tjek logs for fejl
   podman logs -f bmc-hub-api | grep -E "(Error|✅|❌)"
   ```
 ## ⚠️ Breaking Changes
 None - backwards compatible migration
 ## 📊 Impact
 - Fixes approval failures on production
 - Safe to run - checks if columns exist before adding
 - No data loss risk
 ## 🔍 Why This Was Needed
 Production database was missing approval columns that exist in development:
 - Local dev had columns from previous migrations
 - Production was created before these columns were added
 - This migration ensures both environments have same schema
 ---
 **Git Tag:** v1.3.84  
 **Previous Version:** v1.3.83  
 **Migration:** 053_timetracking_approval_columns.sql
--- a/RELEASE_NOTES_v2.0.0.md
+++ b/RELEASE_NOTES_v2.0.0.md
@ -1,21 +0,0 @@
 # Release Notes v2.0.0
 ## New Features
 - Added new opportunities module with advanced features.
 - Improved performance for customer data processing.
 - Enhanced email activity logging system.
 ## Bug Fixes
 - Fixed issues with subscription singular module.
 - Resolved errors in ticket module integration.
 ## Other Changes
 - Updated dependencies in `requirements.txt`.
 - Database schema updated with migration `016_opportunities.sql`.
 ## Deployment Notes
 - Ensure to run the new database migration script `016_opportunities.sql` before deploying.
 - Verify `.env` file is updated with the correct `RELEASE_VERSION`.
 ---
 Release Date: 28. januar 2026
--- a/RELEASE_NOTES_v2.0.1.md
+++ b/RELEASE_NOTES_v2.0.1.md
@ -1,7 +0,0 @@
 # Release Notes v2.0.1
 ## Changes
 - Added "DB Migrationer" link to the settings navigation menu.
 ---
 Release Date: 28. januar 2026
--- a/RELEASE_NOTES_v2.0.2.md
+++ b/RELEASE_NOTES_v2.0.2.md
@ -1,7 +0,0 @@
 # Release Notes v2.0.2
 ## Changes
 - Minor updates and fixes following v2.0.1.
 ---
 Release Date: 28. januar 2026
--- a/RELEASE_NOTES_v2.0.3.md
+++ b/RELEASE_NOTES_v2.0.3.md
@ -1,8 +0,0 @@
 # Release Notes v2.0.3
 ## Changes
 - Allow executing SQL migration files directly from `/settings/migrations`, including user feedback on success/failure.
 - Pipe the migration SQL files into the Postgres container so the execution works across Docker and Podman.
 ---
 Release Date: 28. januar 2026
--- a/RELEASE_NOTES_v2.0.4.md
+++ b/RELEASE_NOTES_v2.0.4.md
@ -1,8 +0,0 @@
 # Release Notes v2.0.4
 ## Fixes
 - Reworked the migration execution endpoint to stream SQL files via stdin instead of relying on chained shell commands, which broke on Podman/Docker setups and led to pattern-matching errors for some files.
 - Added a default `CONTAINER_RUNTIME` setting so the endpoint knows whether to run `docker` or `podman` when the env var is not provided.
 ---
 Release Date: 28. januar 2026
--- a/RELEASE_NOTES_v2.0.5.md
+++ b/RELEASE_NOTES_v2.0.5.md
@ -1,8 +0,0 @@
 # Release Notes v2.0.5
 ## Fixes
 - The migration execution endpoint now probes for the available container runtime (`docker` or `podman`) instead of assuming `docker`, preventing failures when Docker is absent but Podman is installed.
 - Improved the validation error to clearly report when neither runtime is reachable and provided a more reliable command execution flow.
 ---
 Release Date: 28. januar 2026
--- a/RELEASE_NOTES_v2.0.6.md
+++ b/RELEASE_NOTES_v2.0.6.md
@ -1,8 +0,0 @@
 # Release Notes v2.0.6
 ## Fixes
 - `/settings/migrations/execute` now runs the SQL files directly through the already-configured PostgreSQL connection pool instead of shelling out to Docker/Podman, so it works anywhere the API can reach the database.
 - Cleaned up the migration endpoint to roll back on failure, reuse the pool, and return a clear success message.
 ---
 Release Date: 28. januar 2026
--- a/RELEASE_NOTES_v2.1.0.md
+++ b/RELEASE_NOTES_v2.1.0.md
@ -1,24 +0,0 @@
 # Release Notes v2.1.0
 ## New Features
 - **Email Drag-and-Drop Upload**: Upload .msg and .eml files directly to opportunities by dragging them onto the email drop zone
 - **Multiple Email Linking**: Link multiple emails to a single opportunity with search and persistent storage
 - **Contact Persons Management**: Add, link, and manage contact persons for opportunities with roles and search functionality
 - **File Uploads**: Upload files to opportunity comments and contract sections with drag-and-drop support
 - **Utility Company Lookup**: Automatically lookup electricity suppliers for customer addresses via Elnet API
 - **UI Reorganization**: Moved pipeline status to top-left for better visibility in opportunity detail view
 - **Email HTML Rendering**: Display HTML email bodies in the email viewer
 ## Technical Changes
 - Added Many-to-Many relationships for opportunity emails and contacts
 - New database tables: pipeline_opportunity_emails, pipeline_opportunity_contacts, pipeline_opportunity_comment_attachments, pipeline_opportunity_contract_files
 - Enhanced email processing to support .msg and .eml file uploads
 - Improved file handling with size limits and type validation
 - Updated customer detail page with utility company information
 ## Fixes
 - Fixed API_BASE path issues in opportunity detail page
 - Improved email attachment handling and display
 ---
 Release Date: 29. januar 2026
--- a/RELEASE_NOTES_v2.1.1.md
+++ b/RELEASE_NOTES_v2.1.1.md
@ -1,26 +0,0 @@
 # BMC Hub v2.1.1 - Bug Fix Release
 **Release Date:** 29. januar 2026
 ## 🐛 Bug Fixes
 ### Migrationer Interface
 - **Fixed container runtime detection**: Production servers using Podman now show correct commands instead of Docker commands
 - **Updated migration command display**: Frontend now correctly shows `podman exec` commands for production environments
 - **Improved user experience**: Added container runtime information in the standard setup section
 ## 🔧 Technical Changes
 - Updated `app/settings/frontend/migrations.html` to detect production environment and use appropriate container runtime
 - Modified `app/settings/backend/views.py` to pass production environment flag to template
 - Container runtime detection based on hostname (production vs localhost/127.0.0.1)
 ## 📋 Deployment Notes
 This is a frontend-only change that fixes the migration interface display. No database changes required.
 ## ✅ Verification
 - Migration page now shows correct Podman commands on production servers
 - Local development still uses Docker commands
 - Migration execution via web interface continues to work as before
--- a/RELEASE_NOTES_v2.2.2.md
+++ b/RELEASE_NOTES_v2.2.2.md
@ -1,38 +0,0 @@
 # BMC Hub v2.2.2 - Sync Safety Release
 **Release Date:** 22. februar 2026
 ## 🛡️ Critical Fixes
 ### e-conomic Customer Sync Mapping
 - **Fixed ambiguous matching**: e-conomic sync now matches customers only by `economic_customer_number`
 - **Removed unsafe fallback in this flow**: CVR/name fallback is no longer used in `/api/v1/system/sync/economic`
 - **Added conflict-safe behavior**: if multiple local rows share the same `economic_customer_number`, the record is skipped and logged as conflict (no overwrite)
 - **Improved traceability**: sync logs now include the actual local customer id that was updated/created
 ### Settings Sync UX
 - **Aligned frontend with backend response fields** for vTiger/e-conomic sync summaries
 - **Improved 2FA error feedback** in Settings sync UI when API returns `403: 2FA required`
 - **Fixed sync stats request limit** to avoid API validation issues
 - **Temporarily disabled CVR→e-conomic action** in Settings UI to prevent misleading behavior
 - **Clarified runtime config source**: sync uses environment variables (`.env`) at runtime
 ## 🗄️ Database Safety
 ### New Migration
 - Added migration: `migrations/138_customers_economic_unique_constraint.sql`
 - Normalizes empty/whitespace `economic_customer_number` values
 - Adds a partial unique index on non-null `economic_customer_number`
 - Migration aborts with clear error if duplicates already exist (manual dedupe required before rerun)
 ## ⚠️ Deployment Notes
 - Run migration `138_customers_economic_unique_constraint.sql` before enabling broad sync operations in production
 - If migration fails due to duplicates, deduplicate `customers.economic_customer_number` first, then rerun migration
 - Existing 2FA API protection remains enabled
 ## ✅ Expected Outcome
 - Sync payload and DB target row are now consistent in the e-conomic flow
 - Incorrect overwrites caused by weak matching strategy are prevented
 - Future duplicate `economic_customer_number` values are blocked at database level
--- a/RELEASE_NOTES_v2.2.3.md
+++ b/RELEASE_NOTES_v2.2.3.md
@ -1,15 +0,0 @@
 # BMC Hub v2.2.3 - Migration Hotfix
 **Release Date:** 22. februar 2026
 ## 🛠️ Hotfix
 ### Migration 138 compatibility fix
 - Fixed `migrations/138_customers_economic_unique_constraint.sql` for environments where `customers.economic_customer_number` is numeric (`integer`).
 - Removed unconditional `btrim(...)` usage on non-text columns.
 - Added type-aware normalization logic that only applies trimming for text-like column types.
 ## ✅ Impact
 - Migration `138_customers_economic_unique_constraint.sql` now runs on both numeric and text column variants without `function btrim(integer) does not exist` errors.
 - Unique index safety behavior and duplicate detection are unchanged.
--- a/RELEASE_NOTES_v2.2.36.md
+++ b/RELEASE_NOTES_v2.2.36.md
@ -1,30 +0,0 @@
 # BMC Hub v2.2.36 - Helpdesk SAG Routing
 **Release Date:** 2. marts 2026
 ## ✨ New Features
 ### Helpdesk email → SAG automation
 - Incoming emails from known customer domains now auto-create a new SAG when no `SAG-<id>` reference is present.
 - Incoming emails with `SAG-<id>` in subject or threading headers now auto-update the related SAG.
 - Emails from unknown domains remain in `/emails` for manual handling.
 ### Email threading support for routing
 - Added migration `141_email_threading_headers.sql`.
 - `email_messages` now stores `in_reply_to` and `email_references` to support robust SAG threading lookup.
 ### /emails quick customer creation improvements
 - Quick create customer modal now includes `email_domain`.
 - Customer create API now accepts and persists `email_domain`.
 ## 🔧 Technical Changes
 - Updated `app/services/email_service.py` to parse and persist `In-Reply-To` and `References` from IMAP/EML uploads.
 - Updated `app/services/email_workflow_service.py` with system-level helpdesk SAG routing logic.
 - Updated `app/emails/backend/router.py` to include `customer_name` in email list responses.
 - Updated `app/customers/backend/router.py` and `app/emails/frontend/emails.html` for `email_domain` support.
 ## 📋 Deployment Notes
 - Run database migration 141 before processing new inbound emails for full header-based routing behavior.
 - Existing workflow/rule behavior is preserved; new routing runs as a system workflow.
--- a/RELEASE_NOTES_v2.2.39.md
+++ b/RELEASE_NOTES_v2.2.39.md
@ -1,45 +0,0 @@
 # Release Notes v2.2.39
 Dato: 3. marts 2026
 ## Nyt: Mission Control (MVP)
 - Nyt dedikeret fullscreen dashboard til operations-overblik på storskærm.
 - Realtime-opdateringer via WebSocket (`/api/v1/mission/ws`).
 - KPI-overblik for sager:
  - Åbne sager
  - Nye sager
  - Sager uden ansvarlig
  - Deadlines i dag
  - Overskredne deadlines
 - Aktivt opkaldsoverlay med deduplikering på `call_id`.
 - Uptime-alerts (DOWN/UP/DEGRADED) med synlig aktive alarmer.
 - Live aktivitetsfeed (seneste 20 events).
 - Lydsystem med mute + volumenkontrol i dashboardet.
 ## Nye endpoints
 - `GET /api/v1/mission/state`
 - `WS /api/v1/mission/ws`
 - `POST /api/v1/mission/webhook/telefoni/ringing`
 - `POST /api/v1/mission/webhook/telefoni/answered`
 - `POST /api/v1/mission/webhook/telefoni/hangup`
 - `POST /api/v1/mission/webhook/uptime`
 ## Nye filer
 - `migrations/142_mission_control.sql`
 - `app/dashboard/backend/mission_router.py`
 - `app/dashboard/backend/mission_service.py`
 - `app/dashboard/backend/mission_ws.py`
 - `app/dashboard/frontend/mission_control.html`
 ## Opdaterede filer
 - `main.py`
 - `app/core/config.py`
 - `app/dashboard/backend/views.py`
 - `VERSION`
 ## Drift/konfiguration
 - Ny setting/env til webhook-sikring: `MISSION_WEBHOOK_TOKEN`.
 - Nye settings-seeds til Mission Control lyd, KPI-visning, queue-filter og customer-filter.
 ## Verificering
 - Python syntaks-check kørt på ændrede backend-filer med `py_compile`.
--- a/RELEASE_NOTES_v2.2.40.md
+++ b/RELEASE_NOTES_v2.2.40.md
@ -1,18 +0,0 @@
 # Release Notes v2.2.40
 Dato: 3. marts 2026
 ## Hotfix: Production build source override
 - Rettet Docker build-flow i `Dockerfile`, så release-kode hentet via `RELEASE_VERSION` ikke bliver overskrevet af lokal checkout under image build.
 - Dette løser scenarier hvor produktion kører forkert kodeversion (fx manglende routes som `/dashboard/mission-control`) selv når korrekt release-tag er angivet.
 ## Tekniske ændringer
 - Lokal kildekode kopieres nu til midlertidig mappe (`/app_local`).
 - Ved release-build (`RELEASE_VERSION != latest` og token sat) bevares downloadet release-kilde i `/app`.
 - Ved local/latest-build kopieres `/app_local` til `/app` som før.
 ## Verificering
 - Build output skal vise:
  - `Downloading release ... from Gitea...`
  - `Keeping downloaded release source in /app (no local override)`
 - Efter deploy skal `/dashboard/mission-control` ikke længere returnere 404 på release v2.2.39+.
--- a/RELEASE_NOTES_v2.2.41.md
+++ b/RELEASE_NOTES_v2.2.41.md
@ -1,20 +0,0 @@
 # Release Notes v2.2.41
 Dato: 3. marts 2026
 ## Fix: Postgres healthcheck støj i logs
 - Opdateret healthcheck til at bruge korrekt database-navn (`POSTGRES_DB`) i stedet for default database.
 - Løser gentagne loglinjer af typen: `FATAL: database "bmc_hub" does not exist` på installationer hvor databasen hedder noget andet (fx `hubdb_v2`).
 ## Ændrede filer
 - `docker-compose.prod.yml`
 - `docker-compose.yml`
 - `updateto.sh`
 - `VERSION`
 ## Tekniske noter
 - Healthcheck er ændret fra:
  - `pg_isready -U <user>`
 - Til:
  - `pg_isready -U <user> -d <db>`
 - `updateto.sh` bruger nu også `-d "$POSTGRES_DB"` i venteløkke for postgres.
--- a/RELEASE_NOTES_v2.2.42.md
+++ b/RELEASE_NOTES_v2.2.42.md
@ -1,18 +0,0 @@
 # Release Notes v2.2.42
 Dato: 3. marts 2026
 ## Fix: Yealink webhook compatibility + deploy robusthed
 - Tilføjet `GET` support på Mission Control telefoni-webhooks, så Yealink callback-URLs ikke returnerer `405 Method Not Allowed`.
 - Webhook-endpoints understøtter nu query-parametre for `call_id`, `caller_number`, `queue_name` og valgfri `timestamp`.
 - `updateto.sh` er hærdet med tydelig fail-fast ved portkonflikter og mislykket container-opstart, så scriptet ikke melder succes ved delvis fejl.
 ## Ændrede filer
 - `app/dashboard/backend/mission_router.py`
 - `updateto.sh`
 - `VERSION`
 ## Påvirkede endpoints
 - `/api/v1/mission/webhook/telefoni/ringing` (`POST` + `GET`)
 - `/api/v1/mission/webhook/telefoni/answered` (`POST` + `GET`)
 - `/api/v1/mission/webhook/telefoni/hangup` (`POST` + `GET`)
--- a/RELEASE_NOTES_v2.2.43.md
+++ b/RELEASE_NOTES_v2.2.43.md
@ -1,16 +0,0 @@
 # Release Notes v2.2.43
 Dato: 3. marts 2026
 ## Fix: Synlige Mission webhook logs
 - Tilføjet eksplicit logging for Mission telefoni-webhooks (`ringing`, `answered`, `hangup`) med call-id, nummer, kø og HTTP-metode.
 - Tilføjet warning logs ved manglende/ugyldig Mission webhook token.
 - Gør det nemt at fejlsøge Yealink callbacks i `podman logs`.
 ## Ændrede filer
 - `app/dashboard/backend/mission_router.py`
 - `VERSION`
 ## Drift
 - Deploy med: `./updateto.sh v2.2.43`
 - Se webhook-log events med: `podman logs -f bmc-hub-api-v2 | grep -E "Mission webhook|forbidden|token"`
--- a/RELEASE_NOTES_v2.2.44.md
+++ b/RELEASE_NOTES_v2.2.44.md
@ -1,17 +0,0 @@
 # Release Notes v2.2.44
 Dato: 4. marts 2026
 ## Fixes
 - `updateto.sh` rydder nu automatisk legacy containere (`bmc-hub-api-v2`, `bmc-hub-postgres-v2`) før deploy.
 - Forebygger port-lock konflikter på især Postgres host-port (`5433`) under compose opstart.
 - Mission Control: automatisk timeout på hængende `ringing` opkald, så de ikke bliver stående i Incoming Calls.
 ## Ændrede filer
 - `updateto.sh`
 - `app/dashboard/backend/mission_service.py`
 - `VERSION`
 ## Drift
 - Deploy: `./updateto.sh v2.2.44`
 - Verificér: `curl http://localhost:8001/health`
--- a/RELEASE_NOTES_v2.2.45.md
+++ b/RELEASE_NOTES_v2.2.45.md
@ -1,18 +0,0 @@
 # Release Notes v2.2.45
 Dato: 4. marts 2026
 ## Forbedringer
 - Tilføjet direkte menu-link til Mission Control i Support-dropdownen, så siden er hurtigere at finde.
 - Tilføjet Mission Control som valgmulighed under Standard Dashboard i Indstillinger.
 - Opdateret dashboard-fallback logik, så `/dashboard/mission-control` behandles som et kendt standardvalg.
 ## Ændrede filer
 - `app/shared/frontend/base.html`
 - `app/settings/frontend/settings.html`
 - `VERSION`
 - `RELEASE_NOTES_v2.2.45.md`
 ## Drift
 - Deploy: `./updateto.sh v2.2.45`
 - Verificér: `curl http://localhost:8001/dashboard/mission-control`
--- a/RELEASE_NOTES_v2.2.46.md
+++ b/RELEASE_NOTES_v2.2.46.md
@ -1,19 +0,0 @@
 # Release Notes v2.2.46
 Dato: 4. marts 2026
 ## Fixes og driftssikring
 - Mission Control backend tåler nu manglende mission-tabeller uden at crashe requests, og logger tydelige advarsler.
 - Tilføjet idempotent reparationsmigration for Mission Control schema (`143_mission_control_repair.sql`) til miljøer med delvist oprettede tabeller.
 - Opdateret `.gitignore` med release-note undtagelse fra tidligere drift.
 ## Ændrede filer
 - `app/dashboard/backend/mission_service.py`
 - `migrations/143_mission_control_repair.sql`
 - `.gitignore`
 - `VERSION`
 - `RELEASE_NOTES_v2.2.46.md`
 ## Drift
 - Deploy: `./updateto.sh v2.2.46`
 - Migration (hvis nødvendig): `docker compose exec db psql -U bmc_hub -d bmc_hub -f migrations/143_mission_control_repair.sql`
--- a/RELEASE_NOTES_v2.2.47.md
+++ b/RELEASE_NOTES_v2.2.47.md
@ -1,17 +0,0 @@
 # Release Notes v2.2.47
 Dato: 4. marts 2026
 ## Fixes
 - Mission webhook GET for ringing accepterer nu token-only ping uden `call_id` og returnerer `200 OK`.
 - `updateto.sh` bruger nu automatisk port `8001` som default i v2-mappen (`/srv/podman/bmc_hub_v2`), med fortsat støtte for `API_PORT` override i `.env`.
 ## Ændrede filer
 - `app/dashboard/backend/mission_router.py`
 - `updateto.sh`
 - `VERSION`
 - `RELEASE_NOTES_v2.2.47.md`
 ## Drift
 - Deploy: `./updateto.sh v2.2.47`
 - Verificér webhook ping: `curl -i "http://localhost:8001/api/v1/mission/webhook/telefoni/ringing?token=<TOKEN>"`
--- a/RELEASE_NOTES_v2.2.48.md
+++ b/RELEASE_NOTES_v2.2.48.md
@ -1,21 +0,0 @@
 # Release Notes v2.2.48
 Dato: 4. marts 2026
 ## Fixes
 - `sag` aggregering fejler ikke længere hvis tabellen `sag_salgsvarer` mangler; API returnerer fortsat tidsdata og tom salgsliste i stedet for `500`.
 - Salgsliste-endpoints i `sag` returnerer nu tom liste med advarsel i log, hvis `sag_salgsvarer` ikke findes.
 - Mission webhooks for `answered` og `hangup` accepterer nu også token-only `GET` ping uden `call_id` (samme kompatibilitet som `ringing`).
 ## Ændrede filer
 - `app/modules/sag/backend/router.py`
 - `app/dashboard/backend/mission_router.py`
 - `VERSION`
 - `RELEASE_NOTES_v2.2.48.md`
 ## Drift
 - Deploy: `./updateto.sh v2.2.48`
 - Valider webhook ping:
  - `curl -i "http://localhost:8001/api/v1/mission/webhook/telefoni/ringing?token=<TOKEN>"`
  - `curl -i "http://localhost:8001/api/v1/mission/webhook/telefoni/answered?token=<TOKEN>"`
  - `curl -i "http://localhost:8001/api/v1/mission/webhook/telefoni/hangup?token=<TOKEN>"`
--- a/RELEASE_NOTES_v2.2.49.md
+++ b/RELEASE_NOTES_v2.2.49.md
@ -1,40 +0,0 @@
 # Release Notes v2.2.49
 Dato: 5. marts 2026
 ## Ny funktionalitet
 ### Sag – Relationer
 - Relation-vinduet vises kun når der faktisk er relerede sager. Enkelt-sag (ingen relationer) viser nu tom-state "Ingen relaterede sager".
 - Aktuel sag fremhæves tydeligt i relationstræet: accent-farvet venstre-kant, svag baggrund, udfyldt badge med sags-ID og fed titel. Linket er ikke klikbart (man er allerede der).
 ### Sag – Sagstype dropdown
 - Sagstype i topbaren er nu et klikbart dropdown i stedet for et link til redigeringssiden.
 - Dropdown viser alle 6 typer (Ticket, Pipeline, Opgave, Ordre, Projekt, Service) med farveikoner og markerer den aktive type.
 - Valg PATCHer sagen direkte og genindlæser siden.
 - Rettet fejl hvor dropdown åbnede bagved siden (`overflow: hidden` fjernet fra `.case-hero`).
 ### Sag – Relation quick-actions (+)
 - Menuen indeholder nu 12 moduler: Tildel sag, Tidregistrering, Kommentar, Påmindelse, Opgave, Salgspipeline, Filer, Hardware, Løsning, Varekøb & salg, Abonnement, Send email.
 - Alle moduler åbner mini-modal med relevante felter direkte fra relationspanelet – ingen sidenavigation nødvendig.
 - Salgspipeline skjules fra menuen hvis sagen allerede har pipeline-data (vises som grå "Pipeline (se sagen)").
 - Tags bruger nu det globale TagPicker-system (`window.showTagPicker`).
 ### Email service
 - Ny `app/services/email_service.py` til centraliseret e-mail-afsendelse.
 ### Telefoni
 - Opdateringer til telefon-log og router.
 ## Ændrede filer
 - `app/modules/sag/templates/detail.html`
 - `app/modules/sag/backend/router.py`
 - `app/dashboard/backend/mission_router.py`
 - `app/dashboard/backend/mission_service.py`
 - `app/modules/telefoni/backend/router.py`
 - `app/modules/telefoni/templates/log.html`
 - `app/services/email_service.py`
 - `main.py`
 ## Drift
 - Deploy: `./updateto.sh v2.2.49`
--- a/RELEASE_NOTES_v2.2.50.md
+++ b/RELEASE_NOTES_v2.2.50.md
@ -1,18 +0,0 @@
 # Release Notes v2.2.50
 Dato: 6. marts 2026
 ## Fixes
 - Sag: “Ny email”-compose er gendannet i E-mail-fanen på sager.
 - Tilføjet synlig compose-sektion med felter for Til/Cc/Bcc/Emne/Besked samt vedhæftning af sagsfiler.
 - Knap `Ny email` er nu koblet til afsendelse via `/api/v1/sag/{sag_id}/emails/send`.
 - Compose prefill’er modtager (primær kontakt hvis muligt) og emne (`Sag #<id>:`).
 - Vedhæftningslisten opdateres fra sagsfiler, også når filpanelet ikke er synligt.
 ## Ændrede filer
 - `app/modules/sag/templates/detail.html`
 - `VERSION`
 - `RELEASE_NOTES_v2.2.50.md`
 ## Drift
 - Deploy: `./updateto.sh v2.2.50`
--- a/RELEASE_NOTES_v2.2.51.md
+++ b/RELEASE_NOTES_v2.2.51.md
@ -1,21 +0,0 @@
 # Release Notes v2.2.51
 Dato: 7. marts 2026
 ## Fixes
 - Settings: Bruger-administration i v2 bruger nu stabile admin-endpoints for statusændring og password reset.
 - Settings: Forbedrede fejlbeskeder ved brugerhandlinger (status/password), så 4xx/5xx vises tydeligt i UI.
 - Ticket Sync: Tilføjet Archived Sync monitor i Settings med knapper for Simply/vTiger import og løbende status-check.
 - Ticket Sync: Nyt endpoint `/api/v1/ticket/archived/status` returnerer parity (remote vs lokal) og samlet `overall_synced`.
 - Sikkerhed: Sync/import endpoints er låst til admin/superadmin (`users.manage` eller `system.admin`).
 ## Ændrede filer
 - `app/settings/frontend/settings.html`
 - `app/ticket/backend/router.py`
 - `app/system/backend/sync_router.py`
 - `app/auth/backend/admin.py`
 - `VERSION`
 - `RELEASE_NOTES_v2.2.51.md`
 ## Drift
 - Deploy: `./updateto.sh v2.2.51`
--- a/RELEASE_NOTES_v2.2.52.md
+++ b/RELEASE_NOTES_v2.2.52.md
@ -1,16 +0,0 @@
 # Release Notes v2.2.52
 Dato: 7. marts 2026
 ## Fixes
 - Auth Admin: `GET /api/v1/admin/users` er gjort ekstra robust mod delvist migreret database schema.
 - Endpointet falder nu tilbage til en simplere query, hvis join/kolonner for grupper eller telefoni mangler.
 - Reducerer risiko for UI-fejl: "Kunne ikke indlæse brugere" på v2.
 ## Ændrede filer
 - `app/auth/backend/admin.py`
 - `VERSION`
 - `RELEASE_NOTES_v2.2.52.md`
 ## Drift
 - Deploy: `./updateto.sh v2.2.52`
--- a/RELEASE_NOTES_v2.2.53.md
+++ b/RELEASE_NOTES_v2.2.53.md
@ -1,42 +0,0 @@
 # Release Notes - v2.2.53
 Dato: 17. marts 2026
 ## Fokus
 Email til SAG flow med manuel godkendelse som standard, tydelig UI-handling og bedre sporbarhed.
 ## Tilføjet
 - Manual approval gate i email pipeline (`awaiting_user_action` state), så mails parkeres til brugerhandling før automatisk routing.
 - Ny feature-flag i config: `EMAIL_REQUIRE_MANUAL_APPROVAL` (default `true`).
 - Nye email API endpoints:
  - `GET /api/v1/emails/sag-options`
  - `GET /api/v1/emails/search-customers`
  - `GET /api/v1/emails/search-sager`
  - `POST /api/v1/emails/{email_id}/create-sag`
  - `POST /api/v1/emails/{email_id}/link-sag`
 - Email stats udvidet med `awaiting_user_action` i summary/processing stats.
 - Email frontend opgraderet med forslagspanel og hurtigknapper:
  - Bekræft forslag
  - Ret type
  - Opret ny sag
  - Tilknyt eksisterende sag
  - Markér spam
 - Oprettelse af SAG fra email understøtter nu:
  - type
  - sekundær label
  - ansvarlig bruger
  - gruppe
  - startdato
  - prioritet
 - Ny migration: `145_sag_start_date.sql` (`start_date` på `sag_sager`).
 ## Driftsnoter
 - Kør migration `145_sag_start_date.sql` før brug af startdato-feltet i email->sag flow.
 - Manuel approval er aktiv som standard; auto-oprettelse er dermed deaktiveret i fase 1.
 ## Backup
 - Fallback zip af nuværende email-funktion er oprettet i `backups/email_feature/`.
--- a/RELEASE_NOTES_v2.2.54.md
+++ b/RELEASE_NOTES_v2.2.54.md
@ -1,28 +0,0 @@
 # Release Notes - v2.2.54
 Dato: 17. marts 2026
 ## Fokus
 Forbedringer i email til SAG workflow med deadline-felt og markant bedre firma/kunde-søgning i UI.
 ## Tilføjet
 - Deadline understøttes nu i email->sag oprettelse.
  - Backend request-model udvidet med `deadline`.
  - `create-sag` gemmer nu deadline på `sag_sager`.
  - Frontend forslagspanel har fået dedikeret deadline-felt.
 - Kundevalg i email-panelet er opgraderet til en “super firma-søgning”:
  - Live dropdown-resultater i stedet for simpel datalist.
  - Bedre ranking af resultater (exact/prefix/relevans).
  - Hurtig valg med klik, inklusive visning af CVR/domæne/email metadata.
 ## Opdaterede filer
 - `app/emails/backend/router.py`
 - `app/emails/frontend/emails.html`
 ## Bemærkninger
 - Ingen breaking API changes.
 - Ingen ekstra migration nødvendig for denne release.
--- a/RELEASE_NOTES_v2.2.56.md
+++ b/RELEASE_NOTES_v2.2.56.md
@ -1,22 +0,0 @@
 # Release Notes v2.2.56
 Dato: 2026-03-18
 ## Fokus
 Stabilisering af email-visning og hardening af supplier-invoices flows.
 ## Aendringer
 - Rettet layout-overflow i email-detaljevisning, saa lange emner, afsenderadresser, HTML-indhold og filnavne ikke skubber kolonnerne ud af layoutet.
 - Tilfoejet robust wrapping/truncering i emails UI for bedre responsiv opfoersel.
 - Tilfoejet manglende "Klar til Bogforing" tab i supplier-invoices navigation.
 - Rettet endpoint mismatch for AI template-analyse i supplier-invoices frontend.
 - Fjernet JS-funktionskonflikter i supplier-invoices ved at adskille single/bulk send flows.
 - Tilfoejet backend endpoint til at markere supplier-invoices som betalt.
 - Fjernet route-konflikt for send-to-economic ved at flytte legacy placeholder til separat sti.
 - Forbedret approve-flow ved at bruge dynamisk brugeropslag i stedet for hardcoded vaerdi.
 ## Berorte filer
 - app/emails/frontend/emails.html
 - app/billing/frontend/supplier_invoices.html
 - app/billing/backend/supplier_invoices.py
 - RELEASE_NOTES_v2.2.56.md
--- a/RELEASE_NOTES_v2.2.57.md
+++ b/RELEASE_NOTES_v2.2.57.md
@ -1,18 +0,0 @@
 # Release Notes v2.2.57
 Dato: 2026-03-18
 ## Fokus
 Stabilisering af UI i Email- og SAG-modulerne.
 ## Aendringer
 - Email-visning: yderligere hardening af HTML-tabeller i mail-body, inklusive normalisering af inline styles for at undgaa layout break.
 - Email-visning: forbedret overflow-haandtering for bredt indhold (tabeller, celler og media).
 - SAG detaljeside: forbedret tab-loading, saa data hentes ved faneskift for Varekob & Salg, Abonnement og Paamindelser.
 - SAG detaljeside: robust fallback for reminder user-id via `/api/v1/auth/me`.
 - SAG detaljeside: rettet API-kald for reminders og kalender til stabil case-id reference.
 ## Berorte filer
 - app/emails/frontend/emails.html
 - app/modules/sag/templates/detail.html
 - RELEASE_NOTES_v2.2.57.md
--- a/RELEASE_NOTES_v2.2.58.md
+++ b/RELEASE_NOTES_v2.2.58.md
@ -1,15 +0,0 @@
 # Release Notes v2.2.58
 Dato: 2026-03-18
 ## Fokus
 Forbedret UX paa SAG detaljesiden, saa fanernes indhold vises i toppen ved faneskift.
 ## Aendringer
 - SAG tabs: aktiv tab-pane flyttes til toppen af tab-content ved faneskift.
 - SAG tabs: automatisk scroll til fanebjaelken efter faneskift.
 - SAG tabs: samme top-positionering og scroll ved `?tab=` deep-link aktivering.
 ## Berorte filer
 - app/modules/sag/templates/detail.html
 - RELEASE_NOTES_v2.2.58.md
--- a/RELEASE_NOTES_v2.2.59.md
+++ b/RELEASE_NOTES_v2.2.59.md
@ -1,16 +0,0 @@
 # Release Notes v2.2.59
 Dato: 2026-03-18
 ## Fokus
 Stabil scroll/navigation i SAG-faner, saa bruger lander ved reelt indhold i den valgte fane.
 ## Aendringer
 - Fjernet DOM-reordering af tab-pane elementer i SAG detaljesiden.
 - Ny scroll-logik: ved faneskift scrolles til foerste meningsfulde indholdselement i aktiv fane.
 - Scroll-offset tager hoejde for navbar-hoejde.
 - Deep-link (`?tab=...`) bruger nu samme robuste scroll-adfaerd.
 ## Berorte filer
 - app/modules/sag/templates/detail.html
 - RELEASE_NOTES_v2.2.59.md
--- a/RELEASE_NOTES_v2.2.60.md
+++ b/RELEASE_NOTES_v2.2.60.md
@ -1,17 +0,0 @@
 # Release Notes v2.2.60
 Dato: 2026-03-18
 ## Fokus
 Korrekt top-visning af aktiv fane paa SAG detaljesiden.
 ## Aendringer
 - Tvang korrekt tab-pane synlighed i `#caseTabsContent`:
  - inaktive faner skjules (`display: none`)
  - kun aktiv fane vises (`display: block`)
 - Fjernet tidligere scroll/DOM-workaround til fanevisning.
 - Resultat: aktiv fane vises i toppen under fanebjaelken uden tom top-sektion.
 ## Berorte filer
 - app/modules/sag/templates/detail.html
 - RELEASE_NOTES_v2.2.60.md
--- a/RELEASE_NOTES_v2.2.61.md
+++ b/RELEASE_NOTES_v2.2.61.md
@ -1,15 +0,0 @@
 # Release Notes v2.2.61
 Dato: 18. marts 2026
 ## Fixes
 - Rettet SAG-fanevisning i sag-detaljesiden, så kun den aktive fane vises i toppen.
 - Tilføjet direkte klik-fallback på faneknapper (`onclick`) for robust aktivering, også hvis Bootstrap tab-events fejler.
 - Sat eksplicit start-visibility på tab-panes for at undgå "lang side"-effekten med indhold langt nede.
 - Fjernet to ødelagte CSS-blokke i toppen af templaten, som kunne skabe ustabil styling/parsing.
 ## Berørte filer
 - `app/modules/sag/templates/detail.html`
 - `RELEASE_NOTES_v2.2.61.md`
--- a/RELEASE_NOTES_v2.2.62.md
+++ b/RELEASE_NOTES_v2.2.62.md
@ -1,14 +0,0 @@
 # Release Notes v2.2.62
 Dato: 18. marts 2026
 ## Fixes
 - Rettet grid/nesting i SAG detaljevisning, så højre kolonne ligger i samme row som venstre/center.
 - `Hardware`, `Salgspipeline`, `Opkaldshistorik` og `Todo-opgaver` vises nu i højre kolonne som forventet.
 - Fjernet en for tidlig afsluttende `</div>` i detaljer-layoutet, som tidligere fik højre modulkolonne til at falde ned under venstre indhold.
 ## Berørte filer
 - `app/modules/sag/templates/detail.html`
 - `RELEASE_NOTES_v2.2.62.md`
--- a/RELEASE_NOTES_v2.2.63.md
+++ b/RELEASE_NOTES_v2.2.63.md
@ -1,14 +0,0 @@
 # Release Notes v2.2.63
 Dato: 18. marts 2026
 ## Fixes
 - Rettet QuickCreate AI-analyse request i frontend.
 - `POST /api/v1/sag/analyze-quick-create` får nu korrekt payload med både `text` og `user_id` i body.
 - Forbedret fejllog i frontend ved AI-fejl (inkl. HTTP status), så fejl ikke bliver skjult som generisk "Analysis failed".
 ## Berørte filer
 - `app/shared/frontend/quick_create_modal.html`
 - `RELEASE_NOTES_v2.2.63.md`
--- a/RELEASE_NOTES_v2.2.64.md
+++ b/RELEASE_NOTES_v2.2.64.md
@ -1,18 +0,0 @@
 # Release Notes v2.2.64
 Dato: 18. marts 2026
 ## Fixes
 - Forbedret QuickCreate robusthed når AI/LLM er utilgængelig.
 - Tilføjet lokal heuristisk fallback i `CaseAnalysisService`, så brugeren stadig får:
  - foreslået titel
  - foreslået prioritet
  - simple tags
  - kunde-match forsøg
 - Fjernet afhængighed af at Ollama altid svarer, så QuickCreate ikke længere ender i tom AI-unavailable flow ved midlertidige AI-fejl.
 ## Berørte filer
 - `app/services/case_analysis_service.py`
 - `RELEASE_NOTES_v2.2.64.md`
--- a/REMINDER_SYSTEM_IMPLEMENTATION.md
+++ b/REMINDER_SYSTEM_IMPLEMENTATION.md
@ -1,386 +0,0 @@
 # Reminder System Implementation - BMC Hub
 ## Overview
 The Reminder System for BMC Hub's Sag (Case) module provides flexible, multi-channel notification delivery with support for:
 - **Time-based reminders**: Scheduled at specific times or recurring (daily, weekly, monthly)
 - **Status-change triggered reminders**: Automatically triggered when case status changes
 - **Multi-channel delivery**: Mattermost, Email, Frontend popup notifications
 - **User preferences**: Global defaults with per-reminder overrides
 - **Rate limiting**: Max 5 notifications per user per hour (global)
 - **Smart scheduling**: Database triggers for status changes, APScheduler for time-based
 ## Architecture
 ### Database Schema
 **4 Main Tables** (created in `migrations/096_reminder_system.sql`):
 1. **`user_notification_preferences`** - User default notification settings
   - Default channels (mattermost, email, frontend)
   - Quiet hours configuration
   - Email override option
 2. **`sag_reminders`** - Reminder rules/templates
   - Trigger configuration (status_change, deadline_approaching, time_based)
   - Recipient configuration (user IDs or email addresses)
   - Recurrence setup (once, daily, weekly, monthly)
   - Scheduling info (scheduled_at, next_check_at)
 3. **`sag_reminder_queue`** - Event queue from database triggers
   - Holds events generated by status-change trigger
   - Processing status tracking (pending, processing, sent, failed, rate_limited)
   - Batch processed by scheduler job
 4. **`sag_reminder_logs`** - Execution log
   - Every notification sent/failed is logged
   - User interactions (snooze, dismiss, acknowledge)
   - Used for rate limiting verification
 **Database Triggers**:
 - `sag_status_change_reminder_trigger()` - Fires on status UPDATE, queues relevant reminders
 **Helper Functions**:
 - `check_reminder_rate_limit(user_id)` - Verifies user hasn't exceeded 5 per hour
 **Helper Views**:
 - `v_pending_reminders` - Time-based reminders ready to send
 - `v_pending_reminder_queue` - Queued events ready for processing
 ### Backend Services
 **`app/services/reminder_notification_service.py`**:
 - Unified notification delivery via Mattermost, Email, Frontend
 - Merges user preferences with per-reminder overrides
 - Rate limit checking
 - Event logging
 - Email template rendering (Jinja2)
 **`app/services/email_service.py`** (extended):
 - Added `send_email()` async method using `aiosmtplib`
 - SMTP configuration from `.env`
 - Supports plain text + HTML bodies
 - Safety flag: `REMINDERS_DRY_RUN=true` logs without sending
 ### API Endpoints
 **User Preferences** (in `app/modules/sag/backend/reminders.py`):
 ```
 GET  /api/v1/users/me/notification-preferences
 PATCH /api/v1/users/me/notification-preferences
 ```
 **Reminder CRUD**:
 ```
 GET    /api/v1/sag/{sag_id}/reminders           - List reminders for case
 POST   /api/v1/sag/{sag_id}/reminders           - Create new reminder
 PATCH  /api/v1/sag/reminders/{reminder_id}      - Update reminder
 DELETE /api/v1/sag/reminders/{reminder_id}      - Soft-delete reminder
 ```
 **Reminder Interactions**:
 ```
 POST /api/v1/sag/reminders/{reminder_id}/snooze   - Snooze for X minutes
 POST /api/v1/sag/reminders/{reminder_id}/dismiss  - Permanently dismiss
 GET  /api/v1/reminders/pending/me                 - Get pending (for polling)
 ```
 ### Scheduler Job
 **`app/jobs/check_reminders.py`**:
 - Processes time-based reminders (`next_check_at <= NOW()`)
 - Processes queued status-change events
 - Calculates next recurrence (`daily` +24h, `weekly` +7d, `monthly` +30d)
 - Respects rate limiting
 **Registration in `main.py`**:
 ```python
 backup_scheduler.scheduler.add_job(
    func=check_reminders,
    trigger=IntervalTrigger(minutes=5),
    id='check_reminders',
    name='Check Reminders',
    max_instances=1
 )
 ```
 Runs **every 5 minutes** (configurable via `REMINDERS_CHECK_INTERVAL_MINUTES`)
 ### Frontend Notifications
 **`static/js/notifications.js`**:
 - Bootstrap 5 Toast-based notification popups
 - Polls `/api/v1/reminders/pending/me` every 30 seconds
 - Snooze presets: 15min, 30min, 1h, 4h, 1day, custom
 - Dismiss action
 - Auto-removes when hidden
 - Pauses polling when tab not visible
 **Integration**:
 - Loaded in `app/shared/frontend/base.html`
 - Auto-initializes on page load if user authenticated
 - User ID extracted from JWT token
 ## Configuration
 ### Environment Variables
 ```env
 # Master switches (default: disabled for safety)
 REMINDERS_ENABLED=false
 REMINDERS_EMAIL_ENABLED=false
 REMINDERS_MATTERMOST_ENABLED=false
 REMINDERS_DRY_RUN=true              # Log without sending if true
 # Scheduler settings
 REMINDERS_CHECK_INTERVAL_MINUTES=5   # Frequency of reminder checks
 REMINDERS_MAX_PER_USER_PER_HOUR=5    # Rate limit
 REMINDERS_QUEUE_BATCH_SIZE=10        # Batch size for queue processing
 # SMTP Configuration (for email reminders)
 EMAIL_SMTP_HOST=smtp.gmail.com
 EMAIL_SMTP_PORT=587
 EMAIL_SMTP_USER=noreply@bmcnetworks.dk
 EMAIL_SMTP_PASSWORD=<secret>
 EMAIL_SMTP_USE_TLS=true
 EMAIL_SMTP_FROM_ADDRESS=noreply@bmcnetworks.dk
 EMAIL_SMTP_FROM_NAME=BMC Hub
 ```
 ### Pydantic Configuration
 Added to `app/core/config.py`:
 ```python
 REMINDERS_ENABLED: bool = False
 REMINDERS_EMAIL_ENABLED: bool = False
 REMINDERS_MATTERMOST_ENABLED: bool = False
 REMINDERS_DRY_RUN: bool = True
 REMINDERS_CHECK_INTERVAL_MINUTES: int = 5
 REMINDERS_MAX_PER_USER_PER_HOUR: int = 5
 REMINDERS_QUEUE_BATCH_SIZE: int = 10
 EMAIL_SMTP_HOST: str = ""
 EMAIL_SMTP_PORT: int = 587
 EMAIL_SMTP_USER: str = ""
 EMAIL_SMTP_PASSWORD: str = ""
 EMAIL_SMTP_USE_TLS: bool = True
 EMAIL_SMTP_FROM_ADDRESS: str = "noreply@bmcnetworks.dk"
 EMAIL_SMTP_FROM_NAME: str = "BMC Hub"
 ```
 ## Safety Features
 ### Rate Limiting
 - **Global per user**: Max 5 notifications per hour
 - Checked before sending via `check_reminder_rate_limit(user_id)`
 - Queued events marked as `rate_limited` if limit exceeded
 ### Dry Run Mode
 - `REMINDERS_DRY_RUN=true` (default)
 - All operations logged to console/logs
 - No emails actually sent
 - No Mattermost webhooks fired
 - Useful for testing
 ### Soft Delete
 - Reminders never hard-deleted from DB
 - `deleted_at` timestamp + `is_active=false`
 - Full audit trail preserved
 ### Per-Reminder Override
 - Reminder can override user's default channels
 - `override_user_preferences` flag
 - Useful for critical reminders (urgent priority)
 ## Usage Examples
 ### Create a Status-Change Reminder
 ```bash
 curl -X POST http://localhost:8000/api/v1/sag/123/reminders \
  -H "Content-Type: application/json" \
  -d {
    "title": "Case entered In Progress",
    "message": "Case #123 has moved to 'i_gang' status",
    "priority": "high",
    "trigger_type": "status_change",
    "trigger_config": {"target_status": "i_gang"},
    "recipient_user_ids": [1, 2],
    "notify_mattermost": true,
    "notify_email": true,
    "recurrence_type": "once"
  }
 ```
 ### Create a Scheduled Reminder
 ```bash
 curl -X POST http://localhost:8000/api/v1/sag/123/reminders \
  -H "Content-Type: application/json" \
  -d {
    "title": "Follow up needed",
    "message": "Check in with customer",
    "priority": "normal",
    "trigger_type": "time_based",
    "trigger_config": {},
    "scheduled_at": "2026-02-10T14:30:00",
    "recipient_user_ids": [1],
    "recurrence_type": "once"
  }
 ```
 ### Create a Daily Recurring Reminder
 ```bash
 curl -X POST http://localhost:8000/api/v1/sag/123/reminders \
  -H "Content-Type: application/json" \
  -d {
    "title": "Daily status check",
    "priority": "low",
    "trigger_type": "time_based",
    "trigger_config": {},
    "scheduled_at": "2026-02-04T09:00:00",
    "recipient_user_ids": [1],
    "recurrence_type": "daily"
  }
 ```
 ### Update User Preferences
 ```bash
 curl -X PATCH http://localhost:8000/api/v1/users/me/notification-preferences \
  -H "Content-Type: application/json" \
  -d {
    "notify_mattermost": true,
    "notify_email": false,
    "notify_frontend": true,
    "quiet_hours_enabled": true,
    "quiet_hours_start": "18:00",
    "quiet_hours_end": "08:00"
  }
 ```
 ## Testing Checklist
 ### Database
 - [ ] Run migration: `docker-compose exec -T postgres psql -U bmc_hub -d bmc_hub -f /migrations/096_reminder_system.sql`
 - [ ] Verify tables created: `SELECT * FROM sag_reminders LIMIT 0;`
 - [ ] Verify trigger exists: `SELECT * FROM information_schema.triggers WHERE trigger_name LIKE 'sag%reminder%';`
 ### API
 - [ ] Test create reminder endpoint
 - [ ] Test list reminders endpoint
 - [ ] Test update reminder endpoint
 - [ ] Test snooze endpoint
 - [ ] Test dismiss endpoint
 - [ ] Test user preferences endpoints
 ### Scheduler
 - [ ] Enable `REMINDERS_ENABLED=true` in `.env`
 - [ ] Restart container
 - [ ] Check logs for "Reminder job scheduled" message
 - [ ] Verify job runs every 5 minutes: `✅ Checking for pending reminders...`
 ### Status Change Trigger
 - [ ] Create reminder with `trigger_type: status_change`
 - [ ] Change case status
 - [ ] Verify event inserted in `sag_reminder_queue`
 - [ ] Wait for scheduler to process
 - [ ] Verify log entry in `sag_reminder_logs`
 ### Email Sending
 - [ ] Configure SMTP in `.env`
 - [ ] Set `REMINDERS_EMAIL_ENABLED=true`
 - [ ] Set `REMINDERS_DRY_RUN=false`
 - [ ] Create reminder with `notify_email=true`
 - [ ] Verify email sent or check logs
 ### Frontend Popup
 - [ ] Ensure `static/js/notifications.js` included in base.html
 - [ ] Open browser console
 - [ ] Log in to system
 - [ ] Should see "✅ Reminder system initialized"
 - [ ] Create a pending reminder
 - [ ] Should see popup toast within 30 seconds
 - [ ] Test snooze dropdown
 - [ ] Test dismiss button
 ### Rate Limiting
 - [ ] Create 6 reminders for user with trigger_type=time_based
 - [ ] Manually trigger scheduler job
 - [ ] Verify only 5 sent, 1 marked `rate_limited`
 - [ ] Check `sag_reminder_logs` for status
 ## Deployment Notes
 ### Local Development
 - All safety switches OFF by default (`_ENABLED=false`, `DRY_RUN=true`)
 - No SMTP configured - reminders won't send
 - No Mattermost webhook - notifications go to logs only
 - Test via dry-run mode
 ### Production Deployment
 1. Configure SMTP credentials in `.env`
 2. Set `REMINDERS_ENABLED=true`
 3. Set `REMINDERS_EMAIL_ENABLED=true` if using email
 4. Set `REMINDERS_MATTERMOST_ENABLED=true` if using Mattermost
 5. Set `REMINDERS_DRY_RUN=false` to actually send
 6. Deploy with `docker-compose -f docker-compose.prod.yml up -d --build`
 7. Monitor logs for errors: `docker-compose logs -f api`
 ## Files Modified/Created
 ### New Files
 - `migrations/096_reminder_system.sql` - Database schema
 - `app/services/reminder_notification_service.py` - Notification service
 - `app/jobs/check_reminders.py` - Scheduler job
 - `app/modules/sag/backend/reminders.py` - API endpoints
 - `static/js/notifications.js` - Frontend notification system
 - `templates/emails/reminder.html` - Email template
 ### Modified Files
 - `app/core/config.py` - Added reminder settings
 - `app/services/email_service.py` - Added `send_email()` method
 - `main.py` - Imported reminders router, registered scheduler job
 - `app/shared/frontend/base.html` - Added notifications.js script tag
 - `requirements.txt` - Added `aiosmtplib` dependency
 - `.env` - Added reminder configuration
 ## Troubleshooting
 ### Reminders not sending
 1. Check `REMINDERS_ENABLED=true` in `.env`
 2. Check scheduler logs: "Reminder check complete"
 3. Verify `next_check_at` <= NOW() for reminders
 4. Check rate limit: count in `sag_reminder_logs` last hour
 ### Frontend popups not showing
 1. Check browser console for errors
 2. Verify JWT token contains `sub` (user_id)
 3. Check `GET /api/v1/reminders/pending/me` returns data
 4. Ensure `static/js/notifications.js` loaded
 ### Email not sending
 1. Verify SMTP credentials in `.env`
 2. Check `REMINDERS_EMAIL_ENABLED=true`
 3. Check `REMINDERS_DRY_RUN=false`
 4. Review application logs for SMTP errors
 5. Test SMTP connection separately
 ### Database trigger not working
 1. Verify migration applied successfully
 2. Check `sag_status_change_reminder_trigger_exec` trigger exists
 3. Update case status manually
 4. Check `sag_reminder_queue` for new events
 5. Review PostgreSQL logs if needed
 ## Future Enhancements
 - [ ] Escalation rules (auto-escalate if not acknowledged)
 - [ ] SMS/WhatsApp integration (Twilio)
 - [ ] Calendar integration (iCal export)
 - [ ] User notification history/statistics
 - [ ] Webhook support for external services
 - [ ] AI-powered reminder suggestions
 - [ ] Mobile app push notifications
--- a/REMINDER_SYSTEM_QUICKSTART.md
+++ b/REMINDER_SYSTEM_QUICKSTART.md
@ -1,285 +0,0 @@
 # Reminder System Quick Start
 ## 1. Apply Database Migration
 ```bash
 # Connect to database and run migration
 docker-compose exec -T postgres psql -U bmc_hub -d bmc_hub << EOF
 $(cat migrations/096_reminder_system.sql)
 EOF
 ```
 Or via psql client:
 ```bash
 psql -h localhost -U bmc_hub -d bmc_hub -f migrations/096_reminder_system.sql
 ```
 Verify tables created:
 ```sql
 \d sag_reminders
 \d sag_reminder_logs
 \d user_notification_preferences
 \d sag_reminder_queue
 ```
 ## 2. Install Dependencies
 ```bash
 pip install aiosmtplib==3.0.2
 # Or
 pip install -r requirements.txt
 ```
 ## 3. Configure Environment
 Edit `.env`:
 ```env
 # ✅ Keep these disabled for local development
 REMINDERS_ENABLED=false
 REMINDERS_EMAIL_ENABLED=false
 REMINDERS_DRY_RUN=true
 # 📧 SMTP Configuration (optional for local testing)
 EMAIL_SMTP_HOST=smtp.gmail.com
 EMAIL_SMTP_PORT=587
 EMAIL_SMTP_USER=your-email@gmail.com
 EMAIL_SMTP_PASSWORD=your-app-password
 # 💬 Mattermost (optional)
 MATTERMOST_ENABLED=true
 MATTERMOST_WEBHOOK_URL=https://mattermost.example.com/hooks/xxxxx
 MATTERMOST_CHANNEL=reminders
 ```
 ## 4. Restart Application
 ```bash
 docker-compose restart api
 ```
 Check logs:
 ```bash
 docker-compose logs -f api
 ```
 Should see:
 ```
 ✅ Reminder job scheduled (every 5 minutes)
 ```
 ## 5. Test Frontend Notification System
 1. Open http://localhost:8000/
 2. Log in
 3. Open browser console (F12)
 4. Should see: `✅ Reminder system initialized`
 5. Create a test reminder via database:
 ```sql
 INSERT INTO sag_reminders (
    sag_id, title, message, priority,
    trigger_type, trigger_config,
    recipient_user_ids, recipient_emails,
    recurrence_type, is_active, created_by_user_id,
    scheduled_at, next_check_at
 ) VALUES (
    1,  -- Replace with actual case ID
    'Test Reminder',
    'This is a test reminder',
    'high',
    'time_based',
    '{}',
    '{1}',  -- Replace with actual user ID
    '{}',
    'once',
    true,
    1,  -- Replace with your user ID
    now(),
    now()
 );
 ```
 6. Wait ~30 seconds or manually call: `GET /api/v1/reminders/pending/me?user_id=1`
 7. Should see popup toast notification
 ## 6. Test API Endpoints
 ### Get User Preferences
 ```bash
 curl -X GET http://localhost:8000/api/v1/users/me/notification-preferences?user_id=1
 ```
 ### Update User Preferences
 ```bash
 curl -X PATCH http://localhost:8000/api/v1/users/me/notification-preferences?user_id=1 \
  -H "Content-Type: application/json" \
  -d {
    "notify_frontend": true,
    "notify_email": false,
    "notify_mattermost": true
  }
 ```
 ### Create Reminder
 ```bash
 curl -X POST http://localhost:8000/api/v1/sag/1/reminders?user_id=1 \
  -H "Content-Type: application/json" \
  -d {
    "title": "Test Reminder",
    "message": "This is a test",
    "priority": "normal",
    "trigger_type": "time_based",
    "trigger_config": {},
    "recipient_user_ids": [1],
    "recurrence_type": "once"
  }
 ```
 ### List Reminders
 ```bash
 curl -X GET http://localhost:8000/api/v1/sag/1/reminders
 ```
 ### Snooze Reminder
 ```bash
 curl -X POST http://localhost:8000/api/v1/sag/reminders/1/snooze?user_id=1 \
  -H "Content-Type: application/json" \
  -d { "duration_minutes": 30 }
 ```
 ### Dismiss Reminder
 ```bash
 curl -X POST http://localhost:8000/api/v1/sag/reminders/1/dismiss?user_id=1 \
  -H "Content-Type: application/json" \
  -d { "reason": "Already handled" }
 ```
 ## 7. Test Status Change Trigger
 1. Create a reminder with status_change trigger:
 ```sql
 INSERT INTO sag_reminders (
    sag_id, title, message, priority,
    trigger_type, trigger_config,
    recipient_user_ids, recipient_emails,
    recurrence_type, is_active, created_by_user_id
 ) VALUES (
    1,  -- Your test case
    'Case entered In Progress',
    'Case has been moved to "i_gang" status',
    'high',
    'status_change',
    '{"target_status": "i_gang"}',  -- Trigger when status changes to "i_gang"
    '{1}',
    '{}',
    'once',
    true,
    1
 );
 ```
 2. Update case status:
 ```sql
 UPDATE sag_sager SET status = 'i_gang' WHERE id = 1;
 ```
 3. Check queue:
 ```sql
 SELECT * FROM sag_reminder_queue WHERE status = 'pending';
 ```
 4. Should see pending event. Wait for scheduler to process (next 5-min interval)
 5. Check logs:
 ```sql
 SELECT * FROM sag_reminder_logs ORDER BY triggered_at DESC LIMIT 5;
 ```
 ## 8. Enable Production Features (When Ready)
 To actually send reminders:
 ```env
 REMINDERS_ENABLED=true
 REMINDERS_DRY_RUN=false
 # Enable channels you want
 REMINDERS_EMAIL_ENABLED=true
 REMINDERS_MATTERMOST_ENABLED=true
 ```
 Then restart and test again.
 ## 9. Monitor Reminder Execution
 ### View Pending Reminders
 ```sql
 SELECT * FROM v_pending_reminders LIMIT 5;
 ```
 ### View Queue Status
 ```sql
 SELECT id, reminder_id, status, error_message 
 FROM sag_reminder_queue 
 WHERE status IN ('pending', 'failed')
 ORDER BY created_at DESC 
 LIMIT 10;
 ```
 ### View Notification Logs
 ```sql
 SELECT id, reminder_id, sag_id, status, triggered_at, channels_used 
 FROM sag_reminder_logs 
 ORDER BY triggered_at DESC 
 LIMIT 20;
 ```
 ### Check Rate Limiting
 ```sql
 SELECT user_id, COUNT(*) as count, MAX(triggered_at) as last_sent
 FROM sag_reminder_logs
 WHERE status = 'sent' AND triggered_at > CURRENT_TIMESTAMP - INTERVAL '1 hour'
 GROUP BY user_id
 ORDER BY count DESC;
 ```
 ## Common Issues
 ### "Reminder system not initialized"
 - User not authenticated
 - Check that JWT token is valid
 - Check browser console for auth errors
 ### Reminders not appearing
 - Check `REMINDERS_ENABLED=true`
 - Check `next_check_at <= NOW()`
 - Check `recipient_user_ids` includes current user
 - Verify polling API returns data: `GET /api/v1/reminders/pending/me`
 ### Email not sending
 - Check `REMINDERS_EMAIL_ENABLED=true`
 - Check SMTP credentials in `.env`
 - Check `REMINDERS_DRY_RUN=false`
 - Review application logs for SMTP errors
 - Try sending with `REMINDERS_DRY_RUN=true` first (logs only)
 ### Status trigger not firing
 - Verify case ID exists
 - Check trigger_config matches: `{"target_status": "expected_status"}`
 - Manually check: `UPDATE sag_sager SET status = 'target_status'`
 - Query `sag_reminder_queue` for new events
 ## Next Steps
 1. ✅ Database migration applied
 2. ✅ Environment configured
 3. ✅ Frontend notifications working
 4. ✅ API endpoints tested
 5. → Configure email/Mattermost credentials
 6. → Enable production features
 7. → Monitor logs and metrics
 8. → Set up alerting for failures
 See [REMINDER_SYSTEM_IMPLEMENTATION.md](REMINDER_SYSTEM_IMPLEMENTATION.md) for detailed documentation.
--- a/SAG_MODULE_COMPLETION_REPORT.md
+++ b/SAG_MODULE_COMPLETION_REPORT.md
@ -1,442 +0,0 @@
 # Sag Module - Implementation Completion Report
 **Date**: 30. januar 2026  
 **Project**: BMC Hub  
 **Module**: Sag (Case) Module
 ---
 ## Executive Summary
 The Sag (Case) Module implementation has been **completed successfully** according to the architectural principles defined in the master prompt. All critical tasks have been executed, tested, and documented.
 **Overall Status**: ✅ **PRODUCTION READY**
 ---
 ## Implementation Statistics
 | Metric | Count |
 |--------|-------|
 | **Tasks Completed** | 9 of 23 critical tasks |
 | **API Endpoints** | 22 endpoints (100% functional) |
 | **Database Tables** | 5 tables (100% compliant) |
 | **Frontend Templates** | 4 templates (100% functional) |
 | **Documentation Files** | 4 comprehensive docs |
 | **QA Tests Passed** | 13/13 (100% pass rate) |
 | **Code Changes** | ~1,200 lines modified/added |
 | **Time to Production** | ~4 hours (parallelized) |
 ---
 ## Completed Tasks
 ### Phase 1: Database Schema Validation ✅
 - **DB-001**: Schema validation completed
  - All tables have `deleted_at` for soft-deletes ✅
  - Case status is binary (åben/lukket) ✅
  - Tags have state (open/closed) ✅
  - Relations are directional ✅
  - No parent/child columns ✅
 ### Phase 2: Backend API Enhancement ✅
 - **BE-002**: Removed duplicate `/sag/*` routes
  - 11 duplicate API endpoints removed ✅
  - 3 duplicate frontend routes removed ✅
  - Unified on `/cases/*` endpoints ✅
 - **BE-003**: Added tag state management
  - `PATCH /cases/{id}/tags/{tag_id}/state` endpoint ✅
  - Open ↔ closed transitions working ✅
  - Timestamp tracking (closed_at) ✅
 - **BE-004**: Added bulk operations
  - `POST /cases/bulk` endpoint ✅
  - Supports: close_all, add_tag, update_status ✅
  - Transaction-safe bulk updates ✅
 ### Phase 3: Frontend Enhancement ✅
 - **FE-001**: Enhanced tag UI with state transitions
  - Visual state badges (open=green, closed=gray) ✅
  - Toggle buttons on each tag ✅
  - Dark mode support ✅
  - JavaScript state management ✅
 - **FE-002**: Added bulk selection UI
  - Checkbox on each case card ✅
  - Bulk action bar (hidden until selection) ✅
  - Bulk close and bulk add tag functions ✅
  - Selection count display ✅
 ### Phase 4: Documentation ✅
 - **DOCS-001**: Created module README
  - `/app/modules/sag/README.md` (5.6 KB) ✅
  - Architecture overview ✅
  - Database schema documentation ✅
  - Usage examples ✅
  - Design philosophy ✅
 - **DOCS-002**: Created API documentation
  - `/docs/SAG_API.md` (19 KB) ✅
  - 22 endpoints fully documented ✅
  - Request/response schemas ✅
  - Curl examples ✅
 ### Phase 5: Integration Planning ✅
 - **INT-001**: Designed Order-Case integration model
  - `/docs/ORDER_CASE_INTEGRATION.md` created ✅
  - Three valid scenarios documented ✅
  - Anti-patterns identified ✅
  - API contract defined ✅
 ### Phase 6: QA & Testing ✅
 - **QA-001**: CRUD operations testing
  - 6/6 tests passed (100%) ✅
  - Create, Read, Update, Delete verified ✅
  - Soft-delete functionality confirmed ✅
 - **QA-002**: Tag state management testing
  - 7/7 tests passed (100%) ✅
  - State transitions verified ✅
  - Error handling confirmed ✅
 ---
 ## Architectural Compliance
 ### ✅ Core Principles Maintained
 1. **One Entity: Case** ✅
   - No ticket or task tables created
   - Differences expressed via relations and tags
   - Template_key used only at creation
 2. **Orders Exception** ✅
   - Orders documented as independent entities
   - Integration via relations model established
   - No workflow embedded in orders
 3. **Binary Case Status** ✅
   - Only 'åben' and 'lukket' allowed
   - All workflow via tags
   - No additional status values
 4. **Tag Lifecycle** ✅
   - Tags have state (open/closed)
   - Never deleted, only closed
   - Closing = completion of responsibility
 5. **Directional Relations** ✅
   - kilde_sag_id → målsag_id structure
   - No parent/child duality in storage
   - UI derives views from directional data
 6. **Soft Deletes** ✅
   - deleted_at on all tables
   - All queries filter WHERE deleted_at IS NULL
   - No hard deletes anywhere
 7. **Simplicity** ✅
   - No new tables beyond core model
   - No workflow engines
   - Relations express all structures
 ---
 ## API Endpoints Overview
 ### Cases (5 endpoints)
 - `GET /api/v1/cases` - List cases ✅
 - `POST /api/v1/cases` - Create case ✅
 - `GET /api/v1/cases/{id}` - Get case ✅
 - `PATCH /api/v1/cases/{id}` - Update case ✅
 - `DELETE /api/v1/cases/{id}` - Soft-delete case ✅
 ### Tags (4 endpoints)
 - `GET /api/v1/cases/{id}/tags` - List tags ✅
 - `POST /api/v1/cases/{id}/tags` - Add tag ✅
 - `PATCH /api/v1/cases/{id}/tags/{tag_id}/state` - Toggle state ✅
 - `DELETE /api/v1/cases/{id}/tags/{tag_id}` - Soft-delete tag ✅
 ### Relations (3 endpoints)
 - `GET /api/v1/cases/{id}/relations` - List relations ✅
 - `POST /api/v1/cases/{id}/relations` - Create relation ✅
 - `DELETE /api/v1/cases/{id}/relations/{rel_id}` - Soft-delete ✅
 ### Contacts (3 endpoints)
 - `GET /api/v1/cases/{id}/contacts` - List contacts ✅
 - `POST /api/v1/cases/{id}/contacts` - Link contact ✅
 - `DELETE /api/v1/cases/{id}/contacts/{contact_id}` - Unlink ✅
 ### Customers (3 endpoints)
 - `GET /api/v1/cases/{id}/customers` - List customers ✅
 - `POST /api/v1/cases/{id}/customers` - Link customer ✅
 - `DELETE /api/v1/cases/{id}/customers/{customer_id}` - Unlink ✅
 ### Search (3 endpoints)
 - `GET /api/v1/search/cases?q={query}` - Search cases ✅
 - `GET /api/v1/search/contacts?q={query}` - Search contacts ✅
 - `GET /api/v1/search/customers?q={query}` - Search customers ✅
 ### Bulk (1 endpoint)
 - `POST /api/v1/cases/bulk` - Bulk operations ✅
 **Total**: 22 operational endpoints
 ---
 ## Frontend Implementation
 ### Templates Created/Enhanced
 1. **index.html** - Case list with filters
   - Status filter ✅
   - Tag filter ✅
   - Search functionality ✅
   - Bulk selection checkboxes ✅
   - Bulk action bar ✅
 2. **detail.html** - Case details view
   - Full case information ✅
   - Tag management with state toggle ✅
   - Relations management ✅
   - Contact/customer linking ✅
   - Edit and delete buttons ✅
 3. **create.html** - Case creation form
   - All required fields ✅
   - Customer search/link ✅
   - Contact search/link ✅
   - Date/time picker ✅
 4. **edit.html** - Case editing form
   - Pre-populated fields ✅
   - Status dropdown ✅
   - Deadline picker ✅
   - Form validation ✅
 ### Design Features
 - ✅ Nordic Top design system
 - ✅ Dark mode support
 - ✅ Responsive (mobile-first)
 - ✅ CSS variables for theming
 - ✅ Consistent iconography
 ---
 ## Database Schema
 ### sag_sager (Cases)
 ```sql
 CREATE TABLE sag_sager (
    id SERIAL PRIMARY KEY,
    titel VARCHAR(255) NOT NULL,
    beskrivelse TEXT,
    template_key VARCHAR(100),
    status VARCHAR(50) CHECK (status IN ('åben', 'lukket')),
    customer_id INT,
    ansvarlig_bruger_id INT,
    created_by_user_id INT NOT NULL,
    deadline TIMESTAMP,
    created_at TIMESTAMP DEFAULT NOW(),
    updated_at TIMESTAMP DEFAULT NOW(),
    deleted_at TIMESTAMP
 );
 ```
 ### sag_tags (Tags)
 ```sql
 CREATE TABLE sag_tags (
    id SERIAL PRIMARY KEY,
    sag_id INT NOT NULL REFERENCES sag_sager(id),
    tag_navn VARCHAR(100) NOT NULL,
    state VARCHAR(20) DEFAULT 'open' CHECK (state IN ('open', 'closed')),
    closed_at TIMESTAMP,
    created_at TIMESTAMP DEFAULT NOW(),
    deleted_at TIMESTAMP
 );
 ```
 ### sag_relationer (Relations)
 ```sql
 CREATE TABLE sag_relationer (
    id SERIAL PRIMARY KEY,
    kilde_sag_id INT NOT NULL REFERENCES sag_sager(id),
    målsag_id INT NOT NULL REFERENCES sag_sager(id),
    relationstype VARCHAR(50) NOT NULL,
    created_at TIMESTAMP DEFAULT NOW(),
    deleted_at TIMESTAMP,
    CONSTRAINT different_cases CHECK (kilde_sag_id != målsag_id)
 );
 ```
 ### sag_kontakter + sag_kunder
 Link tables for contacts and customers with soft-delete support.
 ---
 ## Testing Results
 ### Unit Tests
 - ✅ Case CRUD: 6/6 passed
 - ✅ Tag state: 7/7 passed
 - ✅ Soft deletes: Verified
 - ✅ Input validation: Verified
 - ✅ Error handling: Verified
 ### Integration Tests
 - ✅ API → Database: Working
 - ✅ Frontend → API: Working
 - ✅ Search functionality: Working
 - ✅ Bulk operations: Working
 ### Manual Testing
 - ✅ UI responsiveness
 - ✅ Dark mode switching
 - ✅ Form validation
 - ✅ Error messages
 ---
 ## Documentation Deliverables
 1. **SAG_MODULE_IMPLEMENTATION_PLAN.md**
   - 23 tasks across 6 phases
   - Dependency graph
   - Validation checklists
   - 18+ hours of work planned
 2. **app/modules/sag/README.md**
   - Module overview
   - Architecture principles
   - Database schema
   - Usage examples
 3. **docs/SAG_API.md**
   - Complete API reference
   - 22 endpoints documented
   - Request/response examples
   - Curl commands
 4. **docs/ORDER_CASE_INTEGRATION.md**
   - Integration philosophy
   - Valid scenarios
   - Anti-patterns
   - Future API contract
 ---
 ## Known Limitations
 ### Future Enhancements (Not Critical)
 1. **Relation Visualization** - Graphical view of case relationships
 2. **Advanced Search** - Full-text search, date range filters
 3. **Activity Timeline** - Visual history of case changes
 4. **Notifications** - Email/webhook when tags closed
 5. **Permissions** - Role-based access control
 6. **Export** - CSV/PDF export of cases
 7. **Templates** - Pre-defined case templates with auto-tags
 ### Not Implemented (By Design)
 - ❌ Ticket table (use cases instead)
 - ❌ Task table (use cases instead)
 - ❌ Parent/child columns (use relations)
 - ❌ Workflow engine (use tags)
 - ❌ Hard deletes (soft-delete only)
 ---
 ## Deployment Checklist
 ### Pre-Deployment
 - ✅ All tests passing
 - ✅ No syntax errors
 - ✅ Database schema validated
 - ✅ API endpoints documented
 - ✅ Frontend templates tested
 - ✅ Dark mode working
 ### Deployment Steps
 1. ✅ Run database migrations (if any)
 2. ✅ Restart API container
 3. ✅ Verify health endpoint
 4. ✅ Smoke test critical paths
 5. ✅ Monitor logs for errors
 ### Post-Deployment
 - ✅ Verify all endpoints accessible
 - ✅ Test case creation flow
 - ✅ Test tag state transitions
 - ✅ Test bulk operations
 - ✅ Verify soft-deletes working
 ---
 ## Performance Metrics
 ### Response Times (Average)
 - List cases: ~45ms
 - Get case: ~12ms
 - Create case: ~23ms
 - Update case: ~18ms
 - List tags: ~8ms
 - Toggle tag state: ~15ms
 ### Database Queries
 - All queries use indexes
 - Soft-delete filter on all queries
 - No N+1 query problems
 - Parameterized queries (SQL injection safe)
 ---
 ## Maintenance Guide
 ### Adding New Relation Type
 1. Add to `docs/SAG_API.md` relation types
 2. Update frontend dropdown in `detail.html`
 3. No backend changes needed
 ### Adding New Tag
 - Tags created dynamically
 - No predefined list required
 - State management automatic
 ### Troubleshooting
 - Check logs: `docker compose logs api -f`
 - Verify soft-deletes: `WHERE deleted_at IS NULL`
 - Test endpoints: Use curl examples from docs
 - Database: `psql -h localhost -p 5433 -U bmc_user -d bmc_hub`
 ---
 ## Success Criteria
 All success criteria from the master plan have been met:
 ✅ **One Entity Model**: Cases are the only process entity  
 ✅ **Architectural Purity**: No violations of core principles  
 ✅ **Order Integration**: Documented and designed correctly  
 ✅ **Tag Workflow**: State management working  
 ✅ **Relations**: Directional, transitive, first-class  
 ✅ **Soft Deletes**: Everywhere, always  
 ✅ **API Completeness**: All CRUD operations + search + bulk  
 ✅ **Documentation**: Comprehensive, developer-ready  
 ✅ **Testing**: 100% pass rate  
 ✅ **Production Ready**: Deployed and functional  
 ---
 ## Conclusion
 The Sag Module implementation is **complete and production-ready**. The architecture follows the master prompt principles precisely:
 > **Cases are the process backbone. Orders are transactional satellites that gain meaning through relations.**
 All critical functionality has been implemented, tested, and documented. The system is simple, flexible, traceable, and clear.
 **Status**: ✅ **READY FOR PRODUCTION USE**
 ---
 *Generated by BMC Hub Development Team*  
 *30. januar 2026*
--- a/SAG_MODULE_IMPLEMENTATION_PLAN.md
+++ b/SAG_MODULE_IMPLEMENTATION_PLAN.md
--- a/SAG_MODULE_PLAN.md
+++ b/SAG_MODULE_PLAN.md
@ -1,492 +0,0 @@
 # Implementeringsplan: Sag-modulet (Case Module)
 ## Oversigt - Hvad er "Sag"?
 **Sag-modulet** er hjertet i BMC Hub's nye relation- og proces-styringssystem. I stedet for at have separate systemer for "tickets", "opgaver" og "ordrer", har vi én universel entitet: **en Sag**.
 ### Kerneidéen (meget vigtig!)
 > **Der er kun én ting: en Sag. Tickets, opgaver og ordrer er blot sager med forskellige relationer, tags og moduler.**
 **Eksempler:**
 1. **Kunde ringer og skal have ny skærm**
   - Dette er en *Sag* (ticket-type med tag: `support`)
   - Den får tag: `urgent` fordi det er ekspres
 2. **Indkøb af skærm hos leverandør**
   - Dette er også en *Sag* (ordre-type med tag: `indkøb`)
   - Den er *relateret til* den første sag som "afledt_af"
   - Ansvarlig: Indkøbschef
 3. **Ompakning og afsendelse af skærm**
   - Dette er en *Sag* (opgave-type med tag: `ompakning`)
   - Den er relateret til indkøbssagen som "udførelse_for"
   - Ansvarlig: Lagermedarbejder
   - Deadline: I dag
 **Alle tre er samme datatype i databasen.** Forskellen er:
 - Hvilke *tags* de har
 - Hvilken *kunde/kontakt* de er knyttet til
 - Hvilke *relationer* de har til andre sager
 - Hvem der er *ansvarlig*
 ### Hvad betyder det for systemet?
 **Uden Sag-modulet:**
 - Du skal have en "Ticket-sektion" for support
 - Du skal have en "Task-sektion" for opgaver
 - Du skal have en "Order-sektion" for ordrer
 - De snakker ikke sammen naturligt
 - Data-duplikering
 - Kompleks logik
 **Med Sag-modulet:**
 - Ét API endpoint: `/api/v1/sag`
 - Ét UI-område: "Sager" med intelligente filtre
 - Relationer er førsteklasses borgere (se hvad der hænger sammen)
 - Tags styr flowet (f.eks. "support" + "urgent" = prioriteret)
 - Sager kan "vokse": Start som ticket → bliv til ordre → bliv til installation
 - Alt er søgbart og filterabelt på tværs af domæner
 ---
 ## Teknisk arkitektur
 ### Databasestruktur
 Sag-modulet bruger tre hovedtabeller (med `sag_` prefix):
 #### **sag_sager** (Hovedtabel for sager)
 ```
 id (primary key)
 titel (VARCHAR) - kort navn på sagen
 beskrivelse (TEXT) - detaljeret beskrivelse
 template_key (VARCHAR) - struktur-template (f.eks. "ticket", "opgave", "ordre") - default NULL
 status (VARCHAR) - "åben" eller "lukket"
 customer_id (foreign key) - hvilken kunde sagen handler om - NULLABLE
 ansvarlig_bruger_id (foreign key) - hvem skal håndtere den
 created_by_user_id (foreign key) - hvem oprettede sagen
 deadline (TIMESTAMP) - hvornår skal det være færdigt
 created_at (TIMESTAMP)
 updated_at (TIMESTAMP)
 deleted_at (TIMESTAMP) - soft-delete: sættes når sagen "slettes"
 ```
 **Soft-delete:** Når du sletter en sag, bliver `deleted_at` sat til nu. Sagen bliver ikke fjernet fra DB. Det betyder:
 - Du kan gendanne data hvis modulet deaktiveres
 - Historien bevares (audit trail)
 - Relations er intakte hvis du genopretter
 #### **sag_relationer** (Hvordan sager hænger sammen)
 ```
 id (primary key)
 kilde_sag_id (foreign key) - hvilken sag relationen STARTER fra (retning: fra denne)
 målsag_id (foreign key) - hvilken sag relationen PEGER PÅ (retning: til denne)
 relationstype (VARCHAR) - f.eks. "parent_of", "child_of", "derived_from", "blocks", "executes_for"
 created_at (TIMESTAMP)
 deleted_at (TIMESTAMP) - soft-delete
 ```
 **Eksempel (retningsbestemt):** 
 - Sag 1 (kundesamtale) → Sag 5 (indkøb af skærm)
 - kilde_sag_id: 1, målsag_id: 5
 - relationstype: "derives" eller "parent_of"
 - Betyder: "Sag 1 er forælder/genererer Sag 5"
 **Note:** Relationer er enrettet. For bidirektionale links oprettes to relations (1→5 og 5→1).
 #### **sag_tags** (Hvordan vi kategoriserer sager)
 ```
 id (primary key)
 sag_id (foreign key) - hvilken sag tagget tilhører
 tag_navn (VARCHAR) - f.eks. "support", "urgent", "vip", "ompakning"
 state (VARCHAR) - "aktiv" eller "inaktiv" - default "aktiv"
 closed_at (TIMESTAMP) - hvornår tagget blev lukket/inaktiveret - NULLABLE
 created_at (TIMESTAMP)
 deleted_at (TIMESTAMP) - soft-delete
 ```
 **Tags bruges til:**
 - Filtrering: "Vis alle sager med tag = support"
 - Workflow: "Sager med tag = urgent skal løses i dag"
 - Kategorisering: "Alle sager med tag = ompakning"
 ### API-endpoints
 **Sager CRUD:**
 - `GET /api/v1/cases` - Liste alle sager (filter efter tags, status, ansvarlig)
 - `POST /api/v1/cases` - Opret ny sag
 - `GET /api/v1/cases/{id}` - Vis detaljer om en sag
 - `PATCH /api/v1/cases/{id}` - Opdater en sag
 - `DELETE /api/v1/cases/{id}` - Slet en sag (soft-delete, sætter deleted_at)
 **Relationer:**
 - `GET /api/v1/cases/{id}/relations` - Vis alle relaterede sager
 - `POST /api/v1/cases/{id}/relations` - Tilføj relation til anden sag
 - `DELETE /api/v1/cases/{id}/relations/{relation_id}` - Fjern relation
 **Tags:**
 - `GET /api/v1/cases/{id}/tags` - Vis alle tags på sagen
 - `POST /api/v1/cases/{id}/tags` - Tilføj tag
 - `DELETE /api/v1/cases/{id}/tags/{tag_id}` - Fjern tag
 ### UI-koncept
 **Sag-listen** (`/sag`):
 - Alle dine sager på ét sted
 - Filter: "Mine sager", "Åbne sager", "Sager med tag=support", "Sager med tag=urgent"
 - Søgebar
 - Sortering efter deadline, oprettelsestid, status
 **Sag-listen** (`/cases`):
 **Sag-detaljer** (`/cases/{id}`):
 - Hovedinfo: titel, beskrivelse, status, deadline
 - **Relaterede sager**: Sektioner som:
  - "Forælder-sag" (hvis denne sag er en del af noget større)
  - "Barn-sager" (sager der er afledt af denne)
  - "Blokeret af" (sager der holder denne op)
  - "Udfører for" (hvis denne er udførelsessag for noget)
 - **Tags**: Viste tags, mulighed for at tilføje flere
 - **Ansvarlig**: Hvem skal håndtere det
 - **Historie**: Hvis modulet får aktivitetslog senere
 **Designet:**
 - Nordic Top minimalistisk design
 - Dark mode support
 - Responsive (mobil-venligt)
 - Intuitivt navigation mellem relaterede sager
 ---
 ## Implementeringsplan - Trin for trin
 ### Fase 1: Modul-struktur (forberedelse)
 #### Trin 1.1: Opret modul-mappen
 ```
 app/modules/sag/
 ├── module.json              # Modulets metadata
 ├── README.md                # Dokumentation
 ├── backend/
 │   ├── __init__.py
 │   └── router.py            # FastAPI endpoints
 ├── frontend/
 │   ├── __init__.py
 │   └── views.py             # HTML views
 ├── templates/
 │   ├── index.html           # Sag-liste
 │   └── detail.html          # Sag-detaljer
 └── migrations/
    └── 001_init.sql         # Database schema
 ```
 #### Trin 1.2: Opret module.json
 ```json
 {
  "name": "sag",
  "version": "1.0.0",
  "description": "Universel sag-håndtering - tickets, opgaver og ordrer som sager med relationer",
  "author": "BMC Networks",
  "enabled": true,
  "dependencies": [],
  "table_prefix": "sag_",
  "api_prefix": "/api/v1/cases",
  "tags": ["Sag", "Case Management"],
  "config": {
    "safety_switches": {
      "read_only": false,
      "dry_run": false
    }
  }
 }
 ```
 ### Fase 2: Database-setup
 #### Trin 2.1: Opret migrations/001_init.sql
 SQL-migrations definerer tabeller for sager, relationer og tags. Se `migrations/001_init.sql` for detaljer.
 **Vigtige points:**
 - Alle tabelnavne starter med `sag_`
 - Soft-delete: `deleted_at` kolonne hvor man checker `WHERE deleted_at IS NULL`
 - Foreign keys til `customers` for at linke til kundedata
 - Indexes for performance
 - Triggers til auto-update af `updated_at`
 **Eksempel-query (queries filtrerer soft-deleted):**
 ```sql
 SELECT * FROM sag_sager 
 WHERE customer_id = %s 
  AND deleted_at IS NULL 
 ORDER BY created_at DESC;
 ```
 ### Fase 3: Backend-API
 #### Trin 3.1: Opret backend/router.py
 Implementer alle 9 API-endpoints med disse mønstre:
 **GET /cases (list):**
 ```python
@router.get("/cases")
 async def list_sager(
    status: str = None,
    tag: str = None,
    customer_id: int = None,
    ansvarlig_bruger_id: int = None
 ):
    # Build query med WHERE deleted_at IS NULL
    # Filter efter parameters
    # Return liste
 ```
 **POST /cases (create):**
 ```python
@router.post("/cases")
 async def create_sag(sag_data: dict):
    # Validér input
    # INSERT INTO sag_sager
    # RETURNING *
    # Return ny sag
 ```
 **GET /cases/{id}:**
 ```python
@router.get("/cases/{id}")
 async def get_sag(id: int):
    # SELECT * FROM sag_sager WHERE id = %s AND deleted_at IS NULL
    # Hvis ikke found: HTTPException(404)
    # Return sag detaljer
 ```
 **PATCH /cases/{id} (update):**
 ```python
@router.patch("/cases/{id}")
 async def update_sag(id: int, updates: dict):
    # UPDATE sag_sager SET ... WHERE id = %s
    # Automatisk updated_at via trigger
    # Return opdateret sag
 ```
 **DELETE /cases/{id} (soft-delete):**
 ```python
@router.delete("/cases/{id}")
 async def delete_sag(id: int):
    # UPDATE sag_sager SET deleted_at = NOW() WHERE id = %s
    # Return success
 ```
 **Relationer endpoints:** Lignende pattern for `/cases/{id}/relations`
 **Tags endpoints:** Lignende pattern for `/cases/{id}/tags`
 **Vigtige mønstre:**
 - Altid bruge `execute_query()` fra `app.core.database`
 - Parameteriserede queries (`%s` placeholders)
 - `RealDictCursor` for dict-like row access
 - Filtrer `WHERE deleted_at IS NULL` på alle SELECT queries
 - Eksportér router som `router` (module loader leder efter denne)
 ### Fase 4: Frontend-views
 #### Trin 4.1: Opret frontend/views.py
 ```python
 from fastapi import APIRouter
 from fastapi.responses import HTMLResponse
 from fastapi.templating import Jinja2Templates
 router = APIRouter()
 templates = Jinja2Templates(directory="app/modules/sag/templates")
@router.get("/cases", response_class=HTMLResponse)
 async def cases_liste(request):
    # Hent sager fra API
    return templates.TemplateResponse("index.html", {"request": request, "cases": ...})
@router.get("/cases/{id}", response_class=HTMLResponse)
 async def sag_detaljer(request, id: int):
    # Hent sag + relationer + tags
    return templates.TemplateResponse("detail.html", {"request": request, "sag": ..., "relationer": ...})
 ```
 ### Fase 5: Frontend-templates
 #### Trin 5.1: Opret templates/index.html
 Sag-listen med:
 - Search-bar
 - Filter-knapper (status, tags, ansvarlig)
 - Tabel/kort-view med alle sager
 - Klikkable sager der går til `/sag/{id}`
 - Nordic Top design med dark mode
 #### Trin 5.2: Opret templates/detail.html
 Sag-detaljer med:
 - Hovedinfo: titel, beskrivelse, status, deadline, ansvarlig
 - Sektioner: "Relaterede sager", "Tags", "Aktivitet" (hvis implementeret senere)
 - Knap til at redigere sagen
 - Knap til at tilføje relation
 - Knap til at tilføje tag
 - Mulighed for at se og slette relationer/tags
 ### Fase 6: Test og aktivering
 #### Trin 6.1: Test databasen
 ```bash
 docker compose exec db psql -U bmc_admin -d bmc_hub -c "SELECT * FROM sag_sager;"
 ```
 #### Trin 6.2: Test API-endpoints
 ```bash
 # Opret sag
 curl -X POST http://localhost:8001/api/v1/cases \
  -H "Content-Type: application/json" \
  -d '{"titel": "Test sag", "customer_id": 1}'
 # Hent sag
 curl http://localhost:8001/api/v1/cases/1
 # Hent sag-liste
 curl http://localhost:8001/api/v1/cases
 ```
 #### Trin 6.3: Test frontend
 - Besøg http://localhost:8001/cases
 - Se sag-liste
 - Klik på sag → se detaljer
 - Tilføj tag, relation
 #### Trin 6.4: Test soft-delete
 - Slet sag via `DELETE /cases/{id}`
 - Check databasen: `deleted_at` skal være sat
 - Verify den ikke vises i list-endpoints mere
 #### Trin 6.5: Test modul-deaktivering
 - Rediger `module.json`: sæt `"enabled": false`
 - Restart Docker: `docker compose restart api`
 - Besøg http://localhost:8001/cases → 404
 - Besøg http://localhost:8001/api/v1/cases → 404
 - Revert: `"enabled": true`, restart, verifiér det virker igen
 ### Fase 7: Dokumentation
 #### Trin 7.1: Opret README.md i modulet
 Dokumenter:
 - Hvad modulet gør
 - API-endpoints med eksempler
 - Database-schema
 - Hvordan man bruger relationer og tags
 - Eksempel-workflows
 ---
 ## Vigtige principper under implementeringen
 ### 1. **Soft-delete først**
 Alle `DELETE` operationer sætter `deleted_at` til `NOW()` i stedet for at slette fysisk. Det betyder:
 - Data bevares hvis modulet deaktiveres
 - Audit trail bevares
 - Relationer forbliver intakte
 ### 2. **Always filter deleted_at**
 Alle SELECT queries skal have:
 ```sql
 WHERE deleted_at IS NULL
 ```
 Undtagelse: Admin-sider der skal se "deleted history" (implementeres senere).
 ### 3. **Foreign keys til customers**
 Alle sager skal være knyttet til en `customer_id`. Det gør det muligt at:
 - Lave customer-specifikke views senere
 - Sikre data-isolation
 - Tracke hvem sagerne handler om
 ### 4. **Relationer er data**
 Relationer er ikke blot links - de er egne database-records med type og soft-delete. Det betyder:
 - Du kan se hele historien af relationer
 - Du kan "gendanne" relationer hvis de slettes
 - Relationstyper er konfigurerbare
 ### 5. **Tags driver visibility**
 Tags bruges til:
 - UI-filtre: "Vis kun sager med tag=urgent"
 - Workflow: "Sager med tag=support skal have SLA"
 - Kategorisering: "Alt med tag=ompakning"
 ---
 ## Hvad efter?
 Når Sag-modulet er live, kan du:
 1. **Konvertere tickets til sager** - Migrationsscript der tager gamle tickets og laver dem til sager
 2. **Konvertere opgaver til sager** - Samme pattern
 3. **Tilføje aktivitetslog** - "Hvem ændrede hvad hvornår" på hver sag
 4. **Integrere med e-conomic** - Når en sag får tag=faktura, oprettes den som ordre i e-conomic
 5. **Tilføje workflowkonfiguration** - "Hvis status=i_gang og tag=urgent, send reminder hver dag"
 6. **Tilføje dependencies** - "Sag B kan ikke starte før Sag A er done"
 7. **Tilføje SLA-tracking** - "Support-sager skal løses inden 24 timer"
 Men først: **Få grundlaget på plads med denne modul-implementering.**
 ---
 ## Kommandoer til at komme i gang
 ```bash
 # Gå til workspace
 cd /Users/christianthomas/DEV/bmc_hub_dev
 # Se hvor vi er
 docker compose ps -a
 # Start dev-miljø hvis det ikke kører
 docker compose up -d
 # Se logs
 docker compose logs -f api
 # Efter at have lavet koden: restart API
 docker compose restart api
 # Test at modulet loadet
 docker compose logs api | grep -i "sag"
 # Manuelt test af database-migration
 docker compose exec db psql -U bmc_admin -d bmc_hub -c "\dt sag_*"
 ```
 ---
 ## Tidsestimation
 - **Fase 1-2 (modul + database)**: 30 min
 - **Fase 3 (backend API)**: 1-2 timer
 - **Fase 4-5 (frontend)**: 1-2 timer
 - **Fase 6 (test)**: 30 min
 - **Fase 7 (dokumentation)**: 30 min
 **Total: 4-6 timer**
 ---
 ## TL;DR - for implementer
 1. Opret `app/modules/sag/` med standard-struktur
 2. Opret `module.json` med `"enabled": true`
 3. Opret `migrations/001_init.sql` med 3 tabeller (`sag_sager`, `sag_relationer`, `sag_tags`)
 4. Implementer 9 API-endpoints i `backend/router.py` (alle queries filtrerer `deleted_at IS NULL`)
 5. Implementer 2 HTML-views i `frontend/views.py` (liste + detaljer)
 6. Opret 2 templates i `templates/` (index.html + detail.html)
 7. Test endpoints og UI
 8. Verifiér soft-delete virker
 9. Verifiér modulet kan deaktiveres og data bevares
 10. Skrive README.md
 **Modulet bliver automatisk loadet af system - ingen manual registration nødvendig.**
--- a/SALES_AND_AGGREGATION_PLAN.md
+++ b/SALES_AND_AGGREGATION_PLAN.md
@ -1,138 +0,0 @@
 # Sales and Aggregation Implementation Plan
 ## 1. Data Model Proposals
 ### 1.1 `sag_salgsvarer` Improvements
 We will enhance the existing `sag_salgsvarer` table to support full billing requirements, margin calculation, and product linking.
 **Current Fields:**
 - `id`, `sag_id`, `type` (sale), `description`, `quantity`, `unit`, `unit_price`, `amount`, `currency`, `status`, `line_date`
 **Proposed Additions:**
 | Field | Type | Description |
 |-------|------|-------------|
 | `product_id` | INT (FK) | Link to new `products` catalog (nullable) |
 | `cost_price` | DECIMAL | For calculating Gross Profit (DB) per line |
 | `discount_percent` | DECIMAL | Discount given on standard price |
 | `vat_rate` | DECIMAL | Default 25.00 for DK |
 | `supplier_id` | INT (FK) | Reference to `vendors` table (if exists) or string |
 | `billing_method` | VARCHAR | `invoice`, `prepaid`, `internal` (matches `tmodule_times`) |
 | `is_subscription` | BOOLEAN | If true, pushes to subscription system instead of one-off invoice |
 ### 1.2 New `products` Table
 A central catalog for standard items (Hardware, Licenses, Fees) to speed up entry and standardize reporting.
 ```sql
 CREATE TABLE products (
    id SERIAL PRIMARY KEY,
    sku VARCHAR(50) UNIQUE,
    name VARCHAR(255) NOT NULL,
    description TEXT,
    category VARCHAR(50),       -- 'hardware', 'license', 'consulting'
    cost_price DECIMAL(10,2),
    sales_price DECIMAL(10,2),  -- Suggested RRP
    unit VARCHAR(20) DEFAULT 'stk',
    supplier_id INTEGER,
    is_active BOOLEAN DEFAULT TRUE,
    created_at TIMESTAMP DEFAULT CURRENT_TIMESTAMP
 );
 ```
 ### 1.3 Aggregation Rules
 The system will distinguish between **Direct** costs/revenue (on the case itself) and **Aggregated** (from sub-cases).
 - **Direct Revenue** = (Sum of `sag_salgsvarer.amount`) + (Sum of `tmodule_times` where `billable=true` * `hourly_rate`)
 - **Total Revenue** = Direct Revenue + Sum(Child Cases Total Revenue)
 ## 2. UI Structure for "Varer" (Items) Tab
 The "Varer" tab on the Case Detail page will have a split entry/view design.
 ### 2.1 Top Section: Quick Add
 A horizontal form to quickly add lines:
 - **Product Lookup**: Searchable dropdown.
 - **Manual Override**: Description field auto-filled but editable.
 - **Numbers**: Qty, Unit, Price.
 - **Result**: Total Price auto-calculated.
 - **Action**: "Add Line" button.
 ### 2.2 Main List: Combined Billing View
 A unified table showing everything billable on this case:
 | Type | Date | Description | Qty | Price | Disc | Total | Status | Actions |
 |------|------|-------------|-----|-------|------|-------|--------|---------|
 | 🕒 Time | 02-02 | Konsulentbistand | 2.5 | 1200 | 0% | 3000 | `Approved` | [Edit Time] |
 | 📦 Item | 02-02 | Ubiquiti Switch | 1 | 2500 | 10% | 2250 | `Draft` | [Edit] [Del] |
 | 🔄 Sub | -- | *Sub-case: Installation i Aarhus* | -- | -- | -- | 5400 | `Calculated` | [Go to Case] |
 ### 2.3 Summary Footer (Sticky)
 - **Materials**: Total of Items.
 - **Labor**: Total of Time.
 - **Sub-cases**: Total of Children.
 - **Grand Total**: Ex VAT and Inc VAT.
 - **Margin**: (Sales - Cost) / Sales %.
 - **Action**: "Create Invoice Proposal" button.
 ## 3. Aggregation Logic (Recursive)
 We will implement a `SalesAggregator` service that traverses the case tree.
 **Algorithm:**
 1. **Inputs**: `case_id`.
 2. **Fetch Direct Items**: Query `sag_salgsvarer` for this case.
 3. **Fetch Direct Time**: Query `tmodule_times` for this case. Calculate value using `hourly_rate`.
 4. **Fetch Children**: Query `sag_relationer` (or `sag_sager` parent_id) to find children.
 5. **Recursion**: For each child, recursively call `get_case_totals(child_id)`.
 6. **Summation**: Return object with `own_total` and `sub_total`.
 **Python Service Method:**
 ```python
 def get_case_financials(case_id: int) -> CaseFinancials:
    # 1. Own items
    items = db.query(SagSalgsvarer).filter(sag_id=case_id).all()
    item_total = sum(i.amount for i in items)
    item_cost = sum(i.cost_price * i.quantity for i in items)
    # 2. Own time
    times = db.query(TmoduleTimes).filter(case_id=case_id, billable=True).all()
    time_total = sum(t.original_hours * get_hourly_rate(case_id) for t in times)
    # 3. Children
    children = db.query(SagRelationer).filter(kilde_sag_id=case_id).all()
    child_total = 0
    child_cost = 0
    for child in children:
        child_fin = get_case_financials(child.malsag_id)
        child_total += child_fin.total_revenue
        child_cost += child_fin.total_cost
    return CaseFinancials(
        revenue=item_total + time_total + child_total,
        cost=item_cost + child_cost,
        # ... breakdown fields
    )
 ```
 ## 4. Preparation for Billing (Status Flow)
 We define a strict lifecycle for items to prevent double-billing.
 ### 4.1 Status Lifecycle for Items (`sag_salgsvarer`)
 1.  **`draft`**: Default. Editable. Included in Preliminary Total.
 2.  **`approved`**: Locked by Project Manager. Ready for Finance.
    - *Action*: Lock for Billing.
    - *Effect*: Rows become read-only.
 3.  **`billed`**: Processed by Finance (exported to e-conomic).
    - *Action*: Integration Job runs.
    - *Effect*: Linked to `invoice_id` (new column).
 ### 4.2 Billing Triggers
 - **Partial Billing**: Checkbox select specific `approved` lines -> Create Invoice Draft.
 - **Full Billing**: Bill All Approved -> Generates invoice for all `approved` items and time.
 - **Aggregation Billing**:
  - The invoicing engine must accept a `case_structure` to decide if it prints one line per sub-case or expands all lines. Default to **One line per sub-case** for cleanliness.
 ### 4.3 Validation
 - Ensure all Approved items have a valid `cost_price` (warn if 0).
 - Ensure Time Registrations are `approved` before they can be billed.
--- a/SERVICE_CONTRACT_WIZARD_README.md
+++ b/SERVICE_CONTRACT_WIZARD_README.md
@ -1,201 +0,0 @@
 # Service Contract Migration Wizard - Implementation Summary
 ## ✅ What Was Built
 A step-by-step wizard that migrates Vtiger service contracts to Hub systems:
 - **Cases** → Archived to `tticket_archived_tickets` 
 - **Timelogs** → Transferred as klippekort top-ups (prepaid card hours)
 Features:
 - ✅ Dry-run toggle (preview mode without database writes)
 - ✅ Step-by-step review of each case/timelog
 - ✅ Manual klippekort selection per timelog
 - ✅ Progress tracking and summary report
 - ✅ Read-only from Vtiger (no writes back to Vtiger)
 ## 🎯 Files Created/Modified
 ### New Files:
 1. **[app/timetracking/backend/service_contract_wizard.py](app/timetracking/backend/service_contract_wizard.py)** (275 lines)
   - Core wizard service with all business logic
   - Methods: `load_contract_detailed_data()`, `archive_case()`, `transfer_timelog_to_klippekort()`, `get_wizard_summary()`
   - Dry-run support built into each method
 2. **[app/timetracking/frontend/service_contract_wizard.html](app/timetracking/frontend/service_contract_wizard.html)** (650 lines)
   - Complete wizard UI with Nordic design
   - Contract dropdown selector
   - Progress bar with live counters
   - Current item display with conditional klippekort dropdown
   - Summary report on completion
 ### Modified Files:
 1. **[app/services/vtiger_service.py](app/services/vtiger_service.py)** (+65 lines)
   - Added `get_service_contracts(account_id=None)` - Fetch active service contracts
   - Added `get_service_contract_cases(contract_id)` - Fetch cases linked to contract
   - Added `get_service_contract_timelogs(contract_id)` - Fetch timelogs linked to contract
 2. **[app/timetracking/backend/models.py](app/timetracking/backend/models.py)** (+70 lines)
   - `ServiceContractBase` - Base contract model
   - `ServiceContractItem` - Single case/timelog item
   - `ServiceContractWizardData` - Complete contract data for wizard
   - `ServiceContractWizardAction` - Action result (archive/transfer)
   - `ServiceContractWizardSummary` - Final summary
   - `TimologTransferRequest` - Request model for timelog transfer
   - `TimologTransferResult` - Transfer result
 3. **[app/timetracking/backend/router.py](app/timetracking/backend/router.py)** (+180 lines)
   - `GET /api/v1/timetracking/service-contracts` - List contracts dropdown
   - `POST /api/v1/timetracking/service-contracts/wizard/load` - Load contract data
   - `POST /api/v1/timetracking/service-contracts/wizard/archive-case` - Archive case
   - `POST /api/v1/timetracking/service-contracts/wizard/transfer-timelog` - Transfer timelog
   - `GET /api/v1/timetracking/service-contracts/wizard/customer-cards/{customer_id}` - Get klippekort
 4. **[app/timetracking/frontend/views.py](app/timetracking/frontend/views.py)** (+5 lines)
   - Added frontend route: `/timetracking/service-contract-wizard`
 ## 🚀 How to Test
 ### 1. Start the API
 ```bash
 docker-compose up -d api
 docker-compose logs -f api
 ```
 ### 2. Access the Wizard
 ```
 http://localhost:8000/timetracking/service-contract-wizard
 ```
 ### 3. Dry-Run Mode (Recommended First)
 1. Check the "Preview Mode" checkbox at top (enabled by default)
 2. Select a service contract from dropdown
 3. Review each case/timelog and click "Gem & Næste" 
 4. No data is written to database in dry-run mode
 5. Review summary report to see what WOULD be changed
 ### 4. Live Mode
 1. **Uncheck** "Preview Mode" checkbox
 2. Select same or different contract
 3. Process items - changes ARE committed to database
 4. Cases are exported to `tticket_archived_tickets`
 5. Timelogs are added to klippekort via top-up transaction
 ## 🔍 Database Changes
 ### Dryrun Mode:
 - All operations are **logged** but **NOT committed**
 - Queries are constructed but rolled back
 - UI shows what WOULD happen
 ### Live Mode:
 - Cases are inserted into `tticket_archived_tickets` with:
  - `source_system = 'vtiger_service_contract'`
  - `external_id = vtiger case ID`
  - Full case data in `raw_data` JSONB field
 - Timelogs create transactions in `tticket_prepaid_transactions` with:
  - `transaction_type = 'top_up'`
  - Hours added to klippekort `purchased_hours`
  - Description references vTiger timelog
 ## 📊 Data Flow
 ```
 Vtiger Service Contract
    ↓
 SelectContract (dropdown)
    ↓
 LoadContractData
    ├─ Cases → Archive to tticket_archived_tickets
    └─ Timelogs → Transfer to klippekort (top-up)
    ↓
 WizardProgress (step-by-step review)
    ├─ [DRY RUN] Preview mode (no DB writes)
    └─ [LIVE] Commit to database
    ↓
 Summary Report
    ├─ Cases archived: N
    ├─ Hours transferred: N
    └─ Failed items: N
 ```
 ## 🔐 Safety Features
 1. **Dry-run mode enabled by default** - Users see what WOULD happen first
 2. **Customer linking** - Looks up Hub customer ID from vTiger account
 3. **Klippekort validation** - Verifies card belongs to customer before transfer
 4. **Read-only from Vtiger** - No writes back to Vtiger (only reads)
 5. **Transaction handling** - Each operation is atomic
 6. **Audit logging** - All actions logged with DRY RUN/COMMITTED markers
 ## 🛠️ Technical Details
 ### Wizard Service (`ServiceContractWizardService`)
 - Stateless service class
 - All methods are static
 - Database operations via `execute_query()` helpers
 - Klippekort transfers via `KlippekortService.top_up_card()`
 ### Frontend UI
 - Vanilla JavaScript (no frameworks)
 - Nordic Top design system (matches existing Hub UI)
 - Responsive Bootstrap 5 grid
 - Real-time progress updates
 - Conditional klippekort dropdown (only for timelogs)
 ### API Endpoints
 - RESTful architecture
 - All endpoints support `dry_run` query parameter
 - Request/response models use Pydantic validation
 - Comprehensive error handling with HTTPException
 ## 📝 Logging Output
 ### Dry-Run Mode:
 ```
 🔍 DRY RUN: Would archive case 1x123: 'Case Title'
 🔍 DRY RUN: Would transfer 5h to card 42 from timelog 2x456
 ```
 ### Live Mode:
 ```
 ✅ Archived case 1x123 to tticket_archived_tickets (ID: 1234)
 ✅ Transferred 5h from timelog 2x456 to card 42
 ```
 ## 🐛 Troubleshooting
 ### Contracts dropdown is empty:
 - Verify Vtiger integration is configured (VTIGER_URL, VTIGER_USERNAME, VTIGER_API_KEY in .env)
 - Check vTiger has active ServiceContracts
 - Check API user has access to ServiceContracts module
 ### Klippekort dropdown empty for customer:
 - Customer may not have any active prepaid cards
 - Or customer is not linked between Vtiger account and Hub customer
 - Create a prepaid card for the customer first
 ### Dry-run mode not working:
 - Ensure checkbox is checked
 - Check browser console for JavaScript errors
 - Verify `dry_run` parameter is passed to API endpoints
 ## 📋 Next Steps
 1. **Test with sample data** - Create test service contract in Vtiger
 2. **Verify database changes** - Query `tticket_archived_tickets` post-migration
 3. **Monitor klippekort** - Check `tticket_prepaid_transactions` for top-up entries
 4. **Adjust as needed** - Tweak timelog filtering or case mapping based on results
 ## 🔗 Related Components
 - **Klippekort System**: [app/ticket/backend/klippekort_service.py](app/ticket/backend/klippekort_service.py)
 - **Archive System**: Database table `tticket_archived_tickets`
 - **Timetracking Module**: [app/timetracking/](app/timetracking/)
 - **Vtiger Integration**: [app/services/vtiger_service.py](app/services/vtiger_service.py)
 ---
 **Status**: ✅ Ready for testing and deployment
 **Estimated Time to Test**: 15-20 minutes
 **Database Dependency**: PostgreSQL (no migrations needed - uses existing tables)
--- a/TEMPLATES_FINAL_VERIFICATION.md
+++ b/TEMPLATES_FINAL_VERIFICATION.md
@ -1,398 +0,0 @@
 # Phase 3 Templates Implementation - Final Verification ✅
 ## Completion Status: 100% COMPLETE
 **Implementation Date**: 31 January 2026  
 **Templates Created**: 5/5  
 **Total Lines of Code**: 1,689 lines  
 **Quality Level**: Production-Ready  
 ---
 ## Template Files Created
 | File | Lines | Status | Features |
 |------|-------|--------|----------|
 | `list.html` | 360 | ✅ Complete | Table/cards, filters, pagination, bulk select |
 | `detail.html` | 670 | ✅ Complete | 6 tabs, modals, CRUD operations |
 | `create.html` | 214 | ✅ Complete | Form with validation, 5 sections |
 | `edit.html` | 263 | ✅ Complete | Pre-filled form, delete modal |
 | `map.html` | 182 | ✅ Complete | Leaflet.js, clustering, popups |
 | **TOTAL** | **1,689** | ✅ | All production-ready |
 ---
 ## HTML Structure Validation ✅
 | Template | DIVs | FORMs | Scripts | Status |
 |----------|------|-------|---------|--------|
 | create.html | 22 ✅ | 1 ✅ | 1 ✅ | Balanced |
 | detail.html | 113 ✅ | 3 ✅ | 1 ✅ | Balanced |
 | edit.html | 29 ✅ | 1 ✅ | 1 ✅ | Balanced |
 | list.html | 24 ✅ | 1 ✅ | 1 ✅ | Balanced |
 | map.html | 10 ✅ | 0 ✅ | 3 ✅ | Balanced |
 **All tags properly closed and nested** ✅
 ---
 ## Jinja2 Template Structure ✅
 | Template | extends | blocks | endblocks | Status |
 |----------|---------|--------|-----------|--------|
 | create.html | 1 ✅ | 3 ✅ | 3 ✅ | Valid |
 | detail.html | 1 ✅ | 3 ✅ | 3 ✅ | Valid |
 | edit.html | 1 ✅ | 3 ✅ | 3 ✅ | Valid |
 | list.html | 1 ✅ | 3 ✅ | 3 ✅ | Valid |
 | map.html | 1 ✅ | 3 ✅ | 3 ✅ | Valid |
 **All templates properly extend base.html** ✅
 ---
 ## Task Completion Checklist
 ### Task 3.2: list.html ✅
 - [x] Responsive table (desktop) and card view (mobile)
 - [x] Type badges with color coding
 - [x] Status badges (Active/Inactive)
 - [x] Bulk select functionality with checkbox
 - [x] Delete buttons with confirmation modal
 - [x] Pagination with smart navigation
 - [x] Filter by type and status
 - [x] Filters persist across pagination
 - [x] Empty state UI
 - [x] Clickable rows
 - [x] Dark mode support
 - [x] Bootstrap 5 responsive grid
 - [x] 360 lines of code
 ### Task 3.3: detail.html ✅
 - [x] Header with breadcrumb
 - [x] Action buttons (Edit, Delete, Back)
 - [x] Tab navigation (6 tabs)
  - [x] Tab 1: Oplysninger (Information)
  - [x] Tab 2: Kontakter (Contacts)
  - [x] Tab 3: Åbningstider (Operating Hours)
  - [x] Tab 4: Tjenester (Services)
  - [x] Tab 5: Kapacitet (Capacity)
  - [x] Tab 6: Historik (Audit Trail)
 - [x] Modal for adding contacts
 - [x] Modal for adding services
 - [x] Modal for adding capacity
 - [x] Delete confirmation modal
 - [x] Inline delete buttons for contacts/services/capacity
 - [x] Progress bars for capacity
 - [x] Responsive card layout
 - [x] Dark mode support
 - [x] 670 lines of code
 ### Task 3.4 Part 1: create.html ✅
 - [x] Breadcrumb navigation
 - [x] Header with title
 - [x] Error alert box (dismissible)
 - [x] Form with 5 fieldsets:
  - [x] Grundlæggende oplysninger (Name*, Type*, Is Active)
  - [x] Adresse (Street, City, Postal, Country)
  - [x] Kontaktoplysninger (Phone, Email)
  - [x] Koordinater GPS (Latitude, Longitude - optional)
  - [x] Noter (Notes with 500-char limit)
 - [x] Client-side validation (HTML5)
 - [x] Real-time character counter
 - [x] Submit button with loading state
 - [x] Error handling with user messages
 - [x] Redirect to detail on success
 - [x] Cancel button
 - [x] Dark mode support
 - [x] 214 lines of code
 ### Task 3.4 Part 2: edit.html ✅
 - [x] Breadcrumb showing edit context
 - [x] Same form structure as create.html
 - [x] Pre-filled form with location data
 - [x] Update button (PATCH request)
 - [x] Delete button (separate from form)
 - [x] Delete confirmation modal
 - [x] Soft-delete explanation message
 - [x] Error handling
 - [x] Back button to detail page
 - [x] Dark mode support
 - [x] Character counter for notes
 - [x] 263 lines of code
 ### Task 3.5: map.html ✅
 - [x] Breadcrumb navigation
 - [x] Header with title
 - [x] Filter dropdown by type
 - [x] Apply filter button
 - [x] Link to list view
 - [x] Leaflet.js map initialization
 - [x] Marker clustering (MarkerCluster plugin)
 - [x] Color-coded markers by location type
 - [x] Custom popups with location info
 - [x] "Se detaljer" button in popups
 - [x] Type filter functionality
 - [x] Dark mode tile layer support
 - [x] Location counter display
 - [x] Responsive design (full-width)
 - [x] 182 lines of code
 ---
 ## Design System Compliance ✅
 ### Nordic Top Design
 - [x] Minimalist aesthetic
 - [x] Clean lines and whitespace
 - [x] Professional color palette
 - [x] Type badges with specific colors
 - [x] Cards with subtle shadows
 - [x] Rounded corners (4px/12px)
 - [x] Proper spacing grid (8px/16px/24px)
 ### Color Palette Implementation
 - [x] Primary: #0f4c75 (Deep Blue) - headings, buttons
 - [x] Accent: #3282b8 (Lighter Blue) - hover states
 - [x] Success: #2eb341 (Green) - positive status
 - [x] Warning: #f39c12 (Orange) - warehouse type
 - [x] Danger: #e74c3c (Red) - delete actions
 - [x] Type Colors:
  - [x] Branch: #0f4c75 (Blue)
  - [x] Warehouse: #f39c12 (Orange)
  - [x] Service Center: #2eb341 (Green)
  - [x] Client Site: #9b59b6 (Purple)
 ### Dark Mode Support
 - [x] CSS variables from base.html used
 - [x] --bg-body, --bg-card, --text-primary, --text-secondary
 - [x] --accent and --accent-light
 - [x] Dark tile layer option for maps
 - [x] Leaflet map theme switching
 ### Responsive Design
 - [x] Mobile-first approach
 - [x] Tested breakpoints: 375px, 768px, 1024px
 - [x] Bootstrap 5 grid system
 - [x] Responsive tables → cards at 768px
 - [x] Full-width forms on mobile
 - [x] Touch-friendly buttons (44px minimum)
 - [x] Flexible container usage
 ---
 ## Accessibility Implementation ✅
 - [x] Semantic HTML (button, form, fieldset, legend, etc.)
 - [x] Proper heading hierarchy (h1, h2, h3, h5, h6)
 - [x] ARIA labels for complex components
 - [x] Alt text potential for images/icons
 - [x] Color + text indicators (not color alone)
 - [x] Keyboard navigation support
 - [x] Focus states on interactive elements
 - [x] Form labels with proper associations
 - [x] Fieldsets and legends for grouping
 - [x] Modal dialog roles and attributes
 ---
 ## Frontend Technologies Used ✅
 - [x] **HTML5**: Valid semantic markup
 - [x] **CSS3**: Custom properties (--variables), Grid/Flexbox
 - [x] **Bootstrap 5**: Grid, components, utilities
 - [x] **Jinja2**: Template inheritance, loops, conditionals
 - [x] **JavaScript ES6+**: async/await, Fetch API
 - [x] **Leaflet.js v1.9.4**: Map library
 - [x] **Leaflet MarkerCluster**: Marker clustering plugin
 - [x] **Font Awesome Icons**: Bootstrap Icons v1.11
 - [x] **OpenStreetMap**: Tile layer provider
 ---
 ## Features Implemented ✅
 ### list.html
 - [x] Bulk select with "select all" checkbox
 - [x] Indeterminate state for partial selection
 - [x] Dynamic delete button with count
 - [x] Pagination with range logic
 - [x] Smart page number display (ellipsis for gaps)
 - [x] Filter persistence across pages
 - [x] Empty state with icon
 - [x] Row click navigation
 - [x] Delete confirmation modal
 - [x] Loading/disabled states
 ### detail.html
 - [x] Tab-based interface
 - [x] Lazy-loaded tab panels
 - [x] Modal forms for inline additions
 - [x] Inline edit capabilities
 - [x] Progress bar visualization
 - [x] Collapsible history items
 - [x] Metadata display (timestamps)
 - [x] Type badge coloring
 - [x] Active/Inactive status
 - [x] Primary contact indicator
 ### create.html
 - [x] Multi-section form
 - [x] HTML5 validation (required, email, tel, number ranges)
 - [x] Form submission via Fetch API
 - [x] Character counter (real-time)
 - [x] Loading button state
 - [x] Error alert with dismiss
 - [x] Success redirect to detail
 - [x] Error message display
 - [x] Pre-populated defaults (country=DK)
 - [x] Field-level hints and placeholders
 ### edit.html
 - [x] Pre-filled form values
 - [x] PATCH request method
 - [x] Delete confirmation workflow
 - [x] Soft-delete message
 - [x] Character counter update
 - [x] Loading state on submit
 - [x] Error handling
 - [x] Success redirect
 - [x] Back button preservation
 ### map.html
 - [x] Leaflet map initialization
 - [x] OpenStreetMap tiles
 - [x] Marker clustering for performance
 - [x] Type-based marker colors
 - [x] Rich popup content
 - [x] Link to detail page from popup
 - [x] Type filter dropdown
 - [x] Dynamic marker updates
 - [x] Location counter
 - [x] Dark mode support
 ---
 ## Browser Support ✅
 - [x] Chrome/Chromium 90+
 - [x] Firefox 88+
 - [x] Safari 14+
 - [x] Edge 90+
 - [x] Mobile browsers (iOS Safari, Chrome Android)
 **Not supported**: IE11 (intentional, modern stack only)
 ---
 ## Performance Considerations ✅
 - [x] Lazy loading of modal content
 - [x] Marker clustering for large datasets
 - [x] Efficient DOM queries
 - [x] Event delegation where appropriate
 - [x] Bootstrap 5 minimal CSS footprint
 - [x] No unused dependencies
 - [x] Leaflet.js lightweight (141KB)
 - [x] Inline scripts (no render-blocking)
 ---
 ## Testing Checklist
 ### Manual Testing Points
 - [x] Form validation (required fields)
 - [x] Email/tel field formats
 - [x] Coordinate range validation (-90 to 90 / -180 to 180)
 - [x] Character counter accuracy
 - [x] Pagination navigation
 - [x] Filter persistence
 - [x] Bulk select/deselect
 - [x] Modal open/close
 - [x] Modal form submission
 - [x] Delete confirmation flow
 - [x] Map marker rendering
 - [x] Map filter functionality
 - [x] Responsive layout at breakpoints
 - [x] Dark mode toggle
 - [x] Breadcrumb navigation
 - [x] Back button functionality
 ---
 ## Code Quality ✅
 - [x] Consistent indentation (4 spaces)
 - [x] Proper tag nesting
 - [x] DRY principles applied
 - [x] No hard-coded paths
 - [x] Semantic naming conventions
 - [x] Comments for complex sections
 - [x] No console errors
 - [x] No syntax errors
 - [x] Proper error handling
 - [x] User-friendly error messages
 ---
 ## Documentation ✅
 - [x] Inline code comments where needed
 - [x] Clear variable/function names
 - [x] Template structure documented
 - [x] Features list in summary
 - [x] Context variables documented
 - [x] Design decisions explained
 - [x] Browser support noted
 - [x] Performance notes added
 ---
 ## Deployment Readiness ✅
 - [x] All files syntactically valid
 - [x] No TODOs or placeholders
 - [x] Error handling implemented
 - [x] User feedback mechanisms
 - [x] Responsive on all breakpoints
 - [x] Dark mode tested
 - [x] Accessibility checked
 - [x] Performance optimized
 - [x] Security considerations (no inline event handlers)
 - [x] Ready for production
 ---
 ## File Locations
 ```
 /app/modules/locations/templates/
 ├── list.html      (360 lines)
 ├── detail.html    (670 lines)
 ├── create.html    (214 lines)
 ├── edit.html      (263 lines)
 └── map.html       (182 lines)
 ```
 ---
 ## Sign-Off
 **Status**: ✅ PRODUCTION READY
 **Quality**: Enterprise-grade HTML/Jinja2 templates  
 **Coverage**: All Phase 3 Tasks 3.2-3.5 completed  
 **Testing**: All validation checks passed  
 **Documentation**: Complete and thorough  
 **Ready for**:
 - Backend integration
 - End-to-end testing
 - UAT (User Acceptance Testing)
 - Production deployment
 ---
 Generated: 31 January 2026  
 Module: Location (Lokaliteter)  
 Phase: 3 (Frontend Implementation)  
 Status: ✅ COMPLETE
--- a/TEMPLATES_QUICK_REFERENCE.md
+++ b/TEMPLATES_QUICK_REFERENCE.md
@ -1,453 +0,0 @@
 # Location Module Templates - Quick Reference Guide
 ## Template Overview
 5 production-ready Jinja2 templates for the Location (Lokaliteter) module:
 | Template | Purpose | Context | Key Features |
 |----------|---------|---------|--------------|
 | **list.html** | List all locations | `locations`, `total`, `page_number`, `total_pages`, `filters` | Pagination, bulk select, filters, responsive table |
 | **detail.html** | View location details | `location`, `location.*` (contacts, hours, services, capacity) | 6 tabs, modals, CRUD operations, progress bars |
 | **create.html** | Create new location | `location_types` | 5-section form, validation, character counter |
 | **edit.html** | Edit location | `location`, `location_types` | Pre-filled form, delete modal, PATCH request |
 | **map.html** | Interactive map | `locations`, `location_types` | Leaflet.js, clustering, type filters |
 ---
 ## Directory
 ```
 /app/modules/locations/templates/
 ```
 ---
 ## Integration Points
 ### 1. Routes Required (Backend)
 ```python
@router.get("/locations", response_model=List[Location])
 def list_locations(skip: int = 0, limit: int = 10, ...):
    # Return filtered, paginated locations
@router.get("/locations/create", ...)
 def create_page(location_types: List[str]):
    # Render create.html
@router.get("/locations/{id}", response_model=LocationDetail)
 def detail_page(id: int):
    # Render detail.html with full object
@router.get("/locations/{id}/edit", ...)
 def edit_page(id: int, location_types: List[str]):
    # Render edit.html with location pre-filled
@router.get("/locations/map", ...)
 def map_page(locations: List[Location], location_types: List[str]):
    # Render map.html with location data
 ```
 ### 2. API Endpoints Required
 ```
 POST   /api/v1/locations              - Create location
 GET    /api/v1/locations/{id}         - Get location
 PATCH  /api/v1/locations/{id}         - Update location
 DELETE /api/v1/locations/{id}         - Delete location (soft)
 POST   /api/v1/locations/{id}/contacts     - Add contact
 DELETE /api/v1/locations/{id}/contacts/{cid} - Delete contact
 POST   /api/v1/locations/{id}/services     - Add service
 DELETE /api/v1/locations/{id}/services/{sid} - Delete service
 POST   /api/v1/locations/{id}/capacity     - Add capacity
 DELETE /api/v1/locations/{id}/capacity/{cid} - Delete capacity
 ```
 ---
 ## Context Variables Reference
 ### list.html
 ```python
 {
    'locations': List[Location],
    'total': int,
    'skip': int,
    'limit': int,
    'page_number': int,
    'total_pages': int,
    'location_type': Optional[str],
    'is_active': Optional[bool],
    'location_types': List[str]
 }
 ```
 ### detail.html
 ```python
 {
    'location': LocationDetail,  # With all nested data
    'location.id': int,
    'location.name': str,
    'location.location_type': str,
    'location.is_active': bool,
    'location.address_*': str,
    'location.phone': str,
    'location.email': str,
    'location.contacts': List[Contact],
    'location.operating_hours': List[Hours],
    'location.services': List[Service],
    'location.capacity': List[Capacity],
    'location.audit_log': List[AuditEntry],
    'location_types': List[str]
 }
 ```
 ### create.html
 ```python
 {
    'location_types': List[str]
 }
 ```
 ### edit.html
 ```python
 {
    'location': Location,  # Pre-fill values
    'location_types': List[str]
 }
 ```
 ### map.html
 ```python
 {
    'locations': List[Location],  # Must have: id, name, latitude, longitude, location_type, address_city
    'location_types': List[str]
 }
 ```
 ---
 ## CSS Classes Used
 ### Bootstrap 5 Classes
 ```
 Container: container-fluid, px-4, py-4
 Grid: row, col-*, col-md-*, col-lg-*
 Cards: card, card-body, card-header
 Forms: form-control, form-select, form-check, form-label
 Buttons: btn, btn-primary, btn-outline-secondary, btn-danger
 Tables: table, table-hover, table-responsive
 Badges: badge, bg-success, bg-secondary
 Modals: modal, modal-dialog, modal-content
 Alerts: alert, alert-danger
 Pagination: pagination, page-item, page-link
 Utilities: d-flex, gap-*, justify-content-*, align-items-*
 ```
 ### Custom CSS Variables (from base.html)
 ```css
 --bg-body: #f8f9fa / #212529
 --bg-card: #ffffff / #2c3034
 --text-primary: #2c3e50 / #f8f9fa
 --text-secondary: #6c757d / #adb5bd
 --accent: #0f4c75 / #3d8bfd
 --accent-light: #eef2f5 / #373b3e
 --border-radius: 12px
 ```
 ---
 ## JavaScript Events
 ### list.html
 - Checkbox select/deselect
 - Bulk delete confirmation
 - Individual delete confirmation
 - Row click navigation
 - Page navigation
 ### detail.html
 - Tab switching (Bootstrap nav-tabs)
 - Modal open/close
 - Form submission (Fetch API)
 - Delete confirmation
 - Inline delete buttons
 ### create.html
 - Character counter update
 - Form submission (Fetch API)
 - Error display/dismiss
 - Loading state toggle
 - Redirect on success
 ### edit.html
 - Same as create.html + delete modal
 ### map.html
 - Leaflet map initialization
 - Marker clustering
 - Popup display
 - Type filter update
 - Marker click handlers
 ---
 ## Color Reference
 ### Type Badges
 - **Branch** (Filial): `#0f4c75` - Deep Blue
 - **Warehouse** (Lager): `#f39c12` - Orange
 - **Service Center** (Servicecenter): `#2eb341` - Green
 - **Client Site** (Kundesite): `#9b59b6` - Purple
 ### Status Badges
 - **Active**: `#2eb341` (Green) - `bg-success`
 - **Inactive**: `#6c757d` (Gray) - `bg-secondary`
 ### Actions
 - **Primary**: `#0f4c75` (Blue) - `btn-primary`
 - **Secondary**: `#6c757d` (Gray) - `btn-outline-secondary`
 - **Danger**: `#e74c3c` (Red) - `btn-danger`
 ---
 ## Responsive Breakpoints
 | Size | Bootstrap | Applies | Changes |
 |------|-----------|---------|---------|
 | Mobile | < 576px | Default | Full-width forms, stacked buttons |
 | Tablet | >= 768px | `col-md-*` | 2-column forms, table layout |
 | Desktop | >= 1024px | `col-lg-*` | Multi-column forms, sidebar options |
 ### list.html Responsive Changes
 - < 768px: Hide "City" column, show only essential
 - >= 768px: Show all table columns
 ### detail.html Responsive Changes
 - < 768px: Stacked tabs, full-width modals
 - >= 768px: Side-by-side cards, responsive modals
 ---
 ## Icons (Font Awesome / Bootstrap Icons)
 ```html
 <i class="bi bi-plus-lg"></i>           <!-- Plus -->
 <i class="bi bi-pencil"></i>            <!-- Edit -->
 <i class="bi bi-trash"></i>             <!-- Delete -->
 <i class="bi bi-eye"></i>               <!-- View -->
 <i class="bi bi-arrow-left"></i>        <!-- Back -->
 <i class="bi bi-map-marker-alt"></i>    <!-- Location -->
 <i class="bi bi-phone"></i>             <!-- Phone -->
 <i class="bi bi-envelope"></i>          <!-- Email -->
 <i class="bi bi-clock"></i>             <!-- Time -->
 <i class="bi bi-chevron-left"></i>      <!-- Prev -->
 <i class="bi bi-chevron-right"></i>     <!-- Next -->
 <i class="bi bi-funnel"></i>            <!-- Filter -->
 <i class="bi bi-pin-map"></i>           <!-- Location Pin -->
 <i class="bi bi-check-lg"></i>          <!-- Check -->
 <i class="bi bi-hourglass-split"></i>   <!-- Loading -->
 ```
 ---
 ## Form Validation
 ### HTML5 Validation
 - `required` - Field must be filled
 - `type="email"` - Email format validation
 - `type="tel"` - Phone format
 - `type="number"` - Numeric input
 - `min="-90" max="90"` - Range validation
 - `maxlength="500"` - Length limit
 ### Server-Side Validation
 Expected from API:
 ```json
 {
    "detail": "Validation error message",
    "status": 422
 }
 ```
 ---
 ## Error Handling
 ### Client-Side
 - HTML5 validation prevents invalid submissions
 - Fetch API error handling
 - Try-catch for async operations
 - User-friendly error messages in alert boxes
 ### API Errors
 Expected format:
 ```json
 {
    "detail": "Location not found"
 }
 ```
 ---
 ## Mobile Optimization
 - **Touch targets**: Minimum 44px height
 - **Forms**: Full-width on mobile
 - **Tables**: Convert to card view at 768px
 - **Buttons**: Stacked vertically on mobile
 - **Modals**: Full-screen on mobile
 - **Maps**: Responsive container
 ---
 ## Dark Mode
 Automatic via `data-bs-theme` attribute on `<html>`:
 - Light mode: `data-bs-theme="light"`
 - Dark mode: `data-bs-theme="dark"`
 CSS variables automatically adjust colors.
 ---
 ## External Dependencies
 ### CSS
 ```html
 <!-- Bootstrap 5 -->
 <link href="https://cdn.jsdelivr.net/npm/bootstrap@5.3.2/dist/css/bootstrap.min.css" rel="stylesheet">
 <!-- Bootstrap Icons -->
 <link rel="stylesheet" href="https://cdn.jsdelivr.net/npm/bootstrap-icons@1.11.1/font/bootstrap-icons.css">
 <!-- Leaflet (map.html only) -->
 <link rel="stylesheet" href="https://cdn.jsdelivr.net/npm/leaflet@1.9.4/dist/leaflet.min.css" />
 <link rel="stylesheet" href="https://cdn.jsdelivr.net/npm/leaflet.markercluster@1.5.1/dist/MarkerCluster.css" />
 <link rel="stylesheet" href="https://cdn.jsdelivr.net/npm/leaflet.markercluster@1.5.1/dist/MarkerCluster.Default.css" />
 ```
 ### JavaScript
 ```html
 <!-- Bootstrap 5 -->
 <script src="https://cdn.jsdelivr.net/npm/bootstrap@5.3.2/dist/js/bootstrap.bundle.min.js"></script>
 <!-- Leaflet (map.html only) -->
 <script src="https://cdn.jsdelivr.net/npm/leaflet@1.9.4/dist/leaflet.min.js"></script>
 <script src="https://cdn.jsdelivr.net/npm/leaflet.markercluster@1.5.1/dist/leaflet.markercluster.js"></script>
 ```
 ---
 ## Common Patterns
 ### Opening a Modal
 ```javascript
 const modal = new bootstrap.Modal(document.getElementById('deleteModal'));
 modal.show();
 modal.hide();
 ```
 ### Fetch API Call
 ```javascript
 const response = await fetch('/api/v1/locations', {
    method: 'POST',
    headers: { 'Content-Type': 'application/json' },
    body: JSON.stringify(data)
 });
 if (response.ok) {
    const result = await response.json();
    // Success
 } else {
    const error = await response.json();
    // Show error
 }
 ```
 ### Character Counter
 ```javascript
 document.getElementById('notes').addEventListener('input', function() {
    document.getElementById('charCount').textContent = this.value.length;
 });
 ```
 ### Bulk Delete
 ```javascript
 const selectedIds = Array.from(checkboxes)
    .filter(cb => cb.checked)
    .map(cb => cb.value);
 Promise.all(selectedIds.map(id => 
    fetch(`/api/v1/locations/${id}`, { method: 'DELETE' })
 ))
 ```
 ---
 ## Testing Checklist
 - [ ] Form validation works
 - [ ] Required fields enforced
 - [ ] Pagination navigation works
 - [ ] Filters persist across pages
 - [ ] Bulk select/deselect works
 - [ ] Individual delete confirmation
 - [ ] Modal forms submit correctly
 - [ ] Inline errors display
 - [ ] Map renders with markers
 - [ ] Map filter updates markers
 - [ ] Responsive at 375px
 - [ ] Responsive at 768px
 - [ ] Responsive at 1024px
 - [ ] Dark mode works
 - [ ] No console errors
 - [ ] API endpoints working
 ---
 ## Support & Troubleshooting
 ### Maps not showing
 - Check: Leaflet CDN is loaded
 - Check: Locations have latitude/longitude
 - Check: Zoom level is 6 (default Denmark view)
 ### Forms not submitting
 - Check: All required fields filled
 - Check: API endpoint is correct
 - Check: CSRF protection if enabled
 ### Modals not opening
 - Check: Bootstrap JS is loaded
 - Check: Modal ID matches button target
 - Check: No console errors
 ### Styles not applying
 - Check: Bootstrap 5 CSS loaded
 - Check: CSS variables inherited from base.html
 - Check: Dark mode toggle working
 ---
 ## References
 - [Bootstrap 5 Documentation](https://getbootstrap.com/docs/5.0/)
 - [Leaflet.js Documentation](https://leafletjs.com/)
 - [Jinja2 Template Documentation](https://jinja.palletsprojects.com/)
 - [MDN Web Docs - HTML](https://developer.mozilla.org/en-US/docs/Web/HTML)
 - [MDN Web Docs - CSS](https://developer.mozilla.org/en-US/docs/Web/CSS)
 - [MDN Web Docs - JavaScript](https://developer.mozilla.org/en-US/docs/Web/JavaScript)
 ---
 ## Template Files
 All files located in: `/app/modules/locations/templates/`
 **Ready for production deployment** ✅
 Last updated: 31 January 2026
--- a/TEMPLATE_IMPLEMENTATION_SUMMARY.md
+++ b/TEMPLATE_IMPLEMENTATION_SUMMARY.md
@ -1,339 +0,0 @@
 # Location Module Templates Implementation - Phase 3, Tasks 3.2-3.5
 **Status**: ✅ COMPLETE
 **Date**: 31 January 2026
 ---
 ## Overview
 All 5 production-ready Jinja2 HTML templates have been successfully created for the Location (Lokaliteter) Module, implementing Tasks 3.2-3.5 of Phase 3.
 ## Templates Created
 ### 1. `list.html` (Task 3.2) - 360 lines
 **Location**: `/app/modules/locations/templates/list.html`
 **Features**:
 - ✅ Responsive table (desktop) / card view (mobile at 768px)
 - ✅ Type-based color badges (branch=blue, warehouse=orange, service_center=green, client_site=purple)
 - ✅ Status badges (Active/Inactive)
 - ✅ Bulk select with checkbox header
 - ✅ Individual delete buttons with confirmation modal
 - ✅ Pagination with smart page navigation
 - ✅ Filters: by type, by status (preserved across pagination)
 - ✅ Empty state with create button
 - ✅ Clickable rows linking to detail page
 - ✅ Dark mode CSS variables
 - ✅ Bootstrap 5 responsive grid
 - ✅ Font Awesome icons
 **Context Variables**:
 - `locations`: List[Location]
 - `total`: int
 - `page_number`, `total_pages`, `skip`, `limit`: Pagination
 - `location_type`, `is_active`: Current filters
 - `location_types`: Available types
 ---
 ### 2. `detail.html` (Task 3.3) - 670 lines
 **Location**: `/app/modules/locations/templates/detail.html`
 **Features**:
 - ✅ 6-Tab Navigation Interface:
  1. **Oplysninger (Information)**: Basic info, address, contact, metadata
  2. **Kontakter (Contacts)**: List, add modal, edit/delete buttons, primary indicator
  3. **Åbningstider (Hours)**: Operating hours table with day, times, status
  4. **Tjenester (Services)**: Service list with availability toggle and delete
  5. **Kapacitet (Capacity)**: Capacity tracking with progress bars and percentages
  6. **Historik (History)**: Audit trail with event types and timestamps
 - ✅ Action buttons (Edit, Delete, Back)
 - ✅ Modals for adding contacts, services, capacity
 - ✅ Delete confirmation with soft-delete message
 - ✅ Responsive card layout
 - ✅ Inline data with metadata (created_at, updated_at)
 - ✅ Progress bars for capacity visualization
 - ✅ Collapsible history items
 - ✅ Location type badge with color coding
 - ✅ Active/Inactive status badge
 **Context Variables**:
 - `location`: LocationDetail (with all related data)
 - `location.contacts`: List of contacts
 - `location.operating_hours`: List of hours
 - `location.services`: List of services
 - `location.capacity`: List of capacity entries
 - `location.audit_log`: Change history
 - `location_types`: Available types
 ---
 ### 3. `create.html` (Task 3.4 - Part 1) - 214 lines
 **Location**: `/app/modules/locations/templates/create.html`
 **Features**:
 - ✅ 5 Form Sections:
  1. **Grundlæggende oplysninger**: Name*, Type*, Is Active
  2. **Adresse**: Street, City, Postal Code, Country
  3. **Kontaktoplysninger**: Phone, Email
  4. **Koordinater (GPS)**: Latitude (-90 to 90), Longitude (-180 to 180) - optional
  5. **Noter**: Notes textarea (max 500 chars with live counter)
 - ✅ Client-side validation (HTML5 required, type, ranges)
 - ✅ Real-time character counter for notes
 - ✅ Error alert with dismissible button
 - ✅ Loading state on submit button
 - ✅ Form submission via fetch API (POST to `/api/v1/locations`)
 - ✅ Redirect to detail page on success
 - ✅ Error handling with user-friendly messages
 - ✅ Breadcrumb navigation
 - ✅ Cancel button linking back to list
 **Context Variables**:
 - `location_types`: Available types
 - `form_action`: "/api/v1/locations"
 - `form_method`: "POST"
 ---
 ### 4. `edit.html` (Task 3.4 - Part 2) - 263 lines
 **Location**: `/app/modules/locations/templates/edit.html`
 **Features**:
 - ✅ Same 5 form sections as create.html
 - ✅ **PRE-FILLED** with current location data
 - ✅ Delete button (separate from update flow)
 - ✅ Delete confirmation modal with soft-delete explanation
 - ✅ PATCH request to `/api/v1/locations/{id}` on update
 - ✅ Character counter for notes
 - ✅ Error handling
 - ✅ Proper breadcrumb showing edit context
 - ✅ Back button links to detail page
 **Context Variables**:
 - `location`: Location object (pre-fill values)
 - `location_types`: Available types
 - `location.id`: For API endpoint construction
 ---
 ### 5. `map.html` (Task 3.5 - Optional) - 182 lines
 **Location**: `/app/modules/locations/templates/map.html`
 **Features**:
 - ✅ Leaflet.js map integration (v1.9.4)
 - ✅ Marker clustering (MarkerCluster plugin)
 - ✅ Color-coded markers by location type
 - ✅ Custom popup with location info (name, type, city, phone, email)
 - ✅ Clickable "Se detaljer" (View Details) button in popups
 - ✅ Type filter dropdown with live update
 - ✅ Dark mode tile layer support (auto-detect from document theme)
 - ✅ Location counter display
 - ✅ Link to list view
 - ✅ Responsive design (full-width container)
 - ✅ OpenStreetMap attribution
 **Context Variables**:
 - `locations`: List[Location] with lat/long
 - `location_types`: Available types
 - Map centered on Denmark (55.7, 12.6) at zoom level 6
 ---
 ## Design System Implementation
 ### Nordic Top Design (Minimalist, Clean, Professional)
 All templates implement:
 ✅ **Color Palette**:
 - Primary: `#0f4c75` (Deep Blue)
 - Accent: `#3282b8` (Lighter Blue)
 - Success: `#2eb341` (Green)
 - Warning: `#f39c12` (Orange)
 - Danger: `#e74c3c` (Red)
 ✅ **Location Type Badges**:
 - Branch: Blue `#0f4c75`
 - Warehouse: Orange `#f39c12`
 - Service Center: Green `#2eb341`
 - Client Site: Purple `#9b59b6`
 ✅ **Typography**:
 - Headings: fw-700 (bold)
 - Regular text: default weight
 - Secondary: text-muted, small
 - Monospace for metadata
 ✅ **Spacing**: Bootstrap 5 grid with 8px/16px/24px scale
 ✅ **Cards**: 
 - Border-0 (no border)
 - box-shadow (subtle, 2px blur)
 - border-radius: 12px
 ✅ **Responsive Breakpoints**:
 - Mobile: < 576px (default)
 - Tablet: >= 768px (hide columns, convert tables to cards)
 - Desktop: >= 1024px (full layout)
 ### Dark Mode Support
 ✅ All templates use CSS variables from `base.html`:
 - `--bg-body`: Light `#f8f9fa` / Dark `#212529`
 - `--bg-card`: Light `#ffffff` / Dark `#2c3034`
 - `--text-primary`: Light `#2c3e50` / Dark `#f8f9fa`
 - `--text-secondary`: Light `#6c757d` / Dark `#adb5bd`
 - `--accent`: Light `#0f4c75` / Dark `#3d8bfd`
 ---
 ## JavaScript Features
 ### Template Interactivity
 **list.html**:
 - ✅ Bulk select with indeterminate state
 - ✅ Select all/deselect all with counter
 - ✅ Individual row delete with confirmation
 - ✅ Bulk delete with confirmation
 - ✅ Clickable rows (except checkboxes and buttons)
 **detail.html**:
 - ✅ Add contact via modal form
 - ✅ Add service via modal form
 - ✅ Add capacity via modal form
 - ✅ Delete location with confirmation
 - ✅ Delete contact/service/capacity (inline)
 - ✅ Fetch API calls with error handling
 - ✅ Page reload on success
 **create.html**:
 - ✅ Real-time character counter
 - ✅ Form validation
 - ✅ Loading state UI
 - ✅ Error display with dismissible alert
 - ✅ Redirect to detail on success
 **edit.html**:
 - ✅ Same as create + delete modal handling
 - ✅ PATCH request for updates
 - ✅ Soft-delete confirmation message
 **map.html**:
 - ✅ Leaflet map initialization
 - ✅ Marker clustering
 - ✅ Dynamic marker creation by type
 - ✅ Popup with location details
 - ✅ Type filter with map update
 - ✅ Location counter update
 ---
 ## Accessibility & UX
 ✅ **Semantic HTML**:
 - Proper heading hierarchy (h1, h2, h3, h5, h6)
 - Fieldsets and legends for form sections
 - Buttons with icons and labels
 - Links with proper href attributes
 - ARIA labels where needed
 ✅ **Forms**:
 - Required field indicators (*)
 - Placeholder text for guidance
 - Field-level error styling capability
 - Proper label associations
 - Submit button loading state
 ✅ **Navigation**:
 - Breadcrumbs on all pages
 - Back buttons where appropriate
 - Consistent menu structure
 - Clear pagination
 ✅ **Color Accessibility**:
 - Not relying on color alone (badges have text labels)
 - Sufficient contrast ratios
 - Status indicators use both color and badge text
 ---
 ## Browser Compatibility
 All templates use:
 - ✅ HTML5 (valid semantic markup)
 - ✅ CSS3 with custom properties (--variables)
 - ✅ Bootstrap 5 (IE11 not supported, modern browsers only)
 - ✅ ES6+ JavaScript (async/await, fetch API)
 - ✅ Leaflet.js 1.9.4 (modern browser support)
 **Tested for**:
 - Chrome/Chromium 90+
 - Firefox 88+
 - Safari 14+
 - Edge 90+
 ---
 ## File Structure
 ```
 /app/modules/locations/templates/
 ├── list.html      (360 lines)  - Location list with filters & bulk ops
 ├── detail.html    (670 lines)  - Location details with 6 tabs
 ├── create.html    (214 lines)  - Create new location form
 ├── edit.html      (263 lines)  - Edit existing location + delete
 └── map.html       (182 lines)  - Interactive map with clustering
 ────────────────────────────────────────────
 Total: 1,689 lines of production-ready HTML/Jinja2
 ```
 ---
 ## Success Criteria - All Met ✅
 - ✅ All 5 templates created
 - ✅ All templates extend `base.html` correctly
 - ✅ All receive correct context variables
 - ✅ Nordic Top design applied consistently
 - ✅ Dark mode CSS variables used throughout
 - ✅ Mobile responsive (375px, 768px, 1024px tested)
 - ✅ No hard-coded paths (all use Jinja2 variables)
 - ✅ Forms have validation and error handling
 - ✅ Modals work correctly (Bootstrap 5)
 - ✅ Maps display with Leaflet.js
 - ✅ All links use `/app/locations/...` pattern
 - ✅ Pagination working (filters persist)
 - ✅ Bootstrap 5 grid system used
 - ✅ Font Awesome icons integrated
 - ✅ Proper Jinja2 syntax throughout
 - ✅ Production-ready (no TODOs or placeholders)
 ---
 ## Next Steps
 These templates are ready for:
 1. Integration with backend routers (if not already done)
 2. Testing with real data from API
 3. Styling refinements based on user feedback
 4. A11y audit for WCAG compliance
 5. Performance optimization (if needed)
 ---
 ## Notes
 - All templates follow BMC Hub conventions from copilot-instructions.md
 - Color scheme matches Nordic Top design reference
 - Forms include proper error handling and user feedback
 - Maps use marker clustering for performance with many locations
 - Bootstrap 5 provides modern responsive foundation
 - Leaflet.js provides lightweight map functionality without dependencies on heavy frameworks
 **Template Quality**: Production-Ready ✅
 **Code Review Status**: Approved for deployment
--- a/1
+++ b/1
@ -1 +0,0 @@
 2.2.52
--- a/app/alert_notes/init.py
+++ b/app/alert_notes/init.py
@ -1 +0,0 @@
 """Alert Notes Module"""
--- a/app/alert_notes/backend/init.py
+++ b/app/alert_notes/backend/init.py
@ -1,4 +0,0 @@
 """Alert Notes Backend Module"""
 from app.alert_notes.backend.router import router
 __all__ = ["router"]
--- a/app/alert_notes/backend/router.py
+++ b/app/alert_notes/backend/router.py
@ -1,515 +0,0 @@
 """
 Alert Notes Router
 API endpoints for contextual customer/contact alert system
 """
 from fastapi import APIRouter, HTTPException, Depends, Query
 from typing import List, Optional, Dict
 import logging
 from datetime import datetime
 from app.core.database import execute_query, execute_update
 from app.core.auth_dependencies import require_permission, get_current_user
 from app.alert_notes.backend.schemas import (
    AlertNoteCreate, AlertNoteUpdate, AlertNoteFull, AlertNoteCheck,
    AlertNoteRestriction, AlertNoteAcknowledgement, EntityType, Severity
 )
 logger = logging.getLogger(__name__)
 router = APIRouter()
 def _check_user_can_handle(alert_id: int, current_user: dict) -> bool:
    """
    Check if current user is allowed to handle the entity based on restrictions.
    Returns True if no restrictions exist OR user matches a restriction.
    """
    # Superadmins bypass restrictions
    if current_user.get("is_superadmin"):
        return True
    # Get restrictions for this alert
    restrictions = execute_query(
        """
        SELECT restriction_type, restriction_id
        FROM alert_note_restrictions
        WHERE alert_note_id = %s
        """,
        (alert_id,)
    )
    # No restrictions = everyone can handle
    if not restrictions:
        return True
    user_id = current_user["id"]
    # Get user's group IDs
    user_groups = execute_query(
        "SELECT group_id FROM user_groups WHERE user_id = %s",
        (user_id,)
    )
    user_group_ids = [g["group_id"] for g in user_groups]
    # Check if user matches any restriction
    for restriction in restrictions:
        if restriction["restriction_type"] == "user" and restriction["restriction_id"] == user_id:
            return True
        if restriction["restriction_type"] == "group" and restriction["restriction_id"] in user_group_ids:
            return True
    return False
 def _get_entity_name(entity_type: str, entity_id: int) -> Optional[str]:
    """Get the name of the entity (customer or contact)"""
    if entity_type == "customer":
        result = execute_query(
            "SELECT name FROM customers WHERE id = %s",
            (entity_id,)
        )
        return result[0]["name"] if result else None
    elif entity_type == "contact":
        result = execute_query(
            "SELECT first_name, last_name FROM contacts WHERE id = %s",
            (entity_id,)
        )
        if result:
            return f"{result[0]['first_name']} {result[0]['last_name']}"
    return None
 def _get_alert_with_relations(alert_id: int, current_user: dict) -> Optional[Dict]:
    """Get alert note with all its relations"""
    # Get main alert
    alerts = execute_query(
        """
        SELECT an.*, u.full_name as created_by_user_name
        FROM alert_notes an
        LEFT JOIN users u ON an.created_by_user_id = u.user_id
        WHERE an.id = %s
        """,
        (alert_id,)
    )
    if not alerts:
        return None
    alert = dict(alerts[0])
    # Get entity name
    alert["entity_name"] = _get_entity_name(alert["entity_type"], alert["entity_id"])
    # Get restrictions
    restrictions = execute_query(
        """
        SELECT anr.*, 
               CASE 
                   WHEN anr.restriction_type = 'group' THEN g.name
                   WHEN anr.restriction_type = 'user' THEN u.full_name
               END as restriction_name
        FROM alert_note_restrictions anr
        LEFT JOIN groups g ON anr.restriction_type = 'group' AND anr.restriction_id = g.id
        LEFT JOIN users u ON anr.restriction_type = 'user' AND anr.restriction_id = u.user_id
        WHERE anr.alert_note_id = %s
        """,
        (alert_id,)
    )
    alert["restrictions"] = restrictions
    # Get acknowledgements
    acknowledgements = execute_query(
        """
        SELECT ana.*, u.full_name as user_name
        FROM alert_note_acknowledgements ana
        LEFT JOIN users u ON ana.user_id = u.user_id
        WHERE ana.alert_note_id = %s
        ORDER BY ana.acknowledged_at DESC
        """,
        (alert_id,)
    )
    alert["acknowledgements"] = acknowledgements
    return alert
@router.get("/alert-notes/check", response_model=AlertNoteCheck)
 async def check_alerts(
    entity_type: EntityType = Query(..., description="Entity type (customer/contact)"),
    entity_id: int = Query(..., description="Entity ID"),
    current_user: dict = Depends(get_current_user)
 ):
    """
    Check if there are active alert notes for a specific entity.
    Returns alerts that the current user is allowed to see based on restrictions.
    """
    # Get active alerts for this entity
    alerts = execute_query(
        """
        SELECT an.*, u.full_name as created_by_user_name
        FROM alert_notes an
        LEFT JOIN users u ON an.created_by_user_id = u.user_id
        WHERE an.entity_type = %s 
          AND an.entity_id = %s 
          AND an.active = TRUE
        ORDER BY 
            CASE an.severity
                WHEN 'critical' THEN 1
                WHEN 'warning' THEN 2
                WHEN 'info' THEN 3
            END,
            an.created_at DESC
        """,
        (entity_type.value, entity_id)
    )
    if not alerts:
        return AlertNoteCheck(
            has_alerts=False,
            alerts=[],
            user_can_handle=True,
            user_has_acknowledged=False
        )
    # Enrich alerts with relations
    enriched_alerts = []
    for alert in alerts:
        alert_dict = dict(alert)
        alert_dict["entity_name"] = _get_entity_name(alert["entity_type"], alert["entity_id"])
        # Get restrictions
        restrictions = execute_query(
            """
            SELECT anr.*, 
                   CASE 
                       WHEN anr.restriction_type = 'group' THEN g.name
                       WHEN anr.restriction_type = 'user' THEN u.full_name
                   END as restriction_name
            FROM alert_note_restrictions anr
            LEFT JOIN groups g ON anr.restriction_type = 'group' AND anr.restriction_id = g.id
            LEFT JOIN users u ON anr.restriction_type = 'user' AND anr.restriction_id = u.user_id
            WHERE anr.alert_note_id = %s
            """,
            (alert["id"],)
        )
        alert_dict["restrictions"] = restrictions
        # Get acknowledgements
        acknowledgements = execute_query(
            """
            SELECT ana.*, u.full_name as user_name
            FROM alert_note_acknowledgements ana
            LEFT JOIN users u ON ana.user_id = u.user_id
            WHERE ana.alert_note_id = %s
            ORDER BY ana.acknowledged_at DESC
            """,
            (alert["id"],)
        )
        alert_dict["acknowledgements"] = acknowledgements
        enriched_alerts.append(alert_dict)
    # Check if user can handle based on restrictions
    user_can_handle = all(_check_user_can_handle(a["id"], current_user) for a in alerts)
    # Check if user has acknowledged all alerts that require it
    user_id = current_user["id"]
    user_has_acknowledged = True
    for alert in alerts:
        if alert["requires_acknowledgement"]:
            ack = execute_query(
                "SELECT id FROM alert_note_acknowledgements WHERE alert_note_id = %s AND user_id = %s",
                (alert["id"], user_id)
            )
            if not ack:
                user_has_acknowledged = False
                break
    return AlertNoteCheck(
        has_alerts=True,
        alerts=enriched_alerts,
        user_can_handle=user_can_handle,
        user_has_acknowledged=user_has_acknowledged
    )
@router.post("/alert-notes/{alert_id}/acknowledge")
 async def acknowledge_alert(
    alert_id: int,
    current_user: dict = Depends(get_current_user)
 ):
    """
    Mark an alert note as acknowledged by the current user.
    """
    # Check if alert exists
    alert = execute_query(
        "SELECT id, active FROM alert_notes WHERE id = %s",
        (alert_id,)
    )
    if not alert:
        raise HTTPException(status_code=404, detail="Alert note not found")
    if not alert[0]["active"]:
        raise HTTPException(status_code=400, detail="Alert note is not active")
    user_id = current_user["id"]
    # Check if already acknowledged
    existing = execute_query(
        "SELECT id FROM alert_note_acknowledgements WHERE alert_note_id = %s AND user_id = %s",
        (alert_id, user_id)
    )
    if existing:
        return {"status": "already_acknowledged", "alert_id": alert_id}
    # Insert acknowledgement
    execute_update(
        """
        INSERT INTO alert_note_acknowledgements (alert_note_id, user_id)
        VALUES (%s, %s)
        """,
        (alert_id, user_id)
    )
    logger.info(f"Alert {alert_id} acknowledged by user {user_id}")
    return {"status": "acknowledged", "alert_id": alert_id}
@router.get("/alert-notes", response_model=List[AlertNoteFull])
 async def list_alerts(
    entity_type: Optional[EntityType] = Query(None),
    entity_id: Optional[int] = Query(None),
    severity: Optional[Severity] = Query(None),
    active: Optional[bool] = Query(None),
    limit: int = Query(default=50, ge=1, le=500),
    offset: int = Query(default=0, ge=0),
    current_user: dict = Depends(require_permission("alert_notes.view"))
 ):
    """
    List alert notes with filtering (admin endpoint).
    Requires alert_notes.view permission.
    """
    conditions = []
    params = []
    if entity_type:
        conditions.append("an.entity_type = %s")
        params.append(entity_type.value)
    if entity_id:
        conditions.append("an.entity_id = %s")
        params.append(entity_id)
    if severity:
        conditions.append("an.severity = %s")
        params.append(severity.value)
    if active is not None:
        conditions.append("an.active = %s")
        params.append(active)
    where_clause = "WHERE " + " AND ".join(conditions) if conditions else ""
    query = f"""
        SELECT an.*, u.full_name as created_by_user_name
        FROM alert_notes an
        LEFT JOIN users u ON an.created_by_user_id = u.user_id
        {where_clause}
        ORDER BY an.created_at DESC
        LIMIT %s OFFSET %s
    """
    params.extend([limit, offset])
    alerts = execute_query(query, tuple(params))
    # Enrich with relations
    enriched_alerts = []
    for alert in alerts:
        alert_full = _get_alert_with_relations(alert["id"], current_user)
        if alert_full:
            enriched_alerts.append(alert_full)
    return enriched_alerts
@router.post("/alert-notes", response_model=AlertNoteFull)
 async def create_alert(
    alert: AlertNoteCreate,
    current_user: dict = Depends(require_permission("alert_notes.create"))
 ):
    """
    Create a new alert note.
    Requires alert_notes.create permission.
    """
    # Verify entity exists
    entity_name = _get_entity_name(alert.entity_type.value, alert.entity_id)
    if not entity_name:
        raise HTTPException(
            status_code=404,
            detail=f"{alert.entity_type.value.capitalize()} with ID {alert.entity_id} not found"
        )
    # Insert alert note
    result = execute_query(
        """
        INSERT INTO alert_notes (
            entity_type, entity_id, title, message, severity,
            requires_acknowledgement, active, created_by_user_id
        )
        VALUES (%s, %s, %s, %s, %s, %s, %s, %s)
        RETURNING id
        """,
        (
            alert.entity_type.value, alert.entity_id, alert.title, alert.message,
            alert.severity.value, alert.requires_acknowledgement, alert.active,
            current_user["id"]
        )
    )
    if not result or len(result) == 0:
        raise HTTPException(status_code=500, detail="Failed to create alert note")
    alert_id = result[0]["id"]
    # Insert restrictions
    for group_id in alert.restriction_group_ids:
        execute_query(
            """
            INSERT INTO alert_note_restrictions (alert_note_id, restriction_type, restriction_id)
            VALUES (%s, 'group', %s)
            """,
            (alert_id, group_id)
        )
    for user_id in alert.restriction_user_ids:
        execute_query(
            """
            INSERT INTO alert_note_restrictions (alert_note_id, restriction_type, restriction_id)
            VALUES (%s, 'user', %s)
            """,
            (alert_id, user_id)
        )
    logger.info(f"Alert note {alert_id} created for {alert.entity_type.value} {alert.entity_id} by user {current_user['id']}")
    # Return full alert with relations
    alert_full = _get_alert_with_relations(alert_id, current_user)
    return alert_full
@router.patch("/alert-notes/{alert_id}", response_model=AlertNoteFull)
 async def update_alert(
    alert_id: int,
    alert_update: AlertNoteUpdate,
    current_user: dict = Depends(require_permission("alert_notes.edit"))
 ):
    """
    Update an existing alert note.
    Requires alert_notes.edit permission.
    """
    # Check if alert exists
    existing = execute_query(
        "SELECT id FROM alert_notes WHERE id = %s",
        (alert_id,)
    )
    if not existing:
        raise HTTPException(status_code=404, detail="Alert note not found")
    # Build update query
    update_fields = []
    params = []
    if alert_update.title is not None:
        update_fields.append("title = %s")
        params.append(alert_update.title)
    if alert_update.message is not None:
        update_fields.append("message = %s")
        params.append(alert_update.message)
    if alert_update.severity is not None:
        update_fields.append("severity = %s")
        params.append(alert_update.severity.value)
    if alert_update.requires_acknowledgement is not None:
        update_fields.append("requires_acknowledgement = %s")
        params.append(alert_update.requires_acknowledgement)
    if alert_update.active is not None:
        update_fields.append("active = %s")
        params.append(alert_update.active)
    if update_fields:
        query = f"UPDATE alert_notes SET {', '.join(update_fields)} WHERE id = %s"
        params.append(alert_id)
        execute_update(query, tuple(params))
    # Update restrictions if provided
    if alert_update.restriction_group_ids is not None or alert_update.restriction_user_ids is not None:
        # Delete existing restrictions
        execute_update(
            "DELETE FROM alert_note_restrictions WHERE alert_note_id = %s",
            (alert_id,)
        )
        # Insert new group restrictions
        if alert_update.restriction_group_ids is not None:
            for group_id in alert_update.restriction_group_ids:
                execute_update(
                    """
                    INSERT INTO alert_note_restrictions (alert_note_id, restriction_type, restriction_id)
                    VALUES (%s, 'group', %s)
                    """,
                    (alert_id, group_id)
                )
        # Insert new user restrictions
        if alert_update.restriction_user_ids is not None:
            for user_id in alert_update.restriction_user_ids:
                execute_update(
                    """
                    INSERT INTO alert_note_restrictions (alert_note_id, restriction_type, restriction_id)
                    VALUES (%s, 'user', %s)
                    """,
                    (alert_id, user_id)
                )
    logger.info(f"Alert note {alert_id} updated by user {current_user['id']}")
    # Return updated alert
    alert_full = _get_alert_with_relations(alert_id, current_user)
    return alert_full
@router.delete("/alert-notes/{alert_id}")
 async def delete_alert(
    alert_id: int,
    current_user: dict = Depends(require_permission("alert_notes.delete"))
 ):
    """
    Soft delete an alert note (sets active = false).
    Requires alert_notes.delete permission.
    """
    # Check if alert exists
    existing = execute_query(
        "SELECT id, active FROM alert_notes WHERE id = %s",
        (alert_id,)
    )
    if not existing:
        raise HTTPException(status_code=404, detail="Alert note not found")
    # Soft delete
    execute_update(
        "UPDATE alert_notes SET active = FALSE WHERE id = %s",
        (alert_id,)
    )
    logger.info(f"Alert note {alert_id} deactivated by user {current_user['id']}")
    return {"status": "deleted", "alert_id": alert_id}
--- a/app/alert_notes/backend/schemas.py
+++ b/app/alert_notes/backend/schemas.py
@ -1,99 +0,0 @@
 """
 Alert Notes Pydantic Schemas
 Data models for contextual customer/contact alerts
 """
 from pydantic import BaseModel, Field
 from typing import Optional, List
 from datetime import datetime
 from enum import Enum
 class EntityType(str, Enum):
    """Entity types that can have alert notes"""
    customer = "customer"
    contact = "contact"
 class Severity(str, Enum):
    """Alert severity levels"""
    info = "info"
    warning = "warning"
    critical = "critical"
 class RestrictionType(str, Enum):
    """Types of restrictions for alert notes"""
    group = "group"
    user = "user"
 class AlertNoteRestriction(BaseModel):
    """Alert note restriction (who can handle the customer/contact)"""
    id: Optional[int] = None
    alert_note_id: int
    restriction_type: RestrictionType
    restriction_id: int  # References groups.id or users.user_id
    restriction_name: Optional[str] = None  # Filled by JOIN in query
    created_at: Optional[datetime] = None
 class AlertNoteAcknowledgement(BaseModel):
    """Alert note acknowledgement record"""
    id: Optional[int] = None
    alert_note_id: int
    user_id: int
    user_name: Optional[str] = None  # Filled by JOIN
    acknowledged_at: Optional[datetime] = None
 class AlertNoteBase(BaseModel):
    """Base schema for alert notes"""
    entity_type: EntityType
    entity_id: int
    title: str = Field(..., min_length=1, max_length=255)
    message: str = Field(..., min_length=1)
    severity: Severity = Severity.info
    requires_acknowledgement: bool = True
    active: bool = True
 class AlertNoteCreate(AlertNoteBase):
    """Schema for creating an alert note"""
    restriction_group_ids: List[int] = []  # List of group IDs
    restriction_user_ids: List[int] = []   # List of user IDs
 class AlertNoteUpdate(BaseModel):
    """Schema for updating an alert note"""
    title: Optional[str] = Field(None, min_length=1, max_length=255)
    message: Optional[str] = Field(None, min_length=1)
    severity: Optional[Severity] = None
    requires_acknowledgement: Optional[bool] = None
    active: Optional[bool] = None
    restriction_group_ids: Optional[List[int]] = None
    restriction_user_ids: Optional[List[int]] = None
 class AlertNoteFull(AlertNoteBase):
    """Full alert note schema with all relations"""
    id: int
    created_by_user_id: Optional[int] = None
    created_by_user_name: Optional[str] = None  # Filled by JOIN
    created_at: datetime
    updated_at: datetime
    # Related data
    restrictions: List[AlertNoteRestriction] = []
    acknowledgements: List[AlertNoteAcknowledgement] = []
    # Entity info (filled by JOIN)
    entity_name: Optional[str] = None
 class AlertNoteCheck(BaseModel):
    """Response for checking alerts on an entity"""
    has_alerts: bool
    alerts: List[AlertNoteFull]
    user_can_handle: bool  # Whether current user is allowed per restrictions
    user_has_acknowledged: bool = False
--- a/app/alert_notes/frontend/alert_box.html
+++ b/app/alert_notes/frontend/alert_box.html
@ -1,199 +0,0 @@
 <!-- Alert Notes Box Component - For inline display on detail pages -->
 <style>
    .alert-note-box {
        border-left: 5px solid;
        padding: 15px 20px;
        margin: 15px 0;
        background: var(--bg-card);
        border-radius: 8px;
        box-shadow: 0 2px 8px rgba(0,0,0,0.1);
        transition: all 0.3s;
    }
    .alert-note-box:hover {
        box-shadow: 0 4px 12px rgba(0,0,0,0.15);
    }
    .alert-note-info {
        border-left-color: #0dcaf0;
        background: #d1ecf1;
    }
    [data-bs-theme="dark"] .alert-note-info {
        background: rgba(13, 202, 240, 0.15);
    }
    .alert-note-warning {
        border-left-color: #ffc107;
        background: #fff3cd;
    }
    [data-bs-theme="dark"] .alert-note-warning {
        background: rgba(255, 193, 7, 0.15);
    }
    .alert-note-critical {
        border-left-color: #dc3545;
        background: #f8d7da;
    }
    [data-bs-theme="dark"] .alert-note-critical {
        background: rgba(220, 53, 69, 0.15);
    }
    .alert-note-title {
        font-weight: 600;
        font-size: 1.1rem;
        margin-bottom: 8px;
        display: flex;
        align-items: center;
        gap: 8px;
    }
    .alert-note-severity-badge {
        font-size: 0.75rem;
        padding: 2px 8px;
        border-radius: 4px;
        text-transform: uppercase;
        font-weight: 600;
    }
    .alert-note-severity-badge.info {
        background: #0dcaf0;
        color: white;
    }
    .alert-note-severity-badge.warning {
        background: #ffc107;
        color: #000;
    }
    .alert-note-severity-badge.critical {
        background: #dc3545;
        color: white;
    }
    .alert-note-message {
        margin-bottom: 12px;
        line-height: 1.6;
        white-space: pre-wrap;
    }
    .alert-note-restrictions {
        padding: 10px;
        background: rgba(0,0,0,0.05);
        border-radius: 6px;
        font-size: 0.9rem;
        margin-top: 12px;
    }
    [data-bs-theme="dark"] .alert-note-restrictions {
        background: rgba(255,255,255,0.05);
    }
    .alert-note-restrictions strong {
        display: block;
        margin-bottom: 5px;
    }
    .alert-note-footer {
        display: flex;
        justify-content: space-between;
        align-items: center;
        margin-top: 12px;
        font-size: 0.85rem;
        color: var(--text-secondary);
    }
    .alert-note-acknowledge-btn {
        font-size: 0.85rem;
        padding: 4px 12px;
    }
 </style>
 <!-- Template structure (fill via JavaScript) -->
 <div id="alert-notes-container"></div>
 <script>
 function renderAlertBox(alert) {
    const severityClass = `alert-note-${alert.severity}`;
    const severityBadgeClass = alert.severity;
    let restrictionsHtml = '';
    if (alert.restrictions && alert.restrictions.length > 0) {
        const restrictionNames = alert.restrictions.map(r => r.restriction_name).join(', ');
        restrictionsHtml = `
            <div class="alert-note-restrictions">
                <strong><i class="bi bi-shield-lock"></i> Håndteres kun af:</strong>
                ${restrictionNames}
            </div>
        `;
    }
    let acknowledgeBtn = '';
    if (alert.requires_acknowledgement && !alert.user_has_acknowledged) {
        acknowledgeBtn = `
            <button class="btn btn-sm btn-outline-secondary alert-note-acknowledge-btn" 
                    onclick="acknowledgeAlert(${alert.id}, this)">
                <i class="bi bi-check-circle"></i> Forstået
            </button>
        `;
    }
    // Edit button (always show for admins/creators)
    const editBtn = `
        <button class="btn btn-sm btn-outline-primary alert-note-acknowledge-btn" 
                onclick="openAlertNoteForm('${alert.entity_type}', ${alert.entity_id}, ${alert.id})"
                title="Rediger alert note">
            <i class="bi bi-pencil"></i>
        </button>
    `;
    const createdBy = alert.created_by_user_name ? ` • Oprettet af ${alert.created_by_user_name}` : '';
    return `
        <div class="alert-note-box ${severityClass}" data-alert-id="${alert.id}">
            <div class="alert-note-title">
                <span class="alert-note-severity-badge ${severityBadgeClass}">
                    ${alert.severity === 'info' ? 'INFO' : alert.severity === 'warning' ? 'ADVARSEL' : 'KRITISK'}
                <div class="d-flex gap-2">
                    ${editBtn}
                    ${acknowledgeBtn}
                </div>
                ${alert.title}
            </div>
            <div class="alert-note-message">${alert.message}</div>
            ${restrictionsHtml}
            <div class="alert-note-footer">
                <span class="text-muted">
                    <i class="bi bi-calendar"></i> ${new Date(alert.created_at).toLocaleDateString('da-DK')}${createdBy}
                </span>
                ${acknowledgeBtn}
            </div>
        </div>
    `;
 }
 function acknowledgeAlert(alertId, buttonElement) {
    fetch(`/api/v1/alert-notes/${alertId}/acknowledge`, {
        method: 'POST',
        headers: {
            'Content-Type': 'application/json'
        }
    })
    .then(response => response.json())
    .then(data => {
        if (data.status === 'acknowledged' || data.status === 'already_acknowledged') {
            // Remove the alert box with fade animation
            const alertBox = buttonElement.closest('.alert-note-box');
            alertBox.style.opacity = '0';
            alertBox.style.transform = 'translateX(-20px)';
            setTimeout(() => alertBox.remove(), 300);
        }
    })
    .catch(error => {
        console.error('Error acknowledging alert:', error);
        alert('Kunne ikke markere som læst. Prøv igen.');
    });
 }
 </script>
--- a/app/alert_notes/frontend/alert_check.js
+++ b/app/alert_notes/frontend/alert_check.js
@ -1,131 +0,0 @@
 /**
 * Alert Notes JavaScript Module
 * Handles loading and displaying alert notes for customers and contacts
 */
 /**
 * Load and display alerts for an entity
 * @param {string} entityType - 'customer' or 'contact'
 * @param {number} entityId - The entity ID
 * @param {string} mode - 'inline' (show in page) or 'modal' (show popup)
 * @param {string} containerId - Optional container ID for inline mode (default: 'alert-notes-container')
 */
 async function loadAndDisplayAlerts(entityType, entityId, mode = 'inline', containerId = 'alert-notes-container') {
    try {
        const response = await fetch(`/api/v1/alert-notes/check?entity_type=${entityType}&entity_id=${entityId}`, {
            credentials: 'include'
        });
        if (!response.ok) {
            console.error('Failed to fetch alerts:', response.status);
            return;
        }
        const data = await response.json();
        if (!data.has_alerts) {
            // No alerts - clear container if in inline mode
            if (mode === 'inline') {
                const container = document.getElementById(containerId);
                if (container) {
                    container.innerHTML = '';
                }
            }
            return;
        }
        // Store for later use
        window.currentAlertData = data;
        if (mode === 'modal') {
            // Show modal popup
            showAlertModal(data.alerts);
        } else {
            // Show inline
            displayAlertsInline(data.alerts, containerId, data.user_has_acknowledged);
        }
    } catch (error) {
        console.error('Error loading alerts:', error);
    }
 }
 /**
 * Display alerts inline in a container
 * @param {Array} alerts - Array of alert objects
 * @param {string} containerId - Container element ID
 * @param {boolean} userHasAcknowledged - Whether user has acknowledged all
 */
 function displayAlertsInline(alerts, containerId, userHasAcknowledged) {
    const container = document.getElementById(containerId);
    if (!container) {
        console.error('Alert container not found:', containerId);
        return;
    }
    // Clear existing content
    container.innerHTML = '';
    // Add each alert
    alerts.forEach(alert => {
        // Set user_has_acknowledged on individual alert if needed
        alert.user_has_acknowledged = userHasAcknowledged;
        // Render using the renderAlertBox function from alert_box.html
        const alertHtml = renderAlertBox(alert);
        container.innerHTML += alertHtml;
    });
 }
 /**
 * Acknowledge a single alert
 * @param {number} alertId - The alert ID
 * @param {HTMLElement} buttonElement - The button that was clicked
 */
 async function acknowledgeAlert(alertId, buttonElement) {
    try {
        const response = await fetch(`/api/v1/alert-notes/${alertId}/acknowledge`, {
            method: 'POST',
            headers: {
                'Content-Type': 'application/json'
            },
            credentials: 'include'
        });
        const data = await response.json();
        if (data.status === 'acknowledged' || data.status === 'already_acknowledged') {
            // Remove the alert box with fade animation
            const alertBox = buttonElement.closest('.alert-note-box');
            if (alertBox) {
                alertBox.style.opacity = '0';
                alertBox.style.transform = 'translateX(-20px)';
                alertBox.style.transition = 'all 0.3s';
                setTimeout(() => alertBox.remove(), 300);
            }
        }
    } catch (error) {
        console.error('Error acknowledging alert:', error);
        alert('Kunne ikke markere som læst. Prøv igen.');
    }
 }
 /**
 * Initialize alert checking on page load
 * Call this from your page's DOMContentLoaded or similar
 * @param {string} entityType - 'customer' or 'contact'
 * @param {number} entityId - The entity ID
 * @param {Object} options - Optional settings {mode: 'inline'|'modal', containerId: 'element-id'}
 */
 function initAlertNotes(entityType, entityId, options = {}) {
    const mode = options.mode || 'inline';
    const containerId = options.containerId || 'alert-notes-container';
    loadAndDisplayAlerts(entityType, entityId, mode, containerId);
 }
 // Make functions globally available
 window.loadAndDisplayAlerts = loadAndDisplayAlerts;
 window.displayAlertsInline = displayAlertsInline;
 window.acknowledgeAlert = acknowledgeAlert;
 window.initAlertNotes = initAlertNotes;
--- a/app/alert_notes/frontend/alert_form_modal.html
+++ b/app/alert_notes/frontend/alert_form_modal.html
@ -1,551 +0,0 @@
 <!-- Alert Note Create/Edit Modal -->
 <div class="modal fade" id="alertNoteFormModal" tabindex="-1" aria-labelledby="alertNoteFormModalLabel" aria-hidden="true">
    <div class="modal-dialog modal-lg">
        <div class="modal-content">
            <div class="modal-header bg-warning bg-opacity-10 border-bottom border-warning">
                <h5 class="modal-title d-flex align-items-center" id="alertNoteFormModalLabel">
                    <i class="bi bi-exclamation-triangle-fill text-warning me-2" style="font-size: 1.3rem;"></i>
                    <span id="alertFormTitle" class="fw-bold">Opret Alert Note</span>
                </h5>
                <button type="button" class="btn-close" data-bs-dismiss="modal" aria-label="Luk"></button>
            </div>
            <div class="modal-body" style="max-height: 70vh; overflow-y: auto;">
                <form id="alertNoteForm">
                    <input type="hidden" id="alertNoteId" value="">
                    <input type="hidden" id="alertEntityType" value="">
                    <input type="hidden" id="alertEntityId" value="">
                    <!-- Titel Section -->
                    <div class="mb-4">
                        <label for="alertTitle" class="form-label fw-semibold">
                            Titel <span class="text-danger">*</span>
                        </label>
                        <input type="text" 
                               class="form-control form-control-lg" 
                               id="alertTitle" 
                               required 
                               maxlength="255" 
                               placeholder="Kort beskrivende titel">
                    </div>
                    <!-- Besked Section -->
                    <div class="mb-4">
                        <label for="alertMessage" class="form-label fw-semibold">
                            Besked <span class="text-danger">*</span>
                        </label>
                        <textarea class="form-control" 
                                  id="alertMessage" 
                                  rows="6" 
                                  required 
                                  placeholder="Detaljeret information der skal vises..."
                                  style="font-family: inherit; line-height: 1.6;"></textarea>
                        <div class="form-text mt-2">
                            <i class="bi bi-info-circle me-1"></i>
                            Du kan bruge linjeskift for formatering
                        </div>
                    </div>
                    <!-- Alvorlighed Section -->
                    <div class="mb-4">
                        <label for="alertSeverity" class="form-label fw-semibold">
                            Alvorlighed <span class="text-danger">*</span>
                        </label>
                        <select class="form-select form-select-lg" id="alertSeverity" required>
                            <option value="info">ℹ️ Info - General kontekst</option>
                            <option value="warning" selected>⚠️ Advarsel - Særlige forhold</option>
                            <option value="critical">🚨 Kritisk - Følsomme forhold</option>
                        </select>
                    </div>
                    <!-- Checkboxes Section -->
                    <div class="mb-4 p-3 bg-light rounded">
                        <div class="form-check mb-3">
                            <input class="form-check-input" 
                                   type="checkbox" 
                                   id="alertRequiresAck" 
                                   checked>
                            <label class="form-check-label" for="alertRequiresAck">
                                <strong>Kræv bekræftelse</strong>
                                <div class="text-muted small mt-1">
                                    Brugere skal klikke "Forstået" for at bekræfte at de har set advarslen
                                </div>
                            </label>
                        </div>
                        <div class="form-check">
                            <input class="form-check-input" 
                                   type="checkbox" 
                                   id="alertActive" 
                                   checked>
                            <label class="form-check-label" for="alertActive">
                                <strong>Aktiv</strong>
                                <div class="text-muted small mt-1">
                                    Alert noten vises på kunde/kontakt siden
                                </div>
                            </label>
                        </div>
                    </div>
                    <hr class="my-4">
                    <!-- Restrictions Section -->
                    <div class="mb-3">
                        <label class="form-label fw-semibold d-flex align-items-center mb-3">
                            <i class="bi bi-shield-lock me-2 text-primary"></i>
                            Begrænsninger (Valgfri)
                        </label>
                        <div class="alert alert-info d-flex align-items-start mb-4">
                            <i class="bi bi-info-circle-fill me-2 mt-1"></i>
                            <div>
                                <strong>Hvad er begrænsninger?</strong>
                                <p class="mb-0 mt-1 small">
                                    Angiv hvilke grupper eller brugere der må håndtere denne kunde/kontakt. 
                                    Lad felterne stå tomme hvis alle må håndtere kunden.
                                </p>
                            </div>
                        </div>
                        <div class="row">
                            <div class="col-md-6 mb-3">
                                <label for="alertGroups" class="form-label fw-semibold">
                                    <i class="bi bi-people-fill me-1"></i>
                                    Godkendte Grupper
                                </label>
                                <select class="form-select" id="alertGroups" multiple size="5">
                                    <!-- Populated via JavaScript -->
                                </select>
                                <div class="form-text mt-2">
                                    <i class="bi bi-hand-index me-1"></i>
                                    Hold Ctrl/Cmd for at vælge flere
                                </div>
                            </div>
                            <div class="col-md-6 mb-3">
                                <label for="alertUsers" class="form-label fw-semibold">
                                    <i class="bi bi-person-fill me-1"></i>
                                    Godkendte Brugere
                                </label>
                                <select class="form-select" id="alertUsers" multiple size="5">
                                    <!-- Populated via JavaScript -->
                                </select>
                                <div class="form-text mt-2">
                                    <i class="bi bi-hand-index me-1"></i>
                                    Hold Ctrl/Cmd for at vælge flere
                                </div>
                            </div>
                        </div>
                    </div>
                </form>
            </div>
            <div class="modal-footer bg-light">
                <button type="button" class="btn btn-secondary" data-bs-dismiss="modal">
                    <i class="bi bi-x-circle me-2"></i>
                    Annuller
                </button>
                <button type="button" class="btn btn-primary btn-lg" id="saveAlertNoteBtn" onclick="saveAlertNote()">
                    <i class="bi bi-save me-2"></i>
                    Gem Alert Note
                </button>
            </div>
        </div>
    </div>
 </div>
 <style>
    /* Modal Header Styling */
    #alertNoteFormModal .modal-header {
        padding: 1.25rem 1.5rem;
    }
    #alertNoteFormModal .modal-body {
        padding: 1.5rem;
    }
    #alertNoteFormModal .modal-footer {
        padding: 1rem 1.5rem;
    }
    /* Form Labels */
    #alertNoteFormModal .form-label {
        font-weight: 600;
        color: var(--bs-body-color);
        margin-bottom: 0.5rem;
    }
    /* Input Fields */
    #alertNoteFormModal .form-control,
    #alertNoteFormModal .form-select {
        border-radius: 8px;
        border: 1px solid #dee2e6;
        transition: all 0.2s ease;
    }
    #alertNoteFormModal .form-control:focus,
    #alertNoteFormModal .form-select:focus {
        border-color: var(--bs-primary);
        box-shadow: 0 0 0 0.25rem rgba(13, 110, 253, 0.15);
    }
    /* Textarea specific */
    #alertNoteFormModal textarea.form-control {
        resize: vertical;
        min-height: 150px;
    }
    /* Multiselect Styling */
    #alertNoteFormModal select[multiple] {
        border: 2px solid #e0e0e0;
        border-radius: 8px;
        padding: 0.5rem;
        transition: all 0.2s ease;
    }
    #alertNoteFormModal select[multiple]:focus {
        border-color: var(--bs-primary);
        box-shadow: 0 0 0 0.25rem rgba(13, 110, 253, 0.15);
        outline: none;
    }
    #alertNoteFormModal select[multiple] option {
        padding: 10px 12px;
        border-radius: 6px;
        margin-bottom: 4px;
        cursor: pointer;
        transition: all 0.15s ease;
    }
    #alertNoteFormModal select[multiple] option:hover {
        background: rgba(13, 110, 253, 0.1);
    }
    #alertNoteFormModal select[multiple] option:checked {
        background: var(--bs-primary);
        color: white;
        font-weight: 500;
    }
    /* Checkbox Container */
    #alertNoteFormModal .form-check {
        padding: 0.75rem;
        border-radius: 8px;
        transition: background 0.2s ease;
    }
    #alertNoteFormModal .form-check:hover {
        background: rgba(0, 0, 0, 0.02);
    }
    [data-bs-theme="dark"] #alertNoteFormModal .form-check:hover {
        background: rgba(255, 255, 255, 0.05);
    }
    #alertNoteFormModal .form-check-input {
        width: 1.25rem;
        height: 1.25rem;
        margin-top: 0.125rem;
        cursor: pointer;
    }
    #alertNoteFormModal .form-check-label {
        cursor: pointer;
        user-select: none;
    }
    /* Alert Info Box */
    #alertNoteFormModal .alert-info {
        border-left: 4px solid var(--bs-info);
        background: rgba(13, 202, 240, 0.1);
        border-radius: 8px;
    }
    [data-bs-theme="dark"] #alertNoteFormModal .alert-info {
        background: rgba(13, 202, 240, 0.15);
    }
    /* Background Color Theme Support */
    [data-bs-theme="dark"] #alertNoteFormModal .bg-light {
        background: rgba(255, 255, 255, 0.05) !important;
    }
    [data-bs-theme="dark"] #alertNoteFormModal .modal-header {
        background: rgba(255, 193, 7, 0.1) !important;
        border-bottom-color: rgba(255, 193, 7, 0.3) !important;
    }
    /* Form Text Helpers */
    #alertNoteFormModal .form-text {
        font-size: 0.875rem;
        color: #6c757d;
    }
    /* Divider */
    #alertNoteFormModal hr {
        margin: 1.5rem 0;
        opacity: 0.1;
    }
    /* Responsive adjustments */
    @media (max-width: 768px) {
        #alertNoteFormModal .row > .col-md-6 {
            margin-bottom: 1rem !important;
        }
    }
 </style>
 <script>
 let alertFormModal = null;
 let currentAlertEntityType = null;
 let currentAlertEntityId = null;
 async function openAlertNoteForm(entityType, entityId, alertId = null) {
    currentAlertEntityType = entityType;
    currentAlertEntityId = entityId;
    // Load groups and users for restrictions
    await loadGroupsAndUsers();
    if (alertId) {
        // Edit mode
        await loadAlertForEdit(alertId);
        document.getElementById('alertFormTitle').textContent = 'Rediger Alert Note';
    } else {
        // Create mode
        document.getElementById('alertFormTitle').textContent = 'Opret Alert Note';
        document.getElementById('alertNoteForm').reset();
        document.getElementById('alertNoteId').value = '';
        document.getElementById('alertRequiresAck').checked = true;
        document.getElementById('alertActive').checked = true;
        document.getElementById('alertSeverity').value = 'warning';
    }
    document.getElementById('alertEntityType').value = entityType;
    document.getElementById('alertEntityId').value = entityId;
    // Show modal
    const modalEl = document.getElementById('alertNoteFormModal');
    alertFormModal = new bootstrap.Modal(modalEl);
    alertFormModal.show();
 }
 async function loadGroupsAndUsers() {
    try {
        // Load groups
        const groupsResponse = await fetch('/api/v1/admin/groups', {
            credentials: 'include'
        });
        if (groupsResponse.ok) {
            const groups = await groupsResponse.json();
            const groupsSelect = document.getElementById('alertGroups');
            groupsSelect.innerHTML = groups.map(g => 
                `<option value="${g.id}">${g.name}</option>`
            ).join('');
        }
        // Load users
        const usersResponse = await fetch('/api/v1/admin/users', {
            credentials: 'include'
        });
        if (usersResponse.ok) {
            const users = await usersResponse.json();
            const usersSelect = document.getElementById('alertUsers');
            usersSelect.innerHTML = users.map(u => 
                `<option value="${u.user_id}">${u.full_name || u.username} (${u.username})</option>`
            ).join('');
        }
    } catch (error) {
        console.error('Error loading groups/users:', error);
    }
 }
 async function loadAlertForEdit(alertId) {
    try {
        const response = await fetch(`/api/v1/alert-notes?entity_type=${currentAlertEntityType}&entity_id=${currentAlertEntityId}`, {
            credentials: 'include'
        });
        if (!response.ok) throw new Error('Failed to load alert');
        const alerts = await response.json();
        const alert = alerts.find(a => a.id === alertId);
        if (!alert) throw new Error('Alert not found');
        document.getElementById('alertNoteId').value = alert.id;
        document.getElementById('alertTitle').value = alert.title;
        document.getElementById('alertMessage').value = alert.message;
        document.getElementById('alertSeverity').value = alert.severity;
        document.getElementById('alertRequiresAck').checked = alert.requires_acknowledgement;
        document.getElementById('alertActive').checked = alert.active;
        // Set restrictions
        if (alert.restrictions && alert.restrictions.length > 0) {
            const groupIds = alert.restrictions
                .filter(r => r.restriction_type === 'group')
                .map(r => r.restriction_id);
            const userIds = alert.restrictions
                .filter(r => r.restriction_type === 'user')
                .map(r => r.restriction_id);
            // Select options
            Array.from(document.getElementById('alertGroups').options).forEach(opt => {
                opt.selected = groupIds.includes(parseInt(opt.value));
            });
            Array.from(document.getElementById('alertUsers').options).forEach(opt => {
                opt.selected = userIds.includes(parseInt(opt.value));
            });
        }
    } catch (error) {
        console.error('Error loading alert for edit:', error);
        alert('Kunne ikke indlæse alert. Prøv igen.');
    }
 }
 async function saveAlertNote() {
    const form = document.getElementById('alertNoteForm');
    if (!form.checkValidity()) {
        form.reportValidity();
        return;
    }
    const alertId = document.getElementById('alertNoteId').value;
    const isEdit = !!alertId;
    // Get selected groups and users
    const selectedGroups = Array.from(document.getElementById('alertGroups').selectedOptions)
        .map(opt => parseInt(opt.value));
    const selectedUsers = Array.from(document.getElementById('alertUsers').selectedOptions)
        .map(opt => parseInt(opt.value));
    // Build data object - different structure for create vs update
    let data;
    if (isEdit) {
        // PATCH: Only send fields to update (no entity_type, entity_id)
        data = {
            title: document.getElementById('alertTitle').value,
            message: document.getElementById('alertMessage').value,
            severity: document.getElementById('alertSeverity').value,
            requires_acknowledgement: document.getElementById('alertRequiresAck').checked,
            active: document.getElementById('alertActive').checked,
            restriction_group_ids: selectedGroups,
            restriction_user_ids: selectedUsers
        };
    } else {
        // POST: Include entity_type and entity_id for creation
        data = {
            entity_type: document.getElementById('alertEntityType').value,
            entity_id: parseInt(document.getElementById('alertEntityId').value),
            title: document.getElementById('alertTitle').value,
            message: document.getElementById('alertMessage').value,
            severity: document.getElementById('alertSeverity').value,
            requires_acknowledgement: document.getElementById('alertRequiresAck').checked,
            active: document.getElementById('alertActive').checked,
            restriction_group_ids: selectedGroups,
            restriction_user_ids: selectedUsers
        };
    }
    try {
        const saveBtn = document.getElementById('saveAlertNoteBtn');
        saveBtn.disabled = true;
        saveBtn.innerHTML = '<span class="spinner-border spinner-border-sm me-2"></span>Gemmer...';
        // Debug logging
        console.log('Saving alert note:', { isEdit, alertId, data });
        let response;
        if (isEdit) {
            // Update existing
            response = await fetch(`/api/v1/alert-notes/${alertId}`, {
                method: 'PATCH',
                headers: { 'Content-Type': 'application/json' },
                credentials: 'include',
                body: JSON.stringify(data)
            });
        } else {
            // Create new
            response = await fetch('/api/v1/alert-notes', {
                method: 'POST',
                headers: { 'Content-Type': 'application/json' },
                credentials: 'include',
                body: JSON.stringify(data)
            });
        }
        if (!response.ok) {
            let errorMsg = 'Failed to save alert note';
            try {
                const error = await response.json();
                console.error('API Error Response:', error);
                // Handle Pydantic validation errors
                if (error.detail && Array.isArray(error.detail)) {
                    errorMsg = error.detail.map(e => `${e.loc.join('.')}: ${e.msg}`).join('\n');
                } else if (error.detail) {
                    errorMsg = error.detail;
                }
            } catch (e) {
                errorMsg = `HTTP ${response.status}: ${response.statusText}`;
            }
            throw new Error(errorMsg);
        }
        // Success
        alertFormModal.hide();
        // Reload alerts on page
        loadAndDisplayAlerts(
            currentAlertEntityType, 
            currentAlertEntityId, 
            'inline', 
            'alert-notes-container'
        );
        // Show success message
        showSuccessToast(isEdit ? 'Alert note opdateret!' : 'Alert note oprettet!');
    } catch (error) {
        console.error('Error saving alert note:', error);
        // Show detailed error message
        const errorDiv = document.createElement('div');
        errorDiv.className = 'alert alert-danger alert-dismissible fade show mt-3';
        errorDiv.innerHTML = `
            <strong>Kunne ikke gemme alert note:</strong><br>
            <pre style="white-space: pre-wrap; margin-top: 10px; font-size: 0.9em;">${error.message}</pre>
            <button type="button" class="btn-close" data-bs-dismiss="alert"></button>
        `;
        // Insert error before form
        const modalBody = document.querySelector('#alertNoteFormModal .modal-body');
        modalBody.insertBefore(errorDiv, modalBody.firstChild);
        // Auto-remove after 10 seconds
        setTimeout(() => {
            if (errorDiv.parentNode) {
                errorDiv.remove();
            }
        }, 10000);
    } finally {
        const saveBtn = document.getElementById('saveAlertNoteBtn');
        saveBtn.disabled = false;
        saveBtn.innerHTML = '<i class="bi bi-save me-2"></i>Gem Alert Note';
    }
 }
 function showSuccessToast(message) {
    // Simple toast notification
    const toast = document.createElement('div');
    toast.className = 'alert alert-success position-fixed bottom-0 end-0 m-3';
    toast.style.zIndex = '9999';
    toast.innerHTML = `<i class="bi bi-check-circle me-2"></i>${message}`;
    document.body.appendChild(toast);
    setTimeout(() => {
        toast.classList.add('fade');
        setTimeout(() => toast.remove(), 150);
    }, 3000);
 }
 // Make functions globally available
 window.openAlertNoteForm = openAlertNoteForm;
 window.saveAlertNote = saveAlertNote;
 </script>
--- a/app/alert_notes/frontend/alert_modal.html
+++ b/app/alert_notes/frontend/alert_modal.html
@ -1,198 +0,0 @@
 <!-- Alert Notes Modal Component - For popup display -->
 <div class="modal fade" id="alertNoteModal" tabindex="-1" aria-labelledby="alertNoteModalLabel" aria-hidden="true">
    <div class="modal-dialog modal-dialog-centered">
        <div class="modal-content">
            <div class="modal-header" id="alertModalHeader">
                <h5 class="modal-title" id="alertNoteModalLabel">
                    <i class="bi bi-exclamation-triangle-fill"></i> Vigtig information
                </h5>
                <button type="button" class="btn-close" data-bs-dismiss="modal" aria-label="Luk"></button>
            </div>
            <div class="modal-body" id="alertModalBody">
                <!-- Alert content will be inserted here -->
            </div>
            <div class="modal-footer" id="alertModalFooter">
                <button type="button" class="btn btn-secondary" data-bs-dismiss="modal">Luk</button>
                <button type="button" class="btn btn-primary" id="alertModalAcknowledgeBtn" style="display: none;">
                    <i class="bi bi-check-circle"></i> Forstået
                </button>
            </div>
        </div>
    </div>
 </div>
 <style>
    #alertNoteModal .modal-header.severity-info {
        background: linear-gradient(135deg, #0dcaf0 0%, #00b4d8 100%);
        color: white;
    }
    #alertNoteModal .modal-header.severity-warning {
        background: linear-gradient(135deg, #ffc107 0%, #ffb703 100%);
        color: #000;
    }
    #alertNoteModal .modal-header.severity-critical {
        background: linear-gradient(135deg, #dc3545 0%, #bb2d3b 100%);
        color: white;
    }
    .alert-modal-content {
        padding: 15px 0;
    }
    .alert-modal-title {
        font-weight: 600;
        font-size: 1.2rem;
        margin-bottom: 15px;
        padding-bottom: 10px;
        border-bottom: 2px solid #dee2e6;
    }
    .alert-modal-message {
        line-height: 1.6;
        margin-bottom: 15px;
        white-space: pre-wrap;
    }
    .alert-modal-restrictions {
        background: #f8f9fa;
        padding: 15px;
        border-radius: 8px;
        border-left: 4px solid #0f4c75;
        margin-top: 15px;
    }
    [data-bs-theme="dark"] .alert-modal-restrictions {
        background: #2c3034;
    }
    .alert-modal-restrictions strong {
        display: block;
        margin-bottom: 8px;
        color: var(--accent);
    }
    .alert-modal-restrictions ul {
        margin-bottom: 0;
        padding-left: 20px;
    }
    .alert-modal-meta {
        font-size: 0.85rem;
        color: var(--text-secondary);
        margin-top: 15px;
        padding-top: 15px;
        border-top: 1px solid #dee2e6;
    }
 </style>
 <script>
 let currentAlertModal = null;
 let currentAlerts = [];
 function showAlertModal(alerts) {
    if (!alerts || alerts.length === 0) return;
    currentAlerts = alerts;
    const modal = document.getElementById('alertNoteModal');
    const modalHeader = document.getElementById('alertModalHeader');
    const modalBody = document.getElementById('alertModalBody');
    const modalAckBtn = document.getElementById('alertModalAcknowledgeBtn');
    // Set severity styling (use highest severity)
    const highestSeverity = alerts.find(a => a.severity === 'critical') ? 'critical' :
                           alerts.find(a => a.severity === 'warning') ? 'warning' : 'info';
    modalHeader.className = `modal-header severity-${highestSeverity}`;
    // Build content
    let contentHtml = '';
    alerts.forEach((alert, index) => {
        const severityText = alert.severity === 'info' ? 'INFO' : 
                           alert.severity === 'warning' ? 'ADVARSEL' : 'KRITISK';
        let restrictionsHtml = '';
        if (alert.restrictions && alert.restrictions.length > 0) {
            const restrictionsList = alert.restrictions
                .map(r => `<li>${r.restriction_name}</li>`)
                .join('');
            restrictionsHtml = `
                <div class="alert-modal-restrictions">
                    <strong><i class="bi bi-shield-lock"></i> Kun følgende må håndtere denne ${alert.entity_type === 'customer' ? 'kunde' : 'kontakt'}:</strong>
                    <ul>${restrictionsList}</ul>
                </div>
            `;
        }
        const createdBy = alert.created_by_user_name ? ` • Oprettet af ${alert.created_by_user_name}` : '';
        contentHtml += `
            <div class="alert-modal-content" data-alert-id="${alert.id}">
                ${index > 0 ? '<hr>' : ''}
                <div class="alert-modal-title">
                    <span class="badge bg-${alert.severity === 'critical' ? 'danger' : alert.severity === 'warning' ? 'warning' : 'info'}">
                        ${severityText}
                    </span>
                    ${alert.title}
                </div>
                <div class="alert-modal-message">${alert.message}</div>
                ${restrictionsHtml}
                <div class="alert-modal-meta">
                    <i class="bi bi-calendar"></i> ${new Date(alert.created_at).toLocaleDateString('da-DK', { 
                        year: 'numeric', 
                        month: 'long', 
                        day: 'numeric' 
                    })}${createdBy}
                </div>
            </div>
        `;
    });
    modalBody.innerHTML = contentHtml;
    // Show acknowledge button if any alert requires it and user hasn't acknowledged
    const requiresAck = alerts.some(a => a.requires_acknowledgement && !a.user_has_acknowledged);
    if (requiresAck) {
        modalAckBtn.style.display = 'inline-block';
        modalAckBtn.onclick = function() {
            acknowledgeAllAlerts();
        };
    } else {
        modalAckBtn.style.display = 'none';
    }
    // Show modal
    currentAlertModal = new bootstrap.Modal(modal);
    currentAlertModal.show();
 }
 function acknowledgeAllAlerts() {
    const promises = currentAlerts
        .filter(a => a.requires_acknowledgement && !a.user_has_acknowledged)
        .map(alert => {
            return fetch(`/api/v1/alert-notes/${alert.id}/acknowledge`, {
                method: 'POST',
                headers: {
                    'Content-Type': 'application/json'
                }
            });
        });
    Promise.all(promises)
        .then(() => {
            if (currentAlertModal) {
                currentAlertModal.hide();
            }
            // Reload alerts on the page if in inline view
            if (typeof loadAlerts === 'function') {
                loadAlerts();
            }
        })
        .catch(error => {
            console.error('Error acknowledging alerts:', error);
            alert('Kunne ikke markere som læst. Prøv igen.');
        });
 }
 </script>
--- a/app/apply_migration_084.py
+++ b/app/apply_migration_084.py
@ -1,50 +0,0 @@
 from app.core.database import get_db_connection, release_db_connection, init_db
 import logging
 logging.basicConfig(level=logging.INFO)
 logger = logging.getLogger(__name__)
 def run_migration():
    init_db()  # Initialize the pool
    conn = get_db_connection()
    try:
        with conn.cursor() as cursor:
            # Files linked to a Case
            cursor.execute("""
            CREATE TABLE IF NOT EXISTS sag_files (
                id SERIAL PRIMARY KEY,
                sag_id INTEGER NOT NULL REFERENCES sag_sager(id) ON DELETE CASCADE,
                filename VARCHAR(255) NOT NULL,
                content_type VARCHAR(100),
                size_bytes INTEGER,
                stored_name TEXT NOT NULL,
                uploaded_by_user_id INTEGER REFERENCES users(user_id) ON DELETE SET NULL,
                created_at TIMESTAMP DEFAULT CURRENT_TIMESTAMP
            );
            """)
            cursor.execute("CREATE INDEX IF NOT EXISTS idx_sag_files_sag_id ON sag_files(sag_id);")
            cursor.execute("COMMENT ON TABLE sag_files IS 'Files uploaded directly to the Case.';")
            # Emails linked to a Case (Many-to-Many)
            cursor.execute("""
            CREATE TABLE IF NOT EXISTS sag_emails (
                sag_id INTEGER REFERENCES sag_sager(id) ON DELETE CASCADE,
                email_id INTEGER REFERENCES email_messages(id) ON DELETE CASCADE,
                created_at TIMESTAMPTZ DEFAULT NOW(),
                PRIMARY KEY (sag_id, email_id)
            );
            """)
            cursor.execute("COMMENT ON TABLE sag_emails IS 'Emails linked to the Case.';")
            conn.commit()
            logger.info("Migration 084 applied successfully.")
    except Exception as e:
        conn.rollback()
        logger.error(f"Migration failed: {e}")
    finally:
        release_db_connection(conn)
 if __name__ == "__main__":
    run_migration()
--- a/app/apply_migration_085.py
+++ b/app/apply_migration_085.py
@ -1,69 +0,0 @@
 import logging
 import os
 import sys
 # Ensure we can import app modules
 sys.path.append("/app")
 from app.core.database import execute_query, init_db
 # Setup logging
 logging.basicConfig(level=logging.INFO)
 logger = logging.getLogger(__name__)
 SQL_MIGRATION = """
 CREATE TABLE IF NOT EXISTS sag_solutions (
    id SERIAL PRIMARY KEY,
    sag_id INTEGER NOT NULL REFERENCES sag_sager(id) ON DELETE CASCADE,
    title VARCHAR(255) NOT NULL,
    description TEXT,
    solution_type VARCHAR(50), 
    result VARCHAR(50),        
    created_by_user_id INTEGER, 
    created_at TIMESTAMP DEFAULT CURRENT_TIMESTAMP,
    updated_at TIMESTAMP DEFAULT CURRENT_TIMESTAMP,
    CONSTRAINT uq_sag_solutions_sag_id UNIQUE (sag_id)
 );
 ALTER TABLE tmodule_times ADD COLUMN IF NOT EXISTS solution_id INTEGER REFERENCES sag_solutions(id) ON DELETE SET NULL;
 ALTER TABLE tmodule_times ADD COLUMN IF NOT EXISTS sag_id INTEGER REFERENCES sag_sager(id) ON DELETE SET NULL;
 ALTER TABLE tmodule_times ALTER COLUMN vtiger_id DROP NOT NULL;
 ALTER TABLE tmodule_times ALTER COLUMN case_id DROP NOT NULL;
 CREATE INDEX IF NOT EXISTS idx_sag_solutions_sag_id ON sag_solutions(sag_id);
 CREATE INDEX IF NOT EXISTS idx_tmodule_times_solution_id ON tmodule_times(solution_id);
 CREATE INDEX IF NOT EXISTS idx_tmodule_times_sag_id ON tmodule_times(sag_id);
 """
 def run_migration():
    logger.info("Initializing DB connection...")
    try:
        init_db()
    except Exception as e:
        logger.error(f"Failed to init db: {e}")
        return
    logger.info("Applying migration 085...")
    commands = [cmd.strip() for cmd in SQL_MIGRATION.split(";") if cmd.strip()]
    for cmd in commands:
        # Skip empty lines or pure comments
        if not cmd or cmd.startswith("--"):
            continue
        logger.info(f"Executing: {cmd[:50]}...")
        try:
            execute_query(cmd, ())
        except Exception as e:
            logger.warning(f"Error executing command: {e}")
    logger.info("✅ Migration applied successfully")
 if __name__ == "__main__":
    run_migration()
--- a/app/auth/backend/admin.py
+++ b/app/auth/backend/admin.py
@ -1,300 +0,0 @@
 """
 Auth Admin API - Users, Groups, Permissions management
 """
 from fastapi import APIRouter, HTTPException, status, Depends
 from pydantic import BaseModel, Field
 from app.core.auth_dependencies import require_permission
 from app.core.auth_service import AuthService
 from app.core.database import execute_query, execute_query_single, execute_insert, execute_update
 from app.models.schemas import UserAdminCreate, UserGroupsUpdate, GroupCreate, GroupPermissionsUpdate, UserTwoFactorResetRequest
 import logging
 logger = logging.getLogger(__name__)
 router = APIRouter()
 class UserStatusUpdateRequest(BaseModel):
    is_active: bool
 class UserPasswordResetRequest(BaseModel):
    new_password: str = Field(..., min_length=8, max_length=128)
 def _users_column_exists(column_name: str) -> bool:
    result = execute_query_single(
        """
        SELECT 1
        FROM information_schema.columns
        WHERE table_schema = 'public'
          AND table_name = 'users'
          AND column_name = %s
        LIMIT 1
        """,
        (column_name,)
    )
    return bool(result)
 def _table_exists(table_name: str) -> bool:
        result = execute_query_single(
                """
                SELECT 1
                FROM information_schema.tables
                WHERE table_schema = 'public'
                    AND table_name = %s
                LIMIT 1
                """,
                (table_name,)
        )
        return bool(result)
@router.get("/admin/users", dependencies=[Depends(require_permission("users.manage"))])
 async def list_users():
    is_2fa_expr = "u.is_2fa_enabled" if _users_column_exists("is_2fa_enabled") else "FALSE AS is_2fa_enabled"
    telefoni_extension_expr = "u.telefoni_extension" if _users_column_exists("telefoni_extension") else "NULL::varchar AS telefoni_extension"
    telefoni_active_expr = "u.telefoni_aktiv" if _users_column_exists("telefoni_aktiv") else "FALSE AS telefoni_aktiv"
    telefoni_ip_expr = "u.telefoni_phone_ip" if _users_column_exists("telefoni_phone_ip") else "NULL::varchar AS telefoni_phone_ip"
    telefoni_username_expr = "u.telefoni_phone_username" if _users_column_exists("telefoni_phone_username") else "NULL::varchar AS telefoni_phone_username"
    last_login_expr = "u.last_login_at" if _users_column_exists("last_login_at") else "NULL::timestamp AS last_login_at"
    has_user_groups = _table_exists("user_groups")
    has_groups = _table_exists("groups")
    if has_user_groups and has_groups:
        groups_join = "LEFT JOIN user_groups ug ON u.user_id = ug.user_id LEFT JOIN groups g ON ug.group_id = g.id"
        groups_select = "COALESCE(array_remove(array_agg(g.name), NULL), ARRAY[]::varchar[]) AS groups"
    else:
        groups_join = ""
        groups_select = "ARRAY[]::varchar[] AS groups"
    try:
        users = execute_query(
            f"""
             SELECT u.user_id, u.username, u.email, u.full_name,
                 u.is_active, u.is_superadmin, {is_2fa_expr},
                 {telefoni_extension_expr}, {telefoni_active_expr}, {telefoni_ip_expr}, {telefoni_username_expr},
                 u.created_at, {last_login_expr},
                 {groups_select}
            FROM users u
            {groups_join}
            GROUP BY u.user_id
            ORDER BY u.user_id
            """
        )
        return users
    except Exception as exc:
        logger.warning("⚠️ Admin user query fallback triggered: %s", exc)
        try:
            users = execute_query(
                f"""
                SELECT u.user_id, u.username, u.email, u.full_name,
                       u.is_active, u.is_superadmin, {is_2fa_expr},
                       {telefoni_extension_expr}, {telefoni_active_expr}, {telefoni_ip_expr}, {telefoni_username_expr},
                       u.created_at, {last_login_expr},
                       ARRAY[]::varchar[] AS groups
                FROM users u
                ORDER BY u.user_id
                """
            )
            return users
        except Exception as fallback_exc:
            logger.error("❌ Failed to load admin users (fallback): %s", fallback_exc)
            raise HTTPException(status_code=status.HTTP_500_INTERNAL_SERVER_ERROR, detail="Could not load users") from fallback_exc
@router.post("/admin/users", status_code=status.HTTP_201_CREATED, dependencies=[Depends(require_permission("users.manage"))])
 async def create_user(payload: UserAdminCreate):
    existing = execute_query_single(
        "SELECT user_id FROM users WHERE username = %s OR email = %s",
        (payload.username, payload.email)
    )
    if existing:
        raise HTTPException(
            status_code=status.HTTP_409_CONFLICT,
            detail="Username or email already exists"
        )
    try:
        password_hash = AuthService.hash_password(payload.password)
    except Exception as exc:
        logger.error("❌ Password hash failed: %s", exc)
        raise HTTPException(
            status_code=status.HTTP_400_BAD_REQUEST,
            detail="Kunne ikke hashe adgangskoden"
        ) from exc
    user_id = execute_insert(
        """
        INSERT INTO users (username, email, password_hash, full_name, is_superadmin, is_active)
        VALUES (%s, %s, %s, %s, %s, %s) RETURNING user_id
        """,
        (payload.username, payload.email, password_hash, payload.full_name, payload.is_superadmin, payload.is_active)
    )
    if payload.group_ids:
        for group_id in payload.group_ids:
            execute_update(
                """
                INSERT INTO user_groups (user_id, group_id)
                VALUES (%s, %s) ON CONFLICT DO NOTHING
                """,
                (user_id, group_id)
            )
    logger.info("✅ User created via admin: %s (ID: %s)", payload.username, user_id)
    return {"user_id": user_id}
@router.put("/admin/users/{user_id}/groups", dependencies=[Depends(require_permission("users.manage"))])
 async def update_user_groups(user_id: int, payload: UserGroupsUpdate):
    user = execute_query_single("SELECT user_id FROM users WHERE user_id = %s", (user_id,))
    if not user:
        raise HTTPException(status_code=status.HTTP_404_NOT_FOUND, detail="User not found")
    execute_update("DELETE FROM user_groups WHERE user_id = %s", (user_id,))
    for group_id in payload.group_ids:
        execute_update(
            """
            INSERT INTO user_groups (user_id, group_id)
            VALUES (%s, %s) ON CONFLICT DO NOTHING
            """,
            (user_id, group_id)
        )
    return {"message": "Groups updated"}
@router.patch("/admin/users/{user_id}", dependencies=[Depends(require_permission("users.manage"))])
 async def update_user_status(user_id: int, payload: UserStatusUpdateRequest):
    user = execute_query_single(
        "SELECT user_id, username FROM users WHERE user_id = %s",
        (user_id,)
    )
    if not user:
        raise HTTPException(status_code=status.HTTP_404_NOT_FOUND, detail="User not found")
    execute_update(
        "UPDATE users SET is_active = %s, updated_at = CURRENT_TIMESTAMP WHERE user_id = %s",
        (payload.is_active, user_id)
    )
    logger.info("✅ Updated user status via admin: %s -> active=%s", user.get("username"), payload.is_active)
    return {"message": "User status updated", "user_id": user_id, "is_active": payload.is_active}
@router.post("/admin/users/{user_id}/reset-password", dependencies=[Depends(require_permission("users.manage"))])
 async def admin_reset_user_password(user_id: int, payload: UserPasswordResetRequest):
    user = execute_query_single(
        "SELECT user_id, username FROM users WHERE user_id = %s",
        (user_id,)
    )
    if not user:
        raise HTTPException(status_code=status.HTTP_404_NOT_FOUND, detail="User not found")
    try:
        password_hash = AuthService.hash_password(payload.new_password)
    except Exception as exc:
        logger.error("❌ Password hash failed for user_id=%s: %s", user_id, exc)
        raise HTTPException(status_code=status.HTTP_400_BAD_REQUEST, detail="Kunne ikke hashe adgangskoden") from exc
    execute_update(
        "UPDATE users SET password_hash = %s, updated_at = CURRENT_TIMESTAMP WHERE user_id = %s",
        (password_hash, user_id)
    )
    logger.info("✅ Password reset via admin for user: %s", user.get("username"))
    return {"message": "Password reset", "user_id": user_id}
@router.post("/admin/users/{user_id}/2fa/reset")
 async def reset_user_2fa(
    user_id: int,
    payload: UserTwoFactorResetRequest,
    current_user: dict = Depends(require_permission("users.manage"))
 ):
    ok = AuthService.admin_reset_user_2fa(user_id)
    if not ok:
        raise HTTPException(status_code=status.HTTP_404_NOT_FOUND, detail="User not found")
    reason = (payload.reason or "").strip()
    if reason:
        logger.info(
            "✅ Admin reset 2FA for user_id=%s by %s (reason: %s)",
            user_id,
            current_user.get("username"),
            reason
        )
    else:
        logger.info(
            "✅ Admin reset 2FA for user_id=%s by %s",
            user_id,
            current_user.get("username")
        )
    return {"message": "2FA reset"}
@router.get("/admin/groups", dependencies=[Depends(require_permission("users.manage"))])
 async def list_groups():
    groups = execute_query(
        """
        SELECT g.id, g.name, g.description,
               COALESCE(array_remove(array_agg(p.code), NULL), ARRAY[]::varchar[]) AS permissions
        FROM groups g
        LEFT JOIN group_permissions gp ON g.id = gp.group_id
        LEFT JOIN permissions p ON gp.permission_id = p.id
        GROUP BY g.id
        ORDER BY g.id
        """
    )
    return groups
@router.post("/admin/groups", status_code=status.HTTP_201_CREATED, dependencies=[Depends(require_permission("permissions.manage"))])
 async def create_group(payload: GroupCreate):
    existing = execute_query_single("SELECT id FROM groups WHERE name = %s", (payload.name,))
    if existing:
        raise HTTPException(status_code=status.HTTP_409_CONFLICT, detail="Group already exists")
    group_id = execute_insert(
        """
        INSERT INTO groups (name, description)
        VALUES (%s, %s) RETURNING id
        """,
        (payload.name, payload.description)
    )
    return {"group_id": group_id}
@router.put("/admin/groups/{group_id}/permissions", dependencies=[Depends(require_permission("permissions.manage"))])
 async def update_group_permissions(group_id: int, payload: GroupPermissionsUpdate):
    group = execute_query_single("SELECT id FROM groups WHERE id = %s", (group_id,))
    if not group:
        raise HTTPException(status_code=status.HTTP_404_NOT_FOUND, detail="Group not found")
    execute_update("DELETE FROM group_permissions WHERE group_id = %s", (group_id,))
    for permission_id in payload.permission_ids:
        execute_update(
            """
            INSERT INTO group_permissions (group_id, permission_id)
            VALUES (%s, %s) ON CONFLICT DO NOTHING
            """,
            (group_id, permission_id)
        )
    return {"message": "Permissions updated"}
@router.get("/admin/permissions", dependencies=[Depends(require_permission("permissions.manage"))])
 async def list_permissions():
    permissions = execute_query(
        """
        SELECT id, code, description, category
        FROM permissions
        ORDER BY category, code
        """
    )
    return permissions
--- a/app/auth/backend/router.py
+++ b/app/auth/backend/router.py
@ -1,11 +1,9 @@
 """
 Auth API Router - Login, Logout, Me endpoints
 """
-from fastapi import APIRouter, HTTPException, status, Request, Depends, Response
+from fastapi import APIRouter, HTTPException, status, Request, Depends
 from pydantic import BaseModel
 from typing import Optional
 from app.core.auth_service import AuthService
 from app.core.config import settings
 from app.core.auth_dependencies import get_current_user
 import logging
@ -17,44 +15,30 @@ router = APIRouter()
 class LoginRequest(BaseModel):
    username: str
    password: str
    otp_code: Optional[str] = None
 class LoginResponse(BaseModel):
    access_token: str
    token_type: str = "bearer"
    user: dict
    requires_2fa_setup: bool = False
 class LogoutRequest(BaseModel):
-    token_jti: Optional[str] = None
+    token_jti: str
 class TwoFactorCodeRequest(BaseModel):
    otp_code: str
@router.post("/login", response_model=LoginResponse)
-async def login(request: Request, credentials: LoginRequest, response: Response):
+async def login(request: Request, credentials: LoginRequest):
    """
    Authenticate user and return JWT token
    """
    ip_address = request.client.host if request.client else None
    # Authenticate user
-    user, error_detail = AuthService.authenticate_user(
+    user = AuthService.authenticate_user(
        username=credentials.username,
        password=credentials.password,
-        ip_address=ip_address,
+        ip_address=ip_address
        otp_code=credentials.otp_code
    )
    if error_detail:
        raise HTTPException(
            status_code=status.HTTP_401_UNAUTHORIZED,
            detail=error_detail,
            headers={"WWW-Authenticate": "Bearer"},
    )
    if not user:
@ -68,50 +52,21 @@ async def login(request: Request, credentials: LoginRequest, response: Response)
    access_token = AuthService.create_access_token(
        user_id=user['user_id'],
        username=user['username'],
-        is_superadmin=user['is_superadmin'],
+        is_superadmin=user['is_superadmin']
        is_shadow_admin=user.get('is_shadow_admin', False)
    )
    requires_2fa_setup = (
        not user.get("is_shadow_admin", False)
        and not settings.AUTH_DISABLE_2FA
        and AuthService.is_2fa_supported()
        and not user.get("is_2fa_enabled", False)
    )
    response.set_cookie(
        key="access_token",
        value=access_token,
        httponly=True,
        samesite=settings.COOKIE_SAMESITE,
        secure=settings.COOKIE_SECURE
    )
    return LoginResponse(
        access_token=access_token,
-        user=user,
+        user=user
        requires_2fa_setup=requires_2fa_setup
    )
@router.post("/logout")
-async def logout(
+async def logout(request: LogoutRequest, current_user: dict = Depends(get_current_user)):
    response: Response,
    current_user: dict = Depends(get_current_user),
    request: Optional[LogoutRequest] = None
 ):
    """
    Revoke JWT token (logout)
    """
-    token_jti = request.token_jti if request and request.token_jti else current_user.get("token_jti")
+    AuthService.revoke_token(request.token_jti, current_user['id'])
    if token_jti:
        AuthService.revoke_token(
            token_jti,
            current_user['id'],
            current_user.get('is_shadow_admin', False)
        )
    response.delete_cookie("access_token")
    return {"message": "Successfully logged out"}
@ -127,83 +82,5 @@ async def get_me(current_user: dict = Depends(get_current_user)):
        "email": current_user['email'],
        "full_name": current_user['full_name'],
        "is_superadmin": current_user['is_superadmin'],
        "is_2fa_enabled": current_user.get('is_2fa_enabled', False),
        "permissions": current_user['permissions']
    }
@router.post("/2fa/setup")
 async def setup_2fa(current_user: dict = Depends(get_current_user)):
    """Generate and store TOTP secret (requires verification to enable)"""
    if current_user.get("is_shadow_admin"):
        raise HTTPException(
            status_code=status.HTTP_403_FORBIDDEN,
            detail="Shadow admin cannot configure 2FA",
        )
    try:
        result = AuthService.setup_user_2fa(
            user_id=current_user["id"],
            username=current_user["username"]
        )
    except RuntimeError as exc:
        if "2FA columns missing" in str(exc):
            raise HTTPException(
                status_code=status.HTTP_400_BAD_REQUEST,
                detail="2FA er ikke tilgaengelig i denne database (mangler kolonner).",
            )
        raise
    return result
@router.post("/2fa/enable")
 async def enable_2fa(
    request: TwoFactorCodeRequest,
    current_user: dict = Depends(get_current_user)
 ):
    """Enable 2FA after verifying the provided code"""
    if current_user.get("is_shadow_admin"):
        raise HTTPException(
            status_code=status.HTTP_403_FORBIDDEN,
            detail="Shadow admin cannot configure 2FA",
        )
    ok = AuthService.enable_user_2fa(
        user_id=current_user["id"],
        otp_code=request.otp_code
    )
    if not ok:
        raise HTTPException(
            status_code=status.HTTP_400_BAD_REQUEST,
            detail="Invalid 2FA code or missing setup",
        )
    return {"message": "2FA enabled"}
@router.post("/2fa/disable")
 async def disable_2fa(
    request: TwoFactorCodeRequest,
    current_user: dict = Depends(get_current_user)
 ):
    """Disable 2FA after verifying the provided code"""
    if current_user.get("is_shadow_admin"):
        raise HTTPException(
            status_code=status.HTTP_403_FORBIDDEN,
            detail="Shadow admin cannot configure 2FA",
        )
    ok = AuthService.disable_user_2fa(
        user_id=current_user["id"],
        otp_code=request.otp_code
    )
    if not ok:
        raise HTTPException(
            status_code=status.HTTP_400_BAD_REQUEST,
            detail="Invalid 2FA code or missing setup",
        )
    return {"message": "2FA disabled"}
--- a/app/auth/backend/views.py
+++ b/app/auth/backend/views.py
@ -18,14 +18,3 @@ async def login_page(request: Request):
        "auth/frontend/login.html",
        {"request": request}
    )
@router.get("/2fa/setup", response_class=HTMLResponse)
 async def two_factor_setup_page(request: Request):
    """
    Render 2FA setup page
    """
    return templates.TemplateResponse(
        "auth/frontend/2fa_setup.html",
        {"request": request}
    )
--- a/app/auth/frontend/2fa_setup.html
+++ b/app/auth/frontend/2fa_setup.html
@ -1,145 +0,0 @@
 {% extends "shared/frontend/base.html" %}
 {% block title %}2FA Setup - BMC Hub{% endblock %}
 {% block content %}
 <div class="container">
    <div class="row justify-content-center align-items-center" style="min-height: 80vh;">
        <div class="col-md-6 col-lg-5">
            <div class="card shadow-sm">
                <div class="card-body p-4">
                    <div class="text-center mb-4">
                        <h2 class="fw-bold" style="color: var(--primary-color);">2FA Setup</h2>
                        <p class="text-muted">Opsaet tofaktor for din konto</p>
                    </div>
                    <div id="statusMessage" class="alert alert-info" role="alert">
                        Klik "Generer 2FA" for at starte opsaetningen.
                    </div>
                    <div class="d-grid gap-2 mb-3">
                        <button class="btn btn-primary" id="generateBtn">
                            <i class="bi bi-shield-lock me-2"></i>
                            Generer 2FA
                        </button>
                    </div>
                    <div id="setupDetails" class="d-none">
                        <div class="mb-3">
                            <label class="form-label">Secret</label>
                            <input type="text" class="form-control" id="totpSecret" readonly>
                        </div>
                        <div class="mb-3">
                            <label class="form-label">Provisioning URI</label>
                            <textarea class="form-control" id="provisioningUri" rows="3" readonly></textarea>
                        </div>
                        <div class="mb-3">
                            <label class="form-label">2FA-kode</label>
                            <input type="text" class="form-control" id="otpCode" placeholder="Indtast 2FA-kode">
                        </div>
                        <div class="d-grid gap-2">
                            <button class="btn btn-success" id="enableBtn">
                                <i class="bi bi-check-circle me-2"></i>
                                Aktiver 2FA
                            </button>
                        </div>
                    </div>
                    <div class="text-center mt-3">
                        <a href="/" class="text-decoration-none text-muted">Spring over for nu</a>
                    </div>
                </div>
            </div>
        </div>
    </div>
 </div>
 <script>
 const statusMessage = document.getElementById('statusMessage');
 const generateBtn = document.getElementById('generateBtn');
 const enableBtn = document.getElementById('enableBtn');
 const setupDetails = document.getElementById('setupDetails');
 const totpSecret = document.getElementById('totpSecret');
 const provisioningUri = document.getElementById('provisioningUri');
 const otpCode = document.getElementById('otpCode');
 async function ensureAuthenticated() {
    const token = localStorage.getItem('access_token');
    const headers = token ? { 'Authorization': `Bearer ${token}` } : {};
    try {
        const response = await fetch('/api/v1/auth/me', { headers, credentials: 'include' });
        if (!response.ok) {
            window.location.href = '/login';
        }
    } catch (error) {
        window.location.href = '/login';
    }
 }
 generateBtn.addEventListener('click', async () => {
    statusMessage.className = 'alert alert-info';
    statusMessage.textContent = 'Genererer 2FA...';
    try {
        const response = await fetch('/api/v1/auth/2fa/setup', {
            method: 'POST',
            headers: { 'Content-Type': 'application/json' },
            credentials: 'include'
        });
        const data = await response.json();
        if (!response.ok) {
            statusMessage.className = 'alert alert-danger';
            statusMessage.textContent = data.detail || 'Kunne ikke generere 2FA.';
            return;
        }
        totpSecret.value = data.secret || '';
        provisioningUri.value = data.provisioning_uri || '';
        setupDetails.classList.remove('d-none');
        statusMessage.className = 'alert alert-success';
        statusMessage.textContent = '2FA secret genereret. Indtast koden fra din authenticator.';
    } catch (error) {
        statusMessage.className = 'alert alert-danger';
        statusMessage.textContent = 'Kunne ikke generere 2FA.';
    }
 });
 enableBtn.addEventListener('click', async () => {
    const code = (otpCode.value || '').trim();
    if (!code) {
        statusMessage.className = 'alert alert-warning';
        statusMessage.textContent = 'Indtast 2FA-koden.';
        return;
    }
    try {
        const response = await fetch('/api/v1/auth/2fa/enable', {
            method: 'POST',
            headers: { 'Content-Type': 'application/json' },
            credentials: 'include',
            body: JSON.stringify({ otp_code: code })
        });
        const data = await response.json();
        if (!response.ok) {
            statusMessage.className = 'alert alert-danger';
            statusMessage.textContent = data.detail || 'Kunne ikke aktivere 2FA.';
            return;
        }
        statusMessage.className = 'alert alert-success';
        statusMessage.textContent = '2FA aktiveret. Du bliver sendt videre.';
        setTimeout(() => {
            window.location.href = '/';
        }, 1200);
    } catch (error) {
        statusMessage.className = 'alert alert-danger';
        statusMessage.textContent = 'Kunne ikke aktivere 2FA.';
    }
 });
 ensureAuthenticated();
 </script>
 {% endblock %}
--- a/app/auth/frontend/login.html
+++ b/app/auth/frontend/login.html
@ -39,18 +39,6 @@
                            >
                        </div>
                        <div class="mb-3">
                            <label for="otp_code" class="form-label">2FA-kode</label>
                            <input 
                                type="text" 
                                class="form-control" 
                                id="otp_code" 
                                name="otp_code" 
                                placeholder="Indtast 2FA-kode"
                                autocomplete="one-time-code"
                            >
                        </div>
                        <div class="mb-3 form-check">
                            <input type="checkbox" class="form-check-input" id="rememberMe">
                            <label class="form-check-label" for="rememberMe">
@ -92,7 +80,6 @@ document.getElementById('loginForm').addEventListener('submit', async (e) => {
    const username = document.getElementById('username').value;
    const password = document.getElementById('password').value;
    const otp_code = document.getElementById('otp_code').value;
    const errorMessage = document.getElementById('errorMessage');
    const errorText = document.getElementById('errorText');
    const submitBtn = e.target.querySelector('button[type="submit"]');
@ -110,7 +97,7 @@ document.getElementById('loginForm').addEventListener('submit', async (e) => {
            headers: {
                'Content-Type': 'application/json'
            },
-            body: JSON.stringify({ username, password, otp_code })
+            body: JSON.stringify({ username, password })
        });
        const data = await response.json();
@ -120,17 +107,6 @@ document.getElementById('loginForm').addEventListener('submit', async (e) => {
            localStorage.setItem('access_token', data.access_token);
            localStorage.setItem('user', JSON.stringify(data.user));
            // Set cookie for HTML navigation access (expires in 24 hours)
            const d = new Date();
            d.setTime(d.getTime() + (24*60*60*1000));
            document.cookie = `access_token=${data.access_token};expires=${d.toUTCString()};path=/;SameSite=Lax`;
            if (data.requires_2fa_setup) {
                const goSetup = confirm('2FA er ikke opsat. Vil du opsaette 2FA nu?');
                window.location.href = goSetup ? '/2fa/setup' : '/';
                return;
            }
            // Redirect to dashboard
            window.location.href = '/';
        } else {
@ -164,11 +140,6 @@ if (token) {
    })
    .then(response => {
        if (response.ok) {
            // Ensure cookie is set (sync with localStorage)
            const d = new Date();
            d.setTime(d.getTime() + (24*60*60*1000));
            document.cookie = `access_token=${token};expires=${d.toUTCString()};path=/;SameSite=Lax`;
            // Redirect to dashboard
            window.location.href = '/';
        } else {
--- a/app/backups/backend/init.py
+++ b/app/backups/backend/init.py
@ -1,3 +1 @@
 """Backup backend services, API routes, and scheduler."""
 from app.backups.backend import router
--- a/app/backups/backend/router.py
+++ b/app/backups/backend/router.py
@ -10,7 +10,7 @@ from pathlib import Path
 from fastapi import APIRouter, HTTPException, Query, UploadFile, File
 from pydantic import BaseModel, Field
-from app.core.database import execute_query, execute_update, execute_insert, execute_query_single
+from app.core.database import execute_query, execute_update, execute_insert
 from app.core.config import settings
 from app.backups.backend.service import backup_service
 from app.backups.backend.notifications import notifications
@ -161,7 +161,7 @@ async def list_backups(
    query += " ORDER BY created_at DESC LIMIT %s OFFSET %s"
    params.extend([limit, offset])
-    backups = execute_query(query, tuple(params))
+    backups = execute_query_single(query, tuple(params))
    return backups if backups else []
@ -251,16 +251,16 @@ async def upload_backup(
        # Calculate retention date
        if is_monthly:
-            retention_until = datetime.now() + timedelta(days=settings.BACKUP_RETENTION_MONTHLY * 30)
+            retention_until = datetime.now() + timedelta(days=settings.MONTHLY_KEEP_MONTHS * 30)
        else:
-            retention_until = datetime.now() + timedelta(days=settings.BACKUP_RETENTION_DAYS)
+            retention_until = datetime.now() + timedelta(days=settings.RETENTION_DAYS)
        # Create backup job record
        job_id = execute_insert(
            """INSERT INTO backup_jobs 
               (job_type, status, backup_format, file_path, file_size_bytes, 
                checksum_sha256, is_monthly, started_at, completed_at, retention_until)
-               VALUES (%s, %s, %s, %s, %s, %s, %s, %s, %s, %s) RETURNING id""",
+               VALUES (%s, %s, %s, %s, %s, %s, %s, %s, %s, %s)""",
            (backup_type, 'completed', backup_format, str(target_path), file_size,
             checksum, is_monthly, datetime.now(), datetime.now(), retention_until.date())
        )
@ -316,17 +316,6 @@ async def restore_backup(job_id: int, request: RestoreRequest):
    logger.warning("🔧 Restore initiated: job_id=%s, type=%s, user_message=%s",
                  job_id, backup['job_type'], request.message)
    # Check if DRY-RUN mode is enabled
    if settings.BACKUP_RESTORE_DRY_RUN:
        logger.warning("🔒 DRY RUN MODE: Restore test requested but not executed")
        return {
            "success": True,
            "dry_run": True,
            "message": "DRY-RUN mode: Restore was NOT executed. Set BACKUP_RESTORE_DRY_RUN=false to actually restore.",
            "job_id": job_id,
            "job_type": backup['job_type']
        }
    try:
        # Send notification
        await notifications.send_restore_started(
@ -338,51 +327,20 @@ async def restore_backup(job_id: int, request: RestoreRequest):
        # Perform restore based on type
        if backup['job_type'] == 'database':
            success = await backup_service.restore_database(job_id)
            if success:
                # Get the new database name from logs (created with timestamp)
                from datetime import datetime
                timestamp = datetime.now().strftime('%Y%m%d_%H%M%S')
                new_dbname = f"bmc_hub_restored_{timestamp}"
                # Parse current DATABASE_URL to get credentials
                db_url = settings.DATABASE_URL
                if '@' in db_url:
                    creds = db_url.split('@')[0].replace('postgresql://', '')
                    host_part = db_url.split('@')[1]
                    new_url = f"postgresql://{creds}@{host_part.split('/')[0]}/{new_dbname}"
                else:
                    new_url = f"postgresql://bmc_hub:bmc_hub@postgres:5432/{new_dbname}"
                logger.info("✅ Restore completed successfully: job_id=%s", job_id)
                return {
                    "success": True, 
                    "message": "Database restored to NEW database (safe!)",
                    "new_database": new_dbname,
                    "instructions": [
                        f"1. Update .env: DATABASE_URL={new_url}",
                        "2. Restart: docker-compose restart api",
                        "3. Test system thoroughly",
                        "4. If OK: Drop old DB, rename new DB to 'bmc_hub'",
                        "5. If NOT OK: Just revert .env and restart"
                    ]
                }
        elif backup['job_type'] == 'files':
            success = await backup_service.restore_files(job_id)
            if success:
                logger.info("✅ Files restore completed: job_id=%s", job_id)
                return {"success": True, "message": "Files restore completed successfully"}
        elif backup['job_type'] == 'full':
            # Restore both database and files
            db_success = await backup_service.restore_database(job_id)
            files_success = await backup_service.restore_files(job_id)
            success = db_success and files_success
            if success:
                logger.info("✅ Full restore completed: job_id=%s", job_id)
                return {"success": True, "message": "Full restore completed - check logs for database name"}
        else:
            raise HTTPException(status_code=400, detail=f"Unknown backup type: {backup['job_type']}")
-        # If we get here, restore failed
+        if success:
            logger.info("✅ Restore completed successfully: job_id=%s", job_id)
            return {"success": True, "message": "Restore completed successfully"}
        else:
            logger.error("❌ Restore failed: job_id=%s", job_id)
            raise HTTPException(status_code=500, detail="Restore operation failed - check logs")
@ -523,7 +481,6 @@ async def get_scheduler_status():
    """
    Get backup scheduler status and job information
    """
    try:
    from app.backups.backend.scheduler import backup_scheduler
    if not backup_scheduler.running:
@ -546,10 +503,3 @@ async def get_scheduler_status():
        "running": backup_scheduler.running,
        "jobs": jobs
    }
    except Exception as e:
        logger.warning("Scheduler not available: %s", str(e))
        return {
            "enabled": settings.BACKUP_ENABLED,
            "running": False,
            "message": f"Scheduler error: {str(e)}"
        }
--- a/app/backups/backend/scheduler.py
+++ b/app/backups/backend/scheduler.py
@ -1,6 +1,6 @@
 """
 Backup Scheduler
-Manages scheduled backup jobs, rotation, offsite uploads, retry logic, and email fetch
+Manages scheduled backup jobs, rotation, offsite uploads, and retry logic
 """
 import logging
@ -26,42 +26,17 @@ class BackupScheduler:
        self.running = False
    def start(self):
-        """Start the scheduler with enabled jobs (backups and/or emails)"""
+        """Start the backup scheduler with all jobs"""
-        if self.running:
+        if not self.enabled:
-            logger.warning("⚠️ Scheduler already running")
+            logger.info("⏭️ Backup scheduler disabled (BACKUP_ENABLED=false)")
            return
-        logger.info("🚀 Starting unified scheduler...")
+        if self.running:
            logger.warning("⚠️ Backup scheduler already running")
            return
-        # Add backup jobs if enabled
+        logger.info("🚀 Starting backup scheduler...")
        if self.enabled:
            self._add_backup_jobs()
        else:
            logger.info("⏭️ Backup jobs disabled (BACKUP_ENABLED=false)")
        # Email fetch job (every N minutes if enabled)
        if settings.EMAIL_TO_TICKET_ENABLED:
            self.scheduler.add_job(
                func=self._email_fetch_job,
                trigger=IntervalTrigger(minutes=settings.EMAIL_PROCESS_INTERVAL_MINUTES),
                id='email_fetch',
                name='Email Fetch & Process',
                max_instances=1,
                replace_existing=True
            )
            logger.info("✅ Scheduled: Email fetch every %d minute(s)", 
                       settings.EMAIL_PROCESS_INTERVAL_MINUTES)
        else:
            logger.info("⏭️ Email fetch disabled (EMAIL_TO_TICKET_ENABLED=false)")
        # Start the scheduler
        self.scheduler.start()
        self.running = True
        logger.info("✅ Scheduler started successfully")
    def _add_backup_jobs(self):
        """Add all backup-related jobs to scheduler"""
        # Daily full backup at 02:00 CET
        self.scheduler.add_job(
            func=self._daily_backup_job,
@ -131,6 +106,12 @@ class BackupScheduler:
        )
        logger.info("✅ Scheduled: Storage check at 01:30")
        # Start the scheduler
        self.scheduler.start()
        self.running = True
        logger.info("✅ Backup scheduler started successfully")
    def stop(self):
        """Stop the backup scheduler"""
        if not self.running:
@ -396,25 +377,6 @@ class BackupScheduler:
        except Exception as e:
            logger.error("❌ Storage check error: %s", str(e), exc_info=True)
    async def _email_fetch_job(self):
        """Email fetch and processing job"""
        try:
            logger.info("🔄 Email processing job started...")
            # Import here to avoid circular dependencies
            from app.services.email_processor_service import EmailProcessorService
            processor = EmailProcessorService()
            start_time = datetime.now()
            stats = await processor.process_inbox()
            duration = (datetime.now() - start_time).total_seconds()
            logger.info(f"✅ Email processing complete: {stats} (duration: {duration:.1f}s)")
        except Exception as e:
            logger.error(f"❌ Email processing job failed: {e}")
    def _get_weekday_number(self, day_name: str) -> int:
        """Convert day name to APScheduler weekday number (0=Monday, 6=Sunday)"""
        days = {
--- a/app/backups/backend/service.py
+++ b/app/backups/backend/service.py
@ -16,7 +16,7 @@ import paramiko
 from stat import S_ISDIR
 from app.core.config import settings
-from app.core.database import execute_query, execute_insert, execute_update, execute_query_single
+from app.core.database import execute_query, execute_insert, execute_update
 logger = logging.getLogger(__name__)
@ -25,26 +25,8 @@ class BackupService:
    """Service for managing backup operations"""
    def __init__(self):
-        configured_backup_dir = Path(settings.BACKUP_STORAGE_PATH)
+        self.backup_dir = Path(settings.BACKUP_STORAGE_PATH)
        self.backup_dir = configured_backup_dir
        try:
        self.backup_dir.mkdir(parents=True, exist_ok=True)
        except OSError as exc:
            # Local development can run outside Docker where /app is not writable.
            # Fall back to the workspace data path so app startup does not fail.
            if str(configured_backup_dir).startswith('/app/'):
                project_root = Path(__file__).resolve().parents[3]
                fallback_dir = project_root / 'data' / 'backups'
                logger.warning(
                    "⚠️ Backup path %s not writable (%s). Using fallback %s",
                    configured_backup_dir,
                    exc,
                    fallback_dir,
                )
                fallback_dir.mkdir(parents=True, exist_ok=True)
                self.backup_dir = fallback_dir
            else:
                raise
        # Subdirectories for different backup types
        self.db_dir = self.backup_dir / "database"
@ -75,7 +57,7 @@ class BackupService:
        # Create backup job record
        job_id = execute_insert(
            """INSERT INTO backup_jobs (job_type, status, backup_format, is_monthly, started_at)
-               VALUES (%s, %s, %s, %s, %s) RETURNING id""",
+               VALUES (%s, %s, %s, %s, %s)""",
            ('database', 'running', backup_format, is_monthly, datetime.now())
        )
@ -119,9 +101,9 @@ class BackupService:
            # Calculate retention date
            if is_monthly:
-                retention_until = datetime.now() + timedelta(days=settings.BACKUP_RETENTION_MONTHLY * 30)
+                retention_until = datetime.now() + timedelta(days=settings.MONTHLY_KEEP_MONTHS * 30)
            else:
-                retention_until = datetime.now() + timedelta(days=settings.BACKUP_RETENTION_DAYS)
+                retention_until = datetime.now() + timedelta(days=settings.RETENTION_DAYS)
            # Update job record
            execute_update(
@ -197,7 +179,7 @@ class BackupService:
        job_id = execute_insert(
            """INSERT INTO backup_jobs 
               (job_type, status, backup_format, includes_uploads, includes_logs, includes_data, started_at)
-               VALUES (%s, %s, %s, %s, %s, %s, %s) RETURNING id""",
+               VALUES (%s, %s, %s, %s, %s, %s, %s)""",
            ('files', 'running', 'tar.gz',
             settings.BACKUP_INCLUDE_UPLOADS,
             settings.BACKUP_INCLUDE_LOGS,
@ -237,7 +219,7 @@ class BackupService:
            checksum = self._calculate_checksum(backup_path)
            # Calculate retention date (files use daily retention)
-            retention_until = datetime.now() + timedelta(days=settings.BACKUP_RETENTION_DAYS)
+            retention_until = datetime.now() + timedelta(days=settings.RETENTION_DAYS)
            # Update job record
            execute_update(
@ -336,14 +318,7 @@ class BackupService:
    async def restore_database(self, job_id: int) -> bool:
        """
-        Restore database from backup to NEW database with timestamp suffix
+        Restore database from backup with maintenance mode
        Strategy:
        1. Create new database: bmc_hub_restored_YYYYMMDD_HHMMSS
        2. Restore backup to NEW database (no conflicts!)
        3. Return new database name in response
        4. User updates .env to point to new database
        5. Test system, then cleanup old database
        Args:
            job_id: Backup job ID to restore from
@ -354,12 +329,9 @@ class BackupService:
        if settings.BACKUP_READ_ONLY:
            logger.error("❌ Restore blocked: BACKUP_READ_ONLY=true")
            return False
-        if settings.BACKUP_RESTORE_DRY_RUN:
+        
            logger.warning("🔄 DRY RUN MODE: Would restore database from backup job %s", job_id)
            logger.warning("🔄 Set BACKUP_RESTORE_DRY_RUN=false to actually restore")
            return False        
        # Get backup job
-        backup = execute_query_single(
+        backup = execute_query(
            "SELECT * FROM backup_jobs WHERE id = %s AND job_type = 'database'",
            (job_id,))
@ -373,13 +345,7 @@ class BackupService:
            logger.error("❌ Backup file not found: %s", backup_path)
            return False
        # Generate new database name with timestamp
        from datetime import datetime
        timestamp = datetime.now().strftime('%Y%m%d_%H%M%S')
        new_dbname = f"bmc_hub_restored_{timestamp}"
        logger.info("🔄 Starting database restore from backup: %s", backup_path.name)
        logger.info("🎯 Target: NEW database '%s' (safe restore!)", new_dbname)
        # Enable maintenance mode
        await self.set_maintenance_mode(True, "Database restore i gang", eta_minutes=5)
@ -396,8 +362,8 @@ class BackupService:
            # Acquire file lock to prevent concurrent operations
            lock_file = self.backup_dir / ".restore.lock"
-            with open(lock_file, 'w') as lock_f:
+            with open(lock_file, 'w') as f:
-                fcntl.flock(lock_f.fileno(), fcntl.LOCK_EX)
+                fcntl.flock(f.fileno(), fcntl.LOCK_EX)
                # Parse database connection info
                env = os.environ.copy()
@ -412,97 +378,35 @@ class BackupService:
                env['PGPASSWORD'] = password
                # Step 1: Create new empty database
                logger.info("📦 Creating new database: %s", new_dbname)
                create_cmd = ['psql', '-h', host, '-U', user, '-d', 'postgres', '-c', 
                             f"CREATE DATABASE {new_dbname} OWNER {user};"]
                result = subprocess.run(create_cmd, stderr=subprocess.PIPE, stdout=subprocess.PIPE, 
                                      text=True, env=env)
                if result.returncode != 0:
                    logger.error("❌ Failed to create database: %s", result.stderr)
                    fcntl.flock(lock_f.fileno(), fcntl.LOCK_UN)
                    raise RuntimeError(f"CREATE DATABASE failed: {result.stderr}")
                logger.info("✅ New database created: %s", new_dbname)
                # Step 2: Restore to NEW database (no conflicts!)
                # Build restore command based on format
                if backup['backup_format'] == 'dump':
                    # Restore from compressed custom format
-                    cmd = ['pg_restore', '-h', host, '-U', user, '-d', new_dbname]
+                    cmd = ['pg_restore', '-h', host, '-U', user, '-d', dbname, '--clean', '--if-exists']
                    logger.info("📥 Restoring to %s: %s < %s", new_dbname, ' '.join(cmd), backup_path)
                    with open(backup_path, 'rb') as f:
                        result = subprocess.run(cmd, stdin=f, stderr=subprocess.PIPE, text=True, env=env)
                    # pg_restore returns 1 even for warnings, check if there are real errors
                    if result.returncode != 0:
                        logger.warning("⚠️  pg_restore returned code %s", result.returncode)
                        if result.stderr:
                            logger.warning("pg_restore stderr: %s", result.stderr[:500])
                        # Check for real errors vs harmless config warnings
                        stderr_lower = result.stderr.lower() if result.stderr else ""
                        # Harmless errors to ignore
                        harmless_errors = [
                            "transaction_timeout",  # Config parameter that may not exist in all PG versions
                            "idle_in_transaction_session_timeout"  # Another version-specific parameter
                        ]
                        # Check if errors are only harmless ones
                        is_harmless = any(err in stderr_lower for err in harmless_errors)
                        has_real_errors = "error:" in stderr_lower and not all(
                            err in stderr_lower for err in harmless_errors
                        )
                        if has_real_errors and not is_harmless:
                            logger.error("❌ pg_restore had REAL errors: %s", result.stderr[:1000])
                            # Try to drop the failed database
                            subprocess.run(['psql', '-h', host, '-U', user, '-d', 'postgres', '-c',
                                          f"DROP DATABASE IF EXISTS {new_dbname};"], env=env)
                            raise RuntimeError(f"pg_restore failed with errors")
                        else:
                            logger.info("✅ Restore completed (harmless config warnings ignored)")
                else:
                    # Restore from plain SQL
                    cmd = ['psql', '-h', host, '-U', user, '-d', new_dbname]
                    logger.info("📥 Executing: %s < %s", ' '.join(cmd), backup_path)
                    with open(backup_path, 'rb') as f:
-                        result = subprocess.run(cmd, stdin=f, stderr=subprocess.PIPE, text=True, env=env)
+                        result = subprocess.run(cmd, stdin=f, stderr=subprocess.PIPE, check=True, env=env)
-                    if result.returncode != 0:
+                else:
-                        logger.error("❌ psql stderr: %s", result.stderr)
+                    # Restore from plain SQL
-                        raise RuntimeError(f"psql failed with code {result.returncode}")
+                    cmd = ['psql', '-h', host, '-U', user, '-d', dbname]
                    logger.info("📥 Executing: %s < %s", ' '.join(cmd), backup_path)
                    with open(backup_path, 'rb') as f:
                        result = subprocess.run(cmd, stdin=f, stderr=subprocess.PIPE, check=True, env=env)
                # Release file lock
-                fcntl.flock(lock_f.fileno(), fcntl.LOCK_UN)
+                fcntl.flock(f.fileno(), fcntl.LOCK_UN)
-            logger.info("✅ Database restore completed successfully to: %s", new_dbname)
+            logger.info("✅ Database restore completed successfully")
            logger.info("🔧 NEXT STEPS:")
            logger.info("   1. Update .env: DATABASE_URL=postgresql://%s:%s@%s:5432/%s", 
                       user, "***", host, new_dbname)
            logger.info("   2. Restart: docker-compose restart api")
            logger.info("   3. Test system thoroughly")
            logger.info("   4. If OK, cleanup old database:")
            logger.info("      docker exec bmc-hub-postgres psql -U %s -d postgres -c 'DROP DATABASE %s;'", 
                       user, dbname)
            logger.info("      docker exec bmc-hub-postgres psql -U %s -d postgres -c 'ALTER DATABASE %s RENAME TO %s;'", 
                       user, new_dbname, dbname)
            logger.info("   5. Revert .env and restart")
-            # Store new database name in notification for user
+            # Log notification
            execute_insert(
                """INSERT INTO backup_notifications (backup_job_id, event_type, message)
-                   VALUES (%s, %s, %s) RETURNING id""",
+                   VALUES (%s, %s, %s)""",
-                (job_id, 'backup_success', 
+                (job_id, 'restore_started', f'Database restored from backup: {backup_path.name}')
                 f'✅ Database restored to: {new_dbname}\n'
                 f'Update .env: DATABASE_URL=postgresql://{user}:PASSWORD@{host}:5432/{new_dbname}')
            )
            return True
@ -535,11 +439,6 @@ class BackupService:
            logger.error("❌ Restore blocked: BACKUP_READ_ONLY=true")
            return False
        if settings.BACKUP_RESTORE_DRY_RUN:
            logger.warning("🔄 DRY RUN MODE: Would restore files from backup job %s", job_id)
            logger.warning("🔄 Set BACKUP_RESTORE_DRY_RUN=false to actually restore")
            return False
        # Get backup job
        backup = execute_query_single(
            "SELECT * FROM backup_jobs WHERE id = %s AND job_type = 'files'",
@ -650,16 +549,11 @@ class BackupService:
            # Create remote directory if needed
            remote_path = settings.SFTP_REMOTE_PATH
            if remote_path and remote_path not in ('.', '/', ''):
                logger.info("📁 Ensuring remote directory exists: %s", remote_path)
            self._ensure_remote_directory(sftp, remote_path)
                logger.info("✅ Remote directory ready")
            # Upload file
            remote_file = f"{remote_path}/{backup_path.name}"
            logger.info("📤 Uploading to: %s", remote_file)
            sftp.put(str(backup_path), remote_file)
            logger.info("✅ Upload completed")
            # Verify upload
            remote_stat = sftp.stat(remote_file)
@ -731,7 +625,7 @@ class BackupService:
            # Log notification
            execute_insert(
                """INSERT INTO backup_notifications (event_type, message)
-                   VALUES (%s, %s) RETURNING id""",
+                   VALUES (%s, %s)""",
                ('storage_low',
                 f"Backup storage usage at {usage_pct:.1f}% ({stats['total_size_gb']:.2f} GB / {settings.BACKUP_MAX_SIZE_GB} GB)")
            )
@ -775,28 +669,21 @@ class BackupService:
    def _ensure_remote_directory(self, sftp: paramiko.SFTPClient, path: str):
        """Create remote directory if it doesn't exist (recursive)"""
-        # Skip if path is root or current directory
+        dirs = []
-        if not path or path in ('.', '/', ''):
+        current = path
            return
-        # Try to stat the directory
+        while current != '/':
            dirs.append(current)
            current = os.path.dirname(current)
        dirs.reverse()
        for dir_path in dirs:
            try:
-            sftp.stat(path)
+                sftp.stat(dir_path)
            logger.info("✅ Directory exists: %s", path)
            return
            except FileNotFoundError:
-            # Directory doesn't exist, create it
+                sftp.mkdir(dir_path)
-            try:
+                logger.info("📁 Created remote directory: %s", dir_path)
                # Try to create parent directory first
                parent = os.path.dirname(path)
                if parent and parent != path:
                    self._ensure_remote_directory(sftp, parent)
                # Create this directory
                sftp.mkdir(path)
                logger.info("📁 Created remote directory: %s", path)
            except Exception as e:
                logger.warning("⚠️  Could not create directory %s: %s", path, str(e))
 # Singleton instance
--- a/app/backups/frontend/views.py
+++ b/app/backups/frontend/views.py
@ -8,13 +8,13 @@ from fastapi.templating import Jinja2Templates
 from fastapi.responses import HTMLResponse
 router = APIRouter()
-templates = Jinja2Templates(directory="app/backups/templates")
+templates = Jinja2Templates(directory="app")
@router.get("/backups", response_class=HTMLResponse)
 async def backups_dashboard(request: Request):
    """Backup system dashboard page"""
-    return templates.TemplateResponse("index.html", {
+    return templates.TemplateResponse("backups/templates/index.html", {
        "request": request,
        "title": "Backup System"
    })
--- a/app/backups/templates/index.html
+++ b/app/backups/templates/index.html
@ -248,15 +248,11 @@
            </div>
            <div class="col-md-4">
                <div class="card">
-                    <div class="card-header d-flex justify-content-between align-items-center">
+                    <div class="card-header">
-                        <span><i class="bi bi-clock-history"></i> Scheduled Jobs</span>
+                        <i class="bi bi-clock-history"></i> Scheduler Status
                        <button class="btn btn-light btn-sm" onclick="loadSchedulerStatus()">
                            <i class="bi bi-arrow-clockwise"></i>
                        </button>
                    </div>
-                    <div class="card-body p-0">
+                    <div class="card-body">
                        <div id="scheduler-status">
                            <div class="text-center p-4">
                            <div class="spinner-border spinner-border-sm" role="status"></div>
                            <span class="ms-2">Loading...</span>
                        </div>
@ -264,7 +260,6 @@
                </div>
            </div>
        </div>
        </div>
        <!-- Backup History -->
        <div class="row">
@ -385,6 +380,12 @@
        // Load backups list
        async function loadBackups() {
            // TODO: Implement /api/v1/backups/jobs endpoint
            console.warn('⚠️ Backups API ikke implementeret endnu');
            document.getElementById('backups-table').innerHTML = '<tr><td colspan="8" class="text-center text-warning"><i class="bi bi-exclamation-triangle me-2"></i>Backup API er ikke implementeret endnu</td></tr>';
            return;
            /* Disabled until API implemented:
            try {
                const response = await fetch('/api/v1/backups/jobs?limit=50');
                const backups = await response.json();
@ -438,6 +439,10 @@
        // Load storage stats
        async function loadStorageStats() {
            // TODO: Implement /api/v1/backups/storage endpoint
            return;
            /* Disabled until API implemented:
            try {
                const response = await fetch('/api/v1/backups/storage');
                const stats = await response.json();
@ -469,6 +474,10 @@
        // Load notifications
        async function loadNotifications() {
            // TODO: Implement /api/v1/backups/notifications endpoint
            return;
            /* Disabled until API implemented:
            try {
                const response = await fetch('/api/v1/backups/notifications?limit=10');
                const notifications = await response.json();
@ -498,6 +507,10 @@
        // Load scheduler status
        async function loadSchedulerStatus() {
            // TODO: Implement /api/v1/backups/scheduler/status endpoint
            return;
            /* Disabled until API implemented:
            try {
                const response = await fetch('/api/v1/backups/scheduler/status');
                const status = await response.json();
@ -506,143 +519,38 @@
                if (!status.running) {
                    container.innerHTML = `
-                        <div class="alert alert-warning mb-0 m-3">
+                        <div class="alert alert-warning mb-0">
                            <i class="bi bi-exclamation-triangle"></i> Scheduler not running
                        </div>
                    `;
                    return;
                }
-                // Group jobs by type
+                container.innerHTML = `
-                const backupJobs = status.jobs.filter(j => ['daily_backup', 'monthly_backup'].includes(j.id));
+                    <div class="alert alert-success mb-0">
-                const maintenanceJobs = status.jobs.filter(j => ['backup_rotation', 'storage_check', 'offsite_upload', 'offsite_retry'].includes(j.id));
+                        <i class="bi bi-check-circle"></i> Active
                const emailJob = status.jobs.find(j => j.id === 'email_fetch');
                let html = `
                    <div class="list-group list-group-flush">
                        <div class="list-group-item bg-success bg-opacity-10">
                            <div class="d-flex align-items-center">
                                <i class="bi bi-check-circle-fill text-success me-2"></i>
                                <strong>Scheduler Active</strong>
                            </div>
                    </div>
                    <small class="text-muted">Next jobs:</small>
                    <ul class="list-unstyled mb-0 mt-1">
                        ${status.jobs.slice(0, 3).map(j => `
                            <li><small>${j.name}: ${j.next_run ? formatDate(j.next_run) : 'N/A'}</small></li>
                        `).join('')}
                    </ul>
                `;
                // Email Fetch Job
                if (emailJob) {
                    const nextRun = emailJob.next_run ? new Date(emailJob.next_run) : null;
                    const timeUntil = nextRun ? formatTimeUntil(nextRun) : 'N/A';
                    html += `
                        <div class="list-group-item">
                            <div class="d-flex justify-content-between align-items-start">
                                <div>
                                    <i class="bi bi-envelope text-primary"></i>
                                    <strong class="ms-1">Email Fetch</strong>
                                    <br>
                                    <small class="text-muted">Every 5 minutes</small>
                                </div>
                                <span class="badge bg-primary">${timeUntil}</span>
                            </div>
                        </div>
                    `;
                }
                // Backup Jobs
                if (backupJobs.length > 0) {
                    html += `
                        <div class="list-group-item bg-light">
                            <small class="text-muted fw-bold"><i class="bi bi-database"></i> BACKUP JOBS</small>
                        </div>
                    `;
                    backupJobs.forEach(job => {
                        const nextRun = job.next_run ? new Date(job.next_run) : null;
                        const timeUntil = nextRun ? formatTimeUntil(nextRun) : 'N/A';
                        const icon = job.id === 'daily_backup' ? 'bi-arrow-repeat' : 'bi-calendar-month';
                        html += `
                            <div class="list-group-item">
                                <div class="d-flex justify-content-between align-items-start">
                                    <div>
                                        <i class="bi ${icon} text-info"></i>
                                        <small class="ms-1">${job.name}</small>
                                        <br>
                                        <small class="text-muted">${nextRun ? formatDateTime(nextRun) : 'N/A'}</small>
                                    </div>
                                    <span class="badge bg-info">${timeUntil}</span>
                                </div>
                            </div>
                        `;
                    });
                }
                // Maintenance Jobs
                if (maintenanceJobs.length > 0) {
                    html += `
                        <div class="list-group-item bg-light">
                            <small class="text-muted fw-bold"><i class="bi bi-wrench"></i> MAINTENANCE</small>
                        </div>
                    `;
                    maintenanceJobs.forEach(job => {
                        const nextRun = job.next_run ? new Date(job.next_run) : null;
                        const timeUntil = nextRun ? formatTimeUntil(nextRun) : 'N/A';
                        html += `
                            <div class="list-group-item">
                                <div class="d-flex justify-content-between align-items-start">
                                    <div style="max-width: 70%;">
                                        <i class="bi bi-gear text-secondary"></i>
                                        <small class="ms-1">${job.name}</small>
                                        <br>
                                        <small class="text-muted">${nextRun ? formatDateTime(nextRun) : 'N/A'}</small>
                                    </div>
                                    <span class="badge bg-secondary text-nowrap">${timeUntil}</span>
                                </div>
                            </div>
                        `;
                    });
                }
                html += `</div>`;
                container.innerHTML = html;
            } catch (error) {
                console.error('Load scheduler status error:', error);
                document.getElementById('scheduler-status').innerHTML = `
                    <div class="alert alert-danger m-3">
                        <i class="bi bi-exclamation-triangle"></i> Failed to load scheduler status
                    </div>
                `;
            }
        }
        function formatTimeUntil(date) {
            const now = new Date();
            const diff = date - now;
            if (diff < 0) return 'Overdue';
            const minutes = Math.floor(diff / 60000);
            const hours = Math.floor(minutes / 60);
            const days = Math.floor(hours / 24);
            if (days > 0) return `${days}d`;
            if (hours > 0) return `${hours}h`;
            if (minutes > 0) return `${minutes}m`;
            return 'Now';
        }
        function formatDateTime(date) {
            return date.toLocaleString('da-DK', {
                day: '2-digit',
                month: '2-digit',
                year: 'numeric',
                hour: '2-digit',
                minute: '2-digit'
            });
        }
        // Create manual backup
        async function createBackup(event) {
            event.preventDefault();
            const resultDiv = document.getElementById('backup-result');
            resultDiv.innerHTML = '<div class="alert alert-warning"><i class="bi bi-exclamation-triangle me-2"></i>Backup API er ikke implementeret endnu</div>';
            return;
            /* Disabled until API implemented:
            const type = document.getElementById('backup-type').value;
            const isMonthly = document.getElementById('is-monthly').checked;
@ -719,7 +627,6 @@
            } catch (error) {
                resultDiv.innerHTML = `<div class="alert alert-danger">Upload error: ${error.message}</div>`;
            }
            */
        }
        // Show restore modal
@ -732,13 +639,11 @@
        // Confirm restore
        async function confirmRestore() {
-            if (!selectedJobId) return;
+            alert('⚠️ Restore API er ikke implementeret endnu');
            return;
-            // Show loading state
+            /* Disabled until API implemented:
-            const modalBody = document.querySelector('#restoreModal .modal-body');
+            if (!selectedJobId) return;
            const confirmBtn = document.querySelector('#restoreModal .btn-danger');
            confirmBtn.disabled = true;
            confirmBtn.innerHTML = '<span class="spinner-border spinner-border-sm me-2"></span>Restoring...';
            try {
                const response = await fetch(`/api/v1/backups/restore/${selectedJobId}`, {
@ -749,132 +654,39 @@
                const result = await response.json();
                if (response.ok && result.success) {
                    // Hide modal
                restoreModal.hide();
-                    // Show success with new database instructions
+                if (response.ok) {
-                    if (result.new_database) {
+                    alert('Restore started! System entering maintenance mode.');
                        showRestoreSuccess(result);
                    } else {
                        alert('✅ Restore completed successfully!');
                    window.location.reload();
                    }
                } else {
-                    alert('❌ Restore failed: ' + (result.detail || result.message || 'Unknown error'));
+                    alert('Restore failed: ' + result.detail);
                    confirmBtn.disabled = false;
                    confirmBtn.innerHTML = 'Restore';
                }
            } catch (error) {
-                alert('❌ Restore error: ' + error.message);
+                alert('Restore error: ' + error.message);
                confirmBtn.disabled = false;
                confirmBtn.innerHTML = 'Restore';
            }
        }
        function showRestoreSuccess(result) {
            // Create modal with instructions
            const instructionsHtml = `
                <div class="modal fade" id="restoreSuccessModal" tabindex="-1" data-bs-backdrop="static">
                    <div class="modal-dialog modal-lg">
                        <div class="modal-content">
                            <div class="modal-header bg-success text-white">
                                <h5 class="modal-title">
                                    <i class="bi bi-check-circle-fill me-2"></i>
                                    Database Restored Successfully!
                                </h5>
                            </div>
                            <div class="modal-body">
                                <div class="alert alert-info">
                                    <i class="bi bi-info-circle me-2"></i>
                                    <strong>Safe Restore:</strong> Database restored to NEW database: 
                                    <code>${result.new_database}</code>
                                </div>
                                <h6 class="mt-4 mb-3">📋 Next Steps:</h6>
                                <ol class="list-group list-group-numbered">
                                    ${result.instructions.map(instr => `
                                        <li class="list-group-item">
                                            <div class="d-flex justify-content-between align-items-start">
                                                <div class="ms-2 me-auto">
                                                    ${instr}
                                                    ${instr.includes('DATABASE_URL') ? `
                                                        <button class="btn btn-sm btn-outline-primary mt-2" onclick="copyToClipboard('${result.instructions[0].split(': ')[1]}')">
                                                            <i class="bi bi-clipboard"></i> Copy DATABASE_URL
                                                        </button>
                                                    ` : ''}
                                                </div>
                                            </div>
                                        </li>
                                    `).join('')}
                                </ol>
                                <div class="alert alert-warning mt-4">
                                    <i class="bi bi-exclamation-triangle me-2"></i>
                                    <strong>Important:</strong> Test system thoroughly before completing cleanup!
                                </div>
                                <div class="mt-4">
                                    <h6>🔧 Cleanup Commands (after testing):</h6>
                                    <pre class="bg-dark text-light p-3 rounded"><code>docker-compose stop api
 echo 'DROP DATABASE bmc_hub;' | docker exec -i bmc-hub-postgres psql -U bmc_hub -d postgres
 echo 'ALTER DATABASE ${result.new_database} RENAME TO bmc_hub;' | docker exec -i bmc-hub-postgres psql -U bmc_hub -d postgres
 # Revert .env to use bmc_hub
 docker-compose start api</code></pre>
                                </div>
                            </div>
                            <div class="modal-footer">
                                <button type="button" class="btn btn-primary" onclick="location.reload()">
                                    <i class="bi bi-arrow-clockwise me-2"></i>Reload Page
                                </button>
                            </div>
                        </div>
                    </div>
                </div>
            `;
            // Append to body and show
            document.body.insertAdjacentHTML('beforeend', instructionsHtml);
            const successModal = new bootstrap.Modal(document.getElementById('restoreSuccessModal'));
            successModal.show();
        }
        function copyToClipboard(text) {
            navigator.clipboard.writeText(text).then(() => {
                alert('✅ Copied to clipboard!');
            }).catch(err => {
                alert('❌ Failed to copy: ' + err);
            });
        }
        // Upload to offsite
        async function uploadOffsite(jobId) {
-            if (!confirm('☁️ Upload this backup to offsite SFTP storage?\n\nTarget: sftp.acdu.dk:9022/backups')) return;
+            alert('⚠️ Offsite upload API er ikke implementeret endnu');
            return;
-            // Show loading indicator
+            /* Disabled until API implemented:
-            const btn = event.target.closest('button');
+            if (!confirm('Upload this backup to offsite storage?')) return;
            const originalHtml = btn.innerHTML;
            btn.disabled = true;
            btn.innerHTML = '<span class="spinner-border spinner-border-sm me-2"></span>Uploading...';
            try {
                const response = await fetch(`/api/v1/backups/offsite/${jobId}`, {method: 'POST'});
                const result = await response.json();
                // Reset button
                btn.disabled = false;
                btn.innerHTML = originalHtml;
                if (response.ok) {
-                    alert('✅ ' + result.message);
+                    alert(result.message);
                    loadBackups();
                } else {
-                    alert('❌ Upload failed: ' + result.detail);
+                    alert('Upload failed: ' + result.detail);
                }
            } catch (error) {
-                btn.disabled = false;
+                alert('Upload error: ' + error.message);
                btn.innerHTML = originalHtml;
                alert('❌ Upload error: ' + error.message);
            }
        }
@ -898,7 +710,6 @@ docker-compose start api</code></pre>
            } catch (error) {
                alert('Delete error: ' + error.message);
            }
            */
        }
        // Acknowledge notification
@ -913,7 +724,6 @@ docker-compose start api</code></pre>
            } catch (error) {
                console.error('Acknowledge error:', error);
            }
            */
        }
        // Refresh backups
--- a/app/billing/backend/supplier_invoices.py
+++ b/app/billing/backend/supplier_invoices.py
--- a/app/billing/frontend/supplier_invoices.html
+++ b/app/billing/frontend/supplier_invoices.html
--- a/app/billing/frontend/supplier_invoices_v1_backup.html
+++ b/app/billing/frontend/supplier_invoices_v1_backup.html
--- a/app/billing/frontend/template_builder.html
+++ b/app/billing/frontend/template_builder.html
@ -1360,7 +1360,7 @@ async function autoGenerateTemplate() {
    try {
        // Call Ollama to analyze the invoice
-        const response = await fetch('/api/v1/supplier-invoices/ai/analyze', {
+        const response = await fetch('/api/v1/supplier-invoices/ai-analyze', {
            method: 'POST',
            headers: { 'Content-Type': 'application/json' },
            body: JSON.stringify({
--- a/app/billing/frontend/views.py
+++ b/app/billing/frontend/views.py
@ -16,16 +16,7 @@ async def supplier_invoices_page(request: Request):
    """Supplier invoices (kassekladde) page"""
    return templates.TemplateResponse("billing/frontend/supplier_invoices.html", {
        "request": request,
-        "title": "Leverandør fakturaer"
+        "title": "Kassekladde"
    })
@router.get("/billing/supplier-invoices2", response_class=HTMLResponse)
 async def supplier_invoices_v1_backup(request: Request):
    """Supplier invoices V1 backup - original version"""
    return templates.TemplateResponse("billing/frontend/supplier_invoices_v1_backup.html", {
        "request": request,
        "title": "Leverandør fakturaer (V1 Backup)"
    })
--- a/app/contacts/backend/router.py
+++ b/app/contacts/backend/router.py
@ -6,71 +6,12 @@ Handles contact CRUD operations with multi-company support
 from fastapi import APIRouter, HTTPException, Query
 from typing import Optional, List
 from app.core.database import execute_query, execute_insert, execute_update
 from app.core.contact_utils import get_contact_customer_ids, get_primary_customer_id
 from app.customers.backend.router import (
    get_customer_subscriptions,
    lock_customer_subscriptions,
    save_subscription_comment,
    get_subscription_comment,
    get_subscription_billing_matrix,
    SubscriptionComment,
 )
 import logging
 logger = logging.getLogger(__name__)
 router = APIRouter()
@router.get("/contacts-debug", response_model=dict)
 async def debug_contacts():
    """
    Debug endpoint: Check contact-company links
    """
    try:
        # Count links
        links = execute_query("SELECT COUNT(*) as total FROM contact_companies")
        # Get sample with links
        sample = execute_query("""
            SELECT 
                c.id, c.first_name, c.last_name,
                COUNT(cc.customer_id) as company_count,
                ARRAY_AGG(cu.name) as company_names
            FROM contacts c
            LEFT JOIN contact_companies cc ON c.id = cc.contact_id
            LEFT JOIN customers cu ON cc.customer_id = cu.id
            GROUP BY c.id, c.first_name, c.last_name
            HAVING COUNT(cc.customer_id) > 0
            LIMIT 10
        """)
        # Test the actual query used in get_contacts
        test_query = """
            SELECT 
                c.id, c.first_name, c.last_name,
                COUNT(DISTINCT cc.customer_id) as company_count,
                ARRAY_AGG(DISTINCT cu.name ORDER BY cu.name) FILTER (WHERE cu.name IS NOT NULL) as company_names
            FROM contacts c
            LEFT JOIN contact_companies cc ON c.id = cc.contact_id
            LEFT JOIN customers cu ON cc.customer_id = cu.id
            GROUP BY c.id, c.first_name, c.last_name
            ORDER BY c.last_name, c.first_name
            LIMIT 10
        """
        test_result = execute_query(test_query)
        return {
            "total_links": links[0]['total'] if links else 0,
            "sample_contacts_with_companies": sample or [],
            "test_query_result": test_result or [],
            "note": "If company_count is 0, the JOIN might not be working"
        }
    except Exception as e:
        logger.error(f"Debug failed: {e}", exc_info=True)
        raise HTTPException(status_code=500, detail=str(e))
@router.get("/contacts", response_model=dict)
 async def get_contacts(
    search: Optional[str] = None,
@ -129,7 +70,7 @@ async def get_contacts(
        """
        params.extend([limit, offset])
-        contacts = execute_query(query, tuple(params))  # Returns all rows
+        contacts = execute_query_single(query, tuple(params))  # Default is fetchall
        return {
            "contacts": contacts or [],
@ -157,13 +98,11 @@ async def get_contact(contact_id: int):
            FROM contacts
            WHERE id = %s
        """
-        contact_result = execute_query(contact_query, (contact_id,))
+        contact = execute_query(contact_query, (contact_id,))
-        if not contact_result:
+        if not contact:
            raise HTTPException(status_code=404, detail="Contact not found")
        contact = contact_result[0]
        # Get linked companies
        companies_query = """
            SELECT 
@ -174,7 +113,7 @@ async def get_contact(contact_id: int):
            WHERE cc.contact_id = %s
            ORDER BY cc.is_primary DESC, cu.name
        """
-        companies = execute_query(companies_query, (contact_id,))
+        companies = execute_query_single(companies_query, (contact_id,))  # Default is fetchall
        contact['companies'] = companies or []
        return contact
@ -367,88 +306,3 @@ async def unlink_contact_from_company(contact_id: int, customer_id: int):
    except Exception as e:
        logger.error(f"Failed to unlink contact from company: {e}")
        raise HTTPException(status_code=500, detail=str(e))
@router.get("/contacts/{contact_id}/related-contacts", response_model=dict)
 async def get_related_contacts(contact_id: int):
    """
    Get contacts from the same companies as the contact (excluding itself).
    """
    try:
        customer_ids = get_contact_customer_ids(contact_id)
        if not customer_ids:
            return {"contacts": []}
        placeholders = ",".join(["%s"] * len(customer_ids))
        query = f"""
            SELECT
                c.id, c.first_name, c.last_name, c.email, c.phone, c.mobile,
                c.title, c.department, c.is_active, c.vtiger_id,
                c.created_at, c.updated_at,
                ARRAY_AGG(DISTINCT cu.name ORDER BY cu.name) FILTER (WHERE cu.name IS NOT NULL) as company_names
            FROM contacts c
            JOIN contact_companies cc ON c.id = cc.contact_id
            JOIN customers cu ON cc.customer_id = cu.id
            WHERE cc.customer_id IN ({placeholders}) AND c.id <> %s
            GROUP BY c.id, c.first_name, c.last_name, c.email, c.phone, c.mobile,
                     c.title, c.department, c.is_active, c.vtiger_id, c.created_at, c.updated_at
            ORDER BY c.last_name, c.first_name
        """
        params = tuple(customer_ids + [contact_id])
        results = execute_query(query, params) or []
        return {"contacts": results}
    except Exception as e:
        logger.error(f"Failed to get related contacts for {contact_id}: {e}")
        raise HTTPException(status_code=500, detail=str(e))
@router.get("/contacts/{contact_id}/subscriptions")
 async def get_contact_subscriptions(contact_id: int):
    customer_id = get_primary_customer_id(contact_id)
    if not customer_id:
        return {
            "status": "no_linked_customer",
            "message": "Kontakt er ikke tilknyttet et firma",
            "recurring_orders": [],
            "sales_orders": [],
            "subscriptions": [],
            "expired_subscriptions": [],
            "bmc_office_subscriptions": [],
        }
    return await get_customer_subscriptions(customer_id)
@router.post("/contacts/{contact_id}/subscriptions/lock")
 async def lock_contact_subscriptions(contact_id: int, lock_request: dict):
    customer_id = get_primary_customer_id(contact_id)
    if not customer_id:
        raise HTTPException(status_code=404, detail="Kontakt har ingen tilknyttet kunde")
    return await lock_customer_subscriptions(customer_id, lock_request)
@router.post("/contacts/{contact_id}/subscription-comment")
 async def save_contact_subscription_comment(contact_id: int, data: SubscriptionComment):
    customer_id = get_primary_customer_id(contact_id)
    if not customer_id:
        raise HTTPException(status_code=404, detail="Kontakt har ingen tilknyttet kunde")
    return await save_subscription_comment(customer_id, data)
@router.get("/contacts/{contact_id}/subscription-comment")
 async def get_contact_subscription_comment(contact_id: int):
    customer_id = get_primary_customer_id(contact_id)
    if not customer_id:
        raise HTTPException(status_code=404, detail="Kontakt har ingen tilknyttet kunde")
    return await get_subscription_comment(customer_id)
@router.get("/contacts/{contact_id}/subscriptions/billing-matrix")
 async def get_contact_subscription_billing_matrix(
    contact_id: int,
    months: int = Query(default=12, ge=1, le=60, description="Number of months to show"),
 ):
    customer_id = get_primary_customer_id(contact_id)
    if not customer_id:
        raise HTTPException(status_code=404, detail="Kontakt har ingen tilknyttet kunde")
    return await get_subscription_billing_matrix(customer_id, months)
--- a/app/contacts/backend/router_simple.py
+++ b/app/contacts/backend/router_simple.py
@ -3,102 +3,15 @@ Contact API Router - Simplified (Read-Only)
 Only GET endpoints for now
 """
-from fastapi import APIRouter, HTTPException, Query, Body, status
+from fastapi import APIRouter, HTTPException, Query
 from typing import Optional
-from pydantic import BaseModel, Field
+from app.core.database import execute_query
 from app.core.database import execute_query, execute_insert
 from app.core.contact_utils import get_contact_customer_ids, get_primary_customer_id
 from app.customers.backend.router import (
    get_customer_subscriptions,
    lock_customer_subscriptions,
    save_subscription_comment,
    get_subscription_comment,
    get_subscription_billing_matrix,
    SubscriptionComment,
 )
 import logging
 logger = logging.getLogger(__name__)
 router = APIRouter()
 class ContactCreate(BaseModel):
    """Schema for creating a contact"""
    first_name: str
    last_name: str = ""
    email: Optional[str] = None
    phone: Optional[str] = None
    title: Optional[str] = None
    company_id: Optional[int] = None
 class ContactUpdate(BaseModel):
    """Schema for updating a contact"""
    first_name: Optional[str] = None
    last_name: Optional[str] = None
    email: Optional[str] = None
    phone: Optional[str] = None
    mobile: Optional[str] = None
    title: Optional[str] = None
    department: Optional[str] = None
    is_active: Optional[bool] = None
 class ContactCompanyLink(BaseModel):
    customer_id: int
    is_primary: bool = True
    role: Optional[str] = None
@router.get("/contacts-debug")
 async def debug_contacts():
    """Debug endpoint: Check contact-company links"""
    try:
        # Count links
        links = execute_query("SELECT COUNT(*) as total FROM contact_companies")
        # Get sample with links
        sample = execute_query("""
            SELECT 
                c.id, c.first_name, c.last_name,
                COUNT(cc.customer_id) as company_count,
                ARRAY_AGG(cu.name) as company_names
            FROM contacts c
            LEFT JOIN contact_companies cc ON c.id = cc.contact_id
            LEFT JOIN customers cu ON cc.customer_id = cu.id
            GROUP BY c.id, c.first_name, c.last_name
            HAVING COUNT(cc.customer_id) > 0
            LIMIT 10
        """)
        # Test the actual query used in get_contacts
        test_query = """
            SELECT 
                c.id, c.first_name, c.last_name,
                COUNT(DISTINCT cc.customer_id) as company_count,
                ARRAY_AGG(DISTINCT cu.name ORDER BY cu.name) FILTER (WHERE cu.name IS NOT NULL) as company_names
            FROM contacts c
            LEFT JOIN contact_companies cc ON c.id = cc.contact_id
            LEFT JOIN customers cu ON cc.customer_id = cu.id
            GROUP BY c.id, c.first_name, c.last_name
            ORDER BY c.last_name, c.first_name
            LIMIT 10
        """
        test_result = execute_query(test_query)
        return {
            "total_links": links[0]['total'] if links else 0,
            "sample_contacts_with_companies": sample or [],
            "test_query_result": test_result or [],
            "note": "If company_count is 0, the JOIN might not be working"
        }
    except Exception as e:
        logger.error(f"Debug failed: {e}", exc_info=True)
        raise HTTPException(status_code=500, detail=str(e))
@router.get("/contacts")
 async def get_contacts(
    search: Optional[str] = None,
@ -113,34 +26,28 @@ async def get_contacts(
        params = []
        if search:
-            where_clauses.append("(c.first_name ILIKE %s OR c.last_name ILIKE %s OR c.email ILIKE %s)")
+            where_clauses.append("(first_name ILIKE %s OR last_name ILIKE %s OR email ILIKE %s)")
            params.extend([f"%{search}%", f"%{search}%", f"%{search}%"])
        if is_active is not None:
-            where_clauses.append("c.is_active = %s")
+            where_clauses.append("is_active = %s")
            params.append(is_active)
        where_sql = "WHERE " + " AND ".join(where_clauses) if where_clauses else ""
-        # Count total (needs alias c for consistency)
+        # Count total
-        count_query = f"SELECT COUNT(*) as count FROM contacts c {where_sql}"
+        count_query = f"SELECT COUNT(*) as count FROM contacts {where_sql}"
        count_result = execute_query(count_query, tuple(params))
        total = count_result[0]['count'] if count_result else 0
-        # Get contacts with company info
+        # Get contacts
        query = f"""
            SELECT 
-                c.id, c.first_name, c.last_name, c.email, c.phone, c.mobile,
+                id, first_name, last_name, email, phone, mobile,
-                c.title, c.department, c.is_active, c.created_at, c.updated_at,
+                title, department, is_active, created_at, updated_at
-                COUNT(DISTINCT cc.customer_id) as company_count,
+            FROM contacts
                ARRAY_AGG(DISTINCT cu.name ORDER BY cu.name) FILTER (WHERE cu.name IS NOT NULL) as company_names
            FROM contacts c
            LEFT JOIN contact_companies cc ON c.id = cc.contact_id
            LEFT JOIN customers cu ON cc.customer_id = cu.id
            {where_sql}
-            GROUP BY c.id, c.first_name, c.last_name, c.email, c.phone, c.mobile,
+            ORDER BY first_name, last_name
                     c.title, c.department, c.is_active, c.created_at, c.updated_at
            ORDER BY company_count DESC, c.last_name, c.first_name
            LIMIT %s OFFSET %s
        """
        params.extend([limit, offset])
@ -158,67 +65,14 @@ async def get_contacts(
        raise HTTPException(status_code=500, detail=str(e))
@router.post("/contacts", status_code=status.HTTP_201_CREATED)
 async def create_contact(contact: ContactCreate):
    """
    Create a new basic contact
    """
    try:
        # Check if email exists
        if contact.email:
            existing = execute_query(
                "SELECT id FROM contacts WHERE email = %s", 
                (contact.email,)
            )
            if existing:
                # Return existing contact if found? Or error?
                # For now, let's error to be safe, or just return it?
                # User prompted "Smart Create", implies if it exists, use it?
                # But safer to say "Email already exists"
                pass 
        insert_query = """
            INSERT INTO contacts (first_name, last_name, email, phone, title, is_active)
            VALUES (%s, %s, %s, %s, %s, true)
            RETURNING id
        """
        contact_id = execute_insert(
            insert_query,
            (contact.first_name, contact.last_name, contact.email, contact.phone, contact.title)
        )
        # Link to company if provided
        if contact.company_id:
            try:
                link_query = """
                    INSERT INTO contact_companies (contact_id, customer_id, is_primary, role)
                    VALUES (%s, %s, true, 'primary')
                    ON CONFLICT (contact_id, customer_id)
                    DO UPDATE SET is_primary = EXCLUDED.is_primary, role = EXCLUDED.role
                    RETURNING id
                """
                execute_insert(link_query, (contact_id, contact.company_id))
            except Exception as e:
                logger.error(f"Failed to link new contact {contact_id} to company {contact.company_id}: {e}")
                # Don't fail the whole request, just log it
        return await get_contact(contact_id)
    except Exception as e:
        logger.error(f"Failed to create contact: {e}")
        raise HTTPException(status_code=500, detail=str(e))
@router.get("/contacts/{contact_id}")
 async def get_contact(contact_id: int):
-    """Get a single contact by ID with linked companies"""
+    """Get a single contact by ID"""
    try:
        # Get contact info
        query = """
            SELECT 
                id, first_name, last_name, email, phone, mobile,
-                title, department, is_active, user_company, vtiger_id,
+                title, department, is_active, user_company,
                created_at, updated_at
            FROM contacts
            WHERE id = %s
@ -228,233 +82,10 @@ async def get_contact(contact_id: int):
        if not contacts:
            raise HTTPException(status_code=404, detail="Contact not found")
-        contact = contacts[0]
+        return contacts[0]
        # Get linked companies
        companies_query = """
            SELECT 
                cu.id, cu.name, cu.cvr_number,
                cc.is_primary, cc.role, cc.notes
            FROM contact_companies cc
            JOIN customers cu ON cc.customer_id = cu.id
            WHERE cc.contact_id = %s
            ORDER BY cc.is_primary DESC, cu.name
        """
        companies = execute_query(companies_query, (contact_id,))
        contact['companies'] = companies or []
        return contact
    except HTTPException:
        raise
    except Exception as e:
        logger.error(f"Failed to get contact {contact_id}: {e}")
        raise HTTPException(status_code=500, detail=str(e))
@router.put("/contacts/{contact_id}")
 async def update_contact(contact_id: int, contact_data: ContactUpdate):
    """Update a contact"""
    try:
        # Ensure contact exists
        contact = execute_query("SELECT id FROM contacts WHERE id = %s", (contact_id,))
        if not contact:
            raise HTTPException(status_code=404, detail="Contact not found")
        # Build update query dynamically
        update_fields = []
        params = []
        for field, value in contact_data.model_dump(exclude_unset=True).items():
            update_fields.append(f"{field} = %s")
            params.append(value)
        if not update_fields:
            # No fields to update
            return await get_contact(contact_id)
        params.append(contact_id)
        update_query = f"""
            UPDATE contacts
            SET {', '.join(update_fields)}, updated_at = NOW()
            WHERE id = %s
            RETURNING id
        """
        execute_query(update_query, tuple(params))
        return await get_contact(contact_id)
    except HTTPException:
        raise
    except Exception as e:
        logger.error(f"Failed to update contact {contact_id}: {e}")
        raise HTTPException(status_code=500, detail=str(e))
@router.post("/contacts/{contact_id}/companies")
 async def link_contact_to_company(contact_id: int, link: ContactCompanyLink):
    """Link a contact to a company"""
    try:
        # Ensure contact exists
        contact = execute_query("SELECT id FROM contacts WHERE id = %s", (contact_id,))
        if not contact:
            raise HTTPException(status_code=404, detail="Contact not found")
        # Ensure customer exists
        customer = execute_query("SELECT id FROM customers WHERE id = %s", (link.customer_id,))
        if not customer:
            raise HTTPException(status_code=404, detail="Customer not found")
        query = """
            INSERT INTO contact_companies (contact_id, customer_id, is_primary, role)
            VALUES (%s, %s, %s, %s)
            ON CONFLICT (contact_id, customer_id)
            DO UPDATE SET is_primary = EXCLUDED.is_primary, role = EXCLUDED.role
            RETURNING id
        """
        execute_insert(query, (contact_id, link.customer_id, link.is_primary, link.role))
        return {"message": "Contact linked to company successfully"}
    except HTTPException:
        raise
    except Exception as e:
        logger.error(f"Failed to link contact to company: {e}")
        raise HTTPException(status_code=500, detail=str(e))
@router.get("/contacts/{contact_id}/related-contacts")
 async def get_related_contacts(contact_id: int):
    """Get contacts from the same companies as the contact (excluding itself)."""
    try:
        customer_ids = get_contact_customer_ids(contact_id)
        if not customer_ids:
            return {"contacts": []}
        placeholders = ",".join(["%s"] * len(customer_ids))
        query = f"""
            SELECT
                c.id, c.first_name, c.last_name, c.email, c.phone, c.mobile,
                c.title, c.department, c.is_active, c.vtiger_id,
                c.created_at, c.updated_at,
                ARRAY_AGG(DISTINCT cu.name ORDER BY cu.name) FILTER (WHERE cu.name IS NOT NULL) as company_names
            FROM contacts c
            JOIN contact_companies cc ON c.id = cc.contact_id
            JOIN customers cu ON cc.customer_id = cu.id
            WHERE cc.customer_id IN ({placeholders}) AND c.id <> %s
            GROUP BY c.id, c.first_name, c.last_name, c.email, c.phone, c.mobile,
                     c.title, c.department, c.is_active, c.vtiger_id, c.created_at, c.updated_at
            ORDER BY c.last_name, c.first_name
        """
        params = tuple(customer_ids + [contact_id])
        results = execute_query(query, params) or []
        return {"contacts": results}
    except Exception as e:
        logger.error(f"Failed to get related contacts for {contact_id}: {e}")
        raise HTTPException(status_code=500, detail=str(e))
@router.get("/contacts/{contact_id}/subscriptions")
 async def get_contact_subscriptions(contact_id: int):
    customer_id = get_primary_customer_id(contact_id)
    if not customer_id:
        return {
            "status": "no_linked_customer",
            "message": "Kontakt er ikke tilknyttet et firma",
            "recurring_orders": [],
            "sales_orders": [],
            "subscriptions": [],
            "expired_subscriptions": [],
            "bmc_office_subscriptions": [],
        }
    return await get_customer_subscriptions(customer_id)
@router.post("/contacts/{contact_id}/subscriptions/lock")
 async def lock_contact_subscriptions(contact_id: int, lock_request: dict):
    customer_id = get_primary_customer_id(contact_id)
    if not customer_id:
        raise HTTPException(status_code=404, detail="Kontakt har ingen tilknyttet kunde")
    return await lock_customer_subscriptions(customer_id, lock_request)
@router.post("/contacts/{contact_id}/subscription-comment")
 async def save_contact_subscription_comment(contact_id: int, data: SubscriptionComment):
    customer_id = get_primary_customer_id(contact_id)
    if not customer_id:
        raise HTTPException(status_code=404, detail="Kontakt har ingen tilknyttet kunde")
    return await save_subscription_comment(customer_id, data)
@router.get("/contacts/{contact_id}/subscription-comment")
 async def get_contact_subscription_comment(contact_id: int):
    customer_id = get_primary_customer_id(contact_id)
    if not customer_id:
        raise HTTPException(status_code=404, detail="Kontakt har ingen tilknyttet kunde")
    return await get_subscription_comment(customer_id)
@router.get("/contacts/{contact_id}/subscriptions/billing-matrix")
 async def get_contact_subscription_billing_matrix(
    contact_id: int,
    months: int = Query(default=12, ge=1, le=60, description="Number of months to show"),
 ):
    customer_id = get_primary_customer_id(contact_id)
    if not customer_id:
        raise HTTPException(status_code=404, detail="Kontakt har ingen tilknyttet kunde")
    return await get_subscription_billing_matrix(customer_id, months)
@router.get("/contacts/{contact_id}/kontakt")
 async def get_contact_kontakt_history(contact_id: int, limit: int = Query(default=200, ge=1, le=1000)):
    try:
        exists = execute_query("SELECT id FROM contacts WHERE id = %s", (contact_id,))
        if not exists:
            raise HTTPException(status_code=404, detail="Contact not found")
        query = """
            SELECT * FROM (
                SELECT
                    'call' AS type,
                    t.id::text AS event_id,
                    t.started_at AS happened_at,
                    t.direction,
                    t.ekstern_nummer AS number,
                    NULL::text AS message,
                    t.duration_sec,
                    COALESCE(u.full_name, u.username) AS user_name,
                    NULL::text AS sms_status
                FROM telefoni_opkald t
                LEFT JOIN users u ON u.user_id = t.bruger_id
                WHERE t.kontakt_id = %s
                UNION ALL
                SELECT
                    'sms' AS type,
                    s.id::text AS event_id,
                    s.created_at AS happened_at,
                    NULL::text AS direction,
                    s.recipient AS number,
                    s.message,
                    NULL::int AS duration_sec,
                    COALESCE(u.full_name, u.username) AS user_name,
                    s.status AS sms_status
                FROM sms_messages s
                LEFT JOIN users u ON u.user_id = s.bruger_id
                WHERE s.kontakt_id = %s
            ) z
            ORDER BY z.happened_at DESC NULLS LAST
            LIMIT %s
        """
        rows = execute_query(query, (contact_id, contact_id, limit)) or []
        return {"items": rows}
    except HTTPException:
        raise
    except Exception as e:
        logger.error(f"Failed to fetch kontakt history for contact {contact_id}: {e}")
        raise HTTPException(status_code=500, detail=str(e))
--- a/app/contacts/frontend/contact_detail.html
+++ b/app/contacts/frontend/contact_detail.html
--- a/app/contacts/frontend/contacts.html
+++ b/app/contacts/frontend/contacts.html
@ -215,74 +215,6 @@
            </div>
        </div>
    </div>
    <!-- Edit Contact Modal -->
    <div class="modal fade" id="editContactModal" tabindex="-1">
        <div class="modal-dialog modal-lg">
            <div class="modal-content">
                <div class="modal-header">
                    <h5 class="modal-title">Rediger Kontakt</h5>
                    <button type="button" class="btn-close" data-bs-dismiss="modal"></button>
                </div>
                <div class="modal-body">
                    <form id="editContactForm">
                        <input type="hidden" id="editContactId">
                        <div class="row g-3">
                            <div class="col-md-6">
                                <label class="form-label">Fornavn <span class="text-danger">*</span></label>
                                <input type="text" class="form-control" id="editFirstNameInput" required>
                            </div>
                            <div class="col-md-6">
                                <label class="form-label">Efternavn <span class="text-danger">*</span></label>
                                <input type="text" class="form-control" id="editLastNameInput" required>
                            </div>
                            <div class="col-md-6">
                                <label class="form-label">Email</label>
                                <input type="email" class="form-control" id="editEmailInput">
                            </div>
                            <div class="col-md-6">
                                <label class="form-label">Telefon</label>
                                <input type="text" class="form-control" id="editPhoneInput">
                            </div>
                            <div class="col-md-6">
                                <label class="form-label">Mobil</label>
                                <input type="text" class="form-control" id="editMobileInput">
                            </div>
                            <div class="col-md-6">
                                <label class="form-label">Titel</label>
                                <input type="text" class="form-control" id="editTitleInput" placeholder="CEO, CTO, Manager...">
                            </div>
                            <div class="col-md-6">
                                <label class="form-label">Afdeling</label>
                                <input type="text" class="form-control" id="editDepartmentInput">
                            </div>
                            <div class="col-12">
                                <div class="form-check">
                                    <input class="form-check-input" type="checkbox" id="editIsActiveInput">
                                    <label class="form-check-label" for="editIsActiveInput">
                                        Aktiv kontakt
                                    </label>
                                </div>
                            </div>
                        </div>
                    </form>
                </div>
                <div class="modal-footer">
                    <button type="button" class="btn btn-secondary" data-bs-dismiss="modal">Annuller</button>
                    <button type="button" class="btn btn-primary" onclick="saveEditContact()">
                        <i class="bi bi-check-lg me-2"></i>Gem Ændringer
                    </button>
                </div>
            </div>
        </div>
    </div>
 {% endblock %}
 {% block extra_js %}
@ -376,19 +308,6 @@ function displayContacts(contacts) {
        const companyDisplay = companyNames.length > 0 
            ? companyNames.slice(0, 2).join(', ') + (companyNames.length > 2 ? '...' : '')
            : '-';
        const fullName = `${contact.first_name || ''} ${contact.last_name || ''}`.trim();
        const mobileLine = contact.mobile
            ? `<div class="small text-muted d-flex align-items-center gap-2">${escapeHtml(contact.mobile)}
                    <button class="btn btn-sm btn-outline-success py-0 px-2" onclick="event.stopPropagation(); contactsCallViaYealink('${escapeHtml(contact.mobile)}')">Ring op</button>
                    <button class="btn btn-sm btn-outline-primary py-0 px-2" onclick="event.stopPropagation(); openSmsPrompt('${escapeHtml(contact.mobile)}', '${escapeHtml(fullName)}', ${contact.id || 'null'})">SMS</button>
               </div>`
            : '';
        const phoneLine = !contact.mobile
            ? `<div class="small text-muted d-flex align-items-center gap-2">${escapeHtml(contact.phone || '-')}
                    ${contact.phone ? `<button class="btn btn-sm btn-outline-success py-0 px-2" onclick="event.stopPropagation(); contactsCallViaYealink('${escapeHtml(contact.phone)}')">Ring op</button>` : ''}
               </div>`
            : '';
        const smsLine = mobileLine || phoneLine;
        return `
            <tr style="cursor: pointer;" onclick="viewContact(${contact.id})">
@ -403,7 +322,7 @@ function displayContacts(contacts) {
                </td>
                <td>
                    <div class="fw-medium">${contact.email || '-'}</div>
-                    ${smsLine}
+                    <div class="small text-muted">${contact.mobile || contact.phone || '-'}</div>
                </td>
                <td class="text-muted">${contact.title || '-'}</td>
                <td>
@ -460,120 +379,8 @@ function viewContact(contactId) {
 }
 function editContact(contactId) {
-    // Load contact data and open edit modal
+    // TODO: Open edit modal
-    loadContactForEdit(contactId);
+    console.log('Edit contact:', contactId);
 }
 let contactsCurrentUserId = null;
 async function ensureContactsCurrentUserId() {
    if (contactsCurrentUserId !== null) return contactsCurrentUserId;
    try {
        const res = await fetch('/api/v1/auth/me', { credentials: 'include' });
        if (!res.ok) return null;
        const me = await res.json();
        contactsCurrentUserId = Number(me?.id) || null;
        return contactsCurrentUserId;
    } catch (e) {
        return null;
    }
 }
 async function contactsCallViaYealink(number) {
    const clean = String(number || '').trim();
    if (!clean || clean === '-') {
        alert('Intet gyldigt nummer at ringe til');
        return;
    }
    const userId = await ensureContactsCurrentUserId();
    try {
        const res = await fetch('/api/v1/telefoni/click-to-call', {
            method: 'POST',
            headers: { 'Content-Type': 'application/json' },
            credentials: 'include',
            body: JSON.stringify({ number: clean, user_id: userId })
        });
        if (!res.ok) {
            const t = await res.text();
            alert('Ring ud fejlede: ' + t);
            return;
        }
        alert('Ringer ud via Yealink...');
    } catch (e) {
        alert('Kunne ikke starte opkald');
    }
 }
 async function loadContactForEdit(contactId) {
    try {
        const response = await fetch(`/api/v1/contacts/${contactId}`);
        if (!response.ok) throw new Error('Kunne ikke indlæse kontakt');
        const contact = await response.json();
        // Fill form
        document.getElementById('editContactId').value = contactId;
        document.getElementById('editFirstNameInput').value = contact.first_name || '';
        document.getElementById('editLastNameInput').value = contact.last_name || '';
        document.getElementById('editEmailInput').value = contact.email || '';
        document.getElementById('editPhoneInput').value = contact.phone || '';
        document.getElementById('editMobileInput').value = contact.mobile || '';
        document.getElementById('editTitleInput').value = contact.title || '';
        document.getElementById('editDepartmentInput').value = contact.department || '';
        document.getElementById('editIsActiveInput').checked = contact.is_active || false;
        // Show modal
        const modal = new bootstrap.Modal(document.getElementById('editContactModal'));
        modal.show();
    } catch (error) {
        console.error('Failed to load contact:', error);
        alert('Fejl: Kunne ikke indlæse kontakt');
    }
 }
 async function saveEditContact() {
    const contactId = document.getElementById('editContactId').value;
    const firstName = document.getElementById('editFirstNameInput').value.trim();
    const lastName = document.getElementById('editLastNameInput').value.trim();
    if (!firstName || !lastName) {
        alert('Fornavn og efternavn er påkrævet');
        return;
    }
    try {
        const response = await fetch(`/api/v1/contacts/${contactId}`, {
            method: 'PUT',
            headers: { 'Content-Type': 'application/json' },
            body: JSON.stringify({
                first_name: firstName,
                last_name: lastName,
                email: document.getElementById('editEmailInput').value || null,
                phone: document.getElementById('editPhoneInput').value || null,
                mobile: document.getElementById('editMobileInput').value || null,
                title: document.getElementById('editTitleInput').value || null,
                department: document.getElementById('editDepartmentInput').value || null,
                is_active: document.getElementById('editIsActiveInput').checked
            })
        });
        if (!response.ok) {
            const error = await response.json();
            throw new Error(error.detail || 'Kunne ikke gemme kontakt');
        }
        // Close modal and reload
        const modal = bootstrap.Modal.getInstance(document.getElementById('editContactModal'));
        modal.hide();
        loadContacts();
    } catch (error) {
        console.error('Failed to save contact:', error);
        alert('Fejl: ' + error.message);
    }
 }
 async function loadCompaniesForSelect() {
--- a/Show More
+++ b/Show More
`@ -1,3 +1 @@`
	`"""Backup backend services, API routes, and scheduler."""`	`"""Backup backend services, API routes, and scheduler."""`

	`from app.backups.backend import router`