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 <noreply@anthropic.com>
This commit is contained in:
parent
6b9222c746
commit
1242c52360
1 changed files with 1 additions and 1 deletions
|
|
@ -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.
|
||||
|
|
|
|||
Loading…
Add table
Reference in a new issue