llama.cpp b12022 forwards extra_params through Responses

A local endpoint returning text does not prove that every sampling parameter reached inference. Within this collection window, llama.cpp merged PR #30959 and listed the fix in b12022: /v1/responses now honors extra_params, allowing settings such as seed and min_p to be forwarded to the server. This is an API behavior fix, not a model release or a performance claim.

1. Separate proposal time from delivery. The PR was opened on October 22, merged on October 31 at 18:08 UTC, and listed in b12022 at 18:59 UTC. The merge and release are the new events. The author says documentation was updated and tests were not added in this PR; that is not evidence of comprehensive client regression coverage.

2. Verify each boundary. An existing endpoint, an accepted request, a forwarded parameter, and a backend honoring that parameter are separate checks. Preserve the full request, server version and logs when diagnosing sampling behavior. HTTP success and a plausible answer alone do not establish that configuration took effect.

3. Upgrade in isolation. Compare identical requests with the same model, template and remaining sampling settings. Responses support does not imply complete parity with every Chat Completions extension. A fixed seed is not a guarantee of byte-identical output across versions.

AraoAI verified the upstream merge and release, but has not independently reproduced this path on hardware. No speed or capability claim is made. The endpoint name is an entry point; parameter behavior is the acceptance criterion.

Source: https://github.com/ggml-org/llama.cpp/pull/30959 Release: https://github.com/ggml-org/llama.cpp/releases/tag/b12022