You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
docs/usermanuals/en/reference/json-output.md: stale — The export example shows quant 'q4_k_m' written to model.q4_k_m.gguf, and the table lists 7 keys. (DOC-D3B03-008) #220
Consumers believe they received a q4_k_m GGUF and ship an f16 intermediate, missing the required llama-quantize step.
Primary finding
DOC-D3B03-008 — docs/usermanuals/en/reference/json-output.md: stale — The export example shows quant 'q4_k_m' written to model.q4_k_m.gguf, and the table lists 7 keys.
The document says. The export example shows quant 'q4_k_m' written to model.q4_k_m.gguf, and the table lists 7 keys.
What the code does. K-quants (q2_k, q3_k_m, q4_k_m, q5_k_m), including the default q4_k_m, are written as an intermediate .f16.gguf with quant='f16', requested_quant='q4_k_m', manual_step_required=true and a followup_command (llama-quantize). The envelope also carries requested_quant, manual_step_required and followup_command, which the page does not document.
User impact. Consumers believe they received a q4_k_m GGUF and ship an f16 intermediate, missing the required llama-quantize step.
Proposed correction. Document requested_quant, manual_step_required and followup_command. Change the example to a K-quant request that yields output_path '...model.f16.gguf', quant 'f16', manual_step_required: true. State that only q8_0/f16 are produced directly.
Turkish mirror. the Turkish page has the same error; fix both in the same PR
Acceptance criteria
Each statement is re-checked against the code at fix time.
Documentation listed above is corrected in English and in its Turkish mirror in the same PR.
Every finding in this issue is resolved or explicitly closed with a reason.
Found by the October 2026 ForgeLM code and documentation review against commit cab2947. Code links point at that commit; line numbers may have moved since. Finding IDs (CR-…, DOC-…, TECH-…) are stable references for this backlog.
Activity