Format integer quality thousandths as a minimal RFC qvalue spelling between zero and one.

• Prepare the supplied thousandths fields for this operation.
• Compare the complete example with the representation used by your own input before carrying the result into another step.

1. Enter thousandths. Use the exact text syntax, units and index conventions explained below.
2. Run the tool. If input validation fails, correct the supplied fields before interpreting any result.
3. Read result.value. Interpret false, null and empty lists using the distinctions below; they can be valid outputs.

Require thousandths as an integer from 0 to 1,000. Emit 0 or 1 at the endpoints; otherwise emit a three-place fractional spelling and remove trailing zeros.^[1]

• No q= prefix, header item or preference ordering is added. Only a qvalue token is formatted.
• Every declared top-level field is required and unexpected fields are rejected. Numeric inputs must be finite; ordinary text fields are bounded to 8,192 UTF-16 code units, with tighter operation-specific limits where stated.
• String lists have at most 128 entries of at most 128 code units; matrices have at most 128 rows and columns. Larger numeric lists and parsed JSON have separate bounded budgets. Nonfinite results and excessively large serialized outputs are rejected.
• Indexes are zero-based and spans have an exclusive end unless explicitly stated otherwise. A valid false, null or empty-list result is distinct from malformed input.

Use a complete protocol or URL parser when interpreting a whole message or address. Preserve raw spelling when required and distinguish HTTP token grammar, URL path normalization and form-style query decoding.

• HTTP Quality Thousandths Parser

  Parse strict HTTP qvalue syntax into exact integer thousandths; no signs, exponent, whitespace or more than three decimals.

• HTTP Content Length Decimal Parser

  Parse Content-Length as exact unsigned ASCII decimal text without unsafe numeric conversion, signs, whitespace or exponent syntax.