Make sure that 99999999999 (eleven nines) is not rejected...

... since we've been shipping such policy for long time.

Related to redmine 6531.
Suggestion (in light of adding a ten-nines case otherwise doubling the code):
```
"ten9s" string => "9999999999";
"eleven9s" string => "99999999999";
"sizes" slist => { "ten", "eleven" };
"pos_$(sizes)" int => "$($(sizes)9s)";
"neg_$(sizes)" int => "-$($(sizes)9s)";
```
It'll make clear how many nines appear in each (and the reader has to count at most once to check the names are faithful); and you can then test
```
vars:
    "sizes" slist => { @(init.sizes) };
    "signs" slist => { "pos", "neg" };
    "big32[pos]" => "2147483647";
    "big32[neg]" => "-2147483648";
classes:
    "$(signs)_$(sizes)_ok" or => { strcmp("$(init.$(signs)_$(sizes))", "$(init.$(sizes)9s)"), # 64-bit
                                   strcmp("$(init.$(signs)_$(sizes))", "$(big32[$(signs)])") # 32-bit
                                   }, scope => "namespace";
    "ok" and { "pos_ten_ok", "neg_ten_ok", "pos_eleven_ok", "neg_eleven_ok" };
```
and use similar automation in reporting.