The transform tool treats a null reflect, copy or origin, and a null
numeric step, as given, but its inputSchema allowed only the non-null
types, so a client that validates against the schema could not send
them. Each of those properties now also allows null. The transform row
in docs/mcp.md says a step that is neither a number nor null is an
error, and that a null dx or dy counts as 0 and still runs the move.