Saying "zero" interferes with the `numb` command

[BawdyInkSlinger]

Describe the bug
The following examples follow this structure:

this is what I spoke

this is what the Caster status window printed
this is what Caster output at my cursor

Examples

numb 0 1 1

Numbers: [<long>] numb <wnKK>, , 0
0

numb 0 90

Numbers: [<long>] numb <wnKK>, , 0
0

numb 1 0 1 1

Numbers: [<long>] numb <wnKK>, , 101
101

numb 1 1 0 1

Numbers: [<long>] numb <wnKK>, , 1101
1101

numb 1 1 0 1 1

Numbers: [<long>] numb <wnKK>, , 1101
1101

numb 1 1 1 0 1

Numbers: [<long>] numb <wnKK>, , 1110
1110

To Reproduce

• See above

Expected behavior
I expect the output to be the full number I spoke.

Screenshots
If applicable, add screenshots to help explain your problem.

System:

• OS: Win 10
• Program: Firefox (in this case, but I've tested it on many programs)
• Version: - Starting Caster v 1.7.0 -
• Python 2.7.18
• Running DNS/DPI from Dragonfly CLI with Natlink.

May be related to #857

[LexiconCode]

This is reproducible with dragonfly's text engine. The issue is either with short integer ref or a ccr bug. Further investigation is needed.