v1.1.0

- In-app notifications: a bell in the top bar backed by Laravel's database
  notification channel, alongside existing e-mail notifications (same
  per-trigger toggle drives both; ticket links now correctly point into the
  recipient's own area instead of always linking to the client view).
- Drag-and-drop attachments on every upload form, plus inline image
  thumbnails in the message thread instead of a plain download link.
- Customer satisfaction (CSAT) rating: clients rate a closed ticket 1-5 stars
  with an optional comment; shown read-only to operators, surfaced as a KPI
  on the stats dashboard, and linked from the "ticket closed" e-mail.
- Saved queue views: operators can save/apply/delete named filter+sort+
  column presets in the ticket queue and mark one as their default.
- Full-text search (MySQL FULLTEXT, portable LIKE fallback) across ticket
  subject/body and reply message bodies, now also on the client's own ticket
  list.
- Stats CSV export for the currently filtered ticket set.
- Optional BookStack knowledge-base integration (off by default): suggests
  articles by category/subcategory while creating a ticket and in a separate
  sidebar for operators on an existing ticket (with a copy-link button).
  Configurable connection/SSL bypass/search-type filter, plus two
  independent per-shelf allow-lists so nothing is ever searched until an
  admin opts specific shelves in.
- Closed tickets no longer show in "Moje zgłoszenia"/"Nieprzypisane"/team
  queue tabs, only under "Zamknięte" (matching how "Otwarte" already worked).
- Wired up the Admin > About "Wersja" field to config('app.version')/VERSION
  in .env instead of a stale hardcoded string.
- Fixed: TicketService::setStatus() now checks a status's stage rather than
  the literal key 'closed' to decide whether to fire the "ticket closed"
  notification/stop the timer.
- Updated README/ARCHITECTURE/CHANGELOG/install/SECURITY docs and all three
  wiki/ role guides for the above; documented a root-vs-www-data file
  ownership gotcha in CLAUDE.md (running artisan commands via a plain
  `docker exec` can leave root-owned Blade cache files that later break
  recompilation for the www-data Apache process).

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>

CLAUDE.md

@@ -47,6 +47,18 @@ with no rebuild or restart:
   `view:cache`), clear them again afterward (`config:clear`/`view:clear`) — this
   app normally runs uncached so edits apply live; leaving a cache on silently
   breaks that workflow.
+- **`sudo docker exec` runs as `root`, not `www-data`.** Apache's worker
+  processes run as `www-data`; anything you run via a plain `docker exec`
+  (`php artisan test`, `tinker`, `view:cache`, etc.) runs as `root`. On this
+  NFS-backed mount, a file Blade compiles/caches while running as `root`
+  (`storage/framework/views/*.php`) can't later be overwritten by `www-data`
+  when a real request needs to recompile it (the source changed) — this
+  surfaces in production as a 500 with `touch(): Utime failed: Operation not
+  permitted`. If you ran `php artisan test`/`tinker`/any artisan command via
+  `docker exec` in a session where you also edited Blade files afterward,
+  finish with `sudo docker exec servicedesk-servicedesk-1 php artisan
+  view:clear` to flush any root-owned compiled views before ending the
+  session — don't wait for a report of a broken page to catch it.
 
 ## Apache `/icons/` alias trap