UI: switch to Syncfusion M3, remove Tailwind;

paginate changelog; docs updated; bump to 2025.1.0-alpha.8

.github/copilot-instructions.md

@@ -60,10 +60,20 @@ Use this as your shared context when proposing changes. Keep edits minimal and m
 - Vite React app; proxies `/api` and `/screenshots` to API in dev (`vite.config.ts`).
 - Uses Syncfusion components; Vite config pre-bundles specific packages to avoid alias issues.
 - Environment: `VITE_API_URL` provided at build/run; in dev compose, proxy handles `/api` so local fetches can use relative `/api/...` paths.
+ - Theming: Syncfusion Material 3 theme is used. All component CSS is imported centrally in `dashboard/src/main.tsx` (base, navigations, buttons, inputs, dropdowns, popups, kanban, grids, schedule, filemanager, notifications, layouts, lists, calendars, splitbuttons, icons). Tailwind CSS has been removed.
  - Scheduler (appointments page): top bar includes Group and Academic Period selectors (Syncfusion DropDownList). Selecting a period calls `POST /api/academic_periods/active`, moves the calendar to today’s month/day within the period year, and refreshes a right-aligned indicator row showing:
    - Holidays present in the current view (count)
    - Period label (display_name or name) with a badge indicating whether any holidays exist in that period (overlap check)
 
+- Program info page (`dashboard/src/programminfo.tsx`):
+  - Loads data from `dashboard/public/program-info.json` (app name, version, build info, tech stack, changelog).
+  - Uses Syncfusion card classes (`e-card`, `e-card-header`, `e-card-title`, `e-card-content`) for consistent styling.
+  - Changelog is paginated with `PagerComponent` (from `@syncfusion/ej2-react-grids`), default page size 5; adjust `pageSize` or add a selector as needed.
+
+- Groups page (`dashboard/src/infoscreen_groups.tsx`):
+  - Migrated to Syncfusion inputs and popups: Buttons, TextBox, DropDownList, Dialog; Kanban remains for drag/drop.
+  - Unified toast/dialog wording; replaced legacy alerts with toasts; spacing handled via inline styles to avoid Tailwind dependency.
+
 Note: Syncfusion usage in the dashboard is already documented above; if a UI for conversion status/downloads is added later, link its routes and components here.
 
 ## Local development
@@ -116,3 +126,13 @@ Questions or unclear areas? Tell us if you need: exact devcontainer debugging st
 - **Usage**: New events/media can optionally reference `academic_period_id` for better organization and filtering.
 - **Constraints**: Only one period can be active at a time; use `init_academic_periods.py` for Austrian school year setup.
  - **UI Integration**: The dashboard highlights the currently selected period and whether a holiday plan exists within that date range. Holiday linkage currently uses date overlap with `school_holidays`; an explicit `academic_period_id` on `school_holidays` can be added later if tighter association is required.
+
+## Changelog Style Guide (Program info)
+
+- Source: `dashboard/public/program-info.json`; newest entry first
+- Fields per release: `version`, `date` (YYYY-MM-DD), `changes` (array of short bullets)
+- Tone: concise, user-facing; German wording; area prefixes allowed (e.g., “UI: …”, “API: …”)
+- Categories via emoji or words: Added (🆕/✨), Changed (🛠️), Fixed (✅/🐛), Removed (🗑️), Security (🔒), Deprecated (⚠️)
+- Breaking changes must be prefixed with `BREAKING:`
+- Keep ≤ 8–10 bullets; summarize or group micro-changes
+- JSON hygiene: valid JSON, no trailing commas, don’t edit historical entries except typos