From 1242c52360238957bfbca780ae332b3816324f22 Mon Sep 17 00:00:00 2001 From: Sam & Claude Date: Sun, 21 Jun 2026 22:46:07 +0200 Subject: [PATCH] docs(zot-rpc): backtick event identifiers in the verdict The bare underscored names (tool_call, tool_use_*, text_delta, assistant_*) were read as markdown emphasis and mangled by prettier; wrap them in code spans so they render literally and stay prettier-immune. Co-Authored-By: Claude Opus 4.8 --- docs/ZOT-RPC-TRANSCRIPT.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/ZOT-RPC-TRANSCRIPT.md b/docs/ZOT-RPC-TRANSCRIPT.md index a24b6dc..30f641b 100644 --- a/docs/ZOT-RPC-TRANSCRIPT.md +++ b/docs/ZOT-RPC-TRANSCRIPT.md @@ -64,7 +64,7 @@ Wire format confirmed: bare event objects, no JSON-RPC envelope. Glasspane's parser shape is correct. The session-lifecycle events (turn_start, turn_end, error, done, user_message, response) are validated against real output. -Tool-lifecycle events (tool*call, tool_use*_, text*delta, assistant*_, tool_result) +Tool-lifecycle events (`tool_call`, `tool_use_*`, `text_delta`, `assistant_*`, `tool_result`) are NOT yet validated — the API key was a placeholder (DeepSeek returned 401 before reaching the agent loop). A re-run with a valid DEEPSEEK_API_KEY is needed to capture a real tool call before the driver can trust those mappings.