chore: update protocol references to v0.4 (#14)

## Summary
- update CLI, SDK, bridge, and docs to reference the MEW Protocol v0.4
release
- bump runtime constants to `mew/v0.4` across agents, clients, and tests
- add migration notes calling out remaining gaps between the
implementation and the v0.4 specification

## Testing
- npm run build
- ./tests/run-all-tests.sh --no-llm --verbose

------
https://chatgpt.com/codex/tasks/task_e_68d75b23555c83259993b4bf0bee6e06

Author: rjcorwin

AGENTS.md

@@ -17,7 +17,7 @@ sdk/typescript-sdk/    # Core packages
 bridge/             # MCP-MEW bridge
 cli/               # Command-line tool
 tests/             # Integration tests (scenario-*)
-spec/              # Protocol specs (v0.3=current, draft=next)
+spec/              # Protocol specs (v0.4=current, draft=next)
 docs/              # Guides in architecture/, guides/, bugs/, progress/
 ```
 

CLAUDE.md

@@ -17,7 +17,7 @@ sdk/typescript-sdk/    # Core packages
 bridge/             # MCP-MEW bridge
 cli/               # Command-line tool
 tests/             # Integration tests (scenario-*)
-spec/              # Protocol specs (v0.3=current, draft=next)
+spec/              # Protocol specs (v0.4=current, draft=next)
 docs/              # Guides in architecture/, guides/, bugs/, progress/
 ```
 

MIGRATION.md

@@ -0,0 +1,13 @@
+# MEW Protocol v0.4 Migration Notes
+
+The repository now references the v0.4 protocol specification. The following implementation gaps remain and should be addressed in follow-up work before claiming full compliance with the v0.4 MEW Protocol.
+
+## CLI
+- The built-in `client connect` and `agent start` workflows still send a legacy `{ type: 'join' }` handshake instead of a v0.4 MEW envelope. The gateway continues to translate this legacy format, but participants should emit full envelopes going forward.
+- `gateway` back-fills envelope fields (protocol, id, timestamps) when participants omit them. Under the v0.4 spec every message on the wire should already be a complete envelope.
+- The note-taker template agent uses the rejected `system/join` message kind. A compliant join/authorization sequence needs to be defined for v0.4.
+
+## SDK
+- The shared `Envelope` type still allows `correlation_id` to be a single string for backward compatibility, whereas v0.4 requires an array of strings. Client code should emit arrays once the ecosystem is ready.
+
+If additional incompatibilities are discovered while adopting the v0.4 protocol, add them here so the work can be prioritized.

README.md

@@ -49,9 +49,9 @@ The **proposal mechanism** ensures humans stay in control. New agents start with
 
 ## 📦 Current Version
 
-**v0.3** - Released 2025-01-09 🎉
+**v0.4** - Released 2025-09-26 🎉
 
-MEW Protocol is in experimental phase (v0.x) with breaking changes allowed between versions. See [spec/v0.3/SPEC.md](/spec/v0.3/SPEC.md) for the current specification.
+MEW Protocol is in experimental phase (v0.x) with breaking changes allowed between versions. See [spec/v0.4/SPEC.md](/spec/v0.4/SPEC.md) for the current specification.
 
 ## 🚀 Quick Start
 
@@ -89,9 +89,9 @@ That's it! MEW guides you through setting up your workspace with:
 
 ## 📚 Learn More
 
-- 📋 [Current Specification (v0.3)](/spec/v0.3/SPEC.md)
+- 📋 [Current Specification (v0.4)](/spec/v0.4/SPEC.md)
 - 📝 [Draft Specification (next version)](/spec/draft/SPEC.md)
-- 🏗️ [Architecture Decision Records](/spec/v0.3/decisions/)
+- 🏗️ [Architecture Decision Records](/spec/v0.4/decisions/)
 - 📜 [Changelog](/CHANGELOG.md)
 
 ## 🐈 Why "MEW"?

bridge/spec/draft/SPEC.md

@@ -35,7 +35,7 @@ Out of scope:
 MEW Space
     │
     ├── Gateway (WebSocket)
-    │      ↕ MEW Protocol v0.3
+    │      ↕ MEW Protocol v0.4
     │
     ├── MCP Bridge Process (@mew-protocol/bridge)
     │   ├── MEWParticipant (SDK base class)
@@ -145,7 +145,7 @@ Identifies this participant as an MCP bridge (required for gateway to use bridge
 ```javascript
 // MEW Request (incoming)
 {
-  "protocol": "mew/v0.3",
+  "protocol": "mew/v0.4",
   "id": "req-123",
   "from": "client",
   "to": ["filesystem"],
@@ -164,7 +164,7 @@ Identifies this participant as an MCP bridge (required for gateway to use bridge
 ```javascript
 // MEW Request (incoming)
 {
-  "protocol": "mew/v0.3",
+  "protocol": "mew/v0.4",
   "id": "req-456",
   "from": "client",
   "to": ["filesystem"],
@@ -200,7 +200,7 @@ Identifies this participant as an MCP bridge (required for gateway to use bridge
 
 // MEW Response (automatic from MEWParticipant)
 {
-  "protocol": "mew/v0.3",
+  "protocol": "mew/v0.4",
   "id": "resp-789",
   "from": "filesystem",
   "to": ["client"],
@@ -437,7 +437,7 @@ Log categories:
 
 ## References
 
-- [MEW Protocol Specification v0.3](../../spec/v0.3/SPEC.md)
+- [MEW Protocol Specification v0.4](../../spec/v0.4/SPEC.md)
 - [MCP Specification](https://modelcontextprotocol.org)
 - [MEW SDK Documentation](../../sdk/spec/draft/SPEC.md)
 - [Test Scenarios](../../tests/scenario-7-mcp-bridge/)

cli/spec/CHANGELOG.md

@@ -11,7 +11,7 @@
 
 ### Changed
 - Updated all references from MEUP to MEW protocol
-- Updated protocol version from v0.2 to v0.3
+- Updated protocol version from v0.2 to v0.4
 - Enhanced participant resolution with multiple fallback strategies
 
 ### Features

cli/spec/draft/SPEC.md

@@ -760,7 +760,7 @@ ls -la .mew/tokens/
 
 ## FIFO Message Format
 
-Messages sent to/from FIFOs use MEW v0.3 protocol format.
+Messages sent to/from FIFOs use MEW v0.4 protocol format.
 
 **Input (to fifo-in):**
 Simplified format - CLI adds protocol envelope fields:
@@ -774,10 +774,10 @@ Simplified format - CLI adds protocol envelope fields:
 ```
 
 **Output (from fifo-out):**
-Full MEW v0.3 envelope:
+Full MEW v0.4 envelope:
 ```json
 {
-  "protocol": "mew/v0.3",
+  "protocol": "mew/v0.4",
   "id": "msg-123",
   "ts": "2025-01-05T12:00:00Z",
   "from": "other-agent",
@@ -897,7 +897,7 @@ defaults:
 
 #### Capability Patterns
 
-Capabilities use JSON pattern matching as defined in MEW v0.3:
+Capabilities use JSON pattern matching as defined in MEW v0.4:
 
 **Simple patterns:**
 ```yaml

cli/spec/draft/decisions/accepted/005-iui-interactive-ui-architecture.md

@@ -27,9 +27,9 @@ This debug mode should be:
 
 Show only JSON messages, require full JSON input:
 ```
-< {"protocol":"mew/v0.3","kind":"system/welcome",...}
-> {"protocol":"mew/v0.3","kind":"chat","payload":{"text":"hello"}}
-< {"protocol":"mew/v0.3","kind":"chat","from":"echo",...}
+< {"protocol":"mew/v0.4","kind":"system/welcome",...}
+> {"protocol":"mew/v0.4","kind":"chat","payload":{"text":"hello"}}
+< {"protocol":"mew/v0.4","kind":"chat","from":"echo",...}
 ```
 
 **Pros:**
@@ -174,7 +174,7 @@ Verbose mode (`/verbose` command) shows full JSON:
 ```
 [10:23:45] → you chat
 {
-  "protocol": "mew/v0.3",
+  "protocol": "mew/v0.4",
   "id": "msg-123",
   "kind": "chat",
   "payload": {"text": "Hello"}
@@ -335,7 +335,7 @@ Active participants:
 > {"kind": "invalid"}
 [10:25:00] → you invalid
 {
-  "protocol": "mew/v0.3",
+  "protocol": "mew/v0.4",
   "id": "msg-456",
   "ts": "2025-01-10T10:25:00Z",
   "from": "human",
@@ -344,7 +344,7 @@ Active participants:
 
 [10:25:01] ← system system/error
 {
-  "protocol": "mew/v0.3",
+  "protocol": "mew/v0.4",
   "kind": "system/error",
   "payload": {
     "error": "Unknown message kind: invalid",

cli/spec/draft/decisions/accepted/008-f4x-safe-fifo-input-mechanism.md

@@ -431,4 +431,4 @@ For backward compatibility, FIFO mode is still supported but not recommended for
 - [Express.js Documentation](https://expressjs.com/)
 - [Unix Domain Sockets](https://man7.org/linux/man-pages/man7/unix.7.html)
 - [MEW CLI Specification](../SPEC.md)
-- [MEW Protocol v0.3 Specification](../../../../spec/v0.3/SPEC.md)
+- [MEW Protocol v0.4 Specification](../../../../spec/v0.4/SPEC.md)

cli/spec/draft/decisions/accepted/009-aud-approval-dialog-ux.md

@@ -182,7 +182,7 @@ This ensures users always know:
 When user selects "Yes, allow all X during this session", the CLI sends a capability grant message:
 ```json
 {
-  "protocol": "mew/v0.3",
+  "protocol": "mew/v0.4",
   "from": "human",
   "to": ["coder-agent"],
   "kind": "capability/grant",
@@ -452,7 +452,7 @@ function ProposalDialog({ proposal, onApprove, onDeny, sessionPermissions }) {
       case 2:
         // Grant capability for all similar operations
         const grant = {
-          protocol: "mew/v0.3",
+          protocol: "mew/v0.4",
           from: participantId,
           to: [proposal.from],
           kind: "capability/grant",