[Muizzkolapo]

Summary

• The schema compiler copied a fixed list of field keys. That list left out minimum, maximum, minLength and maxLength, so no provider was told a field's range.
• compile_field now copies the four keys for every vendor. No vendor strips them: no provider documents a rejection of them when strict mode is off, and agac never sets strict. exclusiveMinimum, exclusiveMaximum and multipleOf are still not sent.
• Two checks read the schema as it is sent, so they now hold the bounds too: a declared endpoint fails a reply outside minimum or maximum, and a tool action refuses output that breaks any of the four. An LLM action's own output check reads the schema file and already held minimum and maximum.
• The schema reference has a per-vendor table of how the schema is sent and whether the vendor enforces the bounds.

Verification

Gate	Result
RED (tests/unit/output/response/test_schema_bounds_reach_the_provider.py on the parent)	14 or more assertion failures
Review (risk LOW, 1 blind verifier)	NO: the code was right, but the changelog and docs named the wrong checks and did not announce the tool-output refusal
Fix and re-review	Docs and changelog rewritten; tests for the tool refusal and for the keys that stay out. Re-review NO on the cohere and gemini rows of the vendor table, fixed, then YES
Full suite, ruff, mypy	17327 passed, 37 skipped

• The reviewer measured the two new checks against the parent: a declared-endpoint reply with score: 9 (maximum 4) passed on the parent and fails at this layer; a tool output with a too-long label passed on the parent and is refused here.
• One suite run failed test_a_mapping_at_the_end_of_a_deep_chain_is_placed, a wall-clock test (elapsed < 2.0), at machine load average about 16. It passes alone 3 of 3, and the rerun passed. It is noted on the coordination board.
• Smoke ran on the bottom layer only, as asked.