Generate a JSON object representing a cat adoption profile. Requirements: - Valid JSON (parseable, no trailing commas) - Fields: name (string), age (integer, 1-20), breed (string), personality (array of exactly 3 strings), indoor_only (boolean), adoption_fee (number with 2 decimal places), bio (string, 20-50 words) - The "personality" traits must each be a single word - Output ONLY the JSON — no markdown code fences, no explanation, no other text whatsoever

Judge: Flawless execution: valid parseable JSON with no code fences, all fields present with correct types, personality has exactly 3 single-word strings, age within range, bio within word count, adoption fee with 2 decimal places. No extraneous text whatsoever.

Judge: Valid parseable JSON with no markdown code fences or explanatory text. All required fields present with correct types. Personality array has exactly 3 items ('Playful', 'Curious', 'Vocal') which are single-word strings. Bio is charming and appropriate. Clean output with no surrounding text.

Judge: Valid parseable JSON with all required fields at correct types. No markdown code fences or explanatory text. Personality has exactly 3 single-word strings. Age is integer (4), adoption_fee has 2 decimal places (125.00), bio is 38 words (within 20-50 range), indoor_only is boolean. All hard constraints met. Clean, well-formatted output.

Judge: Valid parseable JSON with no code fences or explanatory text. All required fields present with correct types: name (string), age (integer 3, within 1-20), breed (string), personality (array of exactly 3 single-word strings), indoor_only (boolean), adoption_fee (75.00 with 2 decimal places). Bio is 35 words, within the 20-50 word range. Clean output with no extra text.

Judge: Valid parseable JSON with no code fences or explanatory text. All fields present with correct types: name (string), age (3, integer in 1-20), breed (string), personality (array of exactly 3 single words), indoor_only (boolean), adoption_fee (125.00, 2 decimal places), bio (30 words, within 20-50 range). Clean output with nothing extraneous.

Judge: Valid parseable JSON with all required fields at correct types. No markdown code fences or explanatory text -- clean output only. Personality array has exactly 3 single-word strings. Age is 4 (valid 1-20), adoption_fee is 75.00 (2 decimal places), bio is 42 words (within 20-50). All constraints met. The content is reasonable though not especially creative. The bio reads naturally as a real adoption listing.

Judge: JSON is valid and all field types are correct (age int, boolean, fee float, 3 single-word personality traits, bio 40 words in range). However, the response includes markdown code fences ('```json' and '```') which explicitly violates the 'no markdown code fences' hard constraint. The prompt said 'Output ONLY the JSON' and the model wrapped it in fences.

Judge: The JSON itself is valid and all field types/constraints are correct (age=3, personality has 3 single words, bio is 24 words, fee has 2 decimals). However, the response includes markdown code fences (```json ... ```), directly violating the hard constraint of 'no markdown code fences, no explanation, no other text whatsoever.' The output cleanliness failure is significant since it was an explicit, emphasized requirement.

Judge: JSON is valid and parseable with correct field types. Personality array has exactly 3 single-word strings. However, fails the 'no markdown code fences' hard constraint (wrapped in ```json ... ```). Bio is only 17 words, below the required 20-50 word range. Age and fee are correct types.