Hard-delete Care remote Queue adapter (Phase 5).

Care Queue Engine is the only path; remove QueueClient, driver config, and remote HTTP tests.

Co-authored-by: Cursor <cursoragent@cursor.com>

docs/care-queue-engine-and-specialty-plan.md

@@ -1,6 +1,6 @@
 # Care Queue Engine + Specialty Modules — Unified Plan
 
-**Status:** Phase 4 complete (Queue healthcare removed); Phase 5 next  
+**Status:** Phase 5 complete (Care remote Queue adapter deleted)  
 **Date:** 2026-07-18  
 **Repos:** ladill-care (primary), ladill-queue (healthcare removal)  
 **Related:** `docs/specialty-module-design-standard.md`
@@ -9,7 +9,7 @@
 
 ## Phase 1 notes (implementation)
 
-- Config: `CARE_QUEUE_DRIVER=native` (default) | `remote` (legacy Ladill Queue HTTP)
+- Config: Care Queue Engine only (in-app tables + `CareQueueEngine`)
 - Tables: `care_service_queues`, `care_service_points`, `care_queue_tickets`
 - Service: `App\Services\Care\CareQueueEngine`
 
@@ -34,7 +34,14 @@
 - Queue marketing/settings copy now Frontdesk & POS only; `assigned_only` kept as generic routing
 - DemoWorld: Care receptionist apps no longer include `queue`; dedicated Queue operators (`demo-*-queue@ladill.com`)
 - Care upgrade banner no longer lists Ladill Queue as a Pro dependency
-- Phase 5 still deletes Care’s remote `QueueClient` adapter
+
+## Phase 5 notes (implementation)
+
+- Deleted `QueueClient`, remote provisioner/bridge arms, Ladill Queue console views/presenter
+- Removed `CARE_QUEUE_DRIVER` / `QUEUE_API_*` from Care config and `.env.example`
+- Bridge / provisioner / specialty activate always use Care Queue Engine tables
+- `care:queue-sync-tickets` remains (native backfill only)
+- Tests assert local `CareQueueTicket` / `CareServiceQueue` (no Queue HTTP fakes)
 
 ---