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>

README.md

@@ -55,6 +55,30 @@ and **[wiki/admin](wiki/admin/README.md)** for role-specific how-to guides.
   categories/statuses/priorities/teams — issued via admin-managed API clients.
   Interactive docs (L5-Swagger) at `/admin/api-docs`.
 - **PWA** — installable manifest + icons for the client-facing area.
+- **In-app notifications** — a bell in the top bar (client/operator/admin areas)
+  backed by Laravel's database notification channel, alongside the existing
+  e-mail notifications (same per-trigger enable toggle drives both).
+- **Attachments** — drag-and-drop upload (in addition to the file picker) and
+  inline image thumbnails in the message thread instead of a plain download link.
+- **Customer satisfaction (CSAT)** — clients rate a ticket 1–5 stars (+ optional
+  comment) once it's closed; average/response-rate surfaced as a KPI on the
+  operator stats dashboard, with a link in the "ticket closed" e-mail.
+- **Saved queue views** — operators can save their current filter/sort/column
+  combination in the ticket queue, mark one as default, and switch between them.
+- **Full-text search** — MySQL/MariaDB `FULLTEXT` search (with a portable `LIKE`
+  fallback) across ticket subject/body and reply message bodies, available in
+  both the operator queue and the client's own ticket list.
+- **Stats export** — the operator stats dashboard can export the currently
+  filtered ticket set as CSV.
+- **BookStack knowledge-base integration** *(optional, off by default)* —
+  suggests relevant BookStack articles by category/subcategory while a ticket
+  is being created, and in a separate sidebar panel on an existing ticket for
+  operators (with a copy-link button). Configured entirely from Admin >
+  Konfiguracja: connection + API token, optional SSL-verification bypass for
+  self-signed instances, page/book search-type filter, and two independent
+  per-shelf allow-lists (nothing is searched until an admin opts specific
+  shelves in, separately for ticket-creation suggestions vs. the operator
+  sidebar).
 
 ## Tech stack
 
@@ -104,7 +128,7 @@ Compose-level and Laravel-level) and the LDAP/SMTP gotcha after a fresh seed.
 src/                     Laravel application
   app/Livewire/          Client/Operator/Admin Livewire components
   app/Models/            Eloquent models
-  app/Services/          TicketService (ticket lifecycle + notifications)
+  app/Services/          TicketService (ticket lifecycle + notifications), BookStackClient
   app/Ldap/              LDAP user model + sync handlers
   database/migrations/   Schema (one file per table group, final shape)
   database/seeders/      DatabaseSeeder — reference data, no ticket data