Complete workplan state model cleanup

dashboard/src/docs/workstreams.md

@@ -20,14 +20,17 @@ as filters change.
 
 | Workstation | Meaning |
 |---|---|
-| **active** | Work in progress or ready to start |
+| **proposed** | Plan exists, but needs review against current repo state |
+| **ready** | Reviewed and ready to execute |
+| **active** | Work is in progress |
 | **blocked** | Stored blocker label; the State Hub can also derive blocked state from unmet exit assertions |
-| **completed** | Formally accepted after custodian review (shown as **accepted** in the overview chart) |
-| **archived** | Closed without completion; no longer relevant |
+| **backlog** | Intentionally parked for later |
+| **finished** | Implementation is complete |
+| **archived** | Closed historical record |
 
 See [Workstream Lifecycle](/docs/workstream-lifecycle) for the full task-flow
-model including derived states (finished, stalled, oldies) and assertion-based
-blocking.
+model including derived health labels (`needs_review`, `stalled`) and
+assertion-based blocking.
 
 ---
 
@@ -91,7 +94,7 @@ create_workstream(
   topic_id    = "<uuid>",
   title       = "Build user authentication",
   description = "JWT-based auth, refresh tokens, middleware",
-  status      = "active",
+  status      = "ready",
   owner       = "human",
   due_date    = "2026-04-01"
 )
@@ -102,7 +105,7 @@ Via REST:
 ```bash
 curl -X POST http://127.0.0.1:8000/workstreams/ \
   -H "Content-Type: application/json" \
-  -d '{"topic_id": "<uuid>", "title": "…", "status": "active"}'
+  -d '{"topic_id": "<uuid>", "title": "…", "status": "ready"}'
 ```
 
 ---
@@ -111,7 +114,7 @@ curl -X POST http://127.0.0.1:8000/workstreams/ \
 
 ```
 get_flow_state(entity_type="workstream", entity_id="<uuid>")
-advance_workstation(entity_type="workstream", entity_id="<uuid>", target_workstation="completed")
+advance_workstation(entity_type="workstream", entity_id="<uuid>", target_workstation="finished")
 ```
 
 Movement is flow-aware: the task-flow engine evaluates the target