Write env-tier tuning overrides (audited).

setup_factor / programming_factor / cycle_factor write the per-bin setup_efficiency / programming_efficiency / cycle_efficiency resolver overrides for every routable process bin at ENV tier; 1.0, their identity, clears the override. processes writes the same three cells for only the processes it names, applied after the flat fields.

The four REFA allowances (verteilzeit_pct, erholzeit_pct, ruestverteilzeit_pct, ruesterholzeit_pct) write the same per-bin overrides, over every bin that reads them.

The six sheet-nesting settings (edge_margin_mm, skeleton_web_mm, the three remnant thresholds and cut_to_size_increment_mm) each write their one cell of the sheet-nesting settings, which is where a sheet part's purchase reads them, and remnant_value_factor its cell of the material valuation policy, beside the remnant-credit answer that switches it on. The three bar stock settings (bar_length_mm, bar_clamp_remnant_mm and the shortest end that counts as a remnant, bar_remnant_min_l_mm) write theirs, which is where a turned part's bar is bought. Like the allowances, 0 is a statement and reset is the way back.

The four inspection_* fields write the platform-wide inspection constants in the global bin — the cells the cost sheet's Prüfung line lets a reader move. They read back on GET /environments/{env_id}/factors with their provenance and the platform value beside them, which is where every resolved factor is published; this endpoint's own read model stays the tuning knobs.

learning_rate writes the env's Wright rate. Every change lands an audit row.

null means "no statement" on every field of this body, and never a write: a client that serialises its whole model sends nulls for the knobs it is silent about, and that must leave them alone. Clearing a knob, so that it reads a parent environment's statement where one exists and else the platform default, is the named reset list — the allowances need it (0 is a statable allowance, so they have no identity value to send), and the multipliers accept it as the spelled-out equivalent of sending 1.0. The inspection cells are the one exception: an explicit null there clears the override, the contract the cost sheet's save dialog was built against.