corezoid-gitcall

# Corezoid Git Call A Git Call node runs your code (9 built-in languages, or a custom Docker image) in an isolated container as one step of a process. Each task is delivered to a `handle` function over JSON-RPC 2.0; the value you return becomes the payload of the next node. ## 1. When to use it — the selection rule Git Call is one of the most constrained nodes on the platform. Use it **only** when a step needs a capability that native nodes and a Code (`api_code`) node cannot provide — parsing a file, an external library, cryptography, or a custom runtime — **and** the work finishes comfortably within the observed runtime budget. For everything else use the native alternative. "One code block is easier to write" is not one of those capabilities. ### Runtime and resource constraints - **Observed execution deadline:** hosted sandbox measurements terminated the handler at approximately 60 s, wall-clock from the moment the task entered the node. Keep handler work comfortably below 50 s rather than relying on the exact cutoff, which is an observed platform behavior rather than a portable contract. On overrun the task was killed and routed to the error path (`__conveyor_git_call_return_type_tag__ = git_call_executing_error`, description `usercode: timeout`). In those measurements, inline cold and warm runs ended at the same point; custom images may have different startup overhead. - **Default resource allocation:** 50 MB RAM and 0.1 CPU from a pool shared by Gi...