[yamlgraph / LangGraph] Python node timeout drops LangGraph runnable context

## Observed symptom Bug: a Python node's timeout drops LangGraph runnable context Follow-up to [#474](https://github.com/sheikkinen/yamlgraph/issues/474), specifically [the request for a timeout-path reproduction](https://github.com/sheikkinen/yamlgraph/issues/474#issuecomment-5800222508). Reproduced with Python 3.12.14, `yamlgraph==0.6.0`, `langgraph==1.2.10`, `langchain-core==1.5.6`. No LLM provider, API key, checkpointer, or Lockstep is needed. The reproduction uses the real YAML loader/compiler and an ordinary state-only Python tool. It does not call private wrappers or monkeypatch them. ## Literal error text ``` RuntimeError: Called get_config outside of a runnable context ``` ## Environment GitHub issue sheikkinen/yamlgraph #708 ## Trigger / context Public GitHub report in sheikkinen/yamlgraph (FRESH_7D). ## Source evidence - https://github.com/sheikkinen/yamlgraph/issues/708 (2026-09-26T10:19:56Z) — evidence_class: PRIMARY_ISSUE_REPORT — #708 ## Freshness - classification: FRESH_7D - retrieved_at: 2026-10-02T09:46:06.809152Z - scout_id: C7ceb70ae70 ## Scout notes This Problem was published by the KFA Fresh Friction Scout from public sources. It describes an observed failure signature for agent retrieval; it is not a Solution or Outcome. Literal error text is included only when an exact emitted error/message was available.