CHANGELOG + comment: correct the file-browser claim (the start-up mount sync already moved it); 9202 gaps measured

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_0159rPz1ZhFKsS53msqPYxtS

controller/internal/stacks/infra.go

@@ -416,9 +416,10 @@ func containerRunning(name string) bool {
 var composeImageLine = regexp.MustCompile(`(?m)^(\s*image:\s*)(\S+)\s*$`)
 
 // reconcileFileBrowserImage moves a RUNNING file browser to the pinned image (R-838, controller v0.291.0). Its compose
-// file is owned by web.SyncFileBrowserMounts (the storage mounts), which runs only when storage changes — so before
-// this, a release that raised FileBrowserImage never reached an installed box. Only the `image:` line is replaced;
-// the mounts stay byte-for-byte. Same image (or no compose file) → nothing. Pinned by TestReconcileFileBrowserImage_*.
+// file is owned by web.SyncFileBrowserMounts, which ALSO runs at every controller start (web/server.go) and renders the
+// pinned image — that is the main route; this is a second net for a start-up sync that failed. Only the `image:` line
+// is replaced; the mounts stay byte-for-byte. Same image (or no compose file) → nothing. Pinned by
+// TestReconcileFileBrowserImage_*.
 func (m *Manager) reconcileFileBrowserImage(dir string) error {
 	composePath := filepath.Join(dir, "docker-compose.yml")
 	cur, err := os.ReadFile(composePath)