Route dashboard status changes through reconciliation

workplans/STATE-WP-0048-ui-state-change-reconciliation.md

@@ -138,7 +138,7 @@ when known.
 
 ```task
 id: STATE-WP-0048-T05
-status: todo
+status: done
 priority: medium
 state_hub_task_id: "04025e9f-b1cc-4b73-b95a-2a53bad6b360"
 ```
@@ -149,6 +149,12 @@ on human review, or out of sync.
 Done when a dashboard user can tell whether their state change has reached the
 repo file or still needs reconciliation.
 
+Result 2026-05-23: dashboard status controls now submit state changes through
+`POST /reconciliation/state-change` with `apply: true` instead of direct DB
+patches. The control reports `synced` when the repo file and cached DB state
+were updated, `queued` for deferred reconciliation, and `needs review` for
+human-confirmation cases.
+
 ## T06 - Add Conflict Handling
 
 ```task
@@ -181,6 +187,10 @@ Done when UI state changes are covered as first-class ADR-001 workflows.
 Progress 2026-05-23: added API tests for classify-only responses, safe
 write-through, missing-file deferral, and human-confirmation message creation.
 
+Progress 2026-05-23: routed dashboard status controls through the
+reconciliation API so UI-originated changes exercise the same write-through and
+deferred-record path as API clients.
+
 ## Acceptance Criteria
 
 - Dashboard state changes never create silent DB/file divergence.