I have an existing Laravel backend that exposes a set of REST APIs. A legacy Blade-based frontend is still attached to the project, but I now have a brand-new standalone frontend (built separately) that should consume those APIs instead. The job is in two clear parts: 1. Strip out the old Blade views, routes, and related assets so the backend is a clean, API-only service. 2. Adjust, extend, or refactor the current endpoints so the new SPA connects seamlessly. The Project must be connected properly to both platforms. You can use the frontend from DreamsPOS and the backend from the provided files. Key context for you: • New frontend modules: User Dashboard, Vendor Dashboard and Admin Panel • The Admin Panel must surface an Analytics Dashboard, so the backend must supply any missing metrics or aggregated data. • Authentication, role checks, pagination, and error handling must work exactly as they do now (Laravel Sanctum is in place). • All responses should be JSON, following existing response formats. Deliverables I expect: • Updated Laravel project (routes, controllers, tests) with the removed obsolete frontend. • Any new or modified API endpoints documented via Swagger or Postman collection. • Environment-agnostic setup instructions so the frontend team can run the API locally or on staging without surprises. • Final smoke test demonstrating the User Dashboard and Admin Panel hitting live endpoints for typical flows (login, data fetch, analytics refresh). Tools in play: Laravel 10, PHP 8.2, MySQL, Git. Please keep the commits granular and push them to a private repo, which I’ll provide. We have strict delivery policies. Please ensure we need the project's delivery by 18th Oct 2025. Please accept that the project is comfortable in delivering the project promptly. Let's start immediately if you’re comfortable with Laravel internals and REST best practices and can move quickly.