fix: Staging directory permission error

.gitea/workflows/staging.yaml

@@ -119,7 +119,7 @@ jobs:
           sudo chmod 755 data/backups data/documents
           # Traefik acme.json requires 600 permissions
           if [ ! -f data/traefik/acme.json ]; then
-            touch data/traefik/acme.json
+            sudo touch data/traefik/acme.json
           fi
           chmod 600 data/traefik/acme.json
 

docs/PROMPTS.md

@@ -22,16 +22,17 @@ You are a senior software engineer specializsing in NodeJS, Typescript, front en
 - Make no assumptions. 
 - Ask clarifying questions. 
 - Ultrathink
-- You will be fixing a bug the system backup and restore function. 
+- You will be implementing a staging environment for this application. 
 
 *** CONTEXT ***
 - This is a modern web app for managing a vehicle fleet. It has both a desktop and mobile versions of the site that both need to maintain feature parity. It's currently deployed via docker compose but in the future will be deployed via k8s.
 - Read README.md CLAUDE.md and AI-INDEX.md and follow relevant instructions to understand this code repository in the context of this change. 
-- There are permission errors with the backup files.  
-- The backup directory is mapped from the filesystem of the host
-- The app is deployed as the gitlab-runner user and group which is a different UID then the nodejs user
-- Start with the files in this directory /Users/egullickson/Documents/Technology/coding/motovaultpro/backend/src/features/backup/api
-- The docker file is located at /Users/egullickson/Documents/Technology/coding/motovaultpro/backend/Dockerfile
+- Currently the application is setup to run only production at the URL https://motovaultpro.com
+- We are adding a staging workflow where first changes are pushed to a stage environment at https://staging.motovaultpro.com
+- The gitea workflow is working for this. 
+- The Let's Encrypt certificates are working for this. 
+- We need to ensure that the application can handle the routes/callbacks
+- Recommend what changes need to be made to auth0 to allow this. 
 
 *** CHANGES TO IMPLEMENT ***
 - Research this code base and ask iterative questions to compile a complete plan.