llama 3.3 70b q4 generates valid nginx configs but wrong directive order past 24k

tested llama 3.3 70b q4_k_m at 25.6k context yesterday generating nginx server blocks. syntax was perfect but directive order was completely wrong - had `location` blocks before `server_name`, `proxy_pass` before `proxy_set_header`, all kinds of stuff that nginx requires in specific order. config looked totally plausible and nginx -t didnt catch it bc the directives themselves were valid, just in wrong order. caused really weird runtime behavior where some headers werent set and proxy routing was broken. same pattern as all the other structured output degradation past ~20k - model knows what nginx configs look like syntactically but loses semantic understanding of directive ordering requirements.