> Just because variables do not have a type (can potentially hold any value) doesn't mean that values have no type. Furthermore, variables potentially holding any value doesn't mean they have no type.
I said they have one type, I didn't say they have no type.
That basically means the same thing. "Typeless dynamic language" and "all variables and object slots having one type" are essentially the same claim: that the bindings or storage locations are all indistinguishable and can take on any value.
(If they have one type, what is that type? And can values be of that type?)
Furthermore, variables potentially holding any value doesn't mean they have no type. It is just a potential. A variable effectively has that type which is actually put into it.
If a given variable is always either a string or nil, then that's what it's type is; the sum type of null (the type that contains nil) and the string type.
It may be the case that in a given language implementation, this fact about the variable is not calculated; but it's still a fact.
Neglecting to analyze the types of variables (and other nodes in the program) is an implementation quality/depth choice, not a kind of type system design.