SafeResponseAI tests JSON guardrails for agents

Prompt-only fixes are a half measure; once LLM output feeds another step, reliability needs a contract, not hope.

• –Schema validation catches malformed JSON and missing fields before they poison downstream actions.
• –A hard `fail` path is healthier than endless repair loops because it caps token burn and makes failures explicit.
• –Retry-cost accounting is a smart product angle because it turns reliability into a measurable budget.
• –Per-step logs and raw-output diffs are the natural companion to validation, because you still need to know why a response broke.
• –This pattern is broadly useful across local models, hosted APIs, and multi-agent runtimes.