#168: Home diagram claimed events.subscribe, which was never built
UnixSocketHerdrClient's own class doc says streaming methods (events.subscribe) 'keep their own long-lived connection and land in a later ticket'. The shipped path polls for status and delivers a turn with agent.prompt. The audit flagged this edge label and it was the last one left.
+1
-1
@@ -40,7 +40,7 @@ flowchart LR
|
||||
|
||||
OPUS -->|"MCP fleet_send (blocks)"| SRV
|
||||
W -.->|"MCP fleet_reply"| SRV
|
||||
CLI -->|"Unix socket<br/>send_text · events.subscribe"| HERDR
|
||||
CLI -->|"Unix socket<br/>agent.prompt · status polling"| HERDR
|
||||
HERDR -->|"drives PTY"| W
|
||||
W -->|"inference"| M
|
||||
|
||||
|
||||
Reference in New Issue
Block a user