Validate precomputed evaluation values against variation types

[typotter]

What changed

Schema and documentation changes require precomputed evaluation defaults and expected values to match the declared variation type.

• Float evaluations accept any JSON number; integer evaluations accept only integral numbers, including 1.0.
• The existing fixture validator applies these constraints directly from the schema.

Why

A numeric string such as "1.5" previously passed validation for a float evaluation, allowing malformed typed getter inputs into downstream runners.

How to verify

• Ran the existing fixture validator: all 12 fixtures pass unchanged.
• Checked the schema against valid and invalid values for both fields across all five variation types.

Impact

For internal, the FFE team catches malformed typed evaluation fixtures before they reach SDK runners, reducing downstream debugging of invalid getter inputs.

[Copilot]

🟢 Approval recommended

The schema and documentation changes are consistent, narrowly scoped, and improve fixture validation without introducing functional code-path risk.

Pull request overview

This PR tightens validation for FLEX precomputed assignment fixtures by updating the JSON Schema (and related docs) so that defaultValue and expectedResult.value must match the declared variationType, preventing malformed typed getter inputs from reaching downstream SDK runners.

Changes:

• Updated schemas/precomputed-assignment.schema.json to conditionally validate defaultValue and expectedResult.value types based on variationType (boolean/string/integer/float/object).
• Clarified documentation in precomputed-assignments/README.md and AGENTS.md to explicitly state the required JSON types for these fields.

File summaries

File	Description
schemas/precomputed-assignment.schema.json	Adds allOf + if/then constraints to enforce defaultValue/expectedResult.value types by variationType.
precomputed-assignments/README.md	Documents the new type-matching requirements for evaluation inputs and expected values.
AGENTS.md	Updates the fixture-authoring guidance to reflect the stricter typed-value validation rules.

Review details

• Files reviewed: 3/3 changed files
• Comments generated: 0
• Review effort level: Lite

---

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

[leoromanovsky]

very nice