diff --git a/Final Report Template 2025 V1 (1).docx b/Final Report Template 2025 V1 (1).docx
deleted file mode 100644
index f3f00d3..0000000
Binary files a/Final Report Template 2025 V1 (1).docx and /dev/null differ
diff --git a/Interim Report C22501743.pdf b/Interim Report C22501743.pdf
deleted file mode 100644
index 0d95e62..0000000
Binary files a/Interim Report C22501743.pdf and /dev/null differ
diff --git a/docs/FOREGROUND_WEB_MOTION_DETECTION_ABSOLUTE_CHECKLIST.md b/docs/FOREGROUND_WEB_MOTION_DETECTION_ABSOLUTE_CHECKLIST.md
deleted file mode 100644
index 84898a8..0000000
--- a/docs/FOREGROUND_WEB_MOTION_DETECTION_ABSOLUTE_CHECKLIST.md
+++ /dev/null
@@ -1,32 +0,0 @@
-# Foreground Web Motion Detection Absolute Checklist
-
-- `MWM-001` Confirm first-release scope is web camera role only and foreground-tab only.
-- `MWM-002` Add detector-related state fields to [WebApp/src/lib/app/store.js](/home/matiss/Documents/Final%20Year%20Project/WebApp/src/lib/app/store.js:4).
-- `MWM-003` Define default motion detector config values for low-power foreground operation.
-- `MWM-004` Create a dedicated detector module under `WebApp/src/lib/app/`.
-- `MWM-005` Implement low-resolution frame sampling from the existing local camera stream.
-- `MWM-006` Implement grayscale conversion and normalized frame-difference scoring.
-- `MWM-007` Implement score smoothing or block aggregation to reduce noise flicker.
-- `MWM-008` Implement detector state machine transitions `idle`, `warming_up`, `monitoring`, `triggered`, `cooldown`.
-- `MWM-009` Implement adaptive sampling so idle sampling is slower than candidate-motion sampling.
-- `MWM-010` Ensure the detector starts only when the device role is `camera`, preview is ready, and detection is armed.
-- `MWM-011` Ensure the detector pauses or stops on camera permission loss, preview teardown, socket disconnect, or page hide.
-- `MWM-012` Add camera dashboard controls for arm/disarm and sensitivity.
-- `MWM-013` Add camera dashboard status UI for detector state and live motion score.
-- `MWM-014` Keep existing manual motion buttons intact and usable.
-- `MWM-015` Wire automatic detector trigger to the existing `startMotion` flow with `triggeredBy: "auto_motion"`.
-- `MWM-016` Prevent duplicate `startMotion` calls while a motion event is already active.
-- `MWM-017` Implement minimum event duration and quiet cooldown before automatic end.
-- `MWM-018` Wire automatic quiet-state completion to the existing `endMotion` flow.
-- `MWM-019` Add activity-log messages for detector armed/disarmed, trigger start, trigger end, and detector pause reasons.
-- `MWM-020` Add local persistence for detector settings so operator choices survive reloads.
-- `MWM-021` Validate that existing client notifications still fire through the unchanged backend event routes.
-- `MWM-022` Validate that existing recording behavior still works for auto-started motion events.
-- `MWM-023` Add unit-level tests for detector scoring and state-machine transitions.
-- `MWM-024` Add integration tests or deterministic mocks for event deduplication and cooldown handling.
-- `MWM-025` Perform manual runtime validation for no-motion idle scene, real person entry, lighting flicker, and camera shake.
-- `MWM-026` Measure runtime CPU/thermal behavior during a long foreground session and tune defaults if needed.
-- `MWM-027` Document the foreground-only assumption and known limits in project docs.
-- `MWM-028` Document recommended operator settings for lowest battery and heat.
-- `MWM-029` Add rollback behavior so disabling detection immediately stops the detector loop and leaves manual controls intact.
-- `MWM-030` Finalize a rollout note describing first-release non-goals such as background detection and ML classification.
diff --git a/docs/FOREGROUND_WEB_MOTION_DETECTION_EXECUTION_PROMPT.md b/docs/FOREGROUND_WEB_MOTION_DETECTION_EXECUTION_PROMPT.md
deleted file mode 100644
index ac1bc5b..0000000
--- a/docs/FOREGROUND_WEB_MOTION_DETECTION_EXECUTION_PROMPT.md
+++ /dev/null
@@ -1,40 +0,0 @@
-# Foreground Web Motion Detection Execution Prompt
-
-Implement automatic foreground-only motion detection for the web camera role using the artifacts below as the source of truth:
-
-- [FOREGROUND_WEB_MOTION_DETECTION_IMPLEMENTATION_PLAN.md](/home/matiss/Documents/Final%20Year%20Project/docs/FOREGROUND_WEB_MOTION_DETECTION_IMPLEMENTATION_PLAN.md)
-- [FOREGROUND_WEB_MOTION_DETECTION_ABSOLUTE_CHECKLIST.md](/home/matiss/Documents/Final%20Year%20Project/docs/FOREGROUND_WEB_MOTION_DETECTION_ABSOLUTE_CHECKLIST.md)
-- [FOREGROUND_WEB_MOTION_DETECTION_VALIDATION_MATRIX.md](/home/matiss/Documents/Final%20Year%20Project/docs/FOREGROUND_WEB_MOTION_DETECTION_VALIDATION_MATRIX.md)
-
-## Delivery Rules
-
-- Treat the implementation plan as authoritative for architecture and sequencing.
-- Complete checklist items atomically and update the validation matrix with evidence as work lands.
-- Do not silently skip hidden work such as store updates, detector lifecycle cleanup, tests, docs, and runtime validation.
-- Reuse the existing backend motion lifecycle before introducing any new backend motion pipeline.
-- Preserve manual motion controls and existing client notification behavior.
-
-## Evidence Rules
-
-- Every completed checklist item must have at least one evidence entry in the validation matrix.
-- `Code` evidence must reference the file changed.
-- `Test` evidence must reference a deterministic automated or manual validation step.
-- `Runtime` evidence must reference an observed app behavior, command result, or manual scenario outcome.
-
-## Completion Gates
-
-- Automatic motion detection works only for the web `camera` role.
-- The detector runs only while the browser tab is in the foreground and the detector is armed.
-- The detector starts and ends existing motion events automatically without duplicate starts.
-- Client notifications and recordings continue to function through existing backend routes.
-- Manual motion controls still work.
-- Detector settings are user-visible and persisted locally.
-- Tests and runtime validation cover idle scenes, real motion, flicker, and camera shake.
-
-## Suggested First Batch
-
-1. Add store fields and camera dashboard controls.
-2. Add the detector module with live score reporting only.
-3. Tune thresholds manually on the camera dashboard.
-4. Wire automatic start/end to the existing motion event flow.
-5. Add tests, docs, and validation evidence.
diff --git a/docs/FOREGROUND_WEB_MOTION_DETECTION_IMPLEMENTATION_PLAN.md b/docs/FOREGROUND_WEB_MOTION_DETECTION_IMPLEMENTATION_PLAN.md
deleted file mode 100644
index d774842..0000000
--- a/docs/FOREGROUND_WEB_MOTION_DETECTION_IMPLEMENTATION_PLAN.md
+++ /dev/null
@@ -1,229 +0,0 @@
-# Foreground Web Motion Detection Implementation Plan
-
-## Summary
-
-Implement automatic motion detection for the `camera` role in the web app while the browser remains open in the foreground on a plugged-in phone. Reuse the existing backend motion event, notification, recording, and stream flows instead of introducing a new backend motion pipeline.
-
-## Goals
-
-- Detect motion automatically from the local camera preview in the web app.
-- Trigger the existing motion event lifecycle with minimal backend change.
-- Minimize battery and heat by using low-resolution frame analysis and adaptive sampling.
-- Keep the first release heuristic and deterministic rather than ML-based.
-- Make behavior observable and tunable from the camera dashboard.
-
-## Constraints
-
-- The browser tab is assumed to remain visible in the foreground.
-- The initial target is the web app camera dashboard, not the Expo mobile app.
-- Existing backend endpoints remain the source of truth for motion events.
-- The current camera role UX in [WebApp/src/routes/camera/+page.svelte](/home/matiss/Documents/Final%20Year%20Project/WebApp/src/routes/camera/+page.svelte:31) must continue to work.
-- The current motion event routes in [Backend/routes/events.ts](/home/matiss/Documents/Final%20Year%20Project/Backend/routes/events.ts:35) and [Backend/routes/events.ts](/home/matiss/Documents/Final%20Year%20Project/Backend/routes/events.ts:142) should be reused.
-
-## Assumptions
-
-- Manual motion controls remain available as an operator override.
-- `triggeredBy` can distinguish manual versus automatic events without a schema change.
-- Persisted per-device motion settings are desirable, but an in-memory first pass is acceptable.
-- The existing recording behavior tied to stream/motion events remains the intended user experience.
-
-## Non-Goals
-
-- True background detection while the browser tab is hidden.
-- ML person/pet/vehicle classification in the first release.
-- Replacing the current notification or recording architecture.
-- Solving appliance-grade uptime guarantees.
-
-## Existing Integration Points
-
-- Camera preview and camera dashboard actions are already hosted in [WebApp/src/routes/camera/+page.svelte](/home/matiss/Documents/Final%20Year%20Project/WebApp/src/routes/camera/+page.svelte:105).
-- Local camera capture and preview lifecycle already exist in [WebApp/src/lib/app/controller.js](/home/matiss/Documents/Final%20Year%20Project/WebApp/src/lib/app/controller.js:233).
-- Manual motion start/end already call the backend in [WebApp/src/lib/app/controller.js](/home/matiss/Documents/Final%20Year%20Project/WebApp/src/lib/app/controller.js:1374).
-- Camera-side state is stored in [WebApp/src/lib/app/store.js](/home/matiss/Documents/Final%20Year%20Project/WebApp/src/lib/app/store.js:4).
-
-## Strategy
-
-### Phase 1: Add Motion Detector State And Controls
-
-Add camera-side detector state to the Svelte store:
-
-- `motionDetectionEnabled`
-- `motionDetectorStatus` such as `idle`, `warming_up`, `monitoring`, `triggered`, `cooldown`
-- `motionSensitivity`
-- `motionSampleIntervalMs`
-- `motionTriggerConsecutiveFrames`
-- `motionQuietCooldownMs`
-- `motionMinimumEventMs`
-- `motionScore`
-- `motionDebugEnabled`
-
-Expose controls on the camera dashboard:
-
-- Arm/disarm automatic detection
-- Sensitivity slider or preset selector
-- Low-power mode preset
-- Live debug score and current detector state
-
-Keep the existing manual `Simulate Motion Event` and `Stop Recording` actions for fallback.
-
-### Phase 2: Build A Lightweight Detector Engine
-
-Create a dedicated detector module, for example `WebApp/src/lib/app/motion-detector.js`, owned by the camera dashboard flow.
-
-Detector design:
-
-- Read from the existing `localCameraStream`
-- Draw frames into an offscreen or hidden canvas
-- Downsample aggressively to about `160x90` or `192x108`
-- Convert to grayscale
-- Compare the current frame against the previous smoothed frame
-- Compute a normalized motion score such as changed-pixel ratio or block-delta score
-- Ignore tiny isolated noise with thresholding and optional block aggregation
-
-Battery and heat controls:
-
-- Default sampling at `1 fps`
-- Burst to `4-6 fps` only after suspicious motion begins
-- Return to low sampling after cooldown
-- Skip work if preview is not ready, detector is disarmed, or document visibility changes
-- Avoid full-resolution processing and avoid network uploads during detection itself
-
-### Phase 3: Add Event State Machine And Backend Reuse
-
-Implement a camera-side state machine:
-
-- `idle` -> `monitoring`
-- `monitoring` -> `candidate_motion`
-- `candidate_motion` -> `triggered`
-- `triggered` -> `cooldown`
-- `cooldown` -> `monitoring`
-
-Trigger rules:
-
-- Require `N` consecutive high-motion frames before starting an event
-- Call the existing backend motion start endpoint once
-- Set `triggeredBy` to `auto_motion`
-- Hold the event open for at least `motionMinimumEventMs`
-- Only end after the score stays below threshold for `motionQuietCooldownMs`
-
-This keeps backend changes minimal because the existing event lifecycle already fans out realtime alerts and push notifications.
-
-### Phase 4: Make Recording Behavior Predictable
-
-The detector should not record constantly.
-
-Recommended behavior:
-
-- Motion detection itself only analyzes low-res frames locally
-- When automatic motion is confirmed, call the existing start-motion flow
-- Continue using the current recording logic already associated with motion and streaming
-- End the motion event only after quiet cooldown, not on every instantaneous dip
-
-This avoids repeated start/stop loops that waste device resources.
-
-### Phase 5: Add Persistence For Operator Settings
-
-Initial implementation can use local storage on the web app for speed.
-
-Second step:
-
-- Add motion settings persistence per camera device
-- Store settings either in `devices.metadata` if introduced later, or in a new `device_motion_settings` table
-- Load persisted settings on device registration or camera dashboard open
-
-Suggested settings:
-
-- Enabled/armed
-- Sensitivity
-- Sample interval
-- Quiet cooldown
-- Minimum event duration
-- Optional region of interest
-
-### Phase 6: Observability And Debugging
-
-Add operator-visible debug surfaces:
-
-- Current motion score
-- Detector state
-- Last trigger time
-- Count of suppressed candidate triggers
-
-Add activity log entries for:
-
-- Detector armed/disarmed
-- Detector warmed up
-- Automatic motion started
-- Automatic motion ended
-- Detector paused because preview or socket is unavailable
-
-### Phase 7: Test And Tune
-
-Testing should cover:
-
-- Low-motion idle scenes
-- Moderate lighting flicker
-- Real person entry into frame
-- Camera shake false positives
-- Reconnection behavior
-- Event deduplication
-
-Tuning targets:
-
-- Low false positive rate in static indoor scenes
-- Trigger latency below about `2 seconds`
-- CPU usage low enough to avoid obvious thermal throttling during foreground operation
-
-## File-Level Change Plan
-
-Primary files:
-
-- [WebApp/src/lib/app/store.js](/home/matiss/Documents/Final%20Year%20Project/WebApp/src/lib/app/store.js:4)
-- [WebApp/src/lib/app/controller.js](/home/matiss/Documents/Final%20Year%20Project/WebApp/src/lib/app/controller.js:233)
-- [WebApp/src/routes/camera/+page.svelte](/home/matiss/Documents/Final%20Year%20Project/WebApp/src/routes/camera/+page.svelte:105)
-
-Likely new files:
-
-- `WebApp/src/lib/app/motion-detector.js`
-- `WebApp/src/lib/app/motion-detector.test.js` or equivalent
-
-Optional later backend files:
-
-- [Backend/db/schema.ts](/home/matiss/Documents/Final%20Year%20Project/Backend/db/schema.ts:14)
-- [Backend/routes/devices.ts](/home/matiss/Documents/Final%20Year%20Project/Backend/routes/devices.ts:41)
-
-## Risk Controls
-
-- Use hysteresis so one threshold starts motion and a lower threshold ends it.
-- Require consecutive-frame confirmation before starting events.
-- Pause detection when preview, permission, or socket connectivity is unavailable.
-- Keep all frame processing local and low resolution.
-- Keep manual controls available during rollout.
-- Ship with debug mode so threshold tuning is possible without code changes.
-
-## Recommended Operator Settings
-
-- Start with the `Balanced` profile on a plugged-in phone.
-- Use `Low Power` if the phone runs warm or the scene is mostly static.
-- Keep the browser tab visible and the camera dashboard open while detection is armed.
-- Leave debug mode off during normal operation and enable it only while tuning thresholds.
-- Prefer a stable camera mount and a consistent indoor lighting setup to reduce false positives.
-
-## Acceptance Criteria
-
-- A camera-role web device can arm automatic motion detection from the camera dashboard.
-- When visible motion enters frame, the web app starts one backend motion event without duplicate starts.
-- Linked clients receive the same notifications they currently receive for manual motion events.
-- Motion events remain open through continuous motion and close only after quiet cooldown.
-- The detector does not continuously upload frames or full video for analysis.
-- Manual motion controls continue to work.
-- Detector state survives normal page usage and fails safely on disconnect or permission loss.
-
-## Recommended Delivery Order
-
-1. Add store state and camera dashboard controls.
-2. Add local detector engine with score reporting only, no event triggering.
-3. Tune thresholds against manual test scenes.
-4. Wire score transitions to automatic event start/end.
-5. Add persistence for detector settings.
-6. Add tests, docs, and rollout notes.
diff --git a/docs/FOREGROUND_WEB_MOTION_DETECTION_VALIDATION_MATRIX.md b/docs/FOREGROUND_WEB_MOTION_DETECTION_VALIDATION_MATRIX.md
deleted file mode 100644
index 388bf8b..0000000
--- a/docs/FOREGROUND_WEB_MOTION_DETECTION_VALIDATION_MATRIX.md
+++ /dev/null
@@ -1,34 +0,0 @@
-# Foreground Web Motion Detection Validation Matrix
-
-| Row ID | Checklist Item | Status | Code | Test | Runtime |
-| --- | --- | --- | --- | --- | --- |
-| `VM-MWM-001` | Confirm first-release scope is web camera role only and foreground-tab only | done | `WebApp/src/lib/app/controller.js` `shouldRunMotionDetector`; `docs/FOREGROUND_WEB_MOTION_DETECTION_IMPLEMENTATION_PLAN.md` Constraints/Non-Goals | `bun run check` | `bun run check` -> `svelte-check found 0 errors and 0 warnings` |
-| `VM-MWM-002` | Add detector-related state fields to store | done | `WebApp/src/lib/app/store.js` `createInitialState`; `WebApp/src/lib/app/controller.js` `getDefaultMotionDetectionState` | `bun run check` | `bun run check` -> `svelte-check found 0 errors and 0 warnings` |
-| `VM-MWM-003` | Define default detector config values | done | `WebApp/src/lib/app/controller.js` `MOTION_DETECTION_PROFILES`, `buildMotionDetectionState` | `bun run check` | `bun run check` -> `svelte-check found 0 errors and 0 warnings` |
-| `VM-MWM-004` | Create dedicated detector module | done | `WebApp/src/lib/app/motion-detector.js` `createMotionDetector` | `bun run test -- src/lib/app/motion-detector.spec.js` | `bun run test -- src/lib/app/motion-detector.spec.js` -> `4 passed` |
-| `VM-MWM-005` | Implement low-resolution frame sampling | done | `WebApp/src/lib/app/motion-detector.js` `DEFAULT_FRAME_WIDTH`, `DEFAULT_FRAME_HEIGHT`, `analyzeFrame` | `bun run test -- src/lib/app/motion-detector.spec.js` | `bun run test -- src/lib/app/motion-detector.spec.js` -> `4 passed` |
-| `VM-MWM-006` | Implement grayscale conversion and frame-difference scoring | done | `WebApp/src/lib/app/motion-detector.js` `computeLuma`, `computeChangedPixelRatio` | `src/lib/app/motion-detector.spec.js` `computes grayscale luminance...`, `reports the ratio...` | `bun run test -- src/lib/app/motion-detector.spec.js` -> `4 passed` |
-| `VM-MWM-007` | Implement score smoothing or block aggregation | done | `WebApp/src/lib/app/motion-detector.js` `DEFAULT_SMOOTHING_FACTOR`, `analyzeFrame` | `bun run test -- src/lib/app/motion-detector.spec.js` | `bun run test -- src/lib/app/motion-detector.spec.js` -> `4 passed` |
-| `VM-MWM-008` | Implement detector state machine transitions | done | `WebApp/src/lib/app/motion-detector.js` `createMotionMachineSnapshot`, `applyMotionStateMachine` | `src/lib/app/motion-detector.spec.js` `requires consecutive high-motion frames...`, `holds motion until minimum duration...` | `bun run test -- src/lib/app/motion-detector.spec.js` -> `4 passed` |
-| `VM-MWM-009` | Implement adaptive sampling | done | `WebApp/src/lib/app/motion-detector.js` `tick`; `WebApp/src/lib/app/controller.js` `MOTION_DETECTION_PROFILES` | `bun run test -- src/lib/app/motion-detector.spec.js` | `bun run check` -> `svelte-check found 0 errors and 0 warnings` |
-| `VM-MWM-010` | Start detector only when camera role, preview, and armed state are valid | done | `WebApp/src/lib/app/controller.js` `shouldRunMotionDetector`, `applyMotionDetectionReadiness` | `bun run check` | `bun run check` -> `svelte-check found 0 errors and 0 warnings` |
-| `VM-MWM-011` | Pause detector on permission loss, preview teardown, disconnect, or page hide | done | `WebApp/src/lib/app/controller.js` `getMotionDetectionPauseReason`, `applyMotionDetectionReadiness`, `onVisibilityChange` | `bun run check` | `bun run check` -> `svelte-check found 0 errors and 0 warnings` |
-| `VM-MWM-012` | Add camera dashboard arm/disarm and sensitivity controls | done | `WebApp/src/routes/camera/+page.svelte` Automatic Detection controls; `WebApp/src/lib/app/controller.js` `setMotionDetectionEnabled`, `setMotionDetectionProfile` | `bun run check` | `bun run check` -> `svelte-check found 0 errors and 0 warnings` |
-| `VM-MWM-013` | Add camera dashboard detector status and score UI | done | `WebApp/src/routes/camera/+page.svelte` Detector State/Motion Score cards | `bun run check` | `bun run check` -> `svelte-check found 0 errors and 0 warnings` |
-| `VM-MWM-014` | Preserve manual motion controls | done | `WebApp/src/routes/camera/+page.svelte` manual buttons; `WebApp/src/lib/app/controller.js` `actions.startMotion`, `actions.endMotion` | `bun run check` | `bun run check` -> `svelte-check found 0 errors and 0 warnings` |
-| `VM-MWM-015` | Trigger existing start-motion flow with `auto_motion` | done | `WebApp/src/lib/app/controller.js` `getMotionStartPayload`, `startMotionEvent`, `syncAutoMotionLifecycle`; `WebApp/src/lib/app/api.js` `events.startMotion` | `bun run check` | `bun run check` -> `svelte-check found 0 errors and 0 warnings` |
-| `VM-MWM-016` | Prevent duplicate automatic motion starts | done | `WebApp/src/lib/app/controller.js` `startMotionEvent`, `syncAutoMotionLifecycle`, `autoMotionTransitionInFlight` | `src/lib/app/motion-detector.spec.js` `requires consecutive high-motion frames...` | `bun run test -- src/lib/app/motion-detector.spec.js` -> `4 passed` |
-| `VM-MWM-017` | Implement minimum event duration and quiet cooldown | done | `WebApp/src/lib/app/motion-detector.js` `applyMotionStateMachine`; `WebApp/src/lib/app/controller.js` `syncAutoMotionLifecycle` | `src/lib/app/motion-detector.spec.js` `holds motion until minimum duration...` | `bun run test -- src/lib/app/motion-detector.spec.js` -> `4 passed` |
-| `VM-MWM-018` | Wire quiet-state completion to existing end-motion flow | done | `WebApp/src/lib/app/controller.js` `endMotionEvent`, `syncAutoMotionLifecycle`, `applyMotionDetectionReadiness` | `src/lib/app/motion-detector.spec.js` `holds motion until minimum duration...` | `bun run check` -> `svelte-check found 0 errors and 0 warnings` |
-| `VM-MWM-019` | Add activity-log messages for detector lifecycle | done | `WebApp/src/lib/app/controller.js` `addActivity` calls in `applyMotionDetectionReadiness`, `setMotionDetectionEnabled`, `startMotionEvent`, `endMotionEvent` | `bun run check` | `bun run check` -> `svelte-check found 0 errors and 0 warnings` |
-| `VM-MWM-020` | Add local persistence for detector settings | done | `WebApp/src/lib/app/controller.js` `loadMotionDetectionSettings`, `persistMotionDetectionSettings`, `updateMotionDetectionState` | `bun run check` | `bun run check` -> `svelte-check found 0 errors and 0 warnings` |
-| `VM-MWM-021` | Validate existing client notifications still work | pending | Existing backend fan-out remains unchanged in `Backend/routes/events.ts` |  | Runtime validation still required with linked client devices |
-| `VM-MWM-022` | Validate recording behavior still works for auto-started events | pending | Existing recording paths remain in `WebApp/src/lib/app/controller.js` `startLocalRecording`, `endMotionEvent`, `uploadStandaloneMotionRecording` |  | Runtime validation still required with an actual auto-triggered event |
-| `VM-MWM-023` | Add unit tests for scoring and state-machine transitions | done | `WebApp/src/lib/app/motion-detector.js` exported helpers; `WebApp/src/lib/app/motion-detector.spec.js` | `bun run test -- src/lib/app/motion-detector.spec.js` | `bun run test -- src/lib/app/motion-detector.spec.js` -> `4 passed` |
-| `VM-MWM-024` | Add integration tests or deterministic mocks for cooldown and dedupe | in_progress | `WebApp/src/lib/app/motion-detector.spec.js` covers deterministic cooldown and trigger gating; controller dedupe still untested | `bun run test -- src/lib/app/motion-detector.spec.js` | Additional controller-level mock coverage still needed |
-| `VM-MWM-025` | Perform manual validation for idle, real motion, flicker, and camera shake | pending |  |  |  |
-| `VM-MWM-026` | Measure runtime CPU and thermal behavior during long foreground session | pending |  |  |  |
-| `VM-MWM-027` | Document foreground-only assumption and limits | done | `docs/FOREGROUND_WEB_MOTION_DETECTION_IMPLEMENTATION_PLAN.md` Constraints/Non-Goals/Acceptance Criteria |  | Doc updated in repo |
-| `VM-MWM-028` | Document recommended low-battery and low-heat settings | done | `docs/FOREGROUND_WEB_MOTION_DETECTION_IMPLEMENTATION_PLAN.md` Battery and heat controls; Recommended Operator Settings |  | Doc updated in repo |
-| `VM-MWM-029` | Add immediate rollback behavior when detection is disabled | done | `WebApp/src/lib/app/controller.js` `setMotionDetectionEnabled`, `applyMotionDetectionReadiness`, `endMotionEvent` | `bun run check` | `bun run check` -> `svelte-check found 0 errors and 0 warnings` |
-| `VM-MWM-030` | Publish rollout note for first-release non-goals | done | `docs/FOREGROUND_WEB_MOTION_DETECTION_IMPLEMENTATION_PLAN.md` Non-Goals |  | Doc updated in repo |
diff --git a/docs/STREAMING_SIMPLIFICATION_ABSOLUTE_CHECKLIST.md b/docs/STREAMING_SIMPLIFICATION_ABSOLUTE_CHECKLIST.md
deleted file mode 100644
index d09b22e..0000000
--- a/docs/STREAMING_SIMPLIFICATION_ABSOLUTE_CHECKLIST.md
+++ /dev/null
@@ -1,75 +0,0 @@
-# Absolute Checklist: Streaming Simplification (WebRTC-only)
-
-## Backend
-
-1. Add/confirm `SIMPLE_STREAMING` environment/config switch (default: true for new deployment profile).
-2. In `Backend/routes/streams.ts`, update `POST /streams/request` to:
-   - keep device role/link validation
-   - create session with status `requested`
-   - emit request event directly compatible with WebRTC-only flow
-   - remove stream-provider payload assumptions from response
-3. In `Backend/routes/streams.ts`, update `POST /streams/:id/accept` to:
-   - validate camera ownership and state
-   - set status to `streaming`
-   - set `startedAt`
-   - emit `stream:started`
-   - remove or gate all publish/subscribe/media-provider dependency
-4. In `Backend/routes/streams.ts`, update `POST /streams/:id/end` to:
-   - require authorized participant (camera or requester)
-   - set status to `ended`
-   - set `endedAt`
-   - emit `stream:ended`
-   - stop any active SFU session only if explicitly still active and configured
-5. In `Backend/routes/streams.ts`, remove any hard dependency on `mediaProvider.createSession` for live functionality.
-6. Gate recording creation in stream end logic behind feature flag (default OFF) or remove endpoint path from phase-1 path.
-7. In `Backend/routes/streams.ts`, return minimal deterministic payload for stream start/accept/end responses.
-8. In `Backend/db/schema.ts`, mark legacy media fields as deprecated comments only (no schema migration required in phase 1).
-9. In `Backend/media/service.ts`, make provider calls no-op for phase-1 streaming runtime or guard them behind non-simplified feature flag.
-10. In `Backend/media/providers/mock.ts`, annotate mock provider methods as metadata-only and remove calls from request/accept/end flow.
-11. In `Backend/media/sfu/service.ts` and `Backend/media/sfu/noop.ts`, ensure no required startup path is executed for default simplified mode.
-12. In `Backend/routes/commands.ts`, document command-table deprecation for stream lifecycle command path; remove active usage if simplified mode is enabled.
-
-## Realtime Gateway
-
-13. In `Backend/realtime/gateway.ts`, remove `stream:frame` event listener and sender path.
-14. In `Backend/realtime/gateway.ts`, remove frame-relay participant cache and related validation branch.
-15. In `Backend/realtime/gateway.ts`, keep only validated `webrtc:signal` logic for offer/answer/candidate/hangup.
-16. In `Backend/realtime/gateway.ts`, simplify signal forwarding so target validation is session ownership + same user context.
-17. In `Backend/realtime/gateway.ts`, remove periodic command retry polling for stream commands when in simplified mode.
-18. Keep `stream:started` and `stream:ended` emit paths with recipient resolution.
-19. Ensure socket middleware still enforces device token auth and role identity checks.
-
-## Web frontend
-
-20. In `WebApp/src/lib/app/controller.js`, collapse stream state to `idle|connecting|active|ended`.
-21. Remove fallback image mode, latest-frame state, and frame receiver logic from controller.
-22. Ensure client side only uses WebRTC peer connection and `<video>` rendering path.
-23. Simplify `ontrack` handling to set remote stream once and ignore duplicate tracks.
-24. Add deterministic peer teardown on `stream:ended`, page unload, and navigation changes.
-25. In `WebApp/src/routes/camera/+page.svelte`, remove preview-to-frame interval fallback sender.
-26. In `WebApp/src/routes/camera/+page.svelte`, ensure camera-side stream path emits offer only and no JPEG payload.
-27. In `WebApp/src/routes/camera/+page.svelte`, remove recording branch that depends on frame transport.
-28. In `WebApp/src/routes/client/+page.svelte`, remove fallback image DOM branch and related status labels.
-
-## Mobile frontend
-
-29. In `MobileApp/src/app-context.tsx`, remove base64 frame stream state and timer lifecycle for frame relay.
-30. In `MobileApp/src/app-context.tsx` and `MobileApp/app/(tabs)/index.tsx`, align stream lifecycle state transitions with web logic.
-31. In `MobileApp/app/(tabs)/index.tsx`, remove capture+`stream:frame` emission loop.
-32. In `MobileApp/app/(tabs)/index.tsx`, remove any image fallback UI path and render strategy for active stream.
-33. In `MobileApp/src/api.ts`, remove calls to publish/subscribe credentials endpoints from simplified runtime flow.
-34. Ensure mobile camera cleanup stops local media and closes RTCPeerConnection on end and unmount.
-
-## Cross-cutting API/docs/config
-
-35. In `Backend/docs/openapi.ts`, update documented streaming contract to only include:
-   - request
-   - accept
-   - end
-   - webrtc signal event behavior
-   - remove references implying frame fallback as primary path
-36. Update any internal docs or README sections describing mock media endpoints as runtime-critical.
-37. Add migration notes to avoid breaking integrations (deprecation and rollback behavior).
-38. Add explicit log markers for stream request/accept/offer/answer/end events with session id and participant ids.
-39. Add compile/build compatibility checks for both apps after removing unused symbols/imports.
-40. Add runtime rollback checklist for disabling `SIMPLE_STREAMING` and re-enabling legacy paths.
diff --git a/docs/STREAMING_SIMPLIFICATION_EXECUTION_PROMPT.md b/docs/STREAMING_SIMPLIFICATION_EXECUTION_PROMPT.md
deleted file mode 100644
index 751124c..0000000
--- a/docs/STREAMING_SIMPLIFICATION_EXECUTION_PROMPT.md
+++ /dev/null
@@ -1,73 +0,0 @@
-# Execution Prompt: Streaming Simplification
-
-You are implementing `STREAMING_SIMPLIFICATION` in `/home/matiss/Documents/Final Year Project`.
-
-## Objective
-Deliver a WebRTC-only streaming architecture for this codebase by implementing the four artifacts:
-1. `docs/STREAMING_SIMPLIFICATION_IMPLEMENTATION_PLAN.md`
-2. `docs/STREAMING_SIMPLIFICATION_ABSOLUTE_CHECKLIST.md`
-3. `docs/STREAMING_SIMPLIFICATION_VALIDATION_MATRIX.md`
-4. This execution prompt.
-
-## Governing constraints
-- Preserve device token auth and role checks.
-- Keep request/accept/end endpoints and WebRTC signaling functional.
-- Remove socket JPEG frame fallback from runtime path.
-- Keep rollback-capable behavior using `SIMPLE_STREAMING` where possible.
-- Do not reintroduce any media-path dependency on mock provider endpoints.
-
-## Execution sequence (strict)
-
-1. Implement all backend stream endpoint and session-state simplifications first.
-2. Simplify realtime gateway signaling path second.
-3. Update web frontend streaming controller and pages.
-4. Update mobile frontend streaming behavior.
-5. Update docs, config notes, and OpenAPI/event description.
-6. Run validation matrix gating; do not mark complete until all required evidence rows are filled.
-
-## Completion gates
-
-### Gate A — Backend
-- `Backend/routes/streams.ts` follows simplified lifecycle only.
-- `Backend/realtime/gateway.ts` contains no frame-relay path in active flow.
-- Unauthorized access checks remain strict and verifiable.
-
-### Gate B — Frontends
-- Web and Mobile each have one stream state machine and one active rendering strategy.
-- No scheduled frame-relay sender/receiver code remains in runtime path.
-- End-of-stream cleanup is deterministic and symmetric.
-
-### Gate C — Delivery readiness
-- OpenAPI/docs updated for simplified contract.
-- Feature flag/rollback documented.
-- Validation matrix entries populated from observed evidence.
-
-## Evidence rules
-
-For every checklist line in `docs/STREAMING_SIMPLIFICATION_ABSOLUTE_CHECKLIST.md`:
-1. Fill corresponding row in `docs/STREAMING_SIMPLIFICATION_VALIDATION_MATRIX.md` from pending -> done.
-2. Populate columns:
-   - **Code Evidence**: file path + symbols/line references
-   - **Test Evidence**: command output or test report artifact names
-   - **Runtime Evidence**: screenshot/video/log excerpt references and scenario details
-3. Keep one evidence item per row if possible; if blocked, include blocker and retry plan.
-
-## Required validation commands (when execution resumes)
-
-- Backend: validate API/types/contracts compile/build and lint status.
-- Gateway: static check that `stream:frame` handlers are absent in effective runtime mode.
-- Frontend: build check for both web and mobile after removing unused imports/state.
-- Runtime smoke checks:
-  - client request -> camera accept -> stream start -> stream end
-  - unauthorized request rejection
-  - cleanup path after end and reconnect
-
-## Final report format
-
-Return a final report with:
-1. Completed tasks grouped by file.
-2. Validation matrix fully updated.
-3. Any deviations from this spec and why.
-4. Exact first and second risk identified after rollout.
-
-Do not introduce additional assumptions not covered in the checklist without updating the checklist and matrix.
diff --git a/docs/STREAMING_SIMPLIFICATION_IMPLEMENTATION_PLAN.md b/docs/STREAMING_SIMPLIFICATION_IMPLEMENTATION_PLAN.md
deleted file mode 100644
index ede1c61..0000000
--- a/docs/STREAMING_SIMPLIFICATION_IMPLEMENTATION_PLAN.md
+++ /dev/null
@@ -1,138 +0,0 @@
-# Implementation Plan: Streaming Simplification (WebRTC-only)
-
-## 0) Goal and scope
-
-### Goal
-Simplify the current streaming architecture to a single production-pragmatic implementation path:
-- Control plane via REST + socket signaling
-- Media plane via WebRTC only
-- No JPEG frame fallback relay
-- Preserve security and device-role authorization
-
-### Scope in/out
-- In scope:
-  - Stream request/accept/end lifecycle
-  - Device role and ownership checks
-  - WebRTC signaling and connection setup/teardown
-  - Frontend Web + Mobile stream runtime paths
-  - API/docs updates for simplified contract
-- Out of scope:
-  - Multi-party broadcast or conferencing
-  - SFU/ingest pipeline replacement in this phase
-  - Media provider feature parity with mock provider URLs
-  - Full recording workflow and upload/finalization
-
-## 1) Current-state constraints to keep
-
-- Devices use bearer tokens and role-based socket/session authentication.
-- Stream request is initiated by a `client` device targeting a linked `camera`.
-- Current schema/event names exist and are used across components.
-- Backend and frontends already support `stream:requested`, `stream:started`, `stream:ended`, and `webrtc:signal`.
-
-## 2) Explicit requirements
-
-1. Runtime complexity reduction:
-   - Keep one media transport: WebRTC.
-   - Remove socket JPEG fallback flow from runtime.
-2. Reliability and safety:
-   - Keep strict owner/role checks for all stream/session endpoints.
-   - Ensure deterministic teardown when stream ends.
-3. Maintainability:
-   - Remove dead or non-critical branches.
-   - Minimize special-case flags and dual state machines.
-4. Backward compatibility strategy:
-   - Prefer a feature flag `SIMPLE_STREAMING` for controlled rollout.
-
-## 3) Assumptions
-
-- Existing database schema can remain (deprecating fields is acceptable for now).
-- Camera and client are expected to be online for primary WebRTC path; if not reachable, stream request/accept will fail gracefully.
-- `stream:frame` is not required for core user value in phase 1.
-- Recording features can be delayed or gated without blocking stream acceptance.
-- Existing command dispatch infrastructure can be simplified or replaced by direct request/session events without redesigning auth.
-
-## 4) Non-goals and excluded behaviors
-
-- No immediate migration to true production-grade media server or SFU.
-- No auto-retry queue for offline command delivery.
-- No new codec/transcoding pipeline.
-
-## 5) Target architecture
-
-### Backend
-- Stream endpoints: request -> accept -> end.
-- Session state transitions:
-  - `requested` -> `streaming` -> `ended`
-- Commands table may be retained only for audit/logging or removed later.
-- Gateway relays:
-  - `webrtc:signal` only for media negotiation.
-  - `stream:started` and `stream:ended` for lifecycle updates.
-
-### Frontend (Web + Mobile)
-- Shared runtime model:
-  - `idle` -> `connecting` -> `active` -> `ended`
-- On camera accept: start WebRTC offer.
-- On client started event: start WebRTC answer/handling.
-- On ended: stop peer connections, clear state.
-- No frame image fallback state/UI.
-
-## 6) Phased implementation strategy
-
-### Phase 1: Contract freeze and safety gate (Day 0)
-1. Lock simplified state contract and event matrix.
-2. Add/validate `SIMPLE_STREAMING` flag and default behavior.
-3. Add migration notes for legacy paths.
-
-### Phase 2: Backend control-plane simplification (Day 1)
-1. Refactor stream request/accept/end handlers to only manage session lifecycle and signaling.
-2. Remove/disable stream-provider-specific runtime side effects from these handlers.
-3. Ensure response payloads are minimal and stable.
-
-### Phase 3: Gateway simplification (Day 1)
-1. Remove `stream:frame` event handler and related relay state.
-2. Keep only validated WebRTC signaling and lifecycle event emitters.
-3. Remove command retry loop if not required by flag.
-
-### Phase 4: Web frontend simplification (Day 2)
-1. Simplify stream controller into single mode.
-2. Remove image fallback flow and related timers/state.
-3. Keep single video render path and deterministic cleanup.
-
-### Phase 5: Mobile frontend simplification (Day 2)
-1. Remove periodic frame capture/relay code and image fallback rendering.
-2. Keep camera capture + WebRTC publish path.
-3. Align end/cleanup behavior with web.
-
-### Phase 6: API/doc/ops cleanup (Day 3)
-1. Update OpenAPI/event docs and internal docs.
-2. Deprecate references to frame-based streaming and mock endpoints in code comments.
-3. Add rollout and rollback runbook.
-
-### Phase 7: Validation and rollout (Day 4)
-1. Manual runtime smoke tests for request/accept/offer/answer/end.
-2. Validate unauthorized access rejection for all endpoints.
-3. Rollout in flag-off/flag-on modes and monitor.
-
-## 7) Sequence and dependency reasoning
-
-- Backend simplification must land before frontend simplification to avoid client calling removed paths.
-- Gateway simplification is independent after stream endpoints are stable but should be merged before frontend hardening.
-- Frontend changes rely on a stable event contract (`webrtc:signal`, `stream:started`, `stream:ended`).
-- Docs/validation are final tasks once behavior stabilizes.
-
-## 8) Failure handling and risk controls
-
-1. **Rollback strategy:** feature flag switch routes behavior back to existing legacy logic.
-2. **Forward progress gate:** stream accept/start should not require any media provider credential.
-3. **Safety gate:** reject unknown/non-matching event payloads in gateway before forwarding.
-4. **Error handling:** explicit peer connection cleanup on timeout/error and session end.
-5. **Observability:** structured logs for request/accept/offer/answer/hangup/end with stream session ids.
-
-## 9) Acceptance criteria
-
-1. `client` -> request -> camera `accept` -> live WebRTC stream works on web and mobile.
-2. No `stream:frame` event is used in runtime media path.
-3. Stream teardown always emits `stream:ended`, clears peer connections, and stops capture.
-4. Unauthorized role/device combinations are rejected with explicit errors.
-5. OpenAPI and internal docs only advertise simplified contract by default.
-6. Feature flag allows toggling between simplified and legacy behavior for quick rollback.
diff --git a/docs/STREAMING_SIMPLIFICATION_ROLLOUT_AND_ROLLBACK.md b/docs/STREAMING_SIMPLIFICATION_ROLLOUT_AND_ROLLBACK.md
deleted file mode 100644
index 5e13502..0000000
--- a/docs/STREAMING_SIMPLIFICATION_ROLLOUT_AND_ROLLBACK.md
+++ /dev/null
@@ -1,45 +0,0 @@
-# Streaming Simplification Rollout And Rollback
-
-## Rollout intent
-
-`SIMPLE_STREAMING` enables the new WebRTC-only control path:
-- direct `stream:requested` fan-out to the camera
-- no media-provider session requirement for request/accept/end
-- no `stream:frame` relay in the backend gateway
-- web client uses only WebRTC offer/answer/candidate signaling
-
-## Migration notes
-
-1. Native mobile is not yet on the WebRTC path.
-2. `MobileApp/package.json` does not include a native WebRTC dependency such as `react-native-webrtc`.
-3. `MobileApp/README.md` documents that the mobile app still relies on legacy `stream:frame` relay.
-4. Because of this, `SIMPLE_STREAMING` defaults to `false`.
-5. Web and backend are prepared for the simplified path now.
-
-## Safe enablement sequence
-
-1. Deploy backend and web changes with `SIMPLE_STREAMING=false`.
-2. Validate legacy mobile behavior still works.
-3. Validate web camera/client behavior with `SIMPLE_STREAMING=true` in a controlled environment.
-4. Add native mobile WebRTC support before changing the default flag value.
-
-## Runtime checks when enabling
-
-1. Request a stream from a web client to a web camera.
-2. Confirm the camera receives `stream:requested`.
-3. Confirm `stream:started` is emitted after accept.
-4. Confirm WebRTC offer/answer/candidate exchange succeeds.
-5. Confirm `stream:ended` tears down both sides cleanly.
-6. Confirm no `stream:frame` messages appear in gateway logs.
-
-## Rollback checklist
-
-1. Set `SIMPLE_STREAMING=false`.
-2. Restart backend instances.
-3. Verify `/streams/request` creates `start_stream` commands again.
-4. Verify mobile frame-relay streaming resumes.
-5. Re-run web and mobile smoke checks on the legacy path.
-
-## Known blocker
-
-Native mobile parity is blocked until a supported RN WebRTC stack is added and wired into `MobileApp/src/app-context.tsx`.
diff --git a/docs/STREAMING_SIMPLIFICATION_VALIDATION_MATRIX.md b/docs/STREAMING_SIMPLIFICATION_VALIDATION_MATRIX.md
deleted file mode 100644
index c8a23a9..0000000
--- a/docs/STREAMING_SIMPLIFICATION_VALIDATION_MATRIX.md
+++ /dev/null
@@ -1,44 +0,0 @@
-# Validation Matrix: Streaming Simplification (WebRTC-only)
-
-| Row ID | Checklist Item | Status | Code Evidence | Test Evidence | Runtime Evidence |
-|---|---|---|---|---|---|
-| B1 | Add/confirm `SIMPLE_STREAMING` environment/config switch | done | `Backend/media/config.ts:28,44-50` (`parseFeatureFlag`, `simpleStreamingEnabled`, `streamRecordingEnabled`) | `bun test` -> `tests/media-config.test.ts` passed (3 cases) | `bunx tsc --noEmit` exited 0 in `Backend/` |
-| B2 | Update stream request endpoint with simplified flow and role/link checks | done | `Backend/routes/streams.ts:168-184` (`createStreamRequestedPayload`, simplified `/streams/request` response) | `bun test` -> `tests/streaming-simple.test.ts` passed (`builds deterministic requested and started payloads`) | `bunx tsc --noEmit` exited 0 in `Backend/` |
-| B3 | Update stream accept endpoint to set `streaming` and emit started | done | `Backend/routes/streams.ts:344-356` (`createStreamStartedPayload`, simplified accept response) | `bun test` -> `tests/streaming-simple.test.ts` passed (`builds deterministic requested and started payloads`) | `bunx tsc --noEmit` exited 0 in `Backend/` |
-| B4 | Update stream end endpoint with proper status, end timestamp, lifecycle emit | done | `Backend/routes/streams.ts:660-721` (`status: nextStatus`, `createStreamEndedPayload`, simplified end response) | `bun test` -> `tests/streaming-simple.test.ts` passed (`normalizes ended payload and strips provider fields from API response`) | `bunx tsc --noEmit` exited 0 in `Backend/` |
-| B5 | Remove media provider dependency in accept logic | done | `Backend/media/service.ts:17-24` (`mediaProviderRuntimeEnabled`, `createLiveMediaSession`), `Backend/routes/streams.ts:320-334` (accept uses wrapper result) | `bun test` -> `tests/media-config.test.ts`, `tests/streaming-simple.test.ts` both passed | `bunx tsc --noEmit` exited 0 in `Backend/` |
-| B6 | Gate/remove recording creation path in stream end logic | done | `Backend/media/config.ts:45,50`, `Backend/routes/streams.ts:681-683` (`streamRecordingEnabled`) | `bun test` passed all 17 tests in `Backend/tests/*` | `bunx tsc --noEmit` exited 0 in `Backend/` |
-| B7 | Return minimal deterministic stream payloads | done | `Backend/streaming/simple.ts:35-73` (`createStream*Payload`, `toSimpleStreamSessionResponse`), `Backend/routes/streams.ts:184,356,721` | `bun test` -> `tests/streaming-simple.test.ts` passed (3 cases) | `bunx tsc --noEmit` exited 0 in `Backend/` |
-| B8 | Document deprecated media fields in schema | done | `Backend/db/schema.ts:68-69` (legacy provider field comments) | `bun test` passed all 17 tests in `Backend/tests/*` | `bunx tsc --noEmit` exited 0 in `Backend/` |
-| B9 | Guard media service calls behind non-simplified mode | done | `Backend/media/service.ts:17-24` (`mediaProviderRuntimeEnabled`, `createLiveMediaSession`) | `bun test` -> `tests/media-config.test.ts` passed (3 cases) | `bunx tsc --noEmit` exited 0 in `Backend/` |
-| B10 | Annotate mock provider as metadata-only in phase-1 path | done | `Backend/media/providers/mock.ts:40-41` (runtime compatibility comment), `Backend/routes/streams.ts:320-334` (runtime no longer requires provider session in simplified mode) | `bun test` passed all 17 tests in `Backend/tests/*` | `bunx tsc --noEmit` exited 0 in `Backend/` |
-| B11 | Ensure SFU service not required in simplified mode | done | `Backend/media/sfu/service.ts:1,6-8` (`simpleStreamingEnabled` short-circuit) | `bun test` passed all 17 tests in `Backend/tests/*` | `bunx tsc --noEmit` exited 0 in `Backend/` |
-| B12 | Deprecate command-table stream lifecycle usage under simplified mode | done | `Backend/routes/commands.ts:53`, `Backend/routes/streams.ts:168-184`, `Backend/realtime/gateway.ts:110-116` | `bun test` passed all 17 tests in `Backend/tests/*` | `bunx tsc --noEmit` exited 0 in `Backend/` |
-| R13 | Remove `stream:frame` event listener/sender from gateway | done | `Backend/realtime/gateway.ts:323-349` (`webrtc:signal` only in streaming path) | `bun test` passed all 17 tests in `Backend/tests/*` | `rg -n "stream:frame" Backend/realtime/gateway.ts` returned no matches; `bunx tsc --noEmit` exited 0 |
-| R14 | Remove frame-relay participant cache and validation branches | done | `Backend/realtime/gateway.ts:240-349` (no `verifiedRelayTargets`, no frame validation branch) | `bun test` passed all 17 tests in `Backend/tests/*` | `rg -n "stream:frame" Backend/realtime/gateway.ts` returned no matches; `bunx tsc --noEmit` exited 0 |
-| R15 | Keep only `webrtc:signal` relay logic for streaming | done | `Backend/realtime/gateway.ts:323-349` (`socket.on('webrtc:signal'...)`) | `bun test` -> `tests/streaming-simple.test.ts` passed (`only relays WebRTC signals between stream participants`) | `rg -n "stream:frame" Backend/realtime/gateway.ts` returned no matches; `bunx tsc --noEmit` exited 0 |
-| R16 | Simplify signal validation to ownership + session checks | done | `Backend/realtime/gateway.ts:330-343` (`streamSessions` lookup + `canRelayWebrtcSignal`), `Backend/streaming/simple.ts:20-33` | `bun test` -> `tests/streaming-simple.test.ts` passed (`only relays WebRTC signals between stream participants`) | `bunx tsc --noEmit` exited 0 in `Backend/` |
-| R17 | Remove command retry polling for stream command queue when flag is enabled | done | `Backend/realtime/gateway.ts:110-116,155-161` (`start_stream` dispatch/retry disabled under `SIMPLE_STREAMING`) | `bun test` passed all 17 tests in `Backend/tests/*` | `bunx tsc --noEmit` exited 0 in `Backend/` |
-| R18 | Preserve `stream:started` and `stream:ended` event emission | done | `Backend/routes/streams.ts:344-353,685-714`, `Backend/realtime/gateway.ts:36-49` (`sendRealtimeToDevice`) | `bun test` -> `tests/streaming-simple.test.ts` passed (`builds deterministic requested and started payloads`, `normalizes ended payload`) | `bunx tsc --noEmit` exited 0 in `Backend/` |
-| R19 | Keep strict socket auth and room handling for devices | done | `Backend/realtime/gateway.ts:176-235` (token auth, role match, room join) | `bun test` -> `tests/device-token.test.ts` passed (2 cases) | `bunx tsc --noEmit` exited 0 in `Backend/` |
-| W20 | Simplify web stream state machine | done | `WebApp/src/lib/app/controller.js:144-152,950-975`, `WebApp/src/lib/app/store.js:43-44` | `npm run check` in `WebApp/` passed (`svelte-check found 0 errors and 0 warnings`) | `npm run build` in `WebApp/` passed |
-| W21 | Remove web fallback image mode and frame state | done | `WebApp/src/lib/app/store.js:43-44`, `WebApp/src/lib/app/controller.js:144-152`, `WebApp/src/routes/client/+page.svelte:183-189` | `npm run check` in `WebApp/` passed (`svelte-check found 0 errors and 0 warnings`) | `rg -n "stream:frame|clientFallbackFrame|getPublishCreds|getSubscribeCreds|frameRelay" WebApp/src` returned no matches; `npm run build` passed |
-| W22 | Enforce video-only rendering path on client | done | `WebApp/src/routes/client/+page.svelte:183-189`, `WebApp/src/lib/app/controller.js:723,950-968` | `npm run check` in `WebApp/` passed (`svelte-check found 0 errors and 0 warnings`) | `npm run build` in `WebApp/` passed |
-| W23 | Simplify `ontrack` handling | done | `WebApp/src/lib/app/controller.js:711-723` (`connection.ontrack`) | `npm run check` in `WebApp/` passed (`svelte-check found 0 errors and 0 warnings`) | `npm run build` in `WebApp/` passed |
-| W24 | Add deterministic teardown path on end/unmount/navigation | done | `WebApp/src/lib/app/controller.js:596-614,975-992,1125-1132` (`teardownPeerConnection`, `stream:ended`, cleanup) | `npm run check` in `WebApp/` passed (`svelte-check found 0 errors and 0 warnings`) | `npm run build` in `WebApp/` passed |
-| W25 | Remove frame capture/sender fallback on web camera page | done | `WebApp/src/lib/app/controller.js:869-882,908-928` (camera request handling now only starts preview/accept/offer), `WebApp/src/routes/camera/+page.svelte` remains preview-only | `npm run check` in `WebApp/` passed (`svelte-check found 0 errors and 0 warnings`) | `rg -n "stream:frame|clientFallbackFrame|getPublishCreds|getSubscribeCreds|frameRelay" WebApp/src` returned no matches; `npm run build` passed |
-| W26 | Ensure camera only sends WebRTC offer path | done | `WebApp/src/lib/app/controller.js:738-749,869-882,908-928` (`startOfferToClient`, `handleCameraStreamRequest`) | `npm run check` in `WebApp/` passed (`svelte-check found 0 errors and 0 warnings`) | `npm run build` in `WebApp/` passed |
-| W27 | Remove recording hooks tied to fallback transport | done | `WebApp/src/lib/app/controller.js:869-882,975-992` (recording kept, fallback transport removed), no frame relay refs remain in `WebApp/src` | `npm run check` in `WebApp/` passed (`svelte-check found 0 errors and 0 warnings`) | `rg -n "stream:frame|clientFallbackFrame|getPublishCreds|getSubscribeCreds|frameRelay" WebApp/src` returned no matches; `npm run build` passed |
-| W28 | Remove client-side image fallback UI branches | done | `WebApp/src/routes/client/+page.svelte:183-189`, `WebApp/src/lib/app/store.js:43-44` | `npm run check` in `WebApp/` passed (`svelte-check found 0 errors and 0 warnings`) | `npm run build` in `WebApp/` passed |
-| M29 | Remove mobile frame relay state and timer lifecycle | blocked | `MobileApp/src/app-context.tsx:86-87,175-213`, `MobileApp/README.md:75-79` show native mobile still depends on frame relay; `MobileApp/package.json` has no `react-native-webrtc` dependency | `npm run lint` in `MobileApp/` passed | `rg -n "react-native-webrtc" MobileApp/package.json` returned no matches; native WebRTC stack still absent |
-| M30 | Align mobile state transitions with web logic | blocked | `MobileApp/src/app-context.tsx:105-113,349-381`, `MobileApp/src/state.ts:92-93`, `MobileApp/README.md:75-79` | `npm run lint` in `MobileApp/` passed | `npx tsc --noEmit` exited 0 in `MobileApp/`; implementation remains blocked by missing native WebRTC runtime |
-| M31 | Remove mobile JPEG relay loop | blocked | `MobileApp/src/app-context.tsx:183-213,312-319`, `MobileApp/README.md:75-79` | `npm run lint` in `MobileApp/` passed | `rg -n "react-native-webrtc" MobileApp/package.json` returned no matches; removing the JPEG loop would break the only current mobile stream path |
-| M32 | Remove mobile image fallback rendering path | blocked | `MobileApp/app/(tabs)/index.tsx:150-151,284`, `MobileApp/src/state.ts:92-93` | `npm run lint` in `MobileApp/` passed | `npx tsc --noEmit` exited 0 in `MobileApp/`; image fallback remains required until native WebRTC view/render support exists |
-| M33 | Remove publish/subscribe credential calls from streaming runtime | blocked | `MobileApp/src/app-context.tsx:312,361`, `MobileApp/src/api.ts:84-85` | `npm run lint` in `MobileApp/` passed | `npx tsc --noEmit` exited 0 in `MobileApp/`; credential calls remain because mobile still follows the legacy relay path |
-| M34 | Ensure mobile peer cleanup on end/unmount | blocked | `MobileApp/src/app-context.tsx:375-412` has no RTCPeerConnection lifecycle to clean up; `MobileApp/README.md:79` documents missing RN WebRTC stack | `npm run lint` in `MobileApp/` passed | `rg -n "react-native-webrtc" MobileApp/package.json` returned no matches; unblock by adding supported native WebRTC dependency and peer lifecycle code |
-| C35 | Update OpenAPI streaming contract | done | `Backend/docs/openapi.ts:740,786,832`; legacy credential/playback stream paths removed from OpenAPI | `bunx tsc --noEmit` exited 0 in `Backend/` | `rg -n "publish-credentials|subscribe-credentials|playback-token" Backend/docs/openapi.ts` returned no matches |
-| C36 | Update docs/comments to remove fallback as primary path | done | `Backend/README.md:133,147,191`, `MobileApp/README.md:75-79`, `Backend/public/backend-architecture.html:499-500`, `Backend/db/schema.ts:68-69` | `npm run check` in `WebApp/` passed; `bunx tsc --noEmit` in `Backend/` passed | `rg -n "stream:frame|frame relay|SIMPLE_STREAMING" Backend/README.md MobileApp/README.md Backend/public/backend-architecture.html docs/STREAMING_SIMPLIFICATION_ROLLOUT_AND_ROLLBACK.md` confirmed updated docs |
-| C37 | Add migration and deprecation guidance | done | `docs/STREAMING_SIMPLIFICATION_ROLLOUT_AND_ROLLBACK.md:11-19`, `Backend/README.md:147-149` | `bunx tsc --noEmit` exited 0 in `Backend/` | `rg -n "Migration notes|Safe enablement sequence" docs/STREAMING_SIMPLIFICATION_ROLLOUT_AND_ROLLBACK.md` returned matches at lines 11 and 19 |
-| C38 | Add structured stream lifecycle logging | done | `Backend/routes/streams.ts:171,230,359,719`, `Backend/realtime/gateway.ts:348` | `bun test` passed all 17 tests in `Backend/tests/*` | `bunx tsc --noEmit` exited 0 in `Backend/`; log markers present for request/accept/end/signal events |
-| C39 | Add compile/build checks after cleanup | done | Validation spans `Backend/`, `WebApp/`, and `MobileApp/` | `bun test` passed (17/17), `npm run check` passed, `npm run lint` passed | `bunx tsc --noEmit` in `Backend/` exited 0, `npm run build` in `WebApp/` passed, `npx tsc --noEmit` in `MobileApp/` exited 0 |
-| C40 | Add rollback runbook for flag behavior | done | `docs/STREAMING_SIMPLIFICATION_ROLLOUT_AND_ROLLBACK.md:35-43` | `bunx tsc --noEmit` exited 0 in `Backend/` | `rg -n "Rollback checklist|Known blocker" docs/STREAMING_SIMPLIFICATION_ROLLOUT_AND_ROLLBACK.md` returned matches at lines 35 and 43 |
diff --git a/docs/TEMP_SECTION_5_3_SNIPPETS.md b/docs/TEMP_SECTION_5_3_SNIPPETS.md
deleted file mode 100644
index f63c205..0000000
--- a/docs/TEMP_SECTION_5_3_SNIPPETS.md
+++ /dev/null
@@ -1,1206 +0,0 @@
-# Section 5.3 Temporary Code Snippets
-
-This file collects the main backend and web app snippets referenced in Section 5.3 so they can be screenshotted easily.
-
-Each snippet includes:
-- a short description of what it demonstrates
-- a source reference you can cite in the report
-- the code excerpt itself
-
----
-
-## Snippet 1: Backend Bootstrap and Route Mounting
-
-**What this shows:**  
-This snippet shows how the backend is assembled in one place. It configures CORS and security middleware, exposes OpenAPI docs, mounts Better Auth, registers the main route groups, and starts the realtime gateway plus background workers.
-
-**Source:** [Backend/index.ts](/home/matiss/Documents/Final%20Year%20Project/Backend/index.ts:28)
-
-```ts
-const app = express();
-const openApiDocument = buildOpenApiDocument();
-const trustedOrigins = process.env.BETTER_AUTH_TRUSTED_ORIGINS
-  ? process.env.BETTER_AUTH_TRUSTED_ORIGINS.split(',').map((origin) => origin.trim()).filter(Boolean)
-  : [];
-const corsMiddleware = cors({
-  origin: trustedOrigins.length > 0 ? trustedOrigins : true,
-  credentials: true,
-});
-
-app.get('/openapi.json', (_req, res) => {
-  res.json(openApiDocument);
-});
-
-app.use('/docs', swaggerUi.serve, swaggerUi.setup(openApiDocument));
-
-app.use(
-  helmet({
-    contentSecurityPolicy: {
-      directives: {
-        ...helmet.contentSecurityPolicy.getDefaultDirectives(),
-        "script-src": ["'self'", "'unsafe-inline'", "cdn.jsdelivr.net", "cdn.tailwindcss.com"],
-        "style-src": ["'self'", "'unsafe-inline'", "cdn.jsdelivr.net", "fonts.googleapis.com"],
-        "font-src": ["'self'", "fonts.gstatic.com"],
-        "connect-src": connectSrcDirectives,
-        "media-src": mediaSrcDirectives,
-        "img-src": ["'self'", "data:", "blob:"],
-      },
-    },
-  }),
-);
-app.use(corsMiddleware);
-app.all('/api/auth/*splat', corsMiddleware, toNodeHandler(auth));
-app.use(rateLimit({ keyPrefix: 'global', windowMs: 60_000, max: 400 }));
-app.use(requestContext);
-app.use(express.json());
-app.use('/sim', express.static('public'));
-app.use('/videos', videosRoutes);
-app.use('/admin', adminRoutes);
-app.use('/devices', rateLimit({ keyPrefix: 'devices', windowMs: 60_000, max: 120 }), devicesRoutes);
-app.use('/device-links', deviceLinksRoutes);
-app.use('/commands', rateLimit({ keyPrefix: 'commands', windowMs: 60_000, max: 120 }), commandsRoutes);
-app.use('/events', rateLimit({ keyPrefix: 'events', windowMs: 60_000, max: 120 }), eventsRoutes);
-app.use('/streams', rateLimit({ keyPrefix: 'streams', windowMs: 60_000, max: 120 }), streamsRoutes);
-app.use('/recordings', rateLimit({ keyPrefix: 'recordings', windowMs: 60_000, max: 120 }), recordingsRoutes);
-app.use('/push-notifications', pushNotificationsRoutes);
-app.use('/audit', auditRoutes);
-app.use('/ops', opsRoutes);
-
-const start = async () => {
-  try {
-    await ensureMinioBucket();
-  } catch (error) {
-    console.error('MinIO initialization failed', error);
-    process.exit(1);
-  }
-
-  setupRealtimeGateway(server);
-  startRecordingsWorker();
-  startPushWorker();
-
-  server.listen(port, () => {
-    console.log(`Server is running on port ${port}`);
-  });
-};
-```
-
----
-
-## Snippet 2: Better Auth Configuration
-
-**What this shows:**  
-This snippet shows how session-based user authentication is integrated with the project database through Better Auth and Drizzle.
-
-**Source:** [Backend/auth.ts](/home/matiss/Documents/Final%20Year%20Project/Backend/auth.ts:13)
-
-```ts
-export const auth = betterAuth({
-  database: drizzleAdapter(db, {
-    provider: 'pg',
-    schema: {
-      ...schema,
-      user: schema.users,
-      account: schema.accounts,
-      session: schema.sessions,
-      verification: schema.verifications,
-    },
-  }),
-  advanced: {
-    database: {
-      generateId: 'uuid',
-    },
-  },
-  emailAndPassword: {
-    enabled: true,
-    password: {
-      hash: async (password) => hashPassword(password),
-      verify: async ({ hash, password }) => verifyPassword(password, hash),
-    },
-  },
-  secret: getRequiredEnv('BETTER_AUTH_SECRET'),
-  baseURL: getBetterAuthBaseUrl(),
-  trustedOrigins,
-});
-```
-
----
-
-## Snippet 3: Core Database Schema
-
-**What this shows:**  
-This excerpt shows the main persistence model used by the system: devices, links between camera and client devices, live stream sessions, recordings, motion events, notifications, and audit logs.
-
-**Source:** [Backend/db/schema.ts](/home/matiss/Documents/Final%20Year%20Project/Backend/db/schema.ts:14)
-
-```ts
-export const devices = pgTable('devices', {
-  id: uuid('id').defaultRandom().primaryKey(),
-  userId: uuid('user_id').notNull().references(() => users.id),
-  name: varchar('name', { length: 255 }),
-  role: varchar('role', { length: 32 }).default('client').notNull(),
-  platform: varchar('platform', { length: 32 }),
-  appVersion: varchar('app_version', { length: 64 }),
-  pushToken: text('push_token'),
-  status: varchar('status', { length: 32 }).default('offline').notNull(),
-  isCamera: boolean('is_camera').default(false).notNull(),
-  lastSeenAt: timestamp('last_seen_at', { withTimezone: true }),
-  updatedAt: timestamp('updated_at', { withTimezone: true }).defaultNow().notNull(),
-  createdAt: timestamp('created_at', { withTimezone: true }).defaultNow().notNull(),
-});
-
-export const deviceLinks = pgTable(
-  'device_links',
-  {
-    id: uuid('id').defaultRandom().primaryKey(),
-    ownerUserId: uuid('owner_user_id').notNull().references(() => users.id),
-    cameraDeviceId: uuid('camera_device_id').notNull().references(() => devices.id),
-    clientDeviceId: uuid('client_device_id').notNull().references(() => devices.id),
-    status: varchar('status', { length: 32 }).default('active').notNull(),
-    createdAt: timestamp('created_at', { withTimezone: true }).defaultNow().notNull(),
-    updatedAt: timestamp('updated_at', { withTimezone: true }).defaultNow().notNull(),
-  },
-  (table) => ({
-    uniqueDevicePair: unique('device_links_camera_client_unique').on(table.cameraDeviceId, table.clientDeviceId),
-  }),
-);
-
-export const streamSessions = pgTable('stream_sessions', {
-  id: uuid('id').defaultRandom().primaryKey(),
-  ownerUserId: uuid('owner_user_id').notNull().references(() => users.id),
-  cameraDeviceId: uuid('camera_device_id').notNull().references(() => devices.id),
-  requesterDeviceId: uuid('requester_device_id').notNull().references(() => devices.id),
-  status: varchar('status', { length: 32 }).default('requested').notNull(),
-  reason: varchar('reason', { length: 32 }).default('on_demand').notNull(),
-  mediaProvider: varchar('media_provider', { length: 32 }).default('mock').notNull(),
-  mediaSessionId: varchar('media_session_id', { length: 255 }),
-  publishEndpoint: text('publish_endpoint'),
-  subscribeEndpoint: text('subscribe_endpoint'),
-  streamKey: varchar('stream_key', { length: 255 }),
-  startedAt: timestamp('started_at', { withTimezone: true }),
-  endedAt: timestamp('ended_at', { withTimezone: true }),
-  metadata: jsonb('metadata').$type<Record<string, unknown> | null>().default(null),
-  createdAt: timestamp('created_at', { withTimezone: true }).defaultNow().notNull(),
-  updatedAt: timestamp('updated_at', { withTimezone: true }).defaultNow().notNull(),
-});
-
-export const recordings = pgTable('recordings', {
-  id: uuid('id').defaultRandom().primaryKey(),
-  ownerUserId: uuid('owner_user_id').notNull().references(() => users.id),
-  streamSessionId: uuid('stream_session_id').references(() => streamSessions.id),
-  cameraDeviceId: uuid('camera_device_id').notNull().references(() => devices.id),
-  requesterDeviceId: uuid('requester_device_id').references(() => devices.id),
-  eventId: uuid('event_id').references(() => events.id),
-  objectKey: varchar('object_key', { length: 1024 }),
-  bucket: varchar('bucket', { length: 255 }),
-  durationSeconds: integer('duration_seconds'),
-  sizeBytes: integer('size_bytes'),
-  status: varchar('status', { length: 32 }).default('awaiting_upload').notNull(),
-  availableAt: timestamp('available_at', { withTimezone: true }),
-  error: text('error'),
-  createdAt: timestamp('created_at', { withTimezone: true }).defaultNow().notNull(),
-  updatedAt: timestamp('updated_at', { withTimezone: true }).defaultNow().notNull(),
-});
-
-export const events = pgTable('events', {
-  id: uuid('id').defaultRandom().primaryKey(),
-  userId: uuid('user_id').notNull().references(() => users.id),
-  deviceId: uuid('device_id').references(() => devices.id),
-  title: varchar('title', { length: 255 }),
-  triggeredBy: varchar('triggered_by', { length: 64 }).default('motion'),
-  status: varchar('status', { length: 32 }).default('recording').notNull(),
-  startedAt: timestamp('started_at', { withTimezone: true }).notNull(),
-  endedAt: timestamp('ended_at', { withTimezone: true }),
-  notifiedAt: timestamp('notified_at', { withTimezone: true }),
-  videoUrl: varchar('video_url', { length: 1024 }).unique(),
-  createdAt: timestamp('created_at', { withTimezone: true }).defaultNow().notNull(),
-  updatedAt: timestamp('updated_at', { withTimezone: true }).defaultNow().notNull(),
-});
-
-export const notifications = pgTable('notifications', {
-  id: uuid('id').defaultRandom().primaryKey(),
-  eventId: uuid('event_id').references(() => events.id).notNull(),
-  userId: uuid('user_id').references(() => users.id).notNull(),
-  sentAt: timestamp('sent_at', { withTimezone: true }).defaultNow().notNull(),
-  channel: varchar('channel', { length: 32 }).notNull(),
-  status: varchar('status', { length: 32 }).default('queued').notNull(),
-  isRead: boolean('is_read').default(false).notNull(),
-});
-
-export const notificationDeliveries = pgTable('notification_deliveries', {
-  id: uuid('id').defaultRandom().primaryKey(),
-  ownerUserId: uuid('owner_user_id').notNull().references(() => users.id),
-  recipientDeviceId: uuid('recipient_device_id').notNull().references(() => devices.id),
-  type: varchar('type', { length: 64 }).notNull(),
-  payload: jsonb('payload').$type<Record<string, unknown> | null>().default(null),
-  status: varchar('status', { length: 32 }).default('queued').notNull(),
-  attempts: integer('attempts').default(0).notNull(),
-  lastError: text('last_error'),
-  sentAt: timestamp('sent_at', { withTimezone: true }),
-  nextAttemptAt: timestamp('next_attempt_at', { withTimezone: true }).defaultNow().notNull(),
-  createdAt: timestamp('created_at', { withTimezone: true }).defaultNow().notNull(),
-  updatedAt: timestamp('updated_at', { withTimezone: true }).defaultNow().notNull(),
-});
-
-export const auditLogs = pgTable('audit_logs', {
-  id: uuid('id').defaultRandom().primaryKey(),
-  ownerUserId: uuid('owner_user_id').notNull().references(() => users.id),
-  actorDeviceId: uuid('actor_device_id').references(() => devices.id),
-  action: varchar('action', { length: 128 }).notNull(),
-  targetType: varchar('target_type', { length: 64 }).notNull(),
-  targetId: varchar('target_id', { length: 255 }).notNull(),
-  metadata: jsonb('metadata').$type<Record<string, unknown> | null>().default(null),
-  ipAddress: text('ip_address'),
-  createdAt: timestamp('created_at', { withTimezone: true }).defaultNow().notNull(),
-});
-```
-
----
-
-## Snippet 4: Device Registration and Token Issuance
-
-**What this shows:**  
-This route creates a device record, automatically links it to opposite-role devices under the same account, and returns a signed device token used for device-level authentication.
-
-**Source:** [Backend/routes/devices.ts](/home/matiss/Documents/Final%20Year%20Project/Backend/routes/devices.ts:41)
-
-```ts
-router.post('/register', requireAuth, async (req, res) => {
-  const parsed = registerSchema.safeParse(req.body);
-
-  if (!parsed.success) {
-    res.status(400).json({ message: 'Invalid request body', errors: parsed.error.flatten() });
-    return;
-  }
-
-  const authSession = req.auth;
-
-  if (!authSession?.user?.id) {
-    res.status(401).json({ message: 'Unauthorized' });
-    return;
-  }
-
-  const now = new Date();
-  const [device] = await db
-    .insert(devices)
-    .values({
-      userId: authSession.user.id,
-      name: parsed.data.name,
-      role: parsed.data.role,
-      isCamera: parsed.data.role === 'camera',
-      platform: parsed.data.platform,
-      appVersion: parsed.data.appVersion,
-      pushToken: parsed.data.pushToken,
-      status: 'online',
-      lastSeenAt: now,
-      updatedAt: now,
-    })
-    .returning({
-      id: devices.id,
-      userId: devices.userId,
-      name: devices.name,
-      role: devices.role,
-      status: devices.status,
-      platform: devices.platform,
-      appVersion: devices.appVersion,
-      lastSeenAt: devices.lastSeenAt,
-      createdAt: devices.createdAt,
-      updatedAt: devices.updatedAt,
-    });
-
-  if (!device) {
-    res.status(500).json({ message: 'Unable to register device' });
-    return;
-  }
-
-  const oppositeRole = device.role === 'camera' ? 'client' : 'camera';
-  const oppositeDevices = await db.query.devices.findMany({
-    where: and(eq(devices.userId, device.userId), eq(devices.role, oppositeRole)),
-  });
-
-  if (oppositeDevices.length > 0) {
-    const linksToCreate = oppositeDevices.map((otherDevice) => ({
-      ownerUserId: device.userId,
-      cameraDeviceId: device.role === 'camera' ? device.id : otherDevice.id,
-      clientDeviceId: device.role === 'client' ? device.id : otherDevice.id,
-      status: 'active' as const,
-    }));
-
-    await db.insert(deviceLinks).values(linksToCreate).onConflictDoNothing();
-  }
-
-  const deviceToken = createDeviceToken({
-    userId: device.userId,
-    deviceId: device.id,
-    role: device.role as 'camera' | 'client',
-  });
-
-  res.status(201).json({
-    message: 'Device registered',
-    device,
-    deviceToken,
-  });
-});
-```
-
----
-
-## Snippet 5: Stream Request Lifecycle
-
-**What this shows:**  
-This route validates the client device, confirms the target is a linked camera, inserts a `stream_sessions` row, and emits a realtime `stream:requested` event in simplified mode.
-
-**Source:** [Backend/routes/streams.ts](/home/matiss/Documents/Final%20Year%20Project/Backend/routes/streams.ts:97)
-
-```ts
-router.post('/request', requireDeviceAuth, async (req, res) => {
-  const parsed = requestStreamSchema.safeParse(req.body ?? {});
-
-  if (!parsed.success) {
-    res.status(400).json({ message: 'Invalid request body', errors: parsed.error.flatten() });
-    return;
-  }
-
-  const deviceAuth = ensureDeviceAuth(req, res);
-  if (!deviceAuth) return;
-
-  const [sourceDevice, cameraDevice] = await Promise.all([
-    db.query.devices.findFirst({
-      where: and(eq(devices.id, deviceAuth.deviceId), eq(devices.userId, deviceAuth.userId)),
-    }),
-    db.query.devices.findFirst({
-      where: and(eq(devices.id, parsed.data.cameraDeviceId), eq(devices.userId, deviceAuth.userId)),
-    }),
-  ]);
-
-  if (!sourceDevice || !cameraDevice) {
-    res.status(404).json({ message: 'Source or camera device not found' });
-    return;
-  }
-
-  if (sourceDevice.role !== 'client') {
-    res.status(403).json({ message: 'Only client devices can request on-demand stream sessions' });
-    return;
-  }
-
-  if (cameraDevice.role !== 'camera') {
-    res.status(400).json({ message: 'cameraDeviceId must point to a camera device' });
-    return;
-  }
-
-  const link = await db.query.deviceLinks.findFirst({
-    where: and(
-      eq(deviceLinks.ownerUserId, deviceAuth.userId),
-      eq(deviceLinks.cameraDeviceId, cameraDevice.id),
-      eq(deviceLinks.clientDeviceId, sourceDevice.id),
-      eq(deviceLinks.status, 'active'),
-    ),
-  });
-
-  if (!link) {
-    res.status(403).json({ message: 'No active link between requester and camera' });
-    return;
-  }
-
-  const now = new Date();
-
-  const [session] = await db
-    .insert(streamSessions)
-    .values({
-      ownerUserId: deviceAuth.userId,
-      cameraDeviceId: cameraDevice.id,
-      requesterDeviceId: sourceDevice.id,
-      status: 'requested',
-      reason: parsed.data.reason,
-      metadata: parsed.data.metadata ?? null,
-      mediaProvider: mediaProvider.name,
-      updatedAt: now,
-    })
-    .returning();
-
-  if (!session) {
-    res.status(500).json({ message: 'Failed creating stream session' });
-    return;
-  }
-
-  if (simpleStreamingEnabled) {
-    const requestPayload = createStreamRequestedPayload(session);
-    const deliveredToCamera = sendRealtimeToDevice(cameraDevice.id, 'stream:requested', requestPayload);
-
-    console.info('[stream.request]', {
-      streamSessionId: session.id,
-      requesterDeviceId: sourceDevice.id,
-      cameraDeviceId: cameraDevice.id,
-      mode: 'simple',
-    });
-
-    sendRealtimeToDevice(sourceDevice.id, 'stream:requested', requestPayload);
-
-    if (!deliveredToCamera) {
-      await enqueuePushNotification({
-        ownerUserId: cameraDevice.userId,
-        recipientDeviceId: cameraDevice.id,
-        type: 'stream_requested',
-        payload: requestPayload,
-      });
-    }
-
-    res.status(201).json({
-      message: 'Stream request sent',
-      streamSession: toSimpleStreamSessionResponse(session),
-    });
-
-    await writeAuditLog({
-      ownerUserId: sourceDevice.userId,
-      actorDeviceId: sourceDevice.id,
-      action: 'stream.requested',
-      targetType: 'stream_session',
-      targetId: session.id,
-      metadata: { cameraDeviceId: cameraDevice.id, reason: session.reason, transport: 'webrtc' },
-      ipAddress: req.ip,
-    });
-    return;
-  }
-```
-
----
-
-## Snippet 6: Stream Accept Lifecycle
-
-**What this shows:**  
-This route moves a stream session from `requested` to `streaming`, records start metadata, optionally initializes SFU state, and emits `stream:started` to the viewer.
-
-**Source:** [Backend/routes/streams.ts](/home/matiss/Documents/Final%20Year%20Project/Backend/routes/streams.ts:276)
-
-```ts
-router.post('/:streamSessionId/accept', requireDeviceAuth, async (req, res) => {
-  const parsedParams = streamParamSchema.safeParse(req.params);
-
-  if (!parsedParams.success) {
-    res.status(400).json({ message: 'Invalid streamSessionId', errors: parsedParams.error.flatten() });
-    return;
-  }
-
-  const parsed = acceptStreamSchema.safeParse(req.body ?? {});
-
-  if (!parsed.success) {
-    res.status(400).json({ message: 'Invalid request body', errors: parsed.error.flatten() });
-    return;
-  }
-
-  const deviceAuth = ensureDeviceAuth(req, res);
-  if (!deviceAuth) return;
-
-  const session = await db.query.streamSessions.findFirst({
-    where: and(
-      eq(streamSessions.id, parsedParams.data.streamSessionId),
-      eq(streamSessions.ownerUserId, deviceAuth.userId),
-      eq(streamSessions.cameraDeviceId, deviceAuth.deviceId),
-    ),
-  });
-
-  if (!session) {
-    res.status(404).json({ message: 'Stream session not found for this camera device' });
-    return;
-  }
-
-  if (session.status !== 'requested' && session.status !== 'starting') {
-    res.status(409).json({ message: `Stream session cannot be accepted from status ${session.status}` });
-    return;
-  }
-
-  const now = new Date();
-  const streamKey = parsed.data.streamKey ?? `stream_${session.id}_${randomUUID()}`;
-  const mediaSession = await createLiveMediaSession({
-    streamSessionId: session.id,
-    ownerUserId: session.ownerUserId,
-    cameraDeviceId: session.cameraDeviceId,
-    requesterDeviceId: session.requesterDeviceId,
-  });
-
-  const [updated] = await db
-    .update(streamSessions)
-    .set({
-      status: 'streaming',
-      streamKey: mediaSession ? streamKey : null,
-      mediaProvider: mediaSession?.provider ?? 'simple',
-      mediaSessionId: mediaSession?.mediaSessionId ?? null,
-      publishEndpoint: mediaSession?.publishUrl ?? null,
-      subscribeEndpoint: mediaSession?.subscribeUrl ?? null,
-      metadata: parsed.data.metadata ?? session.metadata,
-      startedAt: now,
-      updatedAt: now,
-    })
-    .where(eq(streamSessions.id, session.id))
-    .returning();
-
-  if (!updated) {
-    res.status(500).json({ message: 'Failed to update stream session' });
-    return;
-  }
-
-  if (sfuService) {
-    try {
-      await sfuService.startSession({
-        streamSessionId: updated.id,
-        ownerUserId: updated.ownerUserId,
-        cameraDeviceId: updated.cameraDeviceId,
-        requesterDeviceId: updated.requesterDeviceId,
-      });
-      await sfuService.setSessionState(updated.id, 'live');
-    } catch (error) {
-      console.error('Failed starting SFU session', error);
-      res.status(500).json({ message: 'Failed to initialize SFU session' });
-      return;
-    }
-  }
-
-  const startedPayload = createStreamStartedPayload(updated);
-  console.info('[stream.accept]', {
-    streamSessionId: updated.id,
-    requesterDeviceId: updated.requesterDeviceId,
-    cameraDeviceId: updated.cameraDeviceId,
-    mode: mediaSession ? 'legacy' : 'simple',
-  });
-  const deliveredToRequester = sendRealtimeToDevice(session.requesterDeviceId, 'stream:started', startedPayload);
-
-  if (!deliveredToRequester) {
-    await enqueuePushNotification({
-      ownerUserId: session.ownerUserId,
-      recipientDeviceId: session.requesterDeviceId,
-      type: 'stream_started',
-      payload: startedPayload,
-    });
-  }
-
-  res.json({ message: 'Stream accepted', streamSession: toSimpleStreamSessionResponse(updated) });
-
-  await writeAuditLog({
-    ownerUserId: session.ownerUserId,
-    actorDeviceId: session.cameraDeviceId,
-    action: 'stream.accepted',
-    targetType: 'stream_session',
-    targetId: session.id,
-    metadata: mediaSession
-      ? { mediaSessionId: updated.mediaSessionId, mediaProvider: updated.mediaProvider }
-      : { transport: 'webrtc' },
-    ipAddress: req.ip,
-  });
-});
-```
-
----
-
-## Snippet 7: WebRTC Signal Relay
-
-**What this shows:**  
-This Socket.IO handler validates each signal packet against the owning account and active stream session before relaying SDP or ICE data to the target device room.
-
-**Source:** [Backend/realtime/gateway.ts](/home/matiss/Documents/Final%20Year%20Project/Backend/realtime/gateway.ts:323)
-
-```ts
-socket.on('webrtc:signal', async (input) => {
-  const parsed = webrtcSignalSchema.safeParse(input);
-
-  if (!parsed.success) {
-    socket.emit('error:webrtc_signal', {
-      message: 'Invalid WebRTC signal payload',
-      errors: parsed.error.flatten(),
-    });
-    return;
-  }
-
-  const session = await db.query.streamSessions.findFirst({
-    where: and(eq(streamSessions.id, parsed.data.streamSessionId), eq(streamSessions.ownerUserId, auth.userId)),
-  });
-
-  if (!session) {
-    socket.emit('error:webrtc_signal', { message: 'Stream session not found for this account' });
-    return;
-  }
-
-  if (!canRelayWebrtcSignal(session, auth.deviceId, parsed.data.toDeviceId)) {
-    socket.emit('error:webrtc_signal', { message: 'Signal target is not a participant in this stream session' });
-    return;
-  }
-
-  console.info('[stream.signal]', {
-    streamSessionId: parsed.data.streamSessionId,
-    fromDeviceId: auth.deviceId,
-    toDeviceId: parsed.data.toDeviceId,
-    signalType: parsed.data.signalType,
-  });
-
-  io?.to(roomForDevice(parsed.data.toDeviceId)).emit('webrtc:signal', {
-    fromDeviceId: auth.deviceId,
-    streamSessionId: parsed.data.streamSessionId,
-    signalType: parsed.data.signalType,
-    data: parsed.data.data ?? null,
-  });
-});
-```
-
----
-
-## Snippet 8: Motion Event Creation and Fan-Out
-
-**What this shows:**  
-This route creates a motion event, looks up all active client links for the camera, attempts realtime delivery, and falls back to queued push delivery when the client is offline.
-
-**Source:** [Backend/routes/events.ts](/home/matiss/Documents/Final%20Year%20Project/Backend/routes/events.ts:35)
-
-```ts
-router.post('/motion/start', requireDeviceAuth, async (req, res) => {
-  const parsed = startMotionSchema.safeParse(req.body ?? {});
-
-  if (!parsed.success) {
-    res.status(400).json({ message: 'Invalid request body', errors: parsed.error.flatten() });
-    return;
-  }
-
-  const deviceAuth = req.deviceAuth;
-
-  if (!deviceAuth) {
-    res.status(401).json({ message: 'Unauthorized' });
-    return;
-  }
-
-  const cameraDevice = await db.query.devices.findFirst({
-    where: and(eq(devices.id, deviceAuth.deviceId), eq(devices.userId, deviceAuth.userId)),
-  });
-
-  if (!cameraDevice) {
-    res.status(404).json({ message: 'Device not found' });
-    return;
-  }
-
-  if (cameraDevice.role !== 'camera') {
-    res.status(403).json({ message: 'Only camera devices can start motion events' });
-    return;
-  }
-
-  const now = new Date();
-
-  const [event] = await db
-    .insert(events)
-    .values({
-      userId: deviceAuth.userId,
-      deviceId: cameraDevice.id,
-      title: parsed.data.title,
-      triggeredBy: parsed.data.triggeredBy,
-      status: 'recording',
-      startedAt: now,
-      videoUrl: parsed.data.videoUrl,
-      updatedAt: now,
-    })
-    .returning();
-
-  if (!event) {
-    res.status(500).json({ message: 'Failed to create motion event' });
-    return;
-  }
-
-  const activeLinks = await db.query.deviceLinks.findMany({
-    where: and(
-      eq(deviceLinks.ownerUserId, deviceAuth.userId),
-      eq(deviceLinks.cameraDeviceId, cameraDevice.id),
-      eq(deviceLinks.status, 'active'),
-    ),
-  });
-
-  for (const link of activeLinks) {
-    const delivered = sendRealtimeToDevice(link.clientDeviceId, 'motion:detected', {
-      eventId: event.id,
-      cameraDeviceId: cameraDevice.id,
-      title: event.title,
-      triggeredBy: event.triggeredBy,
-      startedAt: event.startedAt,
-    });
-
-    await db.insert(notifications).values({
-      eventId: event.id,
-      userId: deviceAuth.userId,
-      channel: delivered ? 'realtime' : 'queued',
-      status: delivered ? 'delivered' : 'queued',
-      isRead: false,
-      sentAt: now,
-    });
-
-    if (delivered) {
-      await db.insert(notificationDeliveries).values({
-        ownerUserId: deviceAuth.userId,
-        recipientDeviceId: link.clientDeviceId,
-        type: 'motion_detected',
-        payload: {
-          eventId: event.id,
-          cameraDeviceId: cameraDevice.id,
-          startedAt: event.startedAt.toISOString(),
-        },
-        status: 'delivered',
-        attempts: 1,
-        sentAt: now,
-        nextAttemptAt: now,
-        updatedAt: now,
-      });
-    } else {
-      await enqueuePushNotification({
-        ownerUserId: deviceAuth.userId,
-        recipientDeviceId: link.clientDeviceId,
-        type: 'motion_detected',
-        payload: {
-          eventId: event.id,
-          cameraDeviceId: cameraDevice.id,
-          startedAt: event.startedAt.toISOString(),
-        },
-      });
-    }
-  }
-});
-```
-
----
-
-## Snippet 9: Recording Finalization and Download URL Issuance
-
-**What this shows:**  
-This backend code finalizes a recording after upload, marks it ready in the database, and later issues a presigned MinIO download URL to the viewer.
-
-**Source:** [Backend/routes/recordings.ts](/home/matiss/Documents/Final%20Year%20Project/Backend/routes/recordings.ts:64)
-
-```ts
-router.post('/:recordingId/finalize', requireDeviceAuth, async (req, res) => {
-  const parsedParams = recordingParamSchema.safeParse(req.params);
-
-  if (!parsedParams.success) {
-    res.status(400).json({ message: 'Invalid recordingId', errors: parsedParams.error.flatten() });
-    return;
-  }
-
-  const parsed = finalizeSchema.safeParse(req.body ?? {});
-
-  if (!parsed.success) {
-    res.status(400).json({ message: 'Invalid request body', errors: parsed.error.flatten() });
-    return;
-  }
-
-  const deviceAuth = req.deviceAuth;
-
-  if (!deviceAuth) {
-    res.status(401).json({ message: 'Unauthorized' });
-    return;
-  }
-
-  const recording = await db.query.recordings.findFirst({
-    where: and(eq(recordings.id, parsedParams.data.recordingId), eq(recordings.ownerUserId, deviceAuth.userId)),
-  });
-
-  if (!recording) {
-    res.status(404).json({ message: 'Recording not found' });
-    return;
-  }
-
-  if (recording.cameraDeviceId !== deviceAuth.deviceId) {
-    res.status(403).json({ message: 'Only camera device can finalize this recording' });
-    return;
-  }
-
-  const now = new Date();
-  const bucket = parsed.data.bucket;
-  const objectKey = parsed.data.objectKey;
-
-  await ensureMinioBucket();
-
-  try {
-    await minioClient.statObject(bucket, objectKey);
-  } catch (error) {
-    if (objectKey.startsWith('sim/')) {
-      const placeholder = Buffer.from(
-        JSON.stringify({
-          message: 'simulated recording placeholder',
-          recordingId: recording.id,
-          streamSessionId: recording.streamSessionId,
-          createdAt: now.toISOString(),
-        }),
-        'utf8',
-      );
-
-      await minioClient.putObject(bucket, objectKey, placeholder, placeholder.byteLength, {
-        'Content-Type': 'application/json',
-      });
-    } else if (isMissingStorageObjectError(error)) {
-      res.status(409).json({ message: 'Recording object does not exist in storage yet' });
-      return;
-    } else {
-      throw error;
-    }
-  }
-
-  const [updated] = await db
-    .update(recordings)
-    .set({
-      objectKey,
-      bucket,
-      durationSeconds: parsed.data.durationSeconds,
-      sizeBytes: parsed.data.sizeBytes,
-      status: 'ready',
-      availableAt: now,
-      updatedAt: now,
-      error: null,
-    })
-    .where(eq(recordings.id, recording.id))
-    .returning();
-
-  res.json({ message: 'Recording finalized', recording: updated });
-
-  await writeAuditLog({
-    ownerUserId: recording.ownerUserId,
-    actorDeviceId: recording.cameraDeviceId,
-    action: 'recording.finalized',
-    targetType: 'recording',
-    targetId: recording.id,
-    metadata: { objectKey: parsed.data.objectKey, bucket: parsed.data.bucket },
-    ipAddress: req.ip,
-  });
-});
-
-router.get('/:recordingId/download-url', requireDeviceAuth, async (req, res) => {
-  const parsedParams = recordingParamSchema.safeParse(req.params);
-
-  if (!parsedParams.success) {
-    res.status(400).json({ message: 'Invalid recordingId', errors: parsedParams.error.flatten() });
-    return;
-  }
-
-  const deviceAuth = req.deviceAuth;
-
-  if (!deviceAuth) {
-    res.status(401).json({ message: 'Unauthorized' });
-    return;
-  }
-
-  const recording = await db.query.recordings.findFirst({
-    where: and(eq(recordings.id, parsedParams.data.recordingId), eq(recordings.ownerUserId, deviceAuth.userId)),
-  });
-
-  if (!recording) {
-    res.status(404).json({ message: 'Recording not found' });
-    return;
-  }
-
-  if (recording.status !== 'ready' || !recording.objectKey || !recording.bucket) {
-    res.status(409).json({ message: 'Recording is not available yet' });
-    return;
-  }
-
-  try {
-    await minioClient.statObject(recording.bucket, recording.objectKey);
-  } catch (error) {
-    if (isMissingStorageObjectError(error)) {
-      res.status(409).json({ message: 'Recording file is missing from storage' });
-      return;
-    }
-
-    throw error;
-  }
-
-  const downloadUrl = await minioClient.presignedGetObject(
-    recording.bucket,
-    recording.objectKey,
-    minioPresignedExpirySeconds,
-  );
-
-  res.json({
-    recordingId: recording.id,
-    objectKey: recording.objectKey,
-    bucket: recording.bucket,
-    downloadUrl,
-    expiresInSeconds: minioPresignedExpirySeconds,
-  });
-});
-```
-
----
-
-## Snippet 10: Web App State Model
-
-**What this shows:**  
-This is the client-side state shape for the browser app. It tracks authentication, registered device identity, live stream state, motion activity, notifications, and UI modal state.
-
-**Source:** [WebApp/src/lib/app/store.js](/home/matiss/Documents/Final%20Year%20Project/WebApp/src/lib/app/store.js:5)
-
-```js
-export const createInitialState = () => ({
-	page: 'auth',
-	session: null,
-	device: null,
-	deviceToken: null,
-	socketConnected: false,
-	isMotionActive: false,
-	activeMotionSource: null,
-	cameraStatus: 'idle',
-	cameraPreviewReady: false,
-	cameraInputDevices: [],
-	selectedCameraInputId: '',
-	linkedCameras: [],
-	recordings: [],
-	motionNotifications: [],
-	activeCameraDeviceId: null,
-	activeStreamSessionId: null,
-	openLinkedCameraMenuId: null,
-	activityLog: [],
-	cameraSessions: {},
-	connectedStreamSessionIds: [],
-	loading: true,
-	isRegistering: false,
-	authForm: {
-		email: '',
-		password: '',
-		name: ''
-	},
-	onboardingForm: {
-		name: '',
-		role: 'client',
-		pushToken: ''
-	},
-	toasts: [],
-	recordingModal: {
-		open: false,
-		title: 'Recording Playback',
-		url: ''
-	},
-	motionDetection: {
-		enabled: false,
-		profile: 'balanced',
-		state: 'idle',
-		score: 0,
-		debug: false,
-		lastTriggeredAt: null
-	},
-	clientStreamMode: 'none',
-	clientPlaceholderText: 'Select a camera to view',
-	lastError: null
-});
-```
-
----
-
-## Snippet 11: WebRTC Offer Creation in the Web App
-
-**What this shows:**  
-This frontend controller method creates an SDP offer on the camera side and sends it through the backend Socket.IO relay to the client device.
-
-**Source:** [WebApp/src/lib/app/controller.js](/home/matiss/Documents/Final%20Year%20Project/WebApp/src/lib/app/controller.js:1159)
-
-```js
-const startOfferToClient = async (streamSessionId, requesterDeviceId) => {
-	if (!socket) return;
-
-	const connection = await ensurePeerConnection({
-		streamSessionId,
-		targetDeviceId: requesterDeviceId,
-		asCamera: true
-	});
-
-	const offer = await connection.createOffer();
-	await connection.setLocalDescription(offer);
-	socket.emit('webrtc:signal', {
-		toDeviceId: requesterDeviceId,
-		streamSessionId,
-		signalType: 'offer',
-		data: offer
-	});
-};
-```
-
----
-
-## Snippet 12: Recording Finalization from the Web App
-
-**What this shows:**  
-This frontend code polls for the `awaiting_upload` recording row, uploads the locally captured WebM file to object storage, and then calls the backend finalize endpoint.
-
-**Source:** [WebApp/src/lib/app/controller.js](/home/matiss/Documents/Final%20Year%20Project/WebApp/src/lib/app/controller.js:1178)
-
-```js
-const sleep = (ms) => new Promise((resolve) => setTimeout(resolve, ms));
-
-const finalizeRecordingForStream = async (streamSessionId, captureResult) => {
-	const currentDevice = getAppState().device;
-	if (!currentDevice?.id) {
-		addActivity('Recording', 'No device identity for finalize');
-		return false;
-	}
-
-	for (let attempt = 0; attempt < 8; attempt += 1) {
-		const recs = await api.ops.listRecordings().catch(() => ({ recordings: [] }));
-		const recording = (recs.recordings || []).find(
-			(rec) => rec.streamSessionId === streamSessionId && rec.status === 'awaiting_upload'
-		);
-
-		if (recording?.id) {
-			try {
-				if (!captureResult?.blob || captureResult.blob.size === 0) {
-					throw new Error('No captured video blob to upload');
-				}
-				const compressedBlob = await compressRecordingBlob(captureResult.blob);
-
-				const uploadMeta = await api.request('/videos/upload-url', {
-					method: 'POST',
-					body: JSON.stringify({
-						fileName: `stream-${streamSessionId}.webm`,
-						deviceId: currentDevice.id,
-						prefix: 'recordings',
-						recordingId: recording.id
-					})
-				});
-
-				const uploadResponse = await fetch(uploadMeta.uploadUrl, {
-					method: 'PUT',
-					headers: { 'Content-Type': compressedBlob.type || 'video/webm' },
-					body: compressedBlob
-				});
-
-				if (!uploadResponse.ok) {
-					throw new Error(`Upload failed with status ${uploadResponse.status}`);
-				}
-
-				await api.events.finalizeRecording(recording.id, {
-					objectKey: uploadMeta.objectKey,
-					bucket: uploadMeta.bucket,
-					durationSeconds: captureResult.durationSeconds,
-					sizeBytes: compressedBlob.size
-				});
-
-				addActivity('Recording', 'Recording uploaded and finalized');
-				return true;
-			} catch (error) {
-				console.error('Recording upload failed, falling back to simulated key', error);
-				const fallbackObjectKey = `sim/${streamSessionId}/${Date.now()}.webm`;
-				await api.events.finalizeRecording(recording.id, {
-					objectKey: fallbackObjectKey,
-					durationSeconds: captureResult?.durationSeconds ?? 15,
-					sizeBytes: captureResult?.blob?.size ?? 5000000
-				});
-				addActivity('Recording', 'Upload failed; finalized with simulator fallback');
-				return true;
-			}
-		}
-
-		await sleep(350);
-	}
-
-	addActivity('Recording', 'No recording row found to finalize');
-	return false;
-};
-```
-
----
-
-## Snippet 13: Motion Event Lifecycle in the Web App
-
-**What this shows:**  
-This controller code starts a motion event, begins local recording, and later ends the motion event while either closing a stream or uploading a standalone motion clip.
-
-**Source:** [WebApp/src/lib/app/controller.js](/home/matiss/Documents/Final%20Year%20Project/WebApp/src/lib/app/controller.js:1299)
-
-```js
-const getMotionStartPayload = (source = 'manual') =>
-	source === 'auto'
-		? { title: 'Automatic Motion', triggeredBy: 'auto_motion' }
-		: { title: 'Simulated Motion', triggeredBy: 'motion' };
-
-const startMotionEvent = async ({ source = 'manual' } = {}) => {
-	if (getAppState().isMotionActive || lastMotionEventId) {
-		return false;
-	}
-
-	const response = await api.events.startMotion(getMotionStartPayload(source));
-	await startCameraPreview();
-	await startLocalRecording();
-	lastMotionEventId = response.event.id;
-
-	const startedAt = new Date().toISOString();
-	setAppState({
-		isMotionActive: true,
-		activeMotionSource: source
-	});
-
-	if (source === 'auto') {
-		updateMotionDetectionRuntime({ lastTriggeredAt: startedAt });
-	}
-
-	pushToast(source === 'auto' ? 'Automatic motion event started' : 'Motion Event Started', 'success');
-	addActivity(
-		'Motion',
-		source === 'auto' ? `Automatic motion event started (${response.event.id})` : `Started event ${response.event.id}`
-	);
-	return true;
-};
-
-const endMotionEvent = async ({ source = 'manual' } = {}) => {
-	if (!lastMotionEventId) {
-		return false;
-	}
-
-	const eventId = lastMotionEventId;
-	const streamSessionId = activeRecordingStreamSessionId;
-
-	if (streamSessionId) {
-		await api.streams.end(streamSessionId);
-		addActivity('Stream', `Ended stream ${streamSessionId}`);
-	} else if (activeMediaRecorder?.state === 'recording') {
-		const captureResult = await stopLocalRecording();
-		await uploadStandaloneMotionRecording(captureResult);
-	}
-
-	await api.events.endMotion(eventId);
-	lastMotionEventId = null;
-	setAppState({
-		isMotionActive: false,
-		activeMotionSource: null
-	});
-
-	pushToast(source === 'auto' ? 'Automatic motion event ended' : 'Motion Ended', 'success');
-	addActivity(
-		'Motion',
-		source === 'auto' ? `Automatic motion event ended (${eventId})` : `Ended event ${eventId}`
-	);
-	return true;
-};
-
-const syncAutoMotionLifecycle = async ({ activeMotion }) => {
-	if (autoMotionTransitionInFlight) {
-		return;
-	}
-
-	if (activeMotion) {
-		if (getAppState().isMotionActive || lastMotionEventId) {
-			return;
-		}
-
-		autoMotionTransitionInFlight = true;
-		try {
-			await startMotionEvent({ source: 'auto' });
-		} catch (error) {
-			console.error('Failed to auto-start motion event', error);
-			pushToast(error.message || 'Failed to start automatic motion event', 'error');
-		} finally {
-			autoMotionTransitionInFlight = false;
-		}
-		return;
-	}
-
-	if (!isAutoMotionEventActive()) {
-		return;
-	}
-
-	autoMotionTransitionInFlight = true;
-	try {
-		await endMotionEvent({ source: 'auto' });
-	} catch (error) {
-		console.error('Failed to auto-end motion event', error);
-		pushToast(error.message || 'Failed to end automatic motion event', 'error');
-	} finally {
-		autoMotionTransitionInFlight = false;
-	}
-};
-```
diff --git a/docs/architecture-diagram.md b/docs/architecture-diagram.md
deleted file mode 100644
index c96c3b7..0000000
--- a/docs/architecture-diagram.md
+++ /dev/null
@@ -1,48 +0,0 @@
-# SecureCam codebase architecture
-
-```mermaid
-flowchart LR
-  CAMERA["Camera device
-  Mobile camera app / browser simulator"]:::client
-
-  USER["User devices
-  Web app / mobile app"]:::client
-
-  subgraph PLATFORM["SecureCam platform"]
-    BACKEND["Backend service
-    • authentication
-    • device coordination
-    • live stream control
-    • motion events
-    • recordings access"]:::backend
-  end
-
-  DATA["Core data layer
-  PostgreSQL"]:::data
-
-  MEDIA["Media storage
-  MinIO / S3-compatible object storage"]:::data
-
-  NOTIFY["Notifications
-  push + in-app activity updates"]:::service
-
-  CAMERA -->|"motion, stream, recordings"| BACKEND
-  USER -->|"auth, viewing, control"| BACKEND
-
-  BACKEND -->|"app state, users, devices, events"| DATA
-  BACKEND -->|"video and recording assets"| MEDIA
-  BACKEND -->|"alerts and activity fan-out"| NOTIFY
-
-  NOTIFY --> USER
-
-  classDef client fill:#e8f1ff,stroke:#3b82f6,stroke-width:2px,color:#111827;
-  classDef backend fill:#ecfdf3,stroke:#16a34a,stroke-width:2px,color:#111827;
-  classDef data fill:#fff7e8,stroke:#f59e0b,stroke-width:2px,color:#111827;
-  classDef service fill:#f3e8ff,stroke:#9333ea,stroke-width:2px,color:#111827;
-```
-
-## Notes
-
-- This version is intentionally high level.
-- It treats the web app, mobile app, and simulator as client surfaces around one backend platform.
-- Internal backend modules such as routes, workers, realtime gateway, and media scaffolding are abstracted into a single service block.
diff --git a/docs/database-schema-diagram.md b/docs/database-schema-diagram.md
deleted file mode 100644
index 02671e7..0000000
--- a/docs/database-schema-diagram.md
+++ /dev/null
@@ -1,218 +0,0 @@
-# SecureCam database schema
-
-```mermaid
-erDiagram
-    USERS {
-        uuid id PK
-        varchar email UK
-        varchar name
-        varchar password_hash
-        boolean email_verified
-        text image
-        timestamp created_at
-        timestamp updated_at
-    }
-
-    DEVICES {
-        uuid id PK
-        uuid user_id FK
-        varchar name
-        varchar role
-        varchar platform
-        varchar app_version
-        text push_token
-        varchar status
-        boolean is_camera
-        timestamp last_seen_at
-        timestamp updated_at
-        timestamp created_at
-    }
-
-    DEVICE_LINKS {
-        uuid id PK
-        uuid owner_user_id FK
-        uuid camera_device_id FK
-        uuid client_device_id FK
-        varchar status
-        timestamp created_at
-        timestamp updated_at
-    }
-
-    COMMANDS {
-        uuid id PK
-        uuid owner_user_id FK
-        uuid source_device_id FK
-        uuid target_device_id FK
-        varchar command_type
-        jsonb payload
-        varchar status
-        integer retry_count
-        timestamp last_dispatched_at
-        timestamp acknowledged_at
-        text error
-        timestamp created_at
-        timestamp updated_at
-    }
-
-    STREAM_SESSIONS {
-        uuid id PK
-        uuid owner_user_id FK
-        uuid camera_device_id FK
-        uuid requester_device_id FK
-        varchar status
-        varchar reason
-        varchar media_provider
-        varchar media_session_id
-        text publish_endpoint
-        text subscribe_endpoint
-        varchar stream_key
-        timestamp started_at
-        timestamp ended_at
-        jsonb metadata
-        timestamp created_at
-        timestamp updated_at
-    }
-
-    RECORDINGS {
-        uuid id PK
-        uuid owner_user_id FK
-        uuid stream_session_id FK
-        uuid camera_device_id FK
-        uuid requester_device_id FK
-        uuid event_id FK
-        varchar object_key
-        varchar bucket
-        integer duration_seconds
-        integer size_bytes
-        varchar status
-        timestamp available_at
-        text error
-        timestamp created_at
-        timestamp updated_at
-    }
-
-    EVENTS {
-        uuid id PK
-        uuid user_id FK
-        uuid device_id FK
-        varchar title
-        varchar triggered_by
-        varchar status
-        timestamp started_at
-        timestamp ended_at
-        timestamp notified_at
-        varchar video_url UK
-        timestamp created_at
-        timestamp updated_at
-    }
-
-    NOTIFICATIONS {
-        uuid id PK
-        uuid event_id FK
-        uuid user_id FK
-        timestamp sent_at
-        varchar channel
-        varchar status
-        boolean is_read
-    }
-
-    NOTIFICATION_DELIVERIES {
-        uuid id PK
-        uuid owner_user_id FK
-        uuid recipient_device_id FK
-        varchar type
-        jsonb payload
-        varchar status
-        integer attempts
-        text last_error
-        timestamp sent_at
-        timestamp next_attempt_at
-        timestamp created_at
-        timestamp updated_at
-    }
-
-    AUDIT_LOGS {
-        uuid id PK
-        uuid owner_user_id FK
-        uuid actor_device_id FK
-        varchar action
-        varchar target_type
-        varchar target_id
-        jsonb metadata
-        text ip_address
-        timestamp created_at
-    }
-
-    ACCOUNT {
-        uuid id PK
-        uuid user_id FK
-        text account_id
-        text provider_id
-        text access_token
-        text refresh_token
-        timestamp access_token_expires_at
-        timestamp refresh_token_expires_at
-        text id_token
-        text scope
-        text password
-        timestamp created_at
-        timestamp updated_at
-    }
-
-    SESSION {
-        uuid id PK
-        text token UK
-        uuid user_id FK
-        timestamp expires_at
-        text ip_address
-        text user_agent
-        timestamp created_at
-        timestamp updated_at
-    }
-
-    VERIFICATION {
-        uuid id PK
-        text identifier
-        text value
-        timestamp expires_at
-        timestamp created_at
-        timestamp updated_at
-    }
-
-    USERS ||--o{ DEVICES : owns
-    USERS ||--o{ DEVICE_LINKS : owns
-    USERS ||--o{ COMMANDS : owns
-    USERS ||--o{ STREAM_SESSIONS : owns
-    USERS ||--o{ RECORDINGS : owns
-    USERS ||--o{ EVENTS : creates
-    USERS ||--o{ NOTIFICATIONS : receives
-    USERS ||--o{ NOTIFICATION_DELIVERIES : owns
-    USERS ||--o{ AUDIT_LOGS : owns
-    USERS ||--o{ ACCOUNT : auth_account
-    USERS ||--o{ SESSION : auth_session
-
-    DEVICES ||--o{ DEVICE_LINKS : camera_device
-    DEVICES ||--o{ DEVICE_LINKS : client_device
-    DEVICES ||--o{ COMMANDS : source_device
-    DEVICES ||--o{ COMMANDS : target_device
-    DEVICES ||--o{ STREAM_SESSIONS : camera_device
-    DEVICES ||--o{ STREAM_SESSIONS : requester_device
-    DEVICES ||--o{ RECORDINGS : camera_device
-    DEVICES ||--o{ RECORDINGS : requester_device
-    DEVICES ||--o{ EVENTS : triggers
-    DEVICES ||--o{ NOTIFICATION_DELIVERIES : recipient_device
-    DEVICES ||--o{ AUDIT_LOGS : actor_device
-
-    STREAM_SESSIONS ||--o{ RECORDINGS : produces
-    EVENTS o|--o{ RECORDINGS : may_attach
-    EVENTS ||--o{ NOTIFICATIONS : generates
-```
-
-## Notes
-
-- This is generated from the current Drizzle schema in [schema.ts](/home/matiss/Documents/Final Year Project/Backend/db/schema.ts).
-- `VERIFICATION` is currently standalone in the schema and does not reference `USERS`.
-- `DEVICE_LINKS`, `COMMANDS`, `STREAM_SESSIONS`, and `RECORDINGS` each reference `DEVICES` more than once for different roles.
-- `ACCOUNT`, `SESSION`, and `VERIFICATION` are the Better Auth support tables.
-- `recordings` now absorbs the old upload metadata responsibility that previously lived in `videos`.
-- `notification_deliveries` represents push delivery jobs, while `notifications` remains the user-facing event notification history.
diff --git a/docs/project-gantt-chart.md b/docs/project-gantt-chart.md
deleted file mode 100644
index 4efb32d..0000000
--- a/docs/project-gantt-chart.md
+++ /dev/null
@@ -1,56 +0,0 @@
-# SecureCam ideal project Gantt chart
-
-```mermaid
-gantt
-    title SecureCam Project Timeline
-    dateFormat  YYYY-MM-DD
-    axisFormat  %b
-    excludes    weekends
-
-    section Initiation and Planning
-    Project scoping and proposal              :done, a1, 2025-10-15, 10d
-    Requirements gathering and research       :done, a2, after a1, 12d
-    Early architecture and feasibility        :done, a3, after a1, 15d
-
-    section Initial Prototype
-    Core prototype implementation             :done, b1, 2025-10-28, 18d
-    Basic camera-to-client workflow           :done, b2, after b1, 10d
-
-    section Scope Change and Refactor
-    Major scope change identified             :milestone, m1, 2025-11-12, 0d
-    Requirements redefinition                 :crit, c1, 2025-11-13, 8d
-    Architecture redesign                     :crit, c2, after c1, 10d
-    Backend refactor and model cleanup        :crit, c3, after c2, 18d
-    Web and mobile flow realignment           :crit, c4, after c2, 14d
-
-    section Platform Rebuild
-    Authentication and device model           :d1, 2025-12-09, 12d
-    Realtime communication layer              :d2, after d1, 14d
-    Stream control and recording pipeline     :d3, after d2, 16d
-    Storage integration and signed media URLs :d4, after d1, 12d
-    Motion events and activity feed           :d5, after d2, 10d
-
-    section Client Applications
-    Web app feature completion                :e1, 2026-01-20, 18d
-    Mobile app implementation                 :e2, 2026-01-27, 24d
-    Push notifications and user feedback loop :e3, after d5, 12d
-
-    section Quality and Evaluation
-    Integration testing and bug fixing        :f1, 2026-02-24, 18d
-    Performance tuning and resilience review  :f2, after f1, 10d
-    Final validation and demo preparation     :f3, after f2, 8d
-
-    section Dissertation and Delivery
-    Documentation and architecture diagrams   :g1, 2026-03-17, 12d
-    Report writing and iteration              :g2, 2026-03-10, 26d
-    Final edits and submission prep           :g3, after g2, 8d
-    Project complete                          :milestone, m2, 2026-04-17, 0d
-```
-
-## Notes
-
-- Start date assumed: `2025-10-15` to reflect a mid-October project start.
-- Final deadline set to: `2026-04-17`.
-- The chart assumes a major scope shift in mid-November that forced the team to revisit requirements and refactor the platform.
-- The refactor is treated as a real disruption rather than a minor iteration, so the later phases are shown as a rebuild on firmer architecture rather than a straight continuation of the original prototype.
-- This is an "idealised but realistic" plan for documentation purposes, not a claim that every task happened exactly in this order.
diff --git a/docs/temp-section-5-3-diagrams/5.3.1-server-bootstrap.md b/docs/temp-section-5-3-diagrams/5.3.1-server-bootstrap.md
deleted file mode 100644
index 3a259c0..0000000
--- a/docs/temp-section-5-3-diagrams/5.3.1-server-bootstrap.md
+++ /dev/null
@@ -1,29 +0,0 @@
-# 5.3.1 Server Bootstrap and Runtime Setup
-
-This diagram shows how the backend starts, mounts services, and becomes ready to handle API and realtime traffic.
-
-```mermaid
-sequenceDiagram
-    autonumber
-    participant Node as Node Runtime
-    participant Index as Backend/index.ts
-    participant App as Express App
-    participant Auth as Better Auth
-    participant Routes as Route Modules
-    participant MinIO as MinIO
-    participant RT as Socket.IO Gateway
-    participant Rec as Recordings Worker
-    participant Push as Push Worker
-
-    Node->>Index: start process
-    Index->>App: create express app
-    Index->>App: configure helmet + cors + JSON middleware
-    Index->>Auth: mount /api/auth/*
-    Index->>Routes: mount videos/admin/devices/links/streams/events/recordings/ops
-    Index->>MinIO: ensureMinioBucket()
-    MinIO-->>Index: bucket ready
-    Index->>RT: setupRealtimeGateway(server)
-    Index->>Rec: startRecordingsWorker()
-    Index->>Push: startPushWorker()
-    Index->>App: listen on configured port
-```
diff --git a/docs/temp-section-5-3-diagrams/5.3.10-operational-and-support-assets.md b/docs/temp-section-5-3-diagrams/5.3.10-operational-and-support-assets.md
deleted file mode 100644
index ffd32aa..0000000
--- a/docs/temp-section-5-3-diagrams/5.3.10-operational-and-support-assets.md
+++ /dev/null
@@ -1,29 +0,0 @@
-# 5.3.10 Operational Documentation and Support Assets
-
-This diagram maps the implementation code to the support assets used to inspect, document, and validate the system.
-
-```mermaid
-flowchart TD
-    Runtime[Runtime System]
-    APIs[API Routes]
-    Docs[OpenAPI Docs]
-    Sim[Simulator Pages]
-    Workers[Background Workers]
-    Validation[Validation and rollout docs]
-    Admin[Admin / Ops routes]
-
-    Runtime --> APIs
-    Runtime --> Workers
-    Runtime --> Admin
-    APIs --> Docs
-    APIs --> Sim
-    Runtime --> Validation
-
-    subgraph Support["Support layer"]
-        Docs
-        Sim
-        Workers
-        Validation
-        Admin
-    end
-```
diff --git a/docs/temp-section-5-3-diagrams/5.3.2-authentication-and-sessions.md b/docs/temp-section-5-3-diagrams/5.3.2-authentication-and-sessions.md
deleted file mode 100644
index fb4aa06..0000000
--- a/docs/temp-section-5-3-diagrams/5.3.2-authentication-and-sessions.md
+++ /dev/null
@@ -1,30 +0,0 @@
-# 5.3.2 User Authentication and Session Handling
-
-This diagram separates human user authentication from device-level authentication.
-
-```mermaid
-flowchart LR
-    User[User in Browser]
-    AuthAPI[/Better Auth Endpoints/]
-    Session[(session table)]
-    Users[(users table)]
-    Accounts[(account table)]
-    DeviceReg[/Device Registration API/]
-    DeviceToken[Signed Device Token]
-    DeviceAPI[/Device Auth Routes/]
-
-    User -->|sign up / sign in| AuthAPI
-    AuthAPI --> Users
-    AuthAPI --> Accounts
-    AuthAPI --> Session
-    Session -->|cookie-backed session| User
-
-    User -->|authenticated session| DeviceReg
-    DeviceReg -->|register browser as camera/client| DeviceToken
-    DeviceToken --> DeviceAPI
-
-    classDef auth fill:#e8f1ff,stroke:#2563eb,stroke-width:2px,color:#111827;
-    classDef data fill:#fff7e8,stroke:#d97706,stroke-width:2px,color:#111827;
-    class AuthAPI,DeviceReg,DeviceAPI,DeviceToken auth;
-    class Session,Users,Accounts data;
-```
diff --git a/docs/temp-section-5-3-diagrams/5.3.3-device-registration-and-presence.md b/docs/temp-section-5-3-diagrams/5.3.3-device-registration-and-presence.md
deleted file mode 100644
index 7a04fbb..0000000
--- a/docs/temp-section-5-3-diagrams/5.3.3-device-registration-and-presence.md
+++ /dev/null
@@ -1,26 +0,0 @@
-# 5.3.3 Device Identity Registration and Presence
-
-This diagram shows how a signed-in user registers a browser as a device and how presence is maintained after realtime connection.
-
-```mermaid
-sequenceDiagram
-    autonumber
-    participant User as Signed-in User
-    participant Web as WebApp Controller
-    participant Devices as POST /devices/register
-    participant DB as devices + device_links
-    participant Token as Device Token
-    participant Socket as Socket.IO Gateway
-
-    User->>Web: submit onboarding role + name
-    Web->>Devices: register device
-    Devices->>DB: insert devices row
-    Devices->>DB: auto-link to opposite-role devices if present
-    Devices-->>Web: return device + deviceToken
-    Web->>Web: persist saved device record
-    Web->>Socket: connect with device token
-    Socket->>DB: mark device online
-    Web->>Socket: periodic heartbeat
-    Socket->>DB: update lastSeenAt and status
-    Socket-->>Web: connection + heartbeat acknowledgements
-```
diff --git a/docs/temp-section-5-3-diagrams/5.3.4-database-schema-and-persistence.md b/docs/temp-section-5-3-diagrams/5.3.4-database-schema-and-persistence.md
deleted file mode 100644
index 49323ae..0000000
--- a/docs/temp-section-5-3-diagrams/5.3.4-database-schema-and-persistence.md
+++ /dev/null
@@ -1,97 +0,0 @@
-# 5.3.4 Database Schema and Persistence Model
-
-## Core Entity Relationship Diagram
-
-```mermaid
-erDiagram
-    USERS ||--o{ DEVICES : owns
-    USERS ||--o{ DEVICE_LINKS : owns
-    DEVICES ||--o{ DEVICE_LINKS : cameraDeviceId
-    DEVICES ||--o{ DEVICE_LINKS : clientDeviceId
-    USERS ||--o{ STREAM_SESSIONS : owns
-    DEVICES ||--o{ STREAM_SESSIONS : cameraDeviceId
-    DEVICES ||--o{ STREAM_SESSIONS : requesterDeviceId
-
-    USERS {
-      uuid id PK
-      varchar email
-      varchar name
-    }
-    DEVICES {
-      uuid id PK
-      uuid user_id FK
-      varchar role
-      varchar status
-      timestamp last_seen_at
-    }
-    DEVICE_LINKS {
-      uuid id PK
-      uuid owner_user_id FK
-      uuid camera_device_id FK
-      uuid client_device_id FK
-      varchar status
-    }
-    STREAM_SESSIONS {
-      uuid id PK
-      uuid owner_user_id FK
-      uuid camera_device_id FK
-      uuid requester_device_id FK
-      varchar status
-      varchar reason
-    }
-```
-
-## Media and Event Persistence
-
-```mermaid
-erDiagram
-    USERS ||--o{ EVENTS : owns
-    DEVICES ||--o{ EVENTS : triggeredBy
-    STREAM_SESSIONS ||--o{ RECORDINGS : produces
-    EVENTS ||--o{ RECORDINGS : mayCreate
-    USERS ||--o{ NOTIFICATIONS : receives
-    EVENTS ||--o{ NOTIFICATIONS : generates
-    USERS ||--o{ NOTIFICATION_DELIVERIES : owns
-    DEVICES ||--o{ NOTIFICATION_DELIVERIES : targets
-    USERS ||--o{ AUDIT_LOGS : owns
-    DEVICES ||--o{ AUDIT_LOGS : actor
-
-    EVENTS {
-      uuid id PK
-      uuid user_id FK
-      uuid device_id FK
-      varchar status
-      timestamp started_at
-      timestamp ended_at
-    }
-    RECORDINGS {
-      uuid id PK
-      uuid stream_session_id FK
-      uuid event_id FK
-      varchar object_key
-      varchar bucket
-      varchar status
-    }
-    NOTIFICATIONS {
-      uuid id PK
-      uuid event_id FK
-      uuid user_id FK
-      varchar channel
-      varchar status
-    }
-    NOTIFICATION_DELIVERIES {
-      uuid id PK
-      uuid recipient_device_id FK
-      varchar type
-      varchar status
-      int attempts
-    }
-    AUDIT_LOGS {
-      uuid id PK
-      uuid owner_user_id FK
-      uuid actor_device_id FK
-      varchar action
-      varchar target_type
-      varchar target_id
-    }
-```
diff --git a/docs/temp-section-5-3-diagrams/5.3.5-linking-and-control-flow.md b/docs/temp-section-5-3-diagrams/5.3.5-linking-and-control-flow.md
deleted file mode 100644
index 1aca9a1..0000000
--- a/docs/temp-section-5-3-diagrams/5.3.5-linking-and-control-flow.md
+++ /dev/null
@@ -1,36 +0,0 @@
-# 5.3.5 Device Linking and Command-Oriented Control
-
-This comparison diagram contrasts the older command-driven path with the current simplified stream request path.
-
-```mermaid
-flowchart LR
-    subgraph Legacy["Legacy command-oriented path"]
-        LClient[Client Device]
-        LBackend[Backend]
-        LCmd[(commands table)]
-        LGateway[Realtime Gateway]
-        LCamera[Camera Device]
-
-        LClient -->|request stream| LBackend
-        LBackend --> LCmd
-        LCmd --> LGateway
-        LGateway -->|command:received| LCamera
-        LCamera -->|command:ack| LGateway
-        LGateway --> LBackend
-    end
-
-    subgraph Simple["Simplified linked-device path"]
-        SClient[Client Device]
-        SBackend[Backend]
-        SLinks[(device_links)]
-        SSession[(stream_sessions)]
-        SCamera[Camera Device]
-
-        SClient -->|request stream| SBackend
-        SBackend --> SLinks
-        SBackend --> SSession
-        SBackend -->|stream:requested| SCamera
-        SCamera -->|accept| SBackend
-        SBackend -->|stream:started| SClient
-    end
-```
diff --git a/docs/temp-section-5-3-diagrams/5.3.6-stream-sessions-and-signalling.md b/docs/temp-section-5-3-diagrams/5.3.6-stream-sessions-and-signalling.md
deleted file mode 100644
index d4fbfe4..0000000
--- a/docs/temp-section-5-3-diagrams/5.3.6-stream-sessions-and-signalling.md
+++ /dev/null
@@ -1,46 +0,0 @@
-# 5.3.6 Stream Sessions and Signalling
-
-## Stream Request and WebRTC Signalling Sequence
-
-```mermaid
-sequenceDiagram
-    autonumber
-    participant Client as Client Browser
-    participant Backend as Backend /streams
-    participant Links as device_links
-    participant Session as stream_sessions
-    participant Camera as Camera Browser
-    participant RT as Socket.IO Relay
-
-    Client->>Backend: POST /streams/request
-    Backend->>Links: verify active camera-client link
-    Backend->>Session: insert requested session
-    Backend->>Camera: emit stream:requested
-    Camera->>Backend: POST /streams/:id/accept
-    Backend->>Session: update status to streaming
-    Backend->>Client: emit stream:started
-    Camera->>RT: webrtc:signal offer
-    RT->>Client: relay offer
-    Client->>RT: webrtc:signal answer
-    RT->>Camera: relay answer
-    Client->>RT: ICE candidates
-    RT->>Camera: relay ICE candidates
-    Camera->>RT: ICE candidates
-    RT->>Client: relay ICE candidates
-```
-
-## Stream Session State Diagram
-
-```mermaid
-stateDiagram-v2
-    [*] --> requested
-    requested --> streaming: camera accepts
-    requested --> cancelled: requester cancels
-    requested --> failed: validation or delivery failure
-    streaming --> completed: normal end
-    streaming --> cancelled: manual stop
-    streaming --> failed: connection or upload failure
-    completed --> [*]
-    cancelled --> [*]
-    failed --> [*]
-```
diff --git a/docs/temp-section-5-3-diagrams/5.3.7-motion-events-notifications-audit.md b/docs/temp-section-5-3-diagrams/5.3.7-motion-events-notifications-audit.md
deleted file mode 100644
index cf99b10..0000000
--- a/docs/temp-section-5-3-diagrams/5.3.7-motion-events-notifications-audit.md
+++ /dev/null
@@ -1,42 +0,0 @@
-# 5.3.7 Motion Events Notifications and Audit Trail
-
-## Motion Event Lifecycle
-
-```mermaid
-flowchart TD
-    Trigger[Manual trigger or browser motion detector]
-    Start[/POST /events/motion/start/]
-    Event[(events table)]
-    Links[(device_links)]
-    RT[Realtime motion:detected]
-    Push[Queued push notification]
-    End[/POST /events/:id/motion/end/]
-
-    Trigger --> Start
-    Start --> Event
-    Start --> Links
-    Links --> RT
-    Links --> Push
-    RT --> End
-    Push --> End
-    End --> Event
-```
-
-## Activity and Audit Flow
-
-```mermaid
-flowchart LR
-    Camera[Camera Device]
-    Event[(events)]
-    Notif[(notifications)]
-    Delivery[(notification_deliveries)]
-    Audit[(audit_logs)]
-    Client[Client Device]
-
-    Camera --> Event
-    Event --> Notif
-    Event --> Delivery
-    Event --> Audit
-    Notif --> Client
-    Delivery --> Client
-```
diff --git a/docs/temp-section-5-3-diagrams/5.3.8-recordings-and-object-storage.md b/docs/temp-section-5-3-diagrams/5.3.8-recordings-and-object-storage.md
deleted file mode 100644
index 29ba9ba..0000000
--- a/docs/temp-section-5-3-diagrams/5.3.8-recordings-and-object-storage.md
+++ /dev/null
@@ -1,40 +0,0 @@
-# 5.3.8 Recordings and Object Storage
-
-## Recording Pipeline
-
-```mermaid
-sequenceDiagram
-    autonumber
-    participant Cam as Camera Browser
-    participant Ctrl as Web Controller
-    participant Videos as /videos/upload-url
-    participant MinIO as MinIO Object Storage
-    participant Rec as /recordings/:id/finalize
-    participant DB as recordings table
-    participant Viewer as Client Browser
-
-    Cam->>Ctrl: stop local MediaRecorder
-    Ctrl->>Ctrl: compress recording blob
-    Ctrl->>Videos: request presigned upload URL
-    Videos-->>Ctrl: objectKey + uploadUrl
-    Ctrl->>MinIO: PUT recording blob
-    Ctrl->>Rec: finalize recording metadata
-    Rec->>DB: mark recording ready
-    Viewer->>Rec: GET /recordings/:id/download-url
-    Rec-->>Viewer: presigned download URL
-```
-
-## Storage Architecture
-
-```mermaid
-flowchart LR
-    Backend[Backend Service]
-    PG[(Postgres)]
-    MinIO[(MinIO / S3)]
-    Web[Web Client]
-
-    Web -->|stream, event, recording metadata| Backend
-    Backend -->|users, devices, links, sessions, events, recordings| PG
-    Backend -->|presigned upload/download + object checks| MinIO
-    Web -->|PUT / GET via presigned URLs| MinIO
-```
diff --git a/docs/temp-section-5-3-diagrams/5.3.9-web-application-implementation.md b/docs/temp-section-5-3-diagrams/5.3.9-web-application-implementation.md
deleted file mode 100644
index 1416f55..0000000
--- a/docs/temp-section-5-3-diagrams/5.3.9-web-application-implementation.md
+++ /dev/null
@@ -1,53 +0,0 @@
-# 5.3.9 Web Application Implementation
-
-## Web Application Architecture
-
-```mermaid
-flowchart LR
-    Routes[Svelte Route Pages]
-    Controller[controller.js]
-    Store[store.js]
-    API[api.js]
-    Socket[Socket.IO Client]
-    Backend[Backend APIs]
-
-    Routes --> Controller
-    Controller --> Store
-    Controller --> API
-    Controller --> Socket
-    API --> Backend
-    Socket --> Backend
-
-    subgraph RoutePages["Main route pages"]
-        Auth[Auth]
-        Onboarding[Onboarding]
-        Camera[Camera]
-        Client[Client]
-        Activity[Activity]
-        Settings[Settings]
-    end
-
-    Routes --> RoutePages
-```
-
-## UI Flow
-
-```mermaid
-flowchart TD
-    Start[Open WebApp]
-    Auth[Sign in / Sign up]
-    Onboarding[Register browser as device]
-    Role{Chosen role}
-    Camera[Camera dashboard]
-    Client[Client dashboard]
-    Activity[Activity page]
-    Settings[Settings page]
-
-    Start --> Auth --> Onboarding --> Role
-    Role -->|camera| Camera
-    Role -->|client| Client
-    Camera --> Activity
-    Camera --> Settings
-    Client --> Activity
-    Client --> Settings
-```
diff --git a/docs/temp-section-5-3-diagrams/README.md b/docs/temp-section-5-3-diagrams/README.md
deleted file mode 100644
index 91c5f59..0000000
--- a/docs/temp-section-5-3-diagrams/README.md
+++ /dev/null
@@ -1,18 +0,0 @@
-# Temporary Section 5.3 Diagrams
-
-These temporary files contain Mermaid diagrams for the `5.3` implementation chapter.
-
-## Files
-
-- [5.3.1 Server Bootstrap](./5.3.1-server-bootstrap.md)
-- [5.3.2 Authentication and Sessions](./5.3.2-authentication-and-sessions.md)
-- [5.3.3 Device Registration and Presence](./5.3.3-device-registration-and-presence.md)
-- [5.3.4 Database Schema and Persistence](./5.3.4-database-schema-and-persistence.md)
-- [5.3.5 Linking and Control Flow](./5.3.5-linking-and-control-flow.md)
-- [5.3.6 Stream Sessions and Signalling](./5.3.6-stream-sessions-and-signalling.md)
-- [5.3.7 Motion Events Notifications Audit](./5.3.7-motion-events-notifications-audit.md)
-- [5.3.8 Recordings and Object Storage](./5.3.8-recordings-and-object-storage.md)
-- [5.3.9 Web Application Implementation](./5.3.9-web-application-implementation.md)
-- [5.3.10 Operational and Support Assets](./5.3.10-operational-and-support-assets.md)
-
-These are temporary working diagrams intended for screenshots and report drafting.