Prevent stale Livewire hash after deploys — add no-cache headers for HTML responses

After each deploy, Livewire's JS hash changes. Without no-cache on HTML,
browsers serve the old page with the wrong /livewire-{hash}/update endpoint,
causing 404s until the user hard-refreshes.
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

docker/nginx/default.conf

@@ -34,8 +34,10 @@ server {
         try_files $uri $uri/ /index.php?$query_string;
     }
 
-    # Laravel routing
+    # Laravel routing — no browser cache on HTML pages (prevents stale Livewire hash)
     location / {
+        add_header Cache-Control "no-cache, no-store, must-revalidate" always;
+        add_header Pragma "no-cache" always;
         try_files $uri $uri/ /index.php?$query_string;
     }