updates for admin area

CRUD_NOTES.md

@@ -1,32 +0,0 @@
-# BeatBook Admin CRUD
-
-This revision replaces the read-only/placeholder administration sections with persistent CRUD management.
-
-## CRUD resources
-
-- Users
-- Clients
-- DJs
-- Businesses
-- Bookings
-- Payments
-- Reviews
-- Messages
-- Notifications
-- Support tickets
-- Saved reports
-- Content pages
-- Roles
-- Permissions
-- Privacy/legal documents
-- Application settings
-
-## New persistence
-
-Migration `2026_09_12_000004_create_admin_management_tables.php` adds tables for payments, messages, admin notifications, support tickets, saved reports, content pages, legal documents and application settings.
-
-Run `php artisan migrate` on an existing installation. Do not use `migrate:fresh` unless you intentionally want to erase existing data.
-
-Published Privacy, Cookie and Terms records are used by the corresponding public legal pages. Published Content records are available at `/pages/{slug}`.
-
-Notification records are currently managed content; creating a record does not yet dispatch email/push notifications. Saved reports are definitions; a later reporting engine can execute/export them.

REWORK_NOTES.md

@@ -1,26 +0,0 @@
-# BeatBook UI / Backend Rework
-
-## Completed
-- Replaced the generic admin placeholder with real section views for users, DJs, clients, bookings, payments, reviews, messages, notifications, support, reports, content, roles, privacy and settings.
-- Added admin actions for role changes, DJ publish/feature controls, review moderation and cache clearing.
-- Replaced the non-clickable client dashboard with account routes for overview, enquiries, bookings and editable account details.
-- Added responsive admin navigation with a mobile drawer.
-- Added responsive public navigation and mobile menu.
-- Rebuilt home, DJ directory and DJ profile layouts for desktop, tablet and mobile.
-- Added sorting to the DJ directory.
-- Added route coverage tests for account and admin pages.
-- Made auth tests explicitly bypass request-forgery middleware during automated tests only.
-- Restored a clean Laravel .gitignore and ensured composer.lock is not ignored.
-- Updated Laravel 13 request-forgery middleware API usage.
-
-## Notes
-Messages, notifications and support now have proper destinations and admin presentation, but the project currently has no dedicated conversation/support database schema. Their pages therefore show deliberate empty states until those workflows/models are added.
-
-After applying the files run:
-
-    composer install
-    npm install
-    npm run build
-    php artisan optimize:clear
-    php artisan test
-    ./vendor/bin/pint

SECURITY.md

@@ -1,12 +0,0 @@
-# Security baseline
-- Enforce HTTPS/HSTS in production.
-- Keep private/verification uploads outside public storage; authorize every download.
-- Validate MIME and image decoding; strip metadata where appropriate.
-- Use policies for every tenant-owned resource.
-- Enable 2FA for admin/DJ accounts.
-- Verify Stripe webhook signatures and make handlers idempotent.
-- Rate-limit auth, enquiry, review and messaging endpoints.
-- Audit privileged actions; hash IP addresses if retained.
-- Never store card details.
-- Run queues under Supervisor/systemd and keep dependencies patched.
-- Replace placeholder legal policies before launch.