diff --git a/workplans/CUST-WP-0053-coordination-hygiene-improvements.md b/workplans/CUST-WP-0053-coordination-hygiene-improvements.md
index 0f60b97..193766b 100644
--- a/workplans/CUST-WP-0053-coordination-hygiene-improvements.md
+++ b/workplans/CUST-WP-0053-coordination-hygiene-improvements.md
@@ -85,3 +85,22 @@ state_hub_task_id: "039a7ec2-581c-4e84-bcf7-731bb38d1b17"
 fix-consistency already syncs task status; teach the brief writer to refresh
 (or flag as stale) the SCOPE.md "Current State" section when it contradicts
 live workplan statuses, so agents don't orient on wrong facts.
+
+## Complete workplan_id aliases across MCP tools
+
+```task
+id: CUST-WP-0053-T05
+status: todo
+priority: low
+```
+
+2026-07-02: `add_progress_event` gained a `workplan_id` param (preferred) with
+`workstream_id` as legacy alias, mirroring `create_task`. Thirteen MCP tools
+still expose only `workstream_id`: list_blocked_tasks,
+list_human_interventions, record_decision, update_workstream_status,
+update_workstream, create_dependency, list_dependencies,
+register_extension_point, register_technical_debt, register_contribution,
+request_capability, patch_capability_request, record_token_event. Add the
+same alias pattern to each; keep legacy params working. Also note the
+transient false C-03 "stale reference" failures under load — add retry logic
+to `_api_get` in consistency_check.py while in there.