expandPercent property
Probe mode: pad every value handed back, scaled by this percentage of each key's own ceiling — see expansionLength.
Set by the harness for a probe pass and null everywhere else — including
every ordinary recording run, so nothing a normal export reads is ever a
padded value. The padded string is minted as a token like any other, so
identity still names the key, didExceedMaxLines on the walk still says
whether it fit, and the suite's own targeting — which reads through the
same funnel — follows the padding instead of breaking on it.
What the catalog answered (read) records the real value: the export compares that map against the locale files, and a padded value there would make every key look wrong.
Implementation
static int? expandPercent;