Phase 1 UI system

docs/DEPLOYMENT.md

@@ -17,7 +17,7 @@ This document records the explicit runtime requirements and server changes for P
   - `mbstring`
   - `openssl`
   - `pdo`
-  - `pdo_sqlite` for the first live test deployment
+  - `pdo_sqlite` for SQLite test deployments and the default automated test suite
   - `session`
   - `tokenizer`
   - `xml`
@@ -28,6 +28,12 @@ This document records the explicit runtime requirements and server changes for P
   - `bootstrap/cache/`
   - the SQLite database file for SQLite test deployments.
 
+## Local Test Requirements
+
+- The default PHPUnit configuration uses an in-memory SQLite database, so whichever PHP runtime executes `php artisan test` must include `pdo_sqlite` and `sqlite3`.
+- On Windows, `php -m` should list both `PDO` and `pdo_sqlite`; otherwise the feature tests fail before reaching app code with `could not find driver`.
+- WSL Ubuntu is acceptable for local verification when Windows PHP is missing SQLite support, as long as WSL PHP has `pdo_sqlite` and `sqlite3`.
+
 ## Recommended Production Runtime
 
 - Nginx.

docs/INSTALL.md

@@ -31,6 +31,7 @@ APP_DIR=/var/www/technical-services-exchange bash /var/www/technical-services-ex
 ## Important Notes
 
 - The installer is a first-pass Ubuntu/Nginx helper, not a universal hosting panel installer.
+- Local and CI test runners need PHP SQLite support: `pdo_sqlite` and `sqlite3`.
 - Review `.env` before production use.
 - Configure real mail before inviting users.
 - Move sessions, cache, and queues to Redis before serious traffic.

docs/ROADMAP.md

@@ -29,12 +29,13 @@ Provider Exchange is a Laravel application for a provider-centered field-service
 - Payment remains direct between buyer and provider unless a compliant payment partner is deliberately added later.
 - Reputation should be mutual, transparent, and appealable through community review.
 - Dispute voting is a community reputation signal, not legal adjudication.
+- Runtime dependencies, UI components, and themes should stay open-source friendly. Avoid proprietary theme kits, unclear asset licenses, or dependencies that would restrict commercial, nonprofit, or community scaling.
 
 ## Next Build Phases
 
 1. Profile depth: richer galleries, equipment lists, certifications, insurance fields, service coverage maps, and imported review summaries.
 2. Directory quality: saved searches, better filtering, profile badges, availability signals, and stronger buyer/provider discovery pages.
-3. Work-order depth: checklist templates, required evidence rules, appointment windows, onsite timestamps, and change-request records.
+3. Work-order depth: checklist templates, required evidence rules, appointment windows, onsite timestamps, change-request records, and print/PDF export for work-order packets.
 4. Reputation refinement: rating category definitions, anti-abuse controls, edit windows, report flows, and moderation views.
 5. Dispute workflow: better evidence timelines, reason-coded votes, quorum/visibility rules, and admin/community moderation tools.
 6. Notifications: channel preferences, email templates, and event-specific subscription controls.
@@ -42,6 +43,7 @@ Provider Exchange is a Laravel application for a provider-centered field-service
 8. Import tooling: guided manual imports for Field Nation, WorkMarket, and similar profile/review history.
 9. Admin operations: audit logs, queue health, system status, content moderation, and backup/export workflows.
 10. Deployment hardening: production environment docs, queue worker setup, scheduler setup, storage policy, and server provisioning notes.
+11. License and runtime audit: generate and review PHP and JavaScript dependency license reports before adding external theme kits, map any risky package to a replacement, and keep required local/runtime extensions such as `pdo_sqlite` documented for testability.
 
 ## Scaling Risks To Track