Major Comment and codebase cleanup

Documentation/02_Developer_Guide/10_Coding_Conventions.md

@@ -23,7 +23,7 @@ This document outlines the coding conventions and general practices followed wit
 *   **Configuration:** Core application settings are defined in `config/app_settings.json`. Supplier-specific rules are managed in JSON files within the `Presets/` directory. The `Configuration` class (`configuration.py`) is responsible for loading `app_settings.json` and merging it with the selected preset file.
 *   **File Paths:** Use `pathlib.Path` objects for handling file system paths. Avoid using string manipulation for path joining or parsing.
 *   **Docstrings:** Write clear and concise docstrings for modules, classes, methods, and functions, explaining their purpose, arguments, and return values.
-*   **Comments:** Use comments to explain complex logic or non-obvious parts of the code.
+*   **Comments:** Use comments to explain complex logic or non-obvious parts of the code. Avoid obsolete comments (e.g., commented-out old code) and redundant comments (e.g., comments stating the obvious, like `# Import module` or `# Initialize variable`). The goal is to maintain clarity while minimizing unnecessary token usage for LLM tools.
 *   **Imports:** Organize imports at the top of the file, grouped by standard library, third-party libraries, and local modules.
 *   **Naming:**
     *   Use `snake_case` for function and variable names.