Error text for `mimimum` missing whitespace

[mwadams]

The minimum schema evaluation error text emits as

Expected the item count to be greater than or equal to'3'

This is missing a space between equal to and '3'.

It is highly likely that other error messages have the same issue.

1. Scan the embedded resource text and message providers for similar errors, document in this issue.
2. Update the resources and providers to eliminate the problem.

[mwadams]

Root cause

The message quoted in the issue is produced by the minItems evaluation (the "item count" message family). The minimum keyword itself takes a different code path and is correctly spaced. The missing space affects every integer-valued message family, as suspected.

All V5 validation messages are composed in two parts. A resource string that deliberately ends without trailing whitespace (e.g. JsonSchema_ExpectedItemCountGreaterThanOrEquals = "Expected the item count to be greater than or equal to"), plus an appender that writes the quoted expected value into the UTF-8 message buffer.

There are two appenders in src/Corvus.Text.Json/Corvus/Text/Json/JsonSchema/Internal/JsonSchemaEvaluation.cs:

• AppendSingleQuotedValue (two overloads, lines 196 and 218) writes a leading space, then 'value'. Correct.
• AppendQuotedInteger (line 244) writes 'value' with no leading space. This is the defect.

Every message provider that goes through AppendQuotedInteger therefore emits ...to'3'. That is 24 provider methods across three files, four message families with six comparison variants each (Equals, NotEquals, GreaterThan, GreaterThanOrEquals, LessThan, LessThanOrEquals):

Family	Keywords	File
string length	minLength / maxLength	JsonSchemaEvaluation.cs (6 methods)
item count	minItems / maxItems	JsonSchemaEvaluation.Array.cs (6)
contains count	minContains / maxContains	JsonSchemaEvaluation.Array.cs (6)
property count	minProperties / maxProperties	JsonSchemaEvaluation.Object.cs (6)

Correctly spaced paths, needing no change: number comparisons (minimum / maximum / exclusiveMinimum / exclusiveMaximum, multipleOf), type, pattern, string equality and dependent-schema/pattern-property messages. These all go through AppendSingleQuotedValue. The sentence-complete messages (formats, composition, required-property) append nothing. The V4 engine (src-v4) composes its messages via string interpolation with correct spacing and is unaffected. Generated code (source generator, CLI, standalone evaluator output) calls into these runtime message providers rather than embedding message text, so a runtime fix covers every engine and consumer with no regeneration needed.

AppendQuotedInteger has exactly one definition repo-wide, so this is a single-point fix.

Adjacent defect found during the scan

JsonSchema_ExpectedLessThan has the wrong text. Its value reads "The value was expected to be greater than"; it should read "less than". It surfaces through MatchLessThan in JsonSchemaEvaluation.Number.cs (the exclusiveMaximum path), so an exclusiveMaximum failure currently reports the opposite comparison direction. The same copy-paste error exists in both copies of the resource file:

• src/Corvus.Text.Json/Resources/Strings.resx (~line 509)
• src/Corvus.Text.Json.JsonLogic.SourceGenerator/Resources/Strings.resx (~line 497)

The neighbouring entries (ExpectedGreaterThan, ExpectedLessThanOrEquals, etc.) are correct. No missing-space text is baked into any resource string itself; the resources' no-trailing-space convention is intentional and matches the AppendSingleQuotedValue contract.

Plan

1. Test first (repo convention). Extend tests/Corvus.Text.Json.Tests/JsonSchemaEvaluationMessageTests.cs with exact-format assertions (Assert.AreEqual on the full transcoded message, e.g. Expected the item count to be greater than or equal to '3') covering all 24 integer-valued providers, plus a direction assertion for the less-than message (The value was expected to be less than '10'). These must fail before the fix. The existing tests only assert Contains("'3'"), so they do not pin the broken format.
2. Fix AppendQuotedInteger to write the leading space before the opening quote, mirroring AppendSingleQuotedValue, adjusting its buffer-capacity checks for the extra byte. All 24 providers inherit the fix.
3. Fix JsonSchema_ExpectedLessThan in both resx files ("greater than" → "less than"). The JsonLogic source generator's checked-in Strings.Designer.cs embeds resource values in its doc comments, so it gets the matching update.
4. Sweep verification as a gate. Re-scan all JsonSchema_* resource values that end mid-sentence ("to", "than", "of", "equal") and confirm each consumer appends through a space-writing path; confirm no exact-message assertions elsewhere (conformance suites, docs) pin the old text. The diagnosis scan found none.
5. Standard gates. Warning-free build of Corvus.Text.Json.slnx; run Corvus.Text.Json.Tests (message tests plus the schema evaluation suites) on all TFMs with the standard category filters.

The fix will land on feature/910-906-message-whitespace-and-global-namespace, layered with the #906 fix.