Deploying to gh-pages from @ Klipper3d/klipper@2956c1e223 🚀

Config_Changes.html

@@ -1412,9 +1412,26 @@ are not backwards compatible. It is a good idea to review this
 document when upgrading the Klipper software.</p>
 <p>All dates in this document are approximate.</p>
 <h2 id="changes">Changes<a class="headerlink" href="#changes" title="Permanent link">&para;</a></h2>
-<p>20251122: An option <code>axis</code> has been added to <code>[carriage &lt;name&gt;]</code> sections
-for <code>generic_cartesian</code> kinematics, allowing arbitrary names for primary
-carriages. Users are encouraged to explicitly specify <code>axis</code> option now.</p>
+<p>20260109: The status value <code>{printer.probe.last_z_result}</code> is
+deprecated; it will be removed in the near future. Use
+<code>{printer.probe.last_probe_position}</code> instead, and note that this new
+value already has the probe's configured xyz offsets applied.</p>
+<p>20260109: The g-code console text output from the <code>PROBE</code>,
+<code>PROBE_ACCURACY</code>, and similar commands has changed. Now Z heights are
+reported relative to the nominal bed Z position instead of relative to
+the probe's configured <code>z_offset</code>. Similarly, intermediate probe x and
+y console reports will also have the probe's configured <code>x_offset</code> and
+<code>y_offset</code> applied.</p>
+<p>20260109: The <code>[screws_tilt_adjust]</code> module now reports the status
+variable <code>{printer.screws_tilt_adjust.result.screw1.z}</code> with the
+probe's <code>z_offset</code> applied. That is, one would previously need to
+subtract the probe's configured <code>z_offset</code> to find the absolute Z
+deviation at the given screw location and now one must not apply the
+<code>z_offset</code>.</p>
+<p>20251122: An option <code>axis</code> has been added to <code>[carriage &lt;name&gt;]</code>
+sections for <code>generic_cartesian</code> kinematics, allowing arbitrary names
+for primary carriages. Users are encouraged to explicitly specify
+<code>axis</code> option now.</p>
 <p>20251106: The status fields <code>{printer.toolhead.position}</code>,
 <code>{printer.gcode_move.position}</code>,
 <code>{printer.gcode_move.gcode_position}</code>, and

Load_Cell.html

@@ -1696,10 +1696,10 @@ macro. This requires setting up
 <p>Here is a simple macro that can accomplish this. Note that the
 <code>_HOME_Z_FROM_LAST_PROBE</code> macro has to be separate because of the way macros
 work. The sub-call is needed so that the <code>_HOME_Z_FROM_LAST_PROBE</code> macro can
-see the result of the probe in <code>printer.probe.last_z_result</code>.</p>
+see the result of the probe in <code>printer.probe.last_probe_position</code>.</p>
 <div class="highlight"><pre><span></span><code>[gcode_macro _HOME_Z_FROM_LAST_PROBE]
 gcode:
-<span class="w">    </span>{% set z_probed = printer.probe.last_z_result %}
+<span class="w">    </span>{% set z_probed = printer.probe.last_probe_position.z %}
 <span class="w">    </span>{% set z_position = printer.toolhead.position[2] %}
 <span class="w">    </span>{% set z_actual = z_position - z_probed %}
 <span class="w">    </span>SET_KINEMATIC_POSITION Z={z_actual}

Status_Reference.html

@@ -2529,10 +2529,18 @@ is defined):</p>
   during the last QUERY_PROBE command. Note, if this is used in a
   macro, due to the order of template expansion, the QUERY_PROBE
   command must be run prior to the macro containing this reference.</li>
-<li><code>last_z_result</code>: Returns the Z result value of the last PROBE
-  command. Note, if this is used in a macro, due to the order of
-  template expansion, the PROBE (or similar) command must be run prior
-  to the macro containing this reference.</li>
+<li><code>last_probe_position</code>: The results of the last <code>PROBE</code> command. This
+  value is encoded as a <a href="#accessing-coordinates">coordinate</a>. The
+  probe hardware estimates that if one were to command the toolhead to
+  XY position <code>last_probe_position.x</code>,<code>last_probe_position.y</code> and
+  descend then the tip of the toolhead would first contact the bed at
+  a Z height of <code>last_probe_position.z</code>. These coordinates are
+  relative to the frame (that is, they use the coordinate system
+  specified in the config file).  Note, if this is used in a macro,
+  due to the order of template expansion, the <code>PROBE</code> command must be
+  run prior to the macro containing this reference.</li>
+<li><code>last_z_result</code>: This value is deprecated; it will be removed in the
+  near future.</li>
 </ul>
 <h2 id="pwm_cycle_time">pwm_cycle_time<a class="headerlink" href="#pwm_cycle_time" title="Permanent link">&para;</a></h2>
 <p>The following information is available in