Problem

Recent Rel 1.8 issues (Apple Silicon build failure for sztabina, Flyway migration failure at backend startup) were not caught by CI because there is no automated verification that a fresh clone of the repository can be built and started end-to-end using the default Docker Compose setup.

Both issues would have been detected by a simple system-level startup check.

Proposal

Add a minimal CI “clean startup” smoke test that verifies the most basic contract of the project:

A fresh clone can build all components and start using the default docker-compose configuration.

This test should be intentionally simple and fast, and should not attempt to validate application behavior beyond successful startup.

Scope (minimal and intentional)

The CI step should:

1. Build all components (backend, UI, sztabina)
2. Run docker compose up using the default compose file
3. Wait for a basic “system is up” signal (e.g. backend startup log line or open port)
4. Exit successfully if startup completes
5. Tear down containers

No functional tests, no data seeding, no API assertions.

Non-goals

• No full integration test suite
• No long-running containers
• No environment-specific configuration
• No performance or correctness validation

This is a smoke test, not a test framework.

Benefits

• Catches build-context, architecture, and migration issues early
• Verifies cross-component compatibility continuously
• Improves release confidence with minimal CI overhead
• Encodes an implicit project assumption (“it should start”) as an explicit check

Notes

This test should ideally run on:

• PRs targeting wolnosc
• Release tags

to maximize signal while minimizing CI noise.