Your task is to perform a deep and practical review of the provided C++ project/codebase, with primary focus on code quality, readability, maintainability, and secure coding practices. Review the code as if you were preparing professional feedback for a developer who wants to improve the project before submission or production use.

Analyze the code carefully and provide feedback in the following areas:

1. Code Quality and Best Practices
- Evaluate adherence to clean code principles and modern C++ best practices.
- Point out violations of DRY, KISS, separation of concerns, and, when applicable, SOLID principles.
- Identify code smells, unnecessary complexity, duplication, poor abstractions, weak modularity, and bad design decisions.
- Review C++-specific practices such as RAII, const-correctness, ownership clarity, smart pointer usage, copy/move semantics, rule of 3/5/0, exception safety, and avoidance of undefined behavior.

2. Readability and Maintainability
- Evaluate naming clarity, function size, class design, file organization, header/source separation, comments, cohesion, coupling, and overall ease of understanding.
- Point out code that is hard to extend, debug, test, or reason about.
- Review include hygiene, dependency coupling, overuse of inheritance, macro misuse, and template complexity where relevant.
- Suggest refactoring ideas that would improve long-term maintainability.

3. Security Concerns (C++-specific)
- Buffer overflows and out-of-bounds access
- Integer overflow and underflow
- Use-after-free and dangling pointers
- Uninitialized memory reads
- Format string vulnerabilities
- Unsafe input handling and weak validation
- Dangerous file or system operations
- Secrets or credentials exposed in code

For every issue you identify, use exactly this format:

------------------------------
- Category: [Code Quality / Maintainability / Security]
- Severity: [Critical / High / Medium / Low]
- Location: [file, function, class, or module name if identifiable]
- Problem: clearly describe what is wrong
- Why it matters: explain the practical risk or negative impact
- Recommendation: provide a specific and actionable improvement

Additional rules:
- Do not give generic advice unless it is directly supported by the code.
- Base your review on the actual implementation, not assumptions.
- If something is uncertain, label it clearly as a potential risk instead of a confirmed issue.
- Do not invent file names, symbols, or architectural intent if they are not visible in the code.
- Prioritize the most important issues first.
- Be direct and critical, but constructive.
- Focus on meaningful findings rather than minor stylistic preferences unless they noticeably affect readability or maintainability.
- When possible, mention relevant modern C++ alternatives or idioms that would improve the implementation.

At the end, provide:
- Top 5 most important issues
- Highest-priority fixes
- A brief overall assessment of the project’s code quality
- 2–3 strengths of the codebase, if any are clearly present