[rig-sampler] feat(s): add s.integer schema helper

[github-actions]

Sample run: 06-list-source-files.ts

The stub runner executed sample 06 successfully in a single turn — no repair loops. The sample outputs { summary: s.string }, a single-field object wrapping a string summary of the repository's TypeScript source files.

What the run revealed

While sample 06 itself ran cleanly, reviewing the broader set of samples (e.g. 03-diagnose-test-failure.ts with confidence: s.number, 41-parse-coverage.ts) reveals a gap: the harness has no way to express integer constraints. When agents return counts, line numbers, or coverage percentages as whole numbers, s.number accepts floats silently. A model that returns 1.5 for a turn count passes validation today, and the caller gets a float where an integer was intended.

Change

Added s.integer — an IntegerSchema with type: "integer" — following the exact same SchemaHelperFactory pattern as s.number:

• New type IntegerSchema = { type: "integer"; description?: string }
• s.integer helper, callable as bare value or s.integer("description")
• JSON Schema serialization: emits { "type": "integer" } (standard JSON Schema integer type)
• Validation: rejects non-integers via Number.isInteger(), so 1.5 now fails with a clear expected integer message instead of silently passing
• InferSchema<IntegerSchema> maps to TypeScript number (no narrower integer type in TS)
• Constraint updated: createTypedPrimitiveSchema generic constraint widened to include IntegerSchema

Tests added

Three new tests in src/rig.test.ts:

• toJsonSchema coverage for s.integer and s.integer("description")
• Validation accepts whole numbers
• Validation rejects floats with a helpful error message

Generated by Daily Rig Sampler · 106.4 AIC · ⌖ 8.71 AIC · ⊞ 5.2K · ◷