feat: unified messaging v0.4.1 — work orders are messages

Everything is a message. Work orders use message_type: "work-order".
Check returns ALL messages — signal strength highlights, never hides.
New update-status action. Legacy task actions preserved for compat.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

CHANGELOG.md

@@ -1,5 +1,17 @@
 # Changelog
 
+## 0.4.1 (2026-03-20)
+
+### Features
+- **Unified messaging** — Work orders are now messages with `message_type: "work-order"`. No separate task actions needed. Everything flows through `send`, `check`, `respond`. Simplifies the API from 15 actions to 11 core actions (+ 4 legacy compatibility shims).
+- **Open visibility** — Check returns ALL unread messages regardless of agent identity. Signal strength HIGHLIGHTS what's relevant to you but NEVER hides messages. No more missing work orders because they were sent as the wrong type.
+- **New `update-status` action** — Update status on any message (replaces `claim-task` + `update-task`). Works on work-orders but also any message that needs status tracking.
+- **Legacy compatibility** — Old `post-task`, `claim-task`, `list-tasks`, `update-task` actions still work (internally redirect to the unified system). No breaking changes for existing agents.
+
+### Fixes
+- **Ivonne → Codex routing bug** — Ivonne sent a task as a regular message, Codex checked for tasks, didn't find it. Fixed by eliminating the distinction entirely.
+- **Identity-based hiding** — Agents checking as "claude-code" couldn't see messages addressed to their persona name. Fixed by returning ALL messages and using signal strength for highlighting only.
+
 ## 0.4.0 (2026-03-19)
 
 ### Features

package.json

@@ -1,7 +1,7 @@
 {
   "$schema": "https://json.schemastore.org/package.json",
   "name": "whiteport-design-studio",
-  "version": "0.4.0",
+  "version": "0.4.1",
   "description": "Whiteport Design Studio - Strategic design methodology for AI-powered workflows",
   "keywords": [
     "design",

src/skills/design-space/SKILL.md

@@ -220,54 +220,38 @@ See the full conversation thread for a message.
 }
 ```
 
-### Work Orders
+### Work Orders (via unified messaging)
 
-Post, claim, list, and update tasks across agents.
+Work orders are just messages with `message_type: "work-order"`. No separate actions needed.
 
-**Post a work order:**
+**Send a work order:**
 ```json
 {
-  "action": "post-task",
+  "action": "send",
   "from_agent": "saga",
+  "to_agent": "codex",
+  "message_type": "work-order",
   "title": "Implement login flow",
   "content": "Based on scenario SC-03, implement the login/signup flow...",
-  "assignee": "codex",
-  "project": "ugc-app",
-  "priority": "normal"
-}
-```
-
-**List work orders:**
-```json
-{
-  "action": "list-tasks",
   "project": "ugc-app",
   "status": "ready"
 }
 ```
 
-**Claim a work order:**
+**Update status on any message:**
 ```json
 {
-  "action": "claim-task",
+  "action": "update-status",
-  "task_id": "<uuid>",
+  "message_id": "<uuid>",
-  "agent_id": "codex"
-}
-```
-
-**Update work order status:**
-```json
-{
-  "action": "update-task",
-  "task_id": "<uuid>",
   "agent_id": "codex",
-  "status": "done",
+  "status": "in-progress"
-  "result": "Implemented in PR #42"
 }
 ```
 
 **Status lifecycle:** `ready` → `in-progress` → `done` / `blocked`
 
+Work orders appear in the regular message stream — check returns them alongside all other messages. Signal strength highlights relevance but nothing is hidden.
+
 ### Visual Capture (desktop only)
 
 Capture a screenshot or design with visual context. Requires image data.