v1.2 release and migration readiness

Problem

The v1.2 release will introduce breaking changes to MCP tool schemas, eval case formats, and guardrail configurations that existing users and integrated agents depend on. There is no migration path defined — no schema versioning, no deprecation warnings in tool responses, no upgrade guide, and no communication plan for affected users. Without explicit migration readiness, the release will break existing agent configurations silently, forcing users to debug failures themselves. The eval framework also needs migration support so that existing eval suites continue to work or are automatically updated to the new format.

Context

Possible Solutions

Plan

Implementation Progress

Review Feedback

• Review cleared