core: content_blocks raises TypeError on a v0 multimodal block that carries an id
Reading content_blocks on a legacy v0 multimodal block with an id raises TypeError due to duplicate id keyword argument in _convert_legacy_v0_content_block_to_v1.

Affected version
Reports that share this version, grouped in one feed.
Reading content_blocks on a legacy v0 multimodal block with an id raises TypeError due to duplicate id keyword argument in _convert_legacy_v0_content_block_to_v1.
AsyncBaseTracer in langchain-core fails to forward the `name` argument to `_create_tool_run` and the `response` argument to `_errored_llm_run`, causing async tracers (including `with_alisteners`) to record incorrect run names and lose partial LLM outputs on streaming errors, unlike their sync counterparts.
When an AIMessage has tool_calls explicitly set to an empty list while additional_kwargs still contains the original OpenAI tool call payload, the _backwards_compat_tool_calls validator treats the empty list as missing and re-parses the additional_kwargs, causing the cleared tool calls to reappear after deserialization or model reconstruction.
The mustache renderer in langchain-core miscounts section nesting when an inverted section with the same key is nested inside a regular list section. This leads to silently wrong output (e.g., '[[]' instead of '[a][b]') or an IndexError. The depth counter used to handle nested regular sections only increments for 'section' tokens, not for 'inverted section' tokens, causing the inner closing tag to be misinterpreted as the outer section's end.
`InMemoryVectorStore` does not override `_select_relevance_score_fn`, so `similarity_search_with_relevance_scores` and the `similarity_score_threshold` retriever raise `NotImplementedError` even though the store computes cosine similarity internally.
Blob.as_string() uses the default 'utf-8' encoding, which does not strip a UTF-8 byte order mark (BOM). Files written by Windows tools (Notepad, PowerShell, etc.) often include a BOM, and this BOM is returned as part of the string, contaminating downstream processing such as Markdown heading parsing.
In langchain-core's test_convert_to_openai_data_block, the Responses API file/url case sets up test data but never calls the conversion function or asserts the result, leaving the branch untested. The fix adds the missing call and assertion.
PromptTemplate.from_template("Value: {}") is accepted silently, reports an empty input variable, and then raises IndexError on every .format() call. It should be rejected at creation time with a clear ValueError, consistent with the all-digit `{0}` case.