diff --git a/.github/copilot-instructions.md b/.github/copilot-instructions.md
new file mode 100644
index 0000000..0d6aa60
--- /dev/null
+++ b/.github/copilot-instructions.md
@@ -0,0 +1,305 @@
+---
+applyTo: "**"
+---
+
+# AI Agent Instructions for Digitization Toolkit
+
+## Project Overview
+
+Offline-capable digitization toolkit for Raspberry Pi with dual camera support. FastAPI backend + Svelte frontend + PostgreSQL. Designed for standalone deployment in low-resource environments (archives, community centers).
+
+**Critical Architecture Decision:** Backend runs **natively** (not in Docker) to access Raspberry Pi hardware (libcamera, picamera2). Database and frontend run in Docker.
+
+## Core Architecture Patterns
+
+### 1. Dual Deployment Modes
+
+```bash
+# Development (any machine, no cameras): All services in Docker with Vite live reload
+./scripts/start-dev.sh  # or: docker compose -f docker-compose.yml -f docker-compose.dev.yml --profile with-backend up
+
+# Production (Raspberry Pi with cameras): Native backend + Docker DB + pre-built frontend
+./scripts/start.sh      # or: docker compose up -d && cd backend && pixi run dev
+```
+
+**Why:** System camera libraries (python3-libcamera, python3-kms++) cannot be installed via pip and must be accessed from system packages.
+
+### 1a. Offline-First Frontend
+
+The frontend uses a **multi-stage production Docker build** (`frontend/Dockerfile`):
+- Stage 1 (builder): Installs npm deps + compiles SvelteKit → static Node.js server
+- Stage 2 (runner): Copies only the compiled output — no npm, no source code
+
+The running container needs **zero internet access**. The only requirement is a one-time internet-connected build:
+```bash
+# With internet access (e.g. at home / office):
+docker compose build frontend    # or: docker compose build
+
+# Then take the Pi offline — it will run forever from the cached image:
+docker compose up -d
+```
+
+Adapter: `@sveltejs/adapter-node` (produces `node build/index.js`), port 3000.
+
+`docker-compose.dev.yml` overrides the frontend service to use `Dockerfile.dev` (Vite dev server, port 5173, hot reload, volume mounts). Used only during development with internet.
+
+### 2. Camera Backend Plugin System
+
+Two interchangeable backends via `CAMERA_BACKEND` env var:
+- **picamera2** (default): Direct libcamera2 bindings, 91.5% faster, supports live preview
+- **subprocess**: Fallback using rpicam-still CLI, more compatible
+
+Implementation: [backend/capture/backends/](backend/capture/backends/)
+- `base.py`: Abstract `CameraBackend` class
+- `picamera2_backend.py`: Native picamera2 implementation  
+- `subprocess_backend.py`: CLI wrapper via rpicam-still
+
+Switch backends: Set `CAMERA_BACKEND=subprocess` in `.env`
+
+### 3. Hardware Identification System
+
+Cameras identified by **hardware ID** (model + serial), not index (0, 1). Prevents config loss when cables swap.
+
+```python
+# backend/capture/camera_registry.py
+class CameraRegistry:
+    """Global registry at PROJECTS_ROOT/cameras.json tracks:
+    - Hardware IDs (arducam_imx519_<serial>)
+    - Per-camera calibration matrices
+    - Role assignments (left/right)
+    - Human-friendly labels
+    """
+```
+
+API layer ([backend/app/api/cameras.py](backend/app/api/cameras.py)) uses index for simplicity, but core capture layer uses hardware IDs.
+
+## Database & Migrations: CRITICAL RULES
+
+### ⚠️ NEVER Add `Base.metadata.create_all()`
+
+Tables are managed **exclusively through Alembic migrations**. This is not negotiable.
+
+**WRONG:**
+```python
+# app/core/db.py
+def init_db():
+    Base.metadata.create_all(bind=engine)  # ❌ NEVER DO THIS
+```
+
+**CORRECT:**
+```python
+# app/core/db.py
+def init_db() -> None:
+    """Import all models to register them with SQLAlchemy."""
+    import app.models.document  # Just import, no create_all()
+    import app.models.camera
+    import app.models.project
+    import app.models.user
+```
+
+### Workflow for Schema Changes
+
+1. Modify model in `app/models/`
+2. Generate migration: `docker compose exec backend alembic revision --autogenerate -m "description"`
+3. Review generated file in `backend/alembic/versions/`
+4. Apply: `docker compose exec backend alembic upgrade head`
+
+**Native backend with pixi:**
+```bash
+cd backend
+pixi run db-migrate "add new column"  # Generate migration
+pixi run db-upgrade                   # Apply migration
+```
+
+### PostgreSQL Connection Format
+
+Use `postgresql+psycopg://` (psycopg3), **not** `postgresql://` (legacy psycopg2).
+
+```python
+# app/core/config.py
+DATABASE_URL = f"postgresql+psycopg://{user}:{password}@{host}:{port}/{database}"
+```
+
+## Authentication System
+
+**Custom HMAC token system** for offline/standalone operation. Do NOT suggest replacing with JWT libraries (python-jose, PyJWT) or OAuth2.
+
+```python
+# app/core/security.py
+def create_access_token(subject: str) -> str:
+    """Custom token: {b64u(payload)}.{b64u(hmac_sig)}"""
+    # No external JWT library needed for offline Raspberry Pi
+```
+
+Why: Intentionally lightweight for embedded deployment, no OAuth2 providers, minimal dependencies.
+
+## Configuration Management
+
+**Only add settings that application code actually uses.** Infrastructure settings belong in `docker-compose.yml`.
+
+```python
+# app/core/config.py
+class Settings(BaseSettings):
+    DATABASE_USER: str = "user"
+    CAMERA_BACKEND: str = "picamera2"  # ✅ Used by camera registry
+    # NOT: uvicorn_host - that's infrastructure, not application logic
+```
+
+Settings pattern:
+- `Settings` class loads from `.env` via pydantic-settings
+- Computed properties for paths: `projects_dir`, `exports_dir`, `data_dir`
+- Accessed globally via `from app.core.config import settings`
+
+## Dependency Management: Pixi (Recommended)
+
+Project migrated from venv to **pixi** for better reproducibility.
+
+```bash
+# First time setup
+cd backend
+pixi install
+pixi run setup-camera-link  # Raspberry Pi only: links system camera packages
+
+# Common commands
+pixi run dev              # Start dev server
+pixi run test             # Run pytest
+pixi run db-upgrade       # Apply migrations
+pixi add package-name     # Add dependency
+```
+
+Configuration: [backend/pixi.toml](backend/pixi.toml)
+
+**System Package Linking (Raspberry Pi):** Picamera2 requires system-installed libcamera bindings. Pixi task `setup-camera-link` creates `.pth` file to expose `/usr/lib/python3/dist-packages`.
+
+Legacy venv still works but pixi preferred for new development.
+
+## Testing Strategy
+
+```bash
+# Backend tests (in backend/ directory)
+pixi run test                  # All tests
+pixi run test-cameras          # Camera-specific integration tests
+pixi run test-verbose          # Pytest with -v
+
+# Check camera hardware detection
+rpicam-hello --list-cameras
+```
+
+Camera tests handle both backends gracefully, skip if hardware unavailable.
+
+## File Organization
+
+```
+backend/
+├── app/                    # FastAPI application
+│   ├── api/               # Route handlers (documents, cameras, projects, auth)
+│   ├── core/              # Config, DB, security
+│   ├── models/            # SQLAlchemy models
+│   └── schemas/           # Pydantic schemas
+├── capture/               # Camera capture service (hardware layer)
+│   ├── backends/         # Pluggable camera backends
+│   ├── camera_registry.py # Hardware ID tracking
+│   ├── calibration.py    # Camera calibration
+│   └── project_manager.py # Capture orchestration
+├── alembic/               # Database migrations
+└── pixi.toml              # Dependency management
+
+frontend/
+└── src/
+    ├── lib/              # Shared components/utilities
+    └── routes/           # SvelteKit pages
+```
+
+## Documentation & Script Policy for AI Agents
+
+### Documentation Files
+
+**DO NOT create new standalone documentation files** (README.md, GUIDE.md, NOTES.md, etc.) for recording changes or providing instructions.
+
+Instead:
+- **Update THIS file** (.github/copilot-instructions.md) with new patterns or architectural decisions
+- **Create .github/skills/*.md** for reusable procedures (e.g., "how to add a new camera backend")
+- **Update existing docs** (backend/DEVELOPMENT.md, backend/DEPENDENCIES.md) if adding technical details
+
+**Never create:**
+- ❌ CHANGELOG.md, UPDATES.md, NOTES.md - Use git commits
+- ❌ SETUP.md, QUICKSTART.md, CHEATSHEET.md - Info belongs in README.md
+- ❌ INSTRUCTIONS.md, AGENT.md - Update this file instead
+- ❌ Informational "status update" files - These are traceback logs, not documentation
+
+### Shell Scripts
+
+**DO NOT create shell scripts for simple tasks.** The project uses pixi tasks for backend workflows.
+
+**Only create scripts for:**
+- ✅ Multi-service orchestration (start-dev.sh, start.sh, stop.sh)
+- ✅ System-level operations (install-service.sh, uninstall-service.sh)
+
+**Never create scripts for:**
+- ❌ Database migrations - Use `pixi run db-upgrade` or `pixi run db-migrate "message"`
+- ❌ Running single services - Use `pixi run dev` directly
+- ❌ One-time setup tasks - Document in README.md instead
+- ❌ Simple command wrappers - Users can run commands directly
+
+**Existing pixi tasks** (defined in backend/pixi.toml):
+- `pixi run dev` - Start development server
+- `pixi run test` - Run tests
+- `pixi run db-upgrade` - Apply migrations
+- `pixi run db-migrate "message"` - Create migration
+- `pixi run setup-camera-link` - Link system camera packages
+
+**Decision criteria:** "Does this require coordinating multiple services or system-level changes?" If no, use pixi tasks or document the command.
+
+## Common Mistakes AI Agents Make
+
+1. ❌ Re-adding `Base.metadata.create_all()` after it was intentionally removed
+2. ❌ Suggesting JWT/OAuth2 for a standalone offline application
+3. ❌ Adding unused config fields "just in case" to Settings
+4. ❌ Using `postgresql://` instead of `postgresql+psycopg://`
+5. ❌ Creating migrations outside Docker (wrong database host)
+6. ❌ Forgetting backend must run natively for camera access
+7. ❌ Breaking hardware ID system by reverting to index-based camera refs
+8. ❌ Creating new documentation files instead of updating existing ones
+9. ❌ Creating shell scripts for simple tasks (use pixi tasks instead)
+10. ❌ Replacing `frontend/Dockerfile` (production multi-stage build) with `Dockerfile.dev` in `docker-compose.yml` — that would re-introduce npm downloads at startup and break offline use
+
+## Quick Reference Commands
+
+```bash
+# Start full stack development (no cameras) — Vite dev server at :5173
+./scripts/start-dev.sh
+
+# Start production with cameras
+./scripts/start.sh
+
+# Backend only (native)
+cd backend && pixi run dev
+
+# Apply database migrations
+docker compose exec backend alembic upgrade head
+# OR: cd backend && pixi run db-upgrade
+
+# Camera testing
+rpicam-hello --list-cameras
+cd backend && pixi run test-cameras
+
+# Check database connection
+docker compose exec backend python -c "from app.core.db import engine; from sqlalchemy import inspect; print(inspect(engine).get_table_names())"
+```
+
+## Documentation References
+
+- [DEVELOPMENT.md](backend/DEVELOPMENT.md) - Critical development guidelines
+- [DEPENDENCIES.md](backend/DEPENDENCIES.md) - Camera system dependencies
+- [README.md](README.md) - Setup instructions and quick start
+
+## Context for Code Generation
+
+- **Deployment:** Offline-capable Raspberry Pi, single-instance
+- **Database:** PostgreSQL with psycopg3, Alembic-only migrations
+- **Auth:** Custom HMAC tokens (no JWT libraries)
+- **Camera Hardware:** libcamera/picamera2 via system packages
+- **Dependency Manager:** Pixi (preferred), venv (legacy)
+- **Git:** Uses submodules for frontend/backend
+
+**Before making changes:** Check git history to avoid reverting intentional architectural decisions.
diff --git a/.github/instructions/frontend.instructions.md b/.github/instructions/frontend.instructions.md
new file mode 100644
index 0000000..22f1458
--- /dev/null
+++ b/.github/instructions/frontend.instructions.md
@@ -0,0 +1,137 @@
+---
+applyTo: "frontend/**"
+---
+
+# Specific instructions for frontend development.
+
+## ⛔ CSS Location — Non-Negotiable Rules
+
+**ALL CSS must live in `frontend/static/app.css`. No exceptions.**
+
+### FORBIDDEN patterns — never do these:
+
+```svelte
+<!-- ❌ NEVER: <style> blocks inside .svelte files -->
+<style>
+  .my-button { color: red; }
+</style>
+```
+
+```svelte
+<!-- ❌ NEVER: inline style attributes -->
+<div style="color: red; margin: 8px;">...</div>
+<button style="background: blue;">...</button>
+```
+
+```ts
+// ❌ NEVER: style strings in TypeScript/JavaScript
+element.style.color = 'red';
+const styles = { color: 'red' };
+```
+
+```svelte
+<!-- ❌ NEVER: style directives -->
+<div style:color="red">...</div>
+```
+
+### CORRECT pattern — always do this:
+
+Add a named class to `frontend/static/app.css`, then apply it in the template:
+
+```css
+/* frontend/static/app.css */
+.my-button {
+  color: var(--accent-primary);
+  margin: var(--spacing-sm);
+}
+```
+
+```svelte
+<!-- frontend/src/lib/components/MyComponent.svelte -->
+<button class="my-button">Click me</button>
+```
+
+### Dynamic state is the only exception
+
+Only JS-driven dynamic values that cannot be expressed as toggled CSS classes may use a style binding, and only with a CSS variable:
+
+```svelte
+<!-- ✅ ALLOWED only when value is truly dynamic -->
+<div style="--progress: {percent}%">...</div>
+```
+
+```css
+/* The visual rule still lives in app.css */
+.progress-bar::after { width: var(--progress); }
+```
+
+---
+
+## CSS Variables
+
+All colors, spacing, and typography values are defined as CSS variables in `app.css`. **Always use variables — never hard-code values.**
+
+| Variable | Purpose |
+|---|---|
+| `--bg-color` | Page background (#ffffff) |
+| `--bg-gray` | Secondary background (#f2f2f2) |
+| `--text-color` | Body text (#757575) |
+| `--text-dark` | Heading/emphasis text (#000000) |
+| `--text-muted` | Muted/disabled text (#858585) |
+| `--accent-primary` | Brand blue (rgba(41,98,255,0.8)) |
+| `--accent-hover` | Hover accent (#f18e00) |
+| `--accent-link` | Link color (#F2784B) |
+| `--footer-bg` | Footer background (#003660) |
+| `--footer-text` | Footer text (#ffffff) |
+| `--spacing-sm` | 0.5rem |
+| `--spacing-md` | 1rem |
+| `--spacing-lg` | 1.5rem |
+| `--spacing-xl` | 2rem |
+| `--spacing-xxl` | 3rem |
+
+When you need a new reusable value, **add it as a CSS variable in `:root`** inside `app.css` before using it.
+
+---
+
+## CSS Organization in app.css
+
+Follow these section headers when adding new rules:
+
+```css
+/* ==================== */
+/* Component Name       */
+/* ==================== */
+```
+
+Group styles by component or feature. Keep existing sections intact. Do not scatter related rules.
+
+---
+
+## Project Specific Guidelines
+
+- The default screen is a **7-inch display**. All styles must be optimized for 800×480 and 1024×600 resolutions first, then scale up for larger screens.
+- Use relative units (`rem`, `%`, `vh`/`vw`) over fixed `px` wherever possible.
+- Test layout at both 800×480 and 1024×600 before considering work done.
+
+---
+
+## Svelte Component Rules
+
+- `.svelte` files contain **only** `<script>`, template markup, and **no** `<style>` blocks.
+- Apply styling exclusively through CSS classes defined in `app.css`.
+- Use `class:` directive for conditional classes (not `style:`):
+
+```svelte
+<!-- ✅ CORRECT: toggle a class -->
+<div class:active={isActive} class="panel">...</div>
+
+<!-- ❌ WRONG: toggle a style -->
+<div style:background={isActive ? 'blue' : 'gray'}>...</div>
+```
+
+---
+
+## Building
+
+- The project is built on Docker. IDE errors on some library imports are due to VSCode not resolving dependencies installed inside the container — these are not real errors.
+- The backend runs **natively** (not in Docker). See the root `copilot-instructions.md` for details.
diff --git a/.github/instructions/icons.instructions.md b/.github/instructions/icons.instructions.md
new file mode 100644
index 0000000..8c1049f
--- /dev/null
+++ b/.github/instructions/icons.instructions.md
@@ -0,0 +1,128 @@
+---
+applyTo: "frontend/**"
+---
+
+# Icons
+
+## Rules
+
+- **Always use Material Symbols Outlined** for every icon in the application. Do not use SVGs, emoji, Unicode symbols, Heroicons, FontAwesome, Lucide, or any other icon system.
+- **Never install additional icon libraries.** The font is already bundled at `frontend/static/fonts/MaterialSymbolsOutlined.woff2` and loaded in `frontend/static/app.css`.
+- **Never render icons as images** (`<img>`, `<svg>`, background-image). Always use the font span pattern below.
+
+## Required Markup Pattern
+
+Every icon must follow this exact structure — a `<span>` with class `material-symbols-outlined`, containing only the icon name as text:
+
+```svelte
+<span class="material-symbols-outlined">home</span>
+```
+
+Size is controlled by adding one of three modifier classes (default is `icon-md`):
+
+```svelte
+<span class="material-symbols-outlined icon-sm">home</span>   <!-- 18px -->
+<span class="material-symbols-outlined icon-md">home</span>   <!-- 24px -->
+<span class="material-symbols-outlined icon-lg">home</span>   <!-- 32px -->
+```
+
+Do not set font-size on icon spans directly — use the modifier classes.
+
+## Icons Inside Buttons
+
+Place the span as the first child, followed by the label text:
+
+```svelte
+<button class="btn-primary">
+  <span class="material-symbols-outlined icon-sm">add</span>
+  Create New
+</button>
+
+<button class="icon-btn">
+  <span class="material-symbols-outlined icon-sm">edit</span>
+</button>
+```
+
+## Choosing an Icon Name
+
+Pick from the list below. If the right icon isn't here, check https://fonts.google.com/icons (offline deployments: verify the name is in the woff2 before using).
+
+### Navigation & UI
+| Name | Use for |
+|---|---|
+| `dashboard` | Dashboard / grid view |
+| `folder` | Projects / folders |
+| `settings` | Settings / configuration |
+| `logout` | Sign out |
+| `menu` | Hamburger menu |
+| `close` | Close / cancel |
+| `arrow_back` | Back navigation |
+| `arrow_forward` | Forward navigation |
+
+### File Operations
+| Name | Use for |
+|---|---|
+| `folder_open` | Open folder |
+| `description` | Document / file |
+| `upload_file` | Upload |
+| `download` | Download |
+| `delete` | Delete / trash |
+| `edit` | Edit / modify |
+| `save` | Save |
+| `print` | Print |
+
+### Content Actions
+| Name | Use for |
+|---|---|
+| `add` | Add new item |
+| `remove` | Remove item |
+| `search` | Search |
+| `filter_list` | Filter |
+| `sort` | Sort |
+| `more_vert` | More options (vertical) |
+| `more_horiz` | More options (horizontal) |
+
+### Media & Capture
+| Name | Use for |
+|---|---|
+| `photo_camera` | Camera / capture |
+| `image` | Image / photo |
+| `collections` | Gallery / collection |
+| `video_camera_front` | Video camera |
+| `camera_alt` | Alternative camera |
+
+### Status & Feedback
+| Name | Use for |
+|---|---|
+| `check_circle` | Success / complete |
+| `error` | Error |
+| `warning` | Warning |
+| `info` | Information |
+| `help` | Help / support |
+
+### Data & Records
+| Name | Use for |
+|---|---|
+| `article` | Article / record |
+| `book` | Book / publication |
+| `library_books` | Multiple books |
+| `inventory` | Inventory |
+| `archive` | Archive |
+| `collections_bookmark` | Bookmarked collection |
+
+### User & Account
+| Name | Use for |
+|---|---|
+| `person` | Person / user |
+| `account_circle` | User account |
+| `group` | Group / multiple users |
+
+### Utility
+| Name | Use for |
+|---|---|
+| `refresh` | Refresh / reload |
+| `sync` | Synchronize |
+| `visibility` | Show / visible |
+| `visibility_off` | Hide / invisible |
+| `lock` | Locked / secure |
+| `lock_open` | Unlocked |
diff --git a/.gitignore b/.gitignore
index 9165ad9..598718b 100644
--- a/.gitignore
+++ b/.gitignore
@@ -25,4 +25,7 @@ _data/
 _logs/
 
 # Temporary folder
-temp/
\ No newline at end of file
+temp/
+
+# Working files
+docs/RP-008156-DS-2-picamera2-manual.txt
\ No newline at end of file
diff --git a/README.md b/README.md
index 12cef1c..49892d7 100644
--- a/README.md
+++ b/README.md
@@ -34,25 +34,99 @@ An open-source, modular digitization toolkit designed for low-cost, high-quality
 
 Or manually:
 ```bash
-docker compose --profile with-backend up
+docker compose -f docker-compose.yml -f docker-compose.dev.yml --profile with-backend up
 ```
 
 ### Production (Raspberry Pi with cameras)
 
 ```bash
-# One-command startup (Docker + native backend)
+# Build the frontend image first (requires internet — do this at home/office):
+docker compose build
+
+# Then take it offline and run:
 ./scripts/start.sh
 ```
 
 Or manually:
 ```bash
-docker compose up -d && ./scripts/run_backend_native.sh
+# Start database and frontend
+docker compose up -d
+
+# Start backend with pixi
+cd backend && pixi run dev
 ```
 
-**Access:** [http://localhost:5173](http://localhost:5173) (frontend) | [http://localhost:8000/docs](http://localhost:8000/docs) (API)
+**Access (production):** [http://localhost:3000](http://localhost:3000) (frontend) | [http://localhost:8000/docs](http://localhost:8000/docs) (API)
+**Access (dev):** [http://localhost:5173](http://localhost:5173) (frontend, Vite) | [http://localhost:8000/docs](http://localhost:8000/docs) (API)
 
 **Note:** The native backend is required for camera access due to Raspberry Pi-specific libraries (libcamera, picamera2).
 
+### 📦 Backend Dependency Management
+
+The backend uses **pixi** for dependency management:
+
+```bash
+# First time setup
+cd backend
+pixi install
+pixi run setup-camera-link  # Raspberry Pi only
+
+# Start backend
+pixi run dev
+```
+
+## Production Distribution (SD Card Imaging)
+
+The toolkit is designed to ship as a pre-flashed SD card. The end user only needs to insert the card, power on the Pi, and the application starts automatically — no internet connection required.
+
+### Building the golden SD card (requires internet, done once)
+
+```bash
+# 1. Clone the repository onto a fresh Raspberry Pi OS installation
+git clone --recurse-submodules https://github.com/UCSB-AMPLab/digitization-toolkit.git ~/dtk
+cd ~/dtk
+
+# 2. Run the one-time provisioning script (internet required here)
+#    Builds Docker images, installs pixi env, applies DB migrations
+sudo ./scripts/setup.sh
+
+# 3. Install and enable the systemd service (auto-start on boot)
+sudo ./scripts/install-service.sh
+sudo systemctl start dtk
+
+# 4. Verify the app is running
+curl http://localhost:8000/health   # → {"status":"ok"}
+curl -I http://localhost:3000       # → HTTP 200
+```
+
+### Creating an SD card image
+
+```bash
+# On the Pi — shut down cleanly
+sudo systemctl stop dtk
+sudo poweroff
+
+# On a host machine with the SD card inserted (replace sdX with your device)
+sudo dd if=/dev/sdX of=dtk-$(date +%Y%m%d).img bs=4M status=progress
+# Compress for storage/transfer
+xz -T0 dtk-$(date +%Y%m%d).img
+```
+
+### Flashing for end users
+
+Use [Raspberry Pi Imager](https://www.raspberrypi.com/software/) (or `dd`) to write the `.img` to a new SD card.  
+The application starts automatically on boot — no configuration needed.
+
+### What's self-contained after provisioning
+
+| Component | Stored at | Requires internet after setup? |
+|---|---|---|
+| Frontend (SvelteKit) | Docker image in `/var/lib/docker/` | No |
+| PostgreSQL | Docker image in `/var/lib/docker/` | No |
+| Backend Python env | `backend/.pixi/` | No |
+| camera libraries | `/usr/lib/python3/dist-packages/` | No (system OS) |
+| Application data | `/var/lib/dtk/` | No |
+
 ## Setup
 
 This repository uses **Git submodules** for the `frontend` and `backend` code.  
diff --git a/backend b/backend
index 8614051..a172e0e 160000
--- a/backend
+++ b/backend
@@ -1 +1 @@
-Subproject commit 86140518b98f7b5ec08193df6519681b897c5af3
+Subproject commit a172e0efda0cd48194bdcf596592723725fe6f5e
diff --git a/docker-compose.dev.yml b/docker-compose.dev.yml
new file mode 100644
index 0000000..7bfc04b
--- /dev/null
+++ b/docker-compose.dev.yml
@@ -0,0 +1,28 @@
+# Development overrides for Digitization Toolkit
+# Replaces the production frontend with a Vite dev server (live reload).
+# Usage: docker compose -f docker-compose.yml -f docker-compose.dev.yml [--profile with-backend] up
+# Or via the helper script: ./scripts/start-dev.sh
+
+services:
+  frontend:
+    build:
+      context: ./frontend
+      dockerfile: Dockerfile.dev
+    ports:
+      - "5173:5173"
+    environment:
+      - NODE_ENV=development
+      - NPM_CONFIG_AUDIT=false
+      - NPM_CONFIG_FUND=false
+    volumes:
+      - ./frontend:/app
+      - frontend_node_modules:/app/node_modules
+    command: >
+      sh -c "
+        npm install &&
+        npx svelte-kit sync &&
+        npm run dev -- --host 0.0.0.0
+      "
+
+volumes:
+  frontend_node_modules:
\ No newline at end of file
diff --git a/docker-compose.yml b/docker-compose.yml
index 88d9734..c6de7ad 100644
--- a/docker-compose.yml
+++ b/docker-compose.yml
@@ -22,12 +22,13 @@ services:
       - postgres_data:/var/lib/postgresql/data
     healthcheck:
       test: ["CMD-SHELL", "pg_isready -U ${DATABASE_USER:-user} -d ${DATABASE_NAME:-digitization_toolkit}"]
-      interval: 10s
+      interval: 2s
       timeout: 5s
-      retries: 5
+      retries: 15
+      start_period: 5s
 
   # Backend service (optional for Docker-based development)
-  # On Raspberry Pi with cameras, run backend natively: ./scripts/run_backend_native.sh
+  # On Raspberry Pi with cameras, run backend natively: cd backend && pixi run dev
   # For development without camera hardware, use: docker compose --profile with-backend up
   backend:
     profiles: ["with-backend"]  # Optional: only start with --profile with-backend
@@ -55,37 +56,34 @@ services:
     depends_on:
       db:
         condition: service_healthy
-    command: uvicorn app.main:app --host 0.0.0.0 --port 8000 --reload
+    command: >
+      sh -c "alembic upgrade head && uvicorn app.main:app --host 0.0.0.0 --port 8000 --reload"
 
   frontend:
+    # Production image: multi-stage build compiles Svelte at build time.
+    # No npm or source code in the running container → works fully offline
+    # after a one-time internet-connected `docker compose build`.
+    # For live-reload development use: docker compose -f docker-compose.yml -f docker-compose.dev.yml up
     build:
       context: ./frontend
-      dockerfile: Dockerfile.dev
+      dockerfile: Dockerfile
     env_file:
       - ./.env
     ports:
-      - "5173:5173"
-    # Allow container to reach host services
+      - "3000:3000"
+    # Allow container to reach host services (native backend)
     extra_hosts:
       - "host.docker.internal:host-gateway"
     environment:
       - PUBLIC_API_BASE=http://localhost:8000
       - PUBLIC_API_BASE_SSR=http://host.docker.internal:8000
-      - NPM_CONFIG_AUDIT=false
-      - NPM_CONFIG_FUND=false
-    volumes:
-      - ./frontend:/app
-      - frontend_node_modules:/app/node_modules
-    command: >
-      sh -c "
-        rm -rf /app/node_modules/* /app/node_modules/.* /app/package-lock.json 2>/dev/null || true &&
-        npm cache clean --force &&
-        npm install --include=optional --ignore-scripts &&
-        npm rebuild &&
-        npx svelte-kit sync &&
-        npm run dev -- --host 0.0.0.0
-      "
+      - PORT=3000
+      # ORIGIN: uncomment and set to the Pi's IP/hostname if form actions break
+      # (e.g. ORIGIN=http://192.168.1.x:3000). Not needed for API-only frontends.
+      # - ORIGIN=http://localhost:3000
+      - NODE_ENV=production
+    # No depends_on db — the frontend is a Node.js API proxy and never connects
+    # to Postgres directly. Removing this lets db and frontend start in parallel.
 
 volumes:
   postgres_data:
-  frontend_node_modules:
diff --git a/docs/developers/API_REFERENCE.md b/docs/developers/API_REFERENCE.md
index edf1d93..c8dcb10 100644
--- a/docs/developers/API_REFERENCE.md
+++ b/docs/developers/API_REFERENCE.md
@@ -2527,7 +2527,7 @@ LOG_LEVEL=info
 
 ### CORS Configuration
 
-Currently allows `http://localhost:5173` (Svelte dev server).
+Currently allows `http://localhost:5173` (Vite dev server) and `http://localhost:3000` (production Node server).
 
 **For production**, update `app/main.py`:
 ```python
diff --git a/frontend b/frontend
index 396fe7c..c73d6b9 160000
--- a/frontend
+++ b/frontend
@@ -1 +1 @@
-Subproject commit 396fe7ceea58e1dc281fb69216f63c2a2d78996d
+Subproject commit c73d6b9fa34552816eee15637caf4647e2365ef2
diff --git a/scripts/bootstrap_host.sh b/scripts/bootstrap_host.sh
deleted file mode 100755
index b62adf1..0000000
--- a/scripts/bootstrap_host.sh
+++ /dev/null
@@ -1,42 +0,0 @@
-#!/usr/bin/env bash
-set -euo pipefail
-
-# user and group to be changed in prod
-APP_USER="pi"
-APP_GROUP="digitool"
-
-DATA_DIR="/var/lib/dtk"
-LOG_DIR="/var/log/dtk"
-
-echo "[dtk] Bootstrapping host directories and user..."
-
-if [[ "${EUID}" -ne 0 ]]; then
-  echo "ERROR: run as root (try: sudo $0)"
-  exit 1
-fi
-
-getent group "${APP_GROUP}" >/dev/null || groupadd --system "${APP_GROUP}"
-id -u "${APP_USER}" >/dev/null 2>&1 || useradd \
-  --system \
-  --gid "${APP_GROUP}" \
-  --home "${DATA_DIR}" \
-  --shell /usr/sbin/nologin \
-  "${APP_USER}"
-
-mkdir -p \
-  "${DATA_DIR}/projects" \
-  "${DATA_DIR}/exports" \
-  "${DATA_DIR}/backups" \
-  "${DATA_DIR}/db" \
-  "${LOG_DIR}"
-
-# Ownership + permissions
-chown -R "${APP_USER}:${APP_GROUP}" "${DATA_DIR}" "${LOG_DIR}"
-chmod -R 750 "${DATA_DIR}" "${LOG_DIR}"
-
-# Marker file
-echo "DTK bootstrap completed on $(date -Iseconds)" > "${DATA_DIR}/.bootstrap"
-
-echo "[dtk] Done."
-echo "  Data: ${DATA_DIR}"
-echo "  Logs: ${LOG_DIR}"
diff --git a/scripts/dtk.service b/scripts/dtk.service
index 074e495..7b9ec11 100644
--- a/scripts/dtk.service
+++ b/scripts/dtk.service
@@ -5,11 +5,14 @@ Requires=docker.service
 Documentation=https://github.com/UCSB-AMPLab/digitization-toolkit
 
 [Service]
-Type=forking
+Type=simple
 User=pi
 Group=pi
 WorkingDirectory=/home/pi/dtk
 
+# Ensure pixi and docker are on PATH (systemd uses a stripped environment)
+Environment="PATH=/home/pi/.pixi/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin"
+
 # Start the application
 ExecStart=/home/pi/dtk/scripts/start.sh
 ExecStop=/home/pi/dtk/scripts/stop.sh
diff --git a/scripts/install-kiosk-service.sh b/scripts/install-kiosk-service.sh
new file mode 100755
index 0000000..5d1cb8e
--- /dev/null
+++ b/scripts/install-kiosk-service.sh
@@ -0,0 +1,71 @@
+#!/bin/bash
+# Set up kiosk auto-start on boot via autologin + ~/.bash_profile
+#
+# The kiosk must run inside the tty1 login session (not as a standalone
+# systemd service) so that cage (Wayland compositor) takes ownership of
+# tty1, which is what the monitor displays.
+#
+# Boot sequence:
+#   getty@tty1 autologin → bash login shell → .bash_profile → start-kiosk.sh → cage
+#
+# Restart: when cage exits, the shell exits, getty re-autologins, .bash_profile
+# runs again → kiosk restarts automatically.
+
+set -e
+
+KIOSK_USER="${SUDO_USER:-pi}"
+KIOSK_HOME=$(eval echo "~$KIOSK_USER")
+BASH_PROFILE="$KIOSK_HOME/.bash_profile"
+KIOSK_SCRIPT="/home/pi/dtk/scripts/start-kiosk.sh"
+
+echo "Setting up kiosk auto-start for user: $KIOSK_USER"
+echo ""
+
+# ── 1. Ensure autologin is configured for tty1 ──────────────────────────────
+echo "→ Configuring autologin on tty1..."
+sudo mkdir -p /etc/systemd/system/getty@tty1.service.d
+sudo tee /etc/systemd/system/getty@tty1.service.d/autologin.conf > /dev/null << EOF
+[Service]
+ExecStart=
+ExecStart=-/sbin/agetty --autologin $KIOSK_USER --noclear %I \$TERM
+EOF
+sudo systemctl daemon-reload
+
+# ── 2. Write ~/.bash_profile to launch kiosk on tty1 ────────────────────────
+echo "→ Writing $BASH_PROFILE..."
+cat > "$BASH_PROFILE" << EOF
+# ~/.bash_profile - executed for login shells (including autologin on tty1)
+
+# Source .bashrc if present (standard practice)
+if [ -f "\$HOME/.bashrc" ]; then
+    . "\$HOME/.bashrc"
+fi
+
+# Start the kiosk when autologged-in on tty1.
+# cage (Wayland compositor + Chromium) must run from the tty1 login session
+# so it takes ownership of tty1 and is visible on the monitor.
+# When cage exits, this shell exits → getty re-autologins → kiosk restarts.
+if [[ "\$(tty)" == "/dev/tty1" ]]; then
+    exec $KIOSK_SCRIPT
+fi
+EOF
+chown "$KIOSK_USER:$KIOSK_USER" "$BASH_PROFILE"
+
+# ── 3. Remove old kiosk.service if present (replaced by .bash_profile) ──────
+if systemctl is-enabled kiosk.service &>/dev/null; then
+    echo "→ Disabling legacy kiosk.service..."
+    sudo systemctl disable kiosk.service
+    sudo systemctl stop kiosk.service 2>/dev/null || true
+fi
+
+echo ""
+echo "✓ Kiosk auto-start configured!"
+echo ""
+echo "The kiosk will start automatically on next boot."
+echo "(dtk.service starts Docker/backend; autologin starts cage on tty1)"
+echo ""
+echo "To apply immediately without rebooting:"
+echo "  exec /home/pi/dtk/scripts/start-kiosk.sh"
+echo ""
+echo "To disable auto-start, remove the tty1 block from $BASH_PROFILE"
+echo ""
diff --git a/scripts/install-service.sh b/scripts/install-service.sh
index 4a752f4..14adc0c 100755
--- a/scripts/install-service.sh
+++ b/scripts/install-service.sh
@@ -21,6 +21,21 @@ if [ "$EUID" -ne 0 ]; then
     exit 1
 fi
 
+# Guard: make sure setup.sh has been run first
+if [ ! -d "$PROJECT_ROOT/backend/.pixi" ]; then
+    echo "✗ Backend pixi environment not found."
+    echo "  Run setup.sh first (requires internet):"
+    echo "    sudo $PROJECT_ROOT/scripts/setup.sh"
+    exit 1
+fi
+
+if ! docker image inspect dtk-frontend >/dev/null 2>&1; then
+    echo "✗ Frontend Docker image not found."
+    echo "  Run setup.sh first (requires internet):"
+    echo "    sudo $PROJECT_ROOT/scripts/setup.sh"
+    exit 1
+fi
+
 # Check if service file exists
 if [ ! -f "$SERVICE_FILE" ]; then
     echo "✗ Service file not found: $SERVICE_FILE"
diff --git a/scripts/installkb.sh b/scripts/installkb.sh
new file mode 100755
index 0000000..51188d2
--- /dev/null
+++ b/scripts/installkb.sh
@@ -0,0 +1,34 @@
+#!/bin/bash
+# Install Wayland kiosk browser
+
+set -e  # Exit on error
+
+# Get the directory where this script is located
+SCRIPT_DIR="$(cd "$(dirname "${BASH_SOURCE[0]}")" && pwd)"
+
+echo "╔════════════════════════════════════════╗"
+echo "║  Raspberry Pi 5 Wayland Kiosk Setup    ║"
+echo "╚════════════════════════════════════════╝"
+echo ""
+
+echo "Installing Cage (Wayland compositor) and Chromium..."
+sudo apt update
+sudo apt install -y cage chromium-browser
+
+echo ""
+echo "✓ Installation complete!"
+echo ""
+echo "════════════════════════════════════════"
+echo "  To start the kiosk:"
+echo "════════════════════════════════════════"
+echo ""
+echo "  ~/dtk/scripts/start-kiosk.sh"
+echo ""
+echo "════════════════════════════════════════"
+echo "  For auto-start on boot (optional):"
+echo "════════════════════════════════════════"
+echo ""
+echo "  1. Test manually first to ensure it works"
+echo "  2. Then run: sudo ~/dtk/scripts/install-kiosk-service.sh"
+echo ""
+
diff --git a/scripts/restart.sh b/scripts/restart.sh
deleted file mode 100755
index 3c4a064..0000000
--- a/scripts/restart.sh
+++ /dev/null
@@ -1,26 +0,0 @@
-#!/bin/bash
-# Restart script for Digitization Toolkit (Production mode)
-# Safely stops and restarts all services
-
-set -e
-
-SCRIPT_DIR="$(cd "$(dirname "${BASH_SOURCE[0]}")" && pwd)"
-PROJECT_ROOT="$(dirname "$SCRIPT_DIR")"
-
-cd "$PROJECT_ROOT"
-
-echo "=========================================="
-echo "Restarting Digitization Toolkit"
-echo "=========================================="
-echo ""
-
-# Stop everything
-./scripts/stop.sh
-
-echo ""
-echo "→ Waiting 2 seconds before restart..."
-sleep 2
-
-echo ""
-# Start in production mode
-./scripts/start.sh
diff --git a/scripts/run_backend_native.sh b/scripts/run_backend_native.sh
deleted file mode 100755
index d760d26..0000000
--- a/scripts/run_backend_native.sh
+++ /dev/null
@@ -1,98 +0,0 @@
-#!/bin/bash
-# Startup script for running DTK backend natively (outside Docker)
-# This allows direct access to camera hardware while connecting to dockerized DB
-
-set -e
-
-# Color codes for output
-RED='\033[0;31m'
-GREEN='\033[0;32m'
-YELLOW='\033[1;33m'
-BLUE='\033[0;34m'
-NC='\033[0m' # No Color
-
-echo -e "${BLUE}=================================================="
-echo "DTK Backend - Native Startup"
-echo -e "==================================================${NC}"
-echo ""
-
-SCRIPT_DIR="$(cd "$(dirname "${BASH_SOURCE[0]}")" && pwd)"
-PROJECT_ROOT="$(cd "$SCRIPT_DIR/.." && pwd)"
-BACKEND_DIR="$PROJECT_ROOT/backend"
-VENV_DIR="$BACKEND_DIR/.venv"
-
-if [ ! -f "$PROJECT_ROOT/.env" ]; then
-    echo -e "${RED}✗ Error: .env file not found at $PROJECT_ROOT/.env${NC}"
-    echo "  Make sure you're running this from the project root"
-    exit 1
-fi
-
-if [ ! -d "$VENV_DIR" ]; then
-    echo -e "${RED}✗ Error: Virtual environment not found at $VENV_DIR${NC}"
-    echo "  Run: cd backend && python3 -m venv .venv && source .venv/bin/activate && pip install -r requirements.txt"
-    exit 1
-fi
-
-echo -e "${YELLOW}→${NC} Activating virtual environment..."
-source "$VENV_DIR/bin/activate"
-
-if ! command -v uvicorn &> /dev/null; then
-    echo -e "${RED}✗ uvicorn not found in virtual environment${NC}"
-    echo "  Run: pip install -r $BACKEND_DIR/requirements.txt"
-    exit 1
-fi
-
-echo -e "${YELLOW}→${NC} Checking database connectivity..."
-cd "$BACKEND_DIR"
-
-python3 << 'PREFLIGHT_CHECK'
-import sys
-try:
-    from app.core.db import engine
-    from sqlalchemy import text
-    
-    with engine.connect() as conn:
-        result = conn.execute(text('SELECT 1'))
-        result.scalar()
-    
-    print('\033[0;32m✓\033[0m Database connection successful')
-except Exception as e:
-    print(f'\033[0;31m✗ Database connection failed: {e}\033[0m')
-    print(f'\033[1;33m  Make sure Docker containers are running:\033[0m')
-    print(f'    docker compose up db')
-    sys.exit(1)
-PREFLIGHT_CHECK
-
-if [ $? -ne 0 ]; then
-    exit 1
-fi
-
-echo -e "${YELLOW}→${NC} Checking camera availability..."
-python3 << 'CAMERA_CHECK'
-try:
-    from capture.camera_registry import CameraRegistry
-    registry = CameraRegistry()
-    detected = registry.detect_cameras()
-    if detected:
-        print(f'\033[0;32m✓\033[0m Found {len(detected)} camera(s)')
-    else:
-        print('\033[1;33m⚠\033[0m  No cameras detected (capture endpoints will not work)')
-except Exception as e:
-    print(f'\033[1;33m⚠\033[0m  Camera check failed: {e}')
-    print('  (Backend will start but camera endpoints may not work)')
-CAMERA_CHECK
-
-echo ""
-echo -e "${GREEN}✓ Pre-flight checks complete${NC}"
-echo ""
-echo -e "${BLUE}Starting FastAPI backend...${NC}"
-echo -e "  Backend: ${GREEN}http://0.0.0.0:8000${NC}"
-echo -e "  API Docs: ${GREEN}http://localhost:8000/docs${NC}"
-echo -e "  ReDoc: ${GREEN}http://localhost:8000/redoc${NC}"
-echo ""
-echo -e "${YELLOW}Press Ctrl+C to stop${NC}"
-echo ""
-
-# Start uvicorn with auto-reload
-cd "$BACKEND_DIR"
-exec uvicorn app.main:app --reload --host 0.0.0.0 --port 8000
diff --git a/scripts/setup.sh b/scripts/setup.sh
new file mode 100644
index 0000000..9c965a7
--- /dev/null
+++ b/scripts/setup.sh
@@ -0,0 +1,148 @@
+#!/bin/bash
+# One-time provisioning script for Digitization Toolkit
+#
+# Run this ONCE on the Pi while connected to the internet.
+# After completion the SD card can be imaged for offline distribution.
+#
+# What it does:
+#   1. Stops any running services for a clean slate
+#   2. Creates required system directories
+#   3. Builds Docker images (frontend multi-stage, pulls postgres:16-alpine)
+#   4. Installs backend pixi environment (conda-forge packages)
+#   5. Links system camera libraries (picamera2 / libcamera)
+#   6. Starts the DB, applies Alembic migrations, then stops it
+#
+# Usage: sudo ./scripts/setup.sh
+
+set -e
+
+SCRIPT_DIR="$(cd "$(dirname "${BASH_SOURCE[0]}")" && pwd)"
+PROJECT_ROOT="$(dirname "$SCRIPT_DIR")"
+
+# Resolve the real (non-root) user so pixi runs under the correct home dir
+if [ -n "$SUDO_USER" ]; then
+    DTK_USER="$SUDO_USER"
+else
+    DTK_USER="$(whoami)"
+fi
+DTK_USER_HOME=$(eval echo "~$DTK_USER")
+PIXI_BIN="$DTK_USER_HOME/.pixi/bin/pixi"
+
+if [ ! -x "$PIXI_BIN" ]; then
+    echo "✗ pixi not found at $PIXI_BIN"
+    echo "  Install pixi as $DTK_USER first:"
+    echo "    curl -fsSL https://pixi.sh/install.sh | bash"
+    exit 1
+fi
+
+# Run a command as DTK_USER, preserving the pixi bin in PATH
+run_as_user() {
+    sudo -u "$DTK_USER" env HOME="$DTK_USER_HOME" PATH="$DTK_USER_HOME/.pixi/bin:$PATH" "$@"
+}
+
+COMPOSE="docker compose -f $PROJECT_ROOT/docker-compose.yml -f $PROJECT_ROOT/docker-compose.pi.yml"
+
+cd "$PROJECT_ROOT"
+
+echo "=========================================="
+echo " Digitization Toolkit — Initial Setup"
+echo "=========================================="
+echo ""
+
+# ---------------------------------------------------------------------------
+# 1. Stop any running services
+# ---------------------------------------------------------------------------
+echo "→ Stopping any running services..."
+$COMPOSE down 2>/dev/null || true
+echo ""
+
+# ---------------------------------------------------------------------------
+# 2. System directories
+# ---------------------------------------------------------------------------
+echo "→ Creating system directories..."
+mkdir -p /var/lib/dtk/db/postgres
+mkdir -p /var/log/dtk
+chown -R "$DTK_USER:$DTK_USER" /var/lib/dtk /var/log/dtk 2>/dev/null || true
+echo "  /var/lib/dtk  ✓"
+echo "  /var/log/dtk  ✓"
+echo ""
+
+# ---------------------------------------------------------------------------
+# 3. Docker images
+# ---------------------------------------------------------------------------
+echo "→ Pulling base images and building services..."
+$COMPOSE pull db
+$COMPOSE build frontend
+echo ""
+
+# ---------------------------------------------------------------------------
+# 4. Pixi backend environment
+# ---------------------------------------------------------------------------
+echo "→ Installing backend dependencies (pixi)..."
+cd "$PROJECT_ROOT/backend"
+run_as_user "$PIXI_BIN" install
+echo ""
+
+# ---------------------------------------------------------------------------
+# 5. Camera system library link (Raspberry Pi only)
+# ---------------------------------------------------------------------------
+if python3 -c "import picamera2" 2>/dev/null || [ -d /usr/lib/python3/dist-packages/picamera2 ]; then
+    echo "→ Linking system camera libraries..."
+    run_as_user "$PIXI_BIN" run setup-camera-link
+    echo ""
+else
+    echo "→ Skipping camera link (picamera2 not found — OK on non-Pi hardware)"
+    echo ""
+fi
+
+# ---------------------------------------------------------------------------
+# 6. Database initialisation & migrations
+# ---------------------------------------------------------------------------
+cd "$PROJECT_ROOT"
+echo "→ Starting database for migration..."
+$COMPOSE up -d db
+
+echo "  Waiting for PostgreSQL to be ready..."
+for i in $(seq 1 30); do
+    if $COMPOSE exec -T db pg_isready -U "${DATABASE_USER:-user}" -d "${DATABASE_NAME:-digitization_toolkit}" >/dev/null 2>&1; then
+        echo "  Database ready."
+        break
+    fi
+    if [ "$i" -eq 30 ]; then
+        echo "✗ Database did not become ready after 60s."
+        echo "  Check logs: docker compose logs db"
+        $COMPOSE down
+        exit 1
+    fi
+    sleep 2
+done
+
+echo "→ Applying database migrations..."
+# DATABASE_HOST=localhost is already in .env; alembic reaches the DB
+# container via the exposed 5432 port on the host.
+cd "$PROJECT_ROOT/backend"
+run_as_user "$PIXI_BIN" run db-upgrade
+echo ""
+
+echo "→ Stopping database..."
+cd "$PROJECT_ROOT"
+$COMPOSE down
+echo ""
+
+# ---------------------------------------------------------------------------
+# Done
+# ---------------------------------------------------------------------------
+echo "=========================================="
+echo " Setup complete!"
+echo "=========================================="
+echo ""
+echo "The Pi is now ready for offline operation."
+echo ""
+echo "Next steps:"
+echo "  sudo ./scripts/install-service.sh   # Enable auto-start on boot"
+echo ""
+echo "Or start manually:"
+echo "  ./scripts/start.sh"
+echo ""
+echo "To distribute this setup, power off and image the SD card:"
+echo "  sudo poweroff"
diff --git a/scripts/start-dev.bat b/scripts/start-dev.bat
new file mode 100644
index 0000000..425a42a
--- /dev/null
+++ b/scripts/start-dev.bat
@@ -0,0 +1,20 @@
+:: Development startup script for Digitization Toolkit
+:: Starts all services in Docker (database + frontend + backend)
+:: Use this on machines without camera hardware
+
+@echo off
+
+SET script_dir=%~dp0
+CD /D "%script_dir%.."
+
+echo ==========================================
+echo Starting Digitization Toolkit (Development)
+echo ==========================================
+echo.
+echo Starting all services in Docker...
+echo   - Database (PostgreSQL)
+echo   - Frontend (SvelteKit)
+echo   - Backend (FastAPI, no cameras)
+echo.
+
+docker compose -f docker-compose.yml -f docker-compose.dev.yml --profile with-backend up --build
diff --git a/scripts/start-dev.ps1 b/scripts/start-dev.ps1
new file mode 100644
index 0000000..8f1bbdd
--- /dev/null
+++ b/scripts/start-dev.ps1
@@ -0,0 +1,26 @@
+# Development startup script for Digitization Toolkit
+# Starts all services in Docker (database + frontend + backend)
+# Use this on machines without camera hardware
+
+# Exit on error
+$ErrorActionPreference = 'Stop'
+
+# Get script directory and project root
+$ScriptDir = $PSScriptRoot
+$ProjectRoot = Split-Path -Parent $ScriptDir
+
+# Change to project root
+Set-Location $ProjectRoot
+
+Write-Host "==========================================" -ForegroundColor Cyan
+Write-Host "Starting Digitization Toolkit (Development)" -ForegroundColor Cyan
+Write-Host "==========================================" -ForegroundColor Cyan
+Write-Host ""
+Write-Host "Starting all services in Docker..." -ForegroundColor Green
+Write-Host "  - Database (PostgreSQL)"
+Write-Host "  - Frontend (SvelteKit)"
+Write-Host "  - Backend (FastAPI, no cameras)"
+Write-Host ""
+
+# Start Docker Compose with dev configuration
+docker compose -f docker-compose.yml -f docker-compose.dev.yml --profile with-backend up --build
diff --git a/scripts/start-dev.sh b/scripts/start-dev.sh
index d919de2..fdc2f99 100755
--- a/scripts/start-dev.sh
+++ b/scripts/start-dev.sh
@@ -20,4 +20,4 @@ echo "  - Frontend (SvelteKit)"
 echo "  - Backend (FastAPI, no cameras)"
 echo ""
 
-docker compose --profile with-backend up --build
+docker compose -f docker-compose.yml -f docker-compose.dev.yml --profile with-backend up --build
diff --git a/scripts/start-kiosk.sh b/scripts/start-kiosk.sh
new file mode 100755
index 0000000..d8c3e37
--- /dev/null
+++ b/scripts/start-kiosk.sh
@@ -0,0 +1,38 @@
+#!/bin/bash
+# Wayland Kiosk Launcher - starts Chromium in fullscreen using Cage
+
+echo "╔════════════════════════════════════════╗"
+echo "║   Starting Wayland Kiosk Mode          ║"
+echo "╚════════════════════════════════════════╝"
+echo ""
+echo "To exit: Press Ctrl+Alt+F2, then run 'pkill cage'"
+echo ""
+
+# Wait for frontend to be ready
+echo -n "Waiting for frontend at http://localhost:3000..."
+until curl -sSf http://localhost:3000 >/dev/null 2>&1; do
+  echo -n "."
+  sleep 0.2
+done
+echo " ✓ Ready!"
+
+echo ""
+echo "Launching Chromium kiosk..."
+echo ""
+
+# Launch Cage with Chromium in kiosk mode
+# Cage automatically makes the app fullscreen
+exec cage -- chromium-browser \
+  --kiosk \
+  --noerrdialogs \
+  --disable-infobars \
+  --disable-session-crashed-bubble \
+  --disable-features=TranslateUI \
+  --overscroll-history-navigation=0 \
+  --check-for-update-interval=31536000 \
+  --no-first-run \
+  --disable-sync \
+  --disable-background-networking \
+  --disable-default-apps \
+  --disable-extensions \
+  http://localhost:3000
diff --git a/scripts/start.sh b/scripts/start.sh
index 1e888e7..299cd7b 100755
--- a/scripts/start.sh
+++ b/scripts/start.sh
@@ -15,18 +15,15 @@ echo "=========================================="
 echo ""
 
 # Start Docker services (DB + Frontend)
+# Uses docker-compose.pi.yml overlay for proper appliance volume paths (/var/lib/dtk, /var/log/dtk)
 echo "→ Starting database and frontend containers..."
-docker compose up -d
+# --pull never: skip registry checks (device is offline after initial build)
+docker compose -f docker-compose.yml -f docker-compose.pi.yml up -d --pull never
 
 echo ""
-echo "→ Waiting for database to be ready..."
-sleep 3
-
-# Check if database is healthy
-if ! docker compose ps | grep -q "db.*healthy"; then
-    echo "⚠ Warning: Database may still be starting up"
+echo "→ Starting native backend with pixi..."
+PIXI="${HOME}/.pixi/bin/pixi"
+if [ ! -x "$PIXI" ]; then
+    PIXI="$(command -v pixi 2>/dev/null || echo pixi)"
 fi
-
-echo ""
-# Start native backend
-./scripts/run_backend_native.sh
+cd "$PROJECT_ROOT/backend" && "$PIXI" run start
diff --git a/scripts/update.sh b/scripts/update.sh
new file mode 100644
index 0000000..ce69ab6
--- /dev/null
+++ b/scripts/update.sh
@@ -0,0 +1,119 @@
+#!/bin/bash
+# Update Digitization Toolkit to the latest committed code.
+#
+# This script is safe to run on a live Pi — it stops the service, applies
+# changes, runs any new DB migrations, then restarts.
+#
+# For a network-connected Pi (pull latest from git):
+#   git submodule update --remote --merge && sudo ./scripts/update.sh
+#
+# For an offline update from a USB drive, copy the new repo content first,
+# then run this script.
+#
+# Usage: sudo ./scripts/update.sh
+
+set -e
+
+SCRIPT_DIR="$(cd "$(dirname "${BASH_SOURCE[0]}")" && pwd)"
+PROJECT_ROOT="$(dirname "$SCRIPT_DIR")"
+
+# Resolve real user (same logic as setup.sh)
+if [ -n "$SUDO_USER" ]; then
+    DTK_USER="$SUDO_USER"
+else
+    DTK_USER="$(whoami)"
+fi
+DTK_USER_HOME=$(eval echo "~$DTK_USER")
+PIXI_BIN="$DTK_USER_HOME/.pixi/bin/pixi"
+
+run_as_user() {
+    sudo -u "$DTK_USER" env HOME="$DTK_USER_HOME" PATH="$DTK_USER_HOME/.pixi/bin:$PATH" "$@"
+}
+
+COMPOSE="docker compose -f $PROJECT_ROOT/docker-compose.yml -f $PROJECT_ROOT/docker-compose.pi.yml"
+
+cd "$PROJECT_ROOT"
+
+echo "=========================================="
+echo " Digitization Toolkit — Update"
+echo "=========================================="
+echo ""
+
+# ---------------------------------------------------------------------------
+# 1. Stop the service
+# ---------------------------------------------------------------------------
+echo "→ Stopping service..."
+systemctl stop dtk 2>/dev/null || true
+echo ""
+
+# ---------------------------------------------------------------------------
+# 2. Rebuild frontend image (always — picks up any code changes)
+# ---------------------------------------------------------------------------
+echo "→ Rebuilding frontend image..."
+$COMPOSE build frontend
+echo ""
+
+# ---------------------------------------------------------------------------
+# 3. Update pixi environment (picks up any new backend dependencies)
+# ---------------------------------------------------------------------------
+echo "→ Updating backend dependencies (pixi)..."
+cd "$PROJECT_ROOT/backend"
+run_as_user "$PIXI_BIN" install
+echo ""
+
+# ---------------------------------------------------------------------------
+# 4. Apply any new DB migrations
+# ---------------------------------------------------------------------------
+cd "$PROJECT_ROOT"
+echo "→ Starting database for migrations..."
+$COMPOSE up -d db
+
+echo "  Waiting for PostgreSQL to be ready..."
+for i in $(seq 1 30); do
+    if $COMPOSE exec -T db pg_isready -U "${DATABASE_USER:-user}" -d "${DATABASE_NAME:-digitization_toolkit}" >/dev/null 2>&1; then
+        echo "  Database ready."
+        break
+    fi
+    if [ "$i" -eq 30 ]; then
+        echo "✗ Database did not become ready after 60s."
+        $COMPOSE down
+        exit 1
+    fi
+    sleep 2
+done
+
+echo "→ Applying migrations..."
+cd "$PROJECT_ROOT/backend"
+run_as_user "$PIXI_BIN" run db-upgrade
+echo ""
+
+echo "→ Stopping database..."
+cd "$PROJECT_ROOT"
+$COMPOSE down
+echo ""
+
+# ---------------------------------------------------------------------------
+# 5. Restart the service
+# ---------------------------------------------------------------------------
+echo "→ Starting service..."
+systemctl start dtk
+sleep 5
+if systemctl is-active --quiet dtk; then
+    echo "  Service running ✓"
+else
+    echo "✗ Service failed to start. Check logs: journalctl -u dtk -n 50"
+    exit 1
+fi
+echo ""
+
+# ---------------------------------------------------------------------------
+# Done
+# ---------------------------------------------------------------------------
+echo "=========================================="
+echo " Update complete!"
+echo "=========================================="
+echo ""
+echo "  Frontend: http://localhost:3000"
+echo "  Backend:  http://localhost:8000/health"
+echo "  Logs:     journalctl -u dtk -f"
+echo ""