Krzysztof kuhy Rudnicki 8836453f8c fix: initialise the catering queue at startup ... `KuchniaQueueService` had no `init()` call in `main()`, so on a real device the whole feature would have done nothing: every entry point checks `isInitialized` first and returns quietly, which reads as "no delivery today" rather than as an error. All 694 tests passed throughout, because widget tests initialise the service directly. Caught by grepping main.dart before the phone deploy, not by the suite. So it is now a repo invariant: `repo_invariants_test.dart` asserts main() names both catering `init()` calls, and the assertion was checked against a main.dart with the line deleted. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01QQpCiPaSbyRpwsLkH3dgsX		2026-08-23 09:08:54 +02:00
..
desktop	Split wrapper_server and sync_merge into siblings	2026-08-15 16:42:27 +02:00
models	feat: carry the catering credential to the phone	2026-08-23 08:25:27 +02:00
screens	feat: offer delivered dishes to the log form, one tap each	2026-08-23 09:07:17 +02:00
services	fix: initialise the catering queue at startup	2026-08-23 09:08:54 +02:00
ui	Make the meal gate usable without a pointer on a 1366x768 screen	2026-07-30 16:21:27 +02:00
widgets	Read the meal schedule from a forward-only history (Dart)	2026-08-16 14:41:37 +02:00
main.dart	fix: initialise the catering queue at startup	2026-08-23 09:08:54 +02:00