the retired rust script was 155 lines, and both figures for it were wc -l on no commit

Same defect the go figure had, in the rust row: prose that states a measurement
nobody can reproduce. The rust repo said 250 and this repo said 138; the script
is 155 lines at hanzo-rs/sdk@365f06f, the commit whose output the row reproduces
byte-for-byte, and that is also its maximum across its whole history. It was 144
on main's tip before the row landed and 139 when it wrote the earlier client.

The number is the only thing that moves. The claim it decorates — regenerate at
cloud@5126939 through the driver and --check reports [rust] clean — reproduces.

LLM.md

@@ -472,7 +472,7 @@ in one commit. The departure is what drifted: its script defaulted to
 `hanzoai/openapi` `hanzo.yaml@main` while the `.spec-lock` beside it named
 `hanzoai/cloud` `openapi.yaml` at a commit. Regenerating at the ref that lock
 named, through the driver, reports `[rust] clean` — byte-identical to what the
-138-line script produced.
+155-line script produced.
 
 **`hanzoai/ruby-sdk` was a row naming a client nobody shipped** — a hard 404 with
 no redirect, while every genuinely renamed SDK answers 301, and no gem under

sdks.yaml

@@ -739,7 +739,8 @@ sdks:
   #
   # The row reproduces it exactly: regenerated at the ref that lock named
   # (cloud@5126939), `generate.py rust --check` reports clean — byte-for-byte the
-  # tree the 138-line script produced.
+  # tree the 155-line script produced — `wc -l` on that script at the commit
+  # whose output was compared, and its maximum across its whole history.
   #
   # The row that had been deleted BEFORE that would not have compiled, and none
   # of it survives here: no type mapping, no template, `useSingleRequestParameter`