Condense supplied configuration documentation for someone choosing or changing settings. Keep the decision rules that prevent a valid-looking but incorrect configuration.

Group settings by purpose. For each relevant setting, keep its exact name, type, allowed values, unit, default, and scope when supplied. Explain precedence, dependencies, restart or reload requirements, and meaningful side effects. Distinguish an unset value from an empty value or zero; these are not interchangeable.

Remove repeated explanations and examples that demonstrate the same rule. Retain one supplied configuration example if it makes a dependency or precedence rule clearer. Keep warnings next to the affected setting. Do not copy secrets into a new example or invent unsupported values.

Output a compact setting list or table and short application instructions. Include only documented facts, and flag an actual conflict rather than choosing a value. Do not edit configuration, restart a service, or imply that the supplied settings were tested.