v1.2 release and migration readiness

Problem

The v1.2 release will introduce schema changes, new enrichment layers, and potentially breaking updates to the context contract. Users and integrations built against v1.0 need a clear migration path — without upgrade guidance, breaking change communication, and compatibility tooling, the release will either break existing consumers silently or force the team to maintain indefinite backwards compatibility with the v1.0 contract, constraining future evolution.

Context

Possible Solutions

Plan

Implementation Progress

Review Feedback

• Review cleared