Is your feature request related to a problem? Please describe.
The repository has multiple Docker Compose files (production, staging, proxy, local), but CI currently does not validate them. Invalid YAML syntax or schema errors are only caught during deployment or manual testing, which creates a risk of broken builds in production/staging.

Describe the solution you'd like
I propose adding a CI job (or step) that runs docker compose -f <file> config --quiet for each Compose file located in docker-compose/**. This will validate the syntax and schema automatically on every PR.

Are you going to work on implementing this?

• Yes
• No

Additional context
This is a fast, low-cost check that prevents broken deploys due to simple Compose errors. I plan to implement this by adding a new workflow or extending the existing CI pipeline.