Keep a usage-attested single-dash-long spelling whole

[sadigaxund]

A single-dash-long token that a tool's usage line brackets as one stand-alone word keeps its whole name now, instead of splitting after one letter into a short flag plus a fabricated value, so mandible lshw reads -format and -options and mandible fuser reads -SIGNAL. The evidence is the usage line itself, a document location distinct from the row being repaired, so S-145's table-wide gate stays closed for both tools.

Fleet sweep against the 0b30c15 baseline, 2269 tools matched, 0 disappeared: 0 flag losses, 0 subcommand losses or gains, 1 flag gained (lshw 16 to 17, -options having been dropped as the generic option-list placeholder before), and the field-level list is fuser and lshw alone. The one tool that appeared, ccusage, is an executable installed on the box between the baseline and this sweep and has nothing to do with the branch.

The sweep also caught a defect that no gate and neither fixture could: memhog's usage line brackets [-rNUM] exactly the way fuser's brackets [-SIGNAL], so the repair turned a correct -r valued NUM into a valueless -rNUM spelling, at an unchanged flag count of 3. It is refused now when the case changes at the split point, which is the glued-value convention rather than a longer name; fuser's -SIGNAL is uppercase throughout and lshw's -format lowercase throughout, so neither has that transition. Both fixture tools are seed-7 maintainer-audited and the honest family count is 2, below the five-tool bar, so this ships as a gated exception: both fixtures promote, the corpus run is zero-loss, and eight of the nine named controls are byte-identical on the first capture with the #fp2 fingerprint identical for all nine.