Breaking changes and deprecations

No verified breaking changes or deprecations are published for the current Private Preview baseline.

Manager changes are breaking when they alter the heartbeat/control-plane command contract, change ownership semantics, require an incompatible CRD schema, or prevent rollback to an otherwise supported bundle. Future capability inventory may add explicit kind/reference/schema compatibility signals; those are not present in 0.2.0.

Entry template

<Change title>

• Introduced: <version>
• Affected: <protocol, component, deployment mode, or API>
• Change: <precise old and new behavior>
• Impact: <who is affected and how>
• Action: <migration steps>
• Deadline or removal version: <version or date, if committed>
• Rollback constraint: <known limitation>

A deprecation notice must identify a supported alternative and a realistic migration window. Planned Redis and PostgreSQL support must not be represented as a deprecation path because those protocols are not implemented.