nemo-relay-instrument-calls

# Instrument Tool And LLM Calls Use this skill when an app already has tool functions or model/provider calls and needs to run them through NeMo Relay correctly. Keep the original callable behavior stable while adding Relay lifecycle capture. ## Default Guidance - Put a scope around the natural agent, request, workflow, or graph boundary. - Use managed execution APIs first: - Rust: `tool_call_execute(ToolCallExecuteParams::builder()...)`, `llm_call_execute(LlmCallExecuteParams::builder()...)` - Python: `tools.execute(...)`, `llm.execute(...)` - Node.js: `toolCallExecute(...)`, `llmCallExecute(...)` - Go: `tools.Execute(...)`, `llm.Execute(...)` or the top-level wrappers - Use manual lifecycle APIs only when the host framework cannot be wrapped by the managed execute helpers. ## Embedded Runtime Semantics - Managed tool and LLM execution runs conditional-execution guardrails first on the raw input. If rejected, the runtime emits a standalone mark event and does not run request intercepts or the callable. - Request intercepts run after conditional guardrails and rewrite the real input that reaches execution intercepts and the callback. - Sanitize-request guardrails affect emitted start-event payloads only. They do not rewrite the caller-visible request or arguments. - Execution intercepts wrap the callback with the middleware `next` pattern and may short-circuit by returning their own result. - Sanitize-response guardrails affect emitted end-event p...