Add provider tag verification

docs/FORWARD_PHASE_PLAN.md

@@ -33,6 +33,7 @@ The goal is not to clone Field Nation. The goal is to keep the useful operationa
 - Provider and buyer directories use text-based filters instead of normalized category, skill, coverage, remote, rating, and reliability filters.
 - Work-order lists are card-based and lack the dense assigned/available-work table that worked well in Field Nation.
 - Work-order detail now supports contact/support failure logging and first-class change requests, but schedule update requests, running-late records, post-work tag verification, and general report-problem records still need a dedicated workflow.
+- Work-order detail now supports contact/support failure logging, first-class change requests, and post-work provider tag verification; schedule update requests, running-late records, and general report-problem records still need dedicated workflows.
 - Disputes and votes now have reason codes, but quorum rules, visibility rules, and deeper evidence timelines still need a future pass.
 - Reviews exist, but there is no review response, report flow, edit window, moderation queue, category definitions page, or imported/native reputation distinction in the UI.
 - Universal ratings are flexible, but category names are arbitrary strings and not governed by a taxonomy.
@@ -420,7 +421,7 @@ Implementation status:
 - Added provider maximum technician level and self-declared tags in profile editing.
 - Added buyer job technician-level selection and scope mismatch risk detection for smart-hands jobs that include troubleshooting or certification requirements.
 - Added provider directory filters for technician level and taxonomy tag.
-- Deferred buyer post-work tag endorsement/disagreement to the next verification pass.
+- Added buyer post-work tag endorsement/disagreement with buyer-endorsed evidence updates on provider profiles.
 
 ## Phase 10 - Import Tooling And Marketplace History
 
@@ -717,11 +718,10 @@ Provider-protection rules:
 
 ## Recommended Immediate Sequence
 
-1. Post-work provider tag verification: buyer endorsement/disagreement with self-declared level and tags after completed work orders.
-2. Phase 11A: mobile-safe API endpoints for onsite work-order actions.
-3. Phase 12A: notification preference UI and event-channel controls.
-4. Phase 13A: audit logs and moderation/operations queues.
-5. Phase 14A: deployment/scaling hardening.
+1. Phase 11A: mobile-safe API endpoints for onsite work-order actions.
+2. Phase 12A: notification preference UI and event-channel controls.
+3. Phase 13A: audit logs and moderation/operations queues.
+4. Phase 14A: deployment/scaling hardening.
 
 ## Key Design Commitments
 

docs/ROADMAP.md

@@ -20,6 +20,7 @@ Provider Exchange is a Laravel application for a provider-centered field-service
 - Normalized starter taxonomy for work categories, specialties, skills, tools, certifications, and provider tag evidence sources.
 - Explicit technician level ladder from smart hands through project lead.
 - Guided imported-history records for Field Nation, WorkMarket, and similar platforms with privacy controls, selected review excerpts, metrics, proof attachments, and admin verification status.
+- Post-work provider tag verification for completed work orders, including buyer-confirmed level evidence, confirmed/disputed declared tags, suggested tags, and buyer-endorsed profile tag evidence.
 - Configurable attachment storage policy with upload root, disk, size cap, MIME allowlist, image previews, file metadata, and deletion.
 - Mutual reviews with category metrics.
 - Peer-review disputes with comments, evidence, structured recommendations, and public vote breakdowns.
@@ -57,11 +58,11 @@ Provider Exchange is a Laravel application for a provider-centered field-service
 
 ## Phase Checkpoint
 
-Phases 1-10A have been implemented locally through the guided imported-history pass. The next active planning block is:
+Phases 1-10B have been implemented locally through post-work provider tag verification. The next active planning block is:
 
 8. API/mobile prep: token-scoped endpoints, versioned API resources, geolocation check-in groundwork, contact/support failure logging, and mobile-safe work-order actions.
-9. Post-work verification: buyer endorsement or disagreement with provider level/tags after completed work orders, earned evidence upgrades, and transparent tag history.
-10. Notification preference UI and event-channel controls.
+9. Notification preference UI and event-channel controls.
+10. Admin operations, audit logs, and deployment hardening.
 
 Work-order safeguards to carry into the next implementation passes:
 
@@ -125,6 +126,14 @@ Guided imported-history implementation completed:
 - Admin dashboard includes an imported-history verification queue.
 - Imported history remains separate from native TSE reputation.
 
+Post-work provider tag verification completed:
+
+- Buyers and admins can verify provider level/tag evidence after a work order is completed, buyer approved, or closed.
+- Verification records store the provider's declared level, the observed level, a level verdict, confirmed tags, disputed tags, buyer-suggested tags, and notes.
+- Confirmed declared tags upgrade their provider-profile evidence source to `buyer_endorsed`.
+- Provider profiles now show recent completed-work competency evidence separately from imported history and five-star reviews.
+- Providers cannot self-verify their tags from a work order.
+
 Available-work safeguards to carry into directory and job-list phases:
 
 - Available jobs should expose pay type, provider terms, schedule type, work type, rough location, buyer reliability, support/contact certification, scope clarity status, and request/quote count.