Two comments in vendor/raylib that this batch made false

The cursor block said DisableCursor is 'what nothing here needs';
core-3d-picking toggles it from the right mouse button. Enable/DisableCursor
stay generated — they take no arguments, so there is no Flan face to improve,
which is the same rule that leaves GetMouseX there — but the sentence had to
go.

And bindings named draw-cube-v as one of its three deliberately-generated
variants, which it no longer is. The paragraph now says what happened to it
rather than asserting the opposite of the exclude list below it.

vendor/raylib/bindings

@@ -90,13 +90,16 @@ exclude IsWindowReady
 #     generated i32 would take. GetWorldToScreen goes with BeginMode3D
 #     because they read the same camera.
 #
-# What this line splits, and deliberately: draw-cube is here and draw-cube-v
-# is generated, get-world-to-screen is here and get-world-to-screen-ex is
-# generated, update-camera is here and update-camera-pro is generated. Every
-# other family in raylib.flan — the texture draws, the circle draws — sits
-# together, so the split is worth naming: what is hand-written is what the
-# ported examples call, and hand-writing the variants as well would widen the
-# half that has to be maintained by hand for nothing the examples ask for.
+# What this line splits, and deliberately: get-world-to-screen is here and
+# get-world-to-screen-ex is generated, update-camera is here and
+# update-camera-pro is generated. (draw-cube-v was named here as the third
+# such pair and no longer is — see the DrawCubeV line further down, which is
+# what happens to a split of this kind when an example starts calling the
+# other half.) Every other family in raylib.flan — the texture draws, the
+# circle draws — sits together, so the split is worth naming: what is
+# hand-written is what the ported examples call, and hand-writing the variants
+# as well would widen the half that has to be maintained by hand for nothing
+# the examples ask for.
 #
 # What is deliberately NOT here: the window-state family (IsWindowState,
 # SetWindowState, ClearWindowState, ToggleFullscreen, Minimize/Maximize/

vendor/raylib/raylib.flan

@@ -153,7 +153,11 @@
 ;; The cursor's visibility is window state and not input, but it is read and
 ;; written by the same code that reads the mouse, so it sits here.
 ;; hide-cursor only hides it; it does not lock it to the window, which is
-;; what raylib's separate DisableCursor does and which nothing here needs.
+;; what raylib's separate DisableCursor does. Those two — DisableCursor and
+;; EnableCursor — are in the generated half rather than here: they take no
+;; arguments at all, so there is no Flan face for a hand-written line to
+;; improve, which is the same rule that leaves GetMouseX there.
+;; examples/core-3d-picking.flan toggles them from the right mouse button.
 (declare-c show-cursor [] "ShowCursor")
 (declare-c hide-cursor [] "HideCursor")
 (declare-c cursor-hidden? [] bool "IsCursorHidden")