inchang-ing 4ced9dddf5

fix(vllm): fall back to legacy reasoning_content field (#6048) ...

* fix(vllm): fall back to legacy reasoning_content field

* fix(vllm): document the reasoning_content fallback and pin precedence

The previous change set left the docs describing the provider as
preserving only `reasoning`:

- the module docstring now mentions the legacy `reasoning_content`
  wire field, and the vLLM Provider bullet in models/AGENTS.md is
  extended to match the repo's documentation-update policy;

- _create_chat_result evaluated choice["message"] twice, once per key;
  hoist it into a single local and read both keys from it;

- two regression tests pin that a payload carrying both fields keeps
  `reasoning`, so a future refactor cannot silently invert the
  precedence (the existing tests only covered the absent-`reasoning`
  case).

Reported-by: willem-bd

* refactor(vllm): share reasoning fallback and cover follow-up payloads

---------

Co-authored-by: inchang-ing <197932532+inchang-ing@users.noreply.github.com>
Co-authored-by: Willem Jiang <willem.jiang@gmail.com>

2026-10-01 08:12:32 +08:00

..

deerflow

fix(vllm): fall back to legacy reasoning_content field (#6048)

2026-10-01 08:12:32 +08:00

pyproject.toml

feat(authz): add plugin resource targets, provenance, action and management enforcement (#5842)

2026-09-25 14:46:12 +08:00