feat: professional color scheme

[me-marcel]

Pull Request

Current Behavior

Expected Behavior

Related Issue(s)

Type of Change

• 🐛 Bug fix (non-breaking change which fixes an issue)
• ✨ New feature (non-breaking change which adds functionality)
• 💥 Breaking change (fix or feature that would cause existing functionality to not work as expected)
• 📚 Documentation update
• 🔧 Refactoring (no functional changes, no api changes)
• ⚡ Performance improvement
• 🧪 Test improvements
• 🎨 Style/formatting changes
• 🔒 Security improvements

Checklist

Code Quality

• Code follows the project's style guidelines
• Self-review of code has been performed
• Code is commented, particularly in hard-to-understand areas
• Corresponding changes to documentation have been made
• Changes generate no new warnings

Testing

• New and existing unit tests pass locally
• Tests have been added that prove the fix is effective or that the feature works
• All affected projects build, test, and lint successfully
• E2E tests have been run (if applicable)

Compliance

• All commits use conventional commit format (e.g. feat:, fix:, docs:)
• Application and library boundaries and dependencies are valid
• Code follows the project’s style and quality practices
• Nx is used for build, test, and lint (e.g. nx prepush, nx affected)

Documentation

• Relevant docs and READMEs have been updated to reflect changes
• API or public contract changes are documented (if applicable)

Additional Notes

Reviewer Guidelines

• Please ensure all checklist items are verified
• Pay special attention to breaking changes and their impact
• Verify that all tests pass and code quality standards are met
• Check that documentation is updated appropriately

---

Questions or concerns? Contact the development team at hi@forepath.io

[forepath-semantic-release]

This PR is included in version 1.44.0 🎉