2 Commits

Author	SHA1	Message	Date
Jacek Pyziak	933dfcc67b	feat(120): alert component unification ... Phase 120 - Plan 01: - Reusable PHP alert component (resources/views/components/alert.php) with inline SVG icon per type, optional dismiss button. - Missing .alert--info SCSS variant added (#eff6ff/#bfdbfe/#1e3a8a) - fixes black-on-white alert after Fakturownia test connection. - Flash::push(type, message) + Flash::all() with BC for set/get; legacy key heuristic (error/.save/warning -> typed entries). - Central flash renderer in 3 layouts (app/auth/public) iterating Flash::all() through component (.alerts-stack wrap). - Vanilla JS alert-dismiss.js with idempotent guard and delegated click handler on [data-alert-dismiss]. - 36 views migrated off inline <div class="alert alert--TYPE">; .flash--error/success removed from views (orders/show, shipments/prepare). - SCSS rebuilt: public/assets/css/{app,login}.css. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>	2026-05-12 18:47:41 +02:00
Jacek Pyziak	c5b2885b44	feat: Add User-Agent header to Allegro API requests ... - Implemented buildUserAgent() method in AllegroApiClient, AllegroOAuthClient, and AllegroTrackingService to include User-Agent header in all HTTP requests to Allegro API. - Updated .env.example to include APP_VERSION and ALLEGRO_USER_AGENT_URL for configuration. - Created public /info page to provide application details required by Allegro, including app name, version, description, and contact information. - Added minimalist layout for public pages to ensure a professional appearance. - Ensured all changes comply with Allegro's API requirements for User-Agent header.	2026-04-08 20:59:55 +02:00