merge: fix frontend dev cache permissions

docs/operations.md

@@ -36,3 +36,4 @@ No automated backup is configured for the MVP. Use `pg_dump` from the database c
 - The frontend uses the Angular development server and is not production hardened.
 - Role-specific permissions are modeled but not yet enforced per action.
 - External data ingestion is intentionally not automated yet.
+- The Angular development cache is configured under `/tmp/angular-cache` inside the container so the non-root frontend user does not need write access to the bind-mounted source tree.

docs/runbook.md

@@ -23,6 +23,7 @@ docker compose run --rm backend python manage.py createsuperuser
 ## Troubleshooting
 
 - If the frontend shows an authentication error, sign in through `http://localhost:8000/admin/` or DRF login first.
+- If the frontend serves a blank page, check `docker compose logs frontend`. Cache permission errors should be resolved by the configured `/tmp/angular-cache` path; restart with `docker compose up -d frontend`.
 - If backend startup fails, check database readiness with `docker compose logs db`.
 - If dependencies change, rebuild with `docker compose build --no-cache backend frontend`.
 

frontend/angular.json

@@ -1,6 +1,11 @@
 {
   "$schema": "./node_modules/@angular/cli/lib/config/schema.json",
   "version": 1,
+  "cli": {
+    "cache": {
+      "path": "/tmp/angular-cache"
+    }
+  },
   "newProjectRoot": "projects",
   "projects": {
     "hoopscout-frontend": {