Fix/config save error handling (#150)

* fix(docs): Add trailing newlines to documentation files

* fix(web): Resolve font configuration loading error on first page load

- Remove ineffective DOMContentLoaded listener from fonts partial (loads via HTMX after main page DOMContentLoaded)
- Add proper HTMX event handling with htmx:afterSettle for reliable initialization
- Add duplicate initialization protection flag
- Improve error handling with response validation and clearer error messages
- Add fallback initialization check for edge cases
- Ensure DOM elements exist before attempting initialization

Fixes issue where 'Error loading font configuration' appeared on first web UI load when opening fonts tab.

* fix(config): Update plugins_directory to plugin-repos in config template

The web-ui-info plugin is located in plugin-repos/ directory, but the
config template was pointing to plugins/ directory. This caused the
plugin to not be discovered on fresh installations.

- Changed plugins_directory from 'plugins' to 'plugin-repos' in config.template.json
- Matches actual plugin location and code default behavior
- Ensures web-ui-info plugin is available by default on fresh installs

* fix(config): Improve config save error handling

- Make load_config() failure non-fatal in save_raw_file_content
  - Wrapped reload in try-except to prevent save failures when reload fails
  - File save is atomic and successful even if reload fails
  - Logs warning when reload fails but doesn't fail the operation

- Improve error messages in API endpoints
  - Added detailed error logging with full traceback for debugging
  - Extract specific error messages from ConfigError exceptions
  - Include config_path in error messages when available
  - Provide fallback messages for empty error strings

- Enhance frontend error handling
  - Check response status before parsing JSON
  - Better handling of non-JSON error responses
  - Fallback error messages if error details are missing

Fixes issue where 'Error saving config.json: an error occured' was
shown even when the file was saved successfully but reload failed.

---------

Co-authored-by: Chuck <chuck@example.com>

src/config_manager.py

@@ -448,8 +448,18 @@ class ConfigManager:
             
             # If we just saved the main config or secrets, the merged self.config might be stale.
             # Reload it to reflect the new state.
+            # Note: We wrap this in try-except because reload failures (e.g., migration errors)
+            # should not cause the save operation to fail - the file was saved successfully.
             if file_type == "main" or file_type == "secrets":
-                self.load_config()
+                try:
+                    self.load_config()
+                except Exception as reload_error:
+                    # Log the reload error but don't fail the save operation
+                    # The file was saved successfully, reload is just for in-memory consistency
+                    self.logger.warning(
+                        f"Configuration file saved successfully, but reload failed: {reload_error}. "
+                        f"The file on disk is valid, but in-memory config may be stale."
+                    )
 
         except (IOError, OSError, PermissionError) as e:
             error_msg = f"Error writing {file_type} configuration to file {os.path.abspath(path_to_save)}"