34a771bee33adb4a8a9207d5403ecf80fa6774f2
Protocol: - RunContextSchema added to api-types — attached to WsToolCall frames originating from batch runs; type/runId/agentId identify the run - WsRunCompleteSchema added — server sends this when a batch run ends Database: - agent_runs table: one row per run (id, agentId, status, startedAt, completedAt) - agent_run_actions table: one row per mutating tool call (verb: created/updated/deleted, entityType, entityId, entityTitle) Logging logic (backend-client.ts): - On tool_call with runContext: ensure agentRuns row exists, insert agentRunActions for insert/update/delete actions - On run_complete: update agentRuns status and completedAt Scheduler passes agentId in the trigger POST so the backend echoes it back in run_context for correct attribution. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
step 0.1 complete: Type-safe contracts for all backend communication and the batch/storage subsystem
Description
No description provided
Languages
TypeScript
97.9%
CSS
2%